Hierarchy
⤷ PY-IN (Application Component) India
⤷ P40C (Package) HR customizing: India
IMG Activity
ID | OHAIN_OCA002 | Set Up Absence Valuation for Off-Cycle Activities |
Transaction Code | S_EHR_88000040 | (empty) |
Created on | 19990608 | |
Customizing Attributes | OHAIN_OCA002 | Set Up Absence Valuation for Off-Cycle Activities |
Customizing Activity | OHAIN_OCA002 | Set Up Absence Valuation for Off-Cycle Activities |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHAIN_OCA002 |
In this step, you define the following absence valuation rules:
- for the valuation of absences in the off-cycle payroll run;
- for the valuation of absences in the regular payroll run when an off- cycle payroll run has already taken place.
- for valuation of absences in the regular payroll run when no off-cycle payroll run has already taken place.
For this, you will find the additional key field Indicator for absence valuation in off-cycle payroll in the table Absence valuation. Depending on the key you specify, you can access various views of the Absence valuation table:
- Indicator O (valuation in the off-cycle payroll run)
Here you can only specify constants/averages - Indicator R (valuation in regular payroll with OC-coding)
Here you can display all methods for the valuation of absences ("as if" principle, countingclasses, and so on)
In addition to restrictions on valuation according to constants/averages, the valuation of absences in the off-cycle payroll run usually has the same character as a provisional valuation. If you want to make an adjustment between the wage types generated by daily payroll and wage types generated in the second step of the regular payroll run, you must store the relevant personnel calculation rules in the schema.
Example
An employee is paid in advance for his or her holiday. The off-cycle payroll run ascertains the remuneration for this period according to the daily payroll amount.
The employee is subject to an organizational reassignment after the key date for establishing the daily payroll amount. Consequently, the absence has been undervaluated. The correct remuneration is ascertained in the regular payroll run. You collect this remuneration in a special wage type.
You can, in a personnel calculation rule, for example, calculate the difference between the advance payment and the final remuneration, and remunerate the employee with the difference.
Requirements
You must be familiar with the process of customizing absence valuation. You can find information on this in the Implementation Guide (IMG) for Payroll under Absences. Here, you have made the following settings:
- Absence valuation rules for the regular valuation of absences provided that you do not wish to use a special group of absences only for the off-cycle payroll run.
- Daily rules provided that you want to use your own daily rules for the valuation in the off-cycle payroll run.
- Wage types provided that you want to indicate the difference between off-cycle payroll of absences and the regular payroll run after the off-cycle payroll run.
- Counting classes provided that you wish to collect absences that have been remunerated in advance and differences that result from this in your own counting classes.
Standard settings
Recommendation
Activities
- Configure the absence valuation rules for off-cycle payroll. In addition flag the Indicator for absence valuation in off-cycle valuation O and specify the wage types in which payments in advance are to be applied.
- Configure the absence valuation rules for valuation in the regular payroll run with the indicator set to OC. In addition, flag the Indicator for absence valuation in off-cycle payroll R. Configure your rules for the valuation of absences in line with those you have set up for the valuation without off-cycle payroll.
If you consider the payments in advance as final, and do not wish to pay any differences, or have further amounts deducted, you should submit the values that you ascertain in this step to an unpaid counting class. In this case, in the second (regular) payroll run you must not generate wage types that require payment.
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHAIN_OCA002 | IN | India |
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_T554C | V - View | OH00 | 0520 90HR |
History
Last changed by/on | SAP | 19990608 |
SAP Release Created in |