Hierarchy

⤷

⤷

IMG Activity
ID | OHANL_TI364 | Execute time wage type selection rule |
Transaction Code | S_AHR_61014257 | IMG Activity: OHANL_TI364 |
Created on | 19981221 | |
Customizing Attributes | OHANL_TI364 | Execute time wage type selection rule |
Customizing Activity | OHANL_TI364 | Execute time wage type selection rule |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHANL_TI364 |
In this IMG activity, you refer to the processing type to determine the time pairs for which wage types are generated, and how these are stored internally. Wage types are generated using function GWT in personnel calculation schema
TC00.
Example
You want to generate time wage types for all time pairs with the processing type overtime and store them in the overtime wage types internal table.
Requirements
To access the generation rules, you must have previously defined the generation rules, and the groupings.
Standard settings
In the standard system, function GWT is called twice. First, time wage types are generated for the planned working time pairs (time pairs with processing type "S") and are stored internally in the time wage type table.
Afterwards, time wage types are created for the overtime time pairs (time pairs with with processing type "M") and are stored internally in the table of overtime time wage types.
The storing mechanism of the buffer handler is switched on on-line, and off in the background.
Recommendation
Only make changes here if you want to generate wage types for time pairs with other processing types. To do this, do not modify the existing calls of function GWT, but create function GWT with appropriate parameters.
Activities
- Decide which processing types you want wage types to be generated for. For each of them insert function GWT and enter the processing type as the first parameter in personnel calculation schema TM00.
- Specify where you want time wage types to be stored in. There are two options:
- in the daily time wage type table (DZL)
- in the overtime time wage type table generated from time pairs (ZML)
Enter DZL or ZML as the second parameter of function GWT.
Further notes
- Temporary storage of wage types in table ZML only makes sense for wage types that were generated from time pairs for overtime.
- An information type is assigned to the wage types for Payroll, which specifies the type of time. Possible specifications are:
- 'S' - planned work
- 'M' - overtime
- 'A' - absence
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 |
---|---|---|
OHANL_TI364 | NL | Netherlands |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHANL_TI364 | 0 | HLA0009657 | Integration with Time Management |
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 |
PSCC | L - Logical transport object | PE00 | TC00 V | Maintain schema TC00 for wage type generation |
History
Last changed by/on | SAP | 19990308 |
SAP Release Created in |