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_0190 | Specify Evaluation Date |
| Transaction Code | S_L6B_69001353 | (empty) |
| Created on | 20051007 | |
| Customizing Attributes | OHAAL16_0000 | Attributes L16 (Mandatory/Critical) |
| Customizing Activity | OHAAL16_0190 | Specify Evaluation Date |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAAL16_0190 |
Use
In this activity, you specify the key date for update runs, as of which leavers are to be reported for the first time in the specified leaving period as a monthly payslip.
The selected key date must therefore be a date after the completion of the payroll runs and no later than the deadline for the notification period.
For annual payslips, the same key date applies as for leavers in January of the following year.
For transferring legacy data with program RPUGLZA0, you define in this activity the relevant key date for selecting payroll results for which payslips have already been reported, for the specified leaving period. Only those payroll results are taken into account for which the date of the payroll run is no later than midnight on the day before the key date.
By entering a year under Force From, you can specify as of when the system must check the existing payslips for all employees and report these again if necessary.
Example
Leaving Year Leaving Period Current Date Force From
2012 03 21.04.2012 (see Example for Legacy Data Transfer)
... ... ...
2012 08 21.09.2012 (see Example for Monthly Payslip)
2012 09 21.10.2012
2012 10 21.11.2012
2012 11 21.12.2012
2012 12 21.01.2013
2013 01 21.02.2013 (see Example for Annual Payslip)
2013 05 30.06.2013 2010 (see Example for 'Force Payslip Creation')
... ... ...
- Example for Monthly Payslip
An employee leaves on September 30. Payslip L16 must be created by October 31.
The employee's leaving is entered in the system on October 1 and the payroll run is expected to be completed by October 20, so that there will be no more correction runs in payroll after this date. You therefore set the current date for leavers in September to October 21 as the key date for the evaluation.
If you start transaction PCALZ or program RPLGLZA0 to create payslips in production before October 21, leavers for September are not yet taken into account.
If you start transaction PCALZ or program RPLGLZA0 to create payslips in production on or after October 21, leavers for September are taken into account. - Example for Annual Payslip
An employee is active in the company on December 31, and on January 1 of the following year. Annual payslip L16 and SI for the previous year must therefore be created for the employee by the end of February the following year.
The payroll run for February is expected to be completed by February 20, so that there will be no more correction runs in payroll after this date. You therefore set the current date for leavers in January and for annual payslips of the previous calendar year to February 21 as the key date for the evaluation. - Example for Legacy Data Transfer
Payslips for leavers in March were created with old applications. For leavers as of April, the new functionality is to be used.
An employee left on March 31. This was entered in the system on April 1.
The payroll run for April was completed on April 20 so that the date of the payroll run is no later than April 20.
The payslip notification was created with the old application on April 21.
In the payroll run for May, a recalculation for March is carried out for the employee, since payments have been changed retroactively. The date of the payroll run for May is May 20.
You therefore set the current date for the legacy data transfer to April 21 as the key date for the legacy data transfer. In the legacy data transfer carried out with program RPUGLZA0 up to and including March, the recalculation result from May is therefore no longer taken into account.
The recalculation result from May is taken into account when payslips are created in production with transaction PCALZ or program RPLGLZA0. - Example for 'Force Payslip Creation'
An employee leaves in May 2013. Payslip L16 must be created by June 30, 2013.
If you start transaction PCALZ or program RPLGLZA0 to create payslips in production between June 1 and June 30, 2013, leavers for May are taken into account and, in addition, the system checks for all employees, for all periods as of January 2010, whether their payslip has changed in comparison with the saved version. If differences are found, a new payslip is saved and an ELDA notification is created for the changes.
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 |
| T5A7G | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20051010 |
| SAP Release Created in | 470 |
