SAP ABAP IMG Activity OHAAL16_0130 (Define Actions/Reasons for Payslip Creation)
Hierarchy
SAP_HRCAT (Software Component) Sub component SAP_HRCAT of SAP_HR
   PY-AT (Application Component) Austria
     P03C (Package) HR Customizing: Austria
IMG Activity
ID OHAAL16_0130 Define Actions/Reasons for Payslip Creation  
Transaction Code S_L6B_69001347   (empty) 
Created on 20051007    
Customizing Attributes OHAAL16_0000   Attributes L16 (Mandatory/Critical) 
Customizing Activity OHAAL16_0130   Define Actions/Reasons for Payslip Creation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAAL16_0130    

Use

In this Customizing activity, you define for each payslip application the actions and action reasons on the basis of the event of which the start and end of the evaluation period are defined. In the case of a leaving action, monthly payslips are therefore created, for example. Here, the system evaluates actions as of the first record in the infotype so that periods prior to the legacy data transfer are also taken into account.

In this activity, you define all relevant combinations of actions and reasons. You can also map an organizational reassignment, such as an employee leaving and their immediate reentry (into a different company).

Note: If you have entered organizational reassignments in this view, see also the following activity: Maintain Employer Assignment Unit for Company.

Requirements

Standard settings

In client 000, sample Customizing settings are available that you can use as a template for your client.

Activities

  1. Call the Define Actions/Reasons for Payslip Creation activity.
  2. Map all actions and the associated reasons for entries and leavings that you use in your company. Choose the validity period in such a way that for all relevant employees the relevant event falls within the period; otherwise, the system will not be able to identify the event (an entry, for example).
  3. Save your entries.

Example

  • For L16, the evaluation period L16 also starts in the case of an entry action. The evaluation period runs until the employee leaves the company or until the end of the year. At the start of the new year, a new evaluation period starts, provided the employee is still active.
  • An employee goes from being a freelancer/contract employee to a permanent employee. In this case, you must make the following entries:
    • Action "Hiring E18" with encryption XXX6
    • Action "Reassignment E18->L16" with encryption 6661

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_T5A7L V - View SM30  
History
Last changed by/on SAP  20051007 
SAP Release Created in 470