Hierarchy
SAP_HRCIE (Software Component) Sub component SAP_HRCIE of SAP_HR⤷
PY-IE (Application Component) Ireland⤷
P11C (Package) HR customizing: Ireland
IMG Activity
| ID | OHAIEOSP00101B | Create "How Far Bck/Fwd" Rules |
| Transaction Code | S_AHR_61019385 | (empty) |
| Created on | 19991202 | |
| Customizing Attributes | OHAIEOSP00101B | Create "How Far Bck/Fwd" Rules |
| Customizing Activity | OHAIEOSP00101B | Create "How Far Bck/Fwd" Rules |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAIEOSP00101B |
In this step, you define any new "How Far Bck/Fwd" rules you may require for your specific needs.
The "How Far Bck/Fwd" rule defines how far to rollback from to check used entitlements.
Example
A customer may specify that an employee, after one year's service, is allowed four weeks sickness at Full Pay during any period of one year, starting from the first day of absence.
In this case, the "How Far Bck/Fwd" rule has to define how far to rollback as one calendar year.
Extending the Rollback Point in Time Further Back in History
It is possible that, for absence related methods, the point in time could be moved back to the start date of an earlier related absence or linked absence. If the point in time occurs during a related absence or with the defined linking period to related absence then the point in time will be moved to the start date of the earliest linked absence.
The Linking Method field allows up to a 99-day link period to be specified. It is also possible to Exclude Absences that overlap the start of the Rollback Period using Linking Days of 'X'.
The Related Abs field allows the "strictness" of the absence linking to be specified. The absences can be loosely related or strictly related. (The absence subtype type (T554S-ABSTY) is derived for each absence in history. A loose check just checks the first character to be the same as the one being processed, the strict check checks both characters.)
Requirements
Any non-standard rollback period units must be configured in the tables T538A, T5GPBS28, and T5GPBS24 (this is optional, but if the entry is not in T5GPBS24 then the code to handle the time unit must be entered in the customer exit).
Standard settings
SAP only provides seven standard start rules:
- 1 Year Rollback
- 2 Years Rollback
- 3 Years Rollback
- 4 Years Rollback
- 5 Years Rollback
- 6 Years Rollback
- Rollforward
None of the above include linking.
Recommendation
Rollback start rules should only be used with end rule methods:
- Absence Related
- Employee Anniversary Related
- Calendar Date Anniversary Related
The rollforward start rule should only be used with end rule methods:
- Absence History Start Date Related
- Employee Start Date Related
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHAIEOSP00101B | IE | Ireland |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAIEOSP00101B | 0 | AHR0000011 | Absences |
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_T5GPBS21 | V - View | SM30 |
History
| Last changed by/on | SAP | 20060530 |
| SAP Release Created in | 46B |
