Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PT (Application Component) Personnel Time Management⤷
PTIC (Package) HR Time Data: Customizing
IMG Activity
| ID | SIMG_OHT057 | Determine Break Times |
| Transaction Code | S_AHR_61009974 | IMG Activity: SIMG_OHT057 |
| Created on | 19981221 | |
| Customizing Attributes | SIMG_OHT057 | Determine Break Times |
| Customizing Activity | SIMG_OHT057 | Determine Break Times |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OHT057 |
In this step, you determine how breaks in the daily work schedule should be evaluated.
Example
According to the daily work schedule, an employee has a one-hour unpaid break which he can take during core time between 12 o'clock and 2 p.m. He takes a break at 12.30 and resumes work at 1.30 p.m. Before the breaks are evaluated, the resulting time pairs (12.00 - 12.30, 12.30 - 1.30, and 1.30 to 2 o'clock) all have the time identifier "Core time break". After break evaluation, the pairs 12.00 - 12.30 and 1.30 - 2 o'clock have the time identifier "Core time", and the pair 12.30 - 1.30 is assigned the identifier "Core time break".
Requirements
Function TIMTP must come before break evaluation in the schema.
Standard settings
This function starts by determining which pairs belong to the respective break. Non-recorded absences before and after the break are included in the calculation, that is if (in the above example) the employee goes at 11.55 and comes back at 12.55, the time pair is calculated as a break. Non-recorded time pairs are processed first - the system attempts as far as possible to assign the break to non-recorded times. Further processing is done chronologically.
The corresponding break (paid or unpaid) is generated up to the duration specified in the work break schedule. The remaining time is converted to fill time or core time.
Recommendation
Deactivate the function if you use fixed breaks only, i.e. breaks at fixed times.
Activities
- Decide on the sequence in which the different categories of time types should be filled with break time.
- 1 non-recorded times first (pair type = 0) and the rest chronologically
- 2 recorded absences first (pair type = 2)
non-recorded times (pair type = 0)
and the rest chronologically - 3 recorded absences first (pair type = 2)
attendances or off-site work (pair type = 1,3)
and the rest chronologically - 4 non-recorded times first (pair type = 0)
recorded absences (pair type = 2)
and the rest chronologically - Enter one of the above values as parameter 2 of function PBRKS.
- Decide how non-recorded absences before and after the break are to be taken into account.
- blank Only times during the break are counted
- AFT Non-recorded absences after the break
are included in the calculation - ALL Non-recorded absences before and after the break
are included in the calculation - BEF Non-recorded absences before the break
are included in the calculation - Enter one of the above values as parameter 3 of function PBRKS.
Further notes
You can also use a personnel calculation rule to control break evaluation. Enter the personnel calculation rule as the first parameter of function PBRKS.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional 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_OHT057 | 0 | HLA0003735 | Time Evaluation with Clock Times |
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 | TM00 10 | Modify Schema: Function DETTP |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
