Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PT (Application Component) Personnel Time Management⤷
PTIM (Package) HR Time Management Application Development
IMG Activity
| ID | PAY_XX_AB_305 | Prepare Production Startup for the Refinement of Absences |
| Transaction Code | S_L9C_94000892 | IMG Activity: PAY_XX_AB_305 |
| Created on | 20020417 | |
| Customizing Attributes | PAY_XX_AB_305 | Prepare Production Startup for the Refinement of Absences |
| Customizing Activity | PAY_XX_AB_305 | Prepare Production Startup for the Refinement of Absences |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PAY_XX_AB_305 |
Use
In this activity, you prepare the production startup for the refinement of absences by filling the COVER table and specifying the date for production startup.
Defining the date for production startup
In this step, you define the date as of which you want to go live with refining employees absences'. You can set the date based on organizational assignments or absence types. You maintain the COVGL feature (Define Date for Production Startup of Absence Refinement) to do so.
Note:
It may be the case, for example, as a result of an organizational change, that the system determines two different dates for production startup for an employee. If this occurs, the system uses the later date and issues a warning message to inform you of the situation.
If you do not want to define the production startup date, it should be set as 01/01/1800. Check whether the feature is maintained to suit your requirements.
Filling the COVER table
In this step, you fill the COVER cluster table with marked absences from past periods, as required. The RPTBCH00 report (Initialization of COVER Table for Absence Refinement) is available for this purpose. You can use this report if you want to avoid a retroactive accounting run for a period far in the past. Note in particular the points in the report documentation referring to absence times that overlap the start or end date.
Requirements
- If you run payroll for an employee and payroll finds absence records that overlap the production startup date, payroll issues a warning message. The absences that overlap the production startup date are all still processed, but markers are created only as of the production startup date.
- If you did not use SAP HR previously, you may be able to transfer data from a third-party system and fill the COVER table in this way. You must have implemented the country-specific function module HR_COV_MAP_MARK_xx. There is no customer-specific enhancement for this functionality that enhances the country-specific function module.
Recommendation
We recommend that you keep the decision tree of the COVGL feature as simple as possible. A simple solution with as few dates for production startup as possible considerably simplifies the process of comprehending the subsequent results.
As far as possible, you should avoid differentiating dates for production startup on the basis of the absence type. You may want to consider manually preparing some absence records as opposed to specifying different dates for different absence types, for example.
Activities
- Maintain the COVGL feature.
To ensure that production startup runs smoothly, you must ensure that you have not forgotten any employees in the decision tree of the feature.
- Enter dates in the format YYYYMMDD.
- Use absence reporting to ensure that no employee absences overlap the production startup date. Delimit any absences that do overlap the date.
- If required, run the RPTBCH00 report.
Example
If you want to set the production startup date to January 1, 2000, for all employees in Switzerland, enter the date 20000101 in the decision tree under the MOLGA (country grouping) 02.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | E | Invalid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| PAY_XX_AB_305 | AR | Argentina |
| PAY_XX_AB_305 | AT | Austria |
| PAY_XX_AB_305 | AU | Australia |
| PAY_XX_AB_305 | BE | Belgium |
| PAY_XX_AB_305 | BR | Brazil |
| PAY_XX_AB_305 | CA | Canada |
| PAY_XX_AB_305 | CH | Switzerland |
| PAY_XX_AB_305 | CN | China |
| PAY_XX_AB_305 | DE | Germany |
| PAY_XX_AB_305 | DK | Denmark |
| PAY_XX_AB_305 | ES | Spain |
| PAY_XX_AB_305 | FI | Finland |
| PAY_XX_AB_305 | FR | France |
| PAY_XX_AB_305 | GB | United Kingdom |
| PAY_XX_AB_305 | HK | Hong Kong |
| PAY_XX_AB_305 | ID | Indonesia |
| PAY_XX_AB_305 | IE | Ireland |
| PAY_XX_AB_305 | IN | India |
| PAY_XX_AB_305 | IT | Italy |
| PAY_XX_AB_305 | JP | Japan |
| PAY_XX_AB_305 | KR | South Korea |
| PAY_XX_AB_305 | MX | Mexico |
| PAY_XX_AB_305 | MY | Malaysia |
| PAY_XX_AB_305 | NL | Netherlands |
| PAY_XX_AB_305 | NO | Norway |
| PAY_XX_AB_305 | NZ | New Zealand |
| PAY_XX_AB_305 | PH | Philippines |
| PAY_XX_AB_305 | PT | Portugal |
| PAY_XX_AB_305 | SE | Sweden |
| PAY_XX_AB_305 | SG | Singapore |
| PAY_XX_AB_305 | TH | Thailand |
| PAY_XX_AB_305 | TW | Taiwan |
| PAY_XX_AB_305 | US | USA |
| PAY_XX_AB_305 | VE | Venezuela |
| PAY_XX_AB_305 | ZA | South Africa |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | PAY_XX_AB_305 | 0 | HLA0100668 | Bases |
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 |
| PMKC | L - Logical transport object | PE00 | COVGL | Maintain COVGL Feature |
History
| Last changed by/on | SAP | 20030402 |
| SAP Release Created in | 46C |
