Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PT-SP (Application Component) Shift Planning⤷
PP8C (Package) Shift Planning - Customizing
IMG Activity
| ID | SIMG_CFMENUOHP5OODU | Define Report Variant for Time Evaluation |
| Transaction Code | S_AHR_61004991 | IMG Activity: SIMG_CFMENUOHP5OODU |
| Created on | 19981221 | |
| Customizing Attributes | SIMG_CFMENUOHP5OODU | Define Report Variant for Time Evaluation |
| Customizing Activity | SIMG_CFMENUOHP5OODU | Define Report Variant for Time Evaluation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOHP5OODU |
In this step, you specify which time evaluation report variant should be used for Shift Planning.
Requirements
First define a report variant for time evaluation.
Standard settings
The standard SAP system does not contain a report variant for time evaluation.
Activities
In the Value abbr. field, enter the report variant that is to be used when time evaluation is called (that is, the report variant you defined in the Create Report Variant for Time Evaluation) step.
Notes
If no report variant is entered here, the time evaluation report that you defined in the Set Up Time Evaluation Access is run without a variant.
The variant selected here is controlled by the variant stored in user parameter PET.
Further notes
Entries for the amount of leave taken and the quota used, which are determined in time evaluation, only take any changes made in the current planning period into account after the entries have been saved.
This restriction is only valid if leave taken is calculated against the Leave Entitlement infotype (0005) and the quota used against the Absence Quotas infotype (2006) or Attendance Quotas infotype (2007).
Keep in mind that the data entered from RPTIME00 is evaluated as follows:
- Before entries are saved, data is read, evaluated and checked according to the configured schema
- When entries are saved, current quotas, as well as any collisions that may occur with other time data, are checked
Example
An employee can take 10 days of leave (vacation). Schedule 15 days of leave for this employee in the current planning period.
- If you start time evaluation before saving the entries, a period of 15 days is evaluated as 0 productive hours and therefore the 15 days are considered leave days.
- When you try to save the entries, the system issues a message that the quota is exceeded by a total of five days. Correct the leave request by subtracting 5 days. Now you can save the entries.
The collision check saves you from processing time-consuming corrections in the saved shift plans.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOHP5OODU | 0 | HLA0009713 A HLA0009704 |
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_T77S0SC | V - View | OODU | 0000000003 | Working time/shift plan: report variant |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
