Hierarchy
⤷ PT (Application Component) Personnel Time Management
⤷ PTIC (Package) HR Time Data: Customizing
IMG Activity
ID | SIMG_OHT032 | Define Time Types |
Transaction Code | S_AHR_61009085 | IMG Activity: SIMG_OHT032 |
Created on | 19981221 | |
Customizing Attributes | SIMG_OHT032 | Define time types |
Customizing Activity | SIMG_OHT032 | Define time types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OHT032 |
In this step, you define time types, day balances, and period balances for your company.
Time types are semantic groupings of time spans. The balances formed in time evaluation are posted to time types. They determine whether balances should be cumulated in a particular time type on a daily or monthly basis.
Example
Employees in a certain personnel subarea grouping are scheduled to work 8 hours a day. The collective agreement specifies an average daily working time of 7.5 hours. Employees can accumulate compensation time from the difference. Define the time type "Compensation time".
Requirements
You have defined personnel subarea groupings
for time recording.
Standard settings
The standard SAP system contains the most common time types. You can add your own entries if these are not sufficient.
The meaning of the time types is taken from time evaluation's personnel calculation rules. The standard time types are as follows:
- 0002 - Planned working time from daily work schedule
- 0003 - Skeleton time (times which qualify as planned work)
- 0005 - Flex balance (difference between 0003 and 0002)
- 0010 - Attendance (generated or from time events)
- 0020 - Recorded absences (infotype 2001)
- 0030 - Recorded attendances (infotype 2002)
- 0040 - Overtime worked
- 0050 - Productive hours (total of 0010, 0030 and 0040)
The steps on forming balances from time data with
clock times and forming balances without clock times contain more information on the formation of balances.
Recommendation
You should only create new entries if the standard time types are not sufficient for your purposes.
Activities
- Decide which additional time types are required.
- Specify the personnel subarea groupings for time recording for which the time types are valid.
- Decide if the time type should be cumulated on a daily or period basis.
- Specify whether the balance from the previous period or year should be taken over at the start of a new period or year, or whether the cumulation should start from zero.
If you use display objects to display balances in the Time Manager's Workplace, you should note also the information given in the Define Reporting Quota Types IMG activity. - Decide whether the cumulated value of the time type is transferred to another time type at the start of a new period or year.
- Decide whether you want the value of the time type to be transferred to the subsystem. Enter "1" in the Transfer to cluster B1 field if required.
Further notes
Please make all your entries in the name range reserved for customers. Otherwise your entries may be overwritten by a release upgrade. Changing standard SAP entries is similar to making program changes.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | 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_OHT032 | 0 | HLA0006758 | Time Evaluation |
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_T555A | V - View | SM30 | 9999999999 | Define Time Types |
History
Last changed by/on | SAP | 19981221 |
SAP Release Created in |