Hierarchy

⤷

⤷

IMG Activity
ID | OHANL_TI340 | Determine break times |
Transaction Code | S_AHR_61014269 | IMG Activity: OHANL_TI340 |
Created on | 19981221 | |
Customizing Attributes | OHANL_TI340 | Determine break times |
Customizing Activity | OHANL_TI340 | Determine break times |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHANL_TI340 |
In this IMG activity, you determine how the breaks in the daily work schedule are evaluated. This is done using function PBRKS in personnel calculation schema TC00.
Example
You record attendances using infotype 2002, Attendances. According to the daily work schedule, an employee has 1 hour unpaid break which can be taken between 12 noon and 2 p.m. He/she takes the break at 12.30 p.m. and returns at 1.30 p.m. The resulting time pairs 12.00 - 12.30, 12.30 - 1.30 and 1.30 to 2.00 all have the time identifier fill time break before break evaluation. After break evaluation, the pairs 12.00 - 12.30 and 1.30 - 2.00 have the time identifier fill time and the pair 12.30 - 1.30 has the time identifier fill time break.
Requirements
In the personnel calculation schema, function TIMTP must come before function PRBKS for break evaluation.
Standard settings
The function first determines the pairs which belong to the respective break. Non-recorded absences before and after the break are included in the calculation. If the employee in the above example takes the break from 11.55 - 12.55, this time pair is counted as a break. The time pairs that were not recorded are processed first. The system attempts as far as possible to place the break during non-recorded times. Further processing is carried out chronologically.
The break (paid, unpaid) is generated up to the duration specified in the work break schedule. The remaining time is converted to fill or core time.
Recommendation
Deactivate PBRKS if you only work with fixed breaks, and if breaks are always unpaid in your enterprise.
Activities
- Decide on the sequence in which the different categories of time types within the break period should be filled with break time. The following entries are possible in parameter 2:
- 1: the non-recorded times (pair type = 0) first,
then all others in chronological order - 2: the recorded absences (pair type = 2) first,
followed by the non-recorded times (pair type = 0),
and all others in chronological order - 3: the recorded absences (pair type = 2) first,
followed by attendances or off-site work (pair type =1,3),
and all others in chronological order - 4: the non-recorded times (pair type = 0) first,
followed by recorded absences (pair type = 2),
and all others in chronological order - Decide how non-recorded absences before and after the break should be taken into account. The following entries are possible in parameter 3:
- 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
Further notes
You can also control break evaluation using a personnel calculation rule. Enter it as the first parameter of function PBRKS.
Only recorded absences feature in day processing in Payroll, and therefore it makes sense to set parameter 2 to "2".
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_TI340 | NL | Netherlands |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHANL_TI340 | 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 T | Maintain schema TC00 for break times |
History
Last changed by/on | SAP | 19990308 |
SAP Release Created in |