81 Personnel actions Table maintenance and feature IGMOD Transaction code SM31

81 personnel actions table maintenance and feature

This preview shows page 81 - 95 out of 121 pages.

81 Personnel actions: Table maintenance and feature IGMOD Transaction code: SM31 Transaction code: PE03 Table T588C T588D T529A T530 T588B IGMOD Feature
82 User group dependency on menus and info groups Personnel actions: Define infogroups Here you can define if an infogroup is usergroup dependent => parameter ‘UGR’ in System/User profile/Own Data/Parameters. V_T588C Menutype G = Infogroup
83 Personnel actions: Define infogroups Infogroup Here we define the sequence of infotypes (and subtypes) for an infogroup. Table V_T588D
84 Infogroup COP Copy For other actions than first registration. If at Copy the infotype does not exist it becomes create. DEL Delete Delete Infotypes INS Create For first registration. At Create the system will check if an infotype with the same subtype exist. If so, INS becomes MOD LIS9 Delimit Infotypes delimit (at leaving). Never use LIS9 for IT0000 and IT0001! These 2 infotypes have to stay with endda = 31.12.9999 even for employees who are leaving. MOD Change To change existing infotypes INSS Create (no MOD) Create even if an infotype exists. No switch to MOD if the same infotype exist . Personnel actions: Define infogroups Possible operations
85 Personnel actions: Define infogroups Infogroup modificator Feature IGMOD
86 Personnel actions: Define infogroups Infogroup modificator Feature IGMOD
87 Sequences of infotypes linked to an action (MASSN) Personnel actions: Define types of actions
88 Sequences of infotypes linked to an action (MASSN) Personnel actions: Define types of actions
89 Sequences of infotypes linked to an action (MASSN) Personnel actions: Define types of actions TABEL T529A Type of procedure (MASSN) = 01 Description procedure = Hiring Function char for action = 1 1 First hiring; 7 Transfer from recruitment; 0 Other Status clientspec. = blank
90 Sequences of infotypes linked to an action (MASSN) Employment Status = 3 Status special payment = blank Feature for action sequence = blank MSN20 leave; MSN21 rehiring; ... Infogroup Date control Personnel actions: Define types of actions
91 Here you define which procedure must be displayed an in which sequence Personnel actions: Change action menu
92 Exercise: Personnel actions Create a new procedure ‘EXTERNAL EMPLOYEE XX’ Use procedure ZA to ZZ Include Infotype 0001 and Infotype 0002 Use infogroup ZA to ZZ Include this in transaction PA40 Use action menu ’01’, reference usergroup ’00’ and line number XX
93 Agenda 7 7 PA as ‘ Consultant ’ (Master Data Customizing) 1 1 Overview Personnel Administration (PA) 2 2 PA as ‘ End User ’ (Data maintenance) Infotypes and subtypes 3 3 Time constraints and validity periods 4 4 5 5 Data maintenance procedures and actions 6 6 General concepts IMG <> Table maintenance 8 8 Customizing tables 9 9 10 10 10 10 Infotypes structure and attributes 11 11 11 Personnel actions 12 12 12 12 Dynamic actions, features and user exits 13 13 Legacy System Migration Workbench
94 Master Data processes: Dynamic actions (1) Dynamic actions If the maintenance of an infotype has an impact on a second one, the system will automatically propose you, just after, another screen to maintain the second infotype.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture