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 | OHTY035 | Update Cumulated Balances |
| Transaction Code | S_AHR_61009163 | IMG Activity: OHTY035 |
| Created on | 19981221 | |
| Customizing Attributes | OHTY035 | Update Cumulated Balances |
| Customizing Activity | OHTY035 | Update Cumulated Balances |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHTY035 |
As well as the day balances which are assigned to the individual days evaluated, time balances can be cumulated per period and stored in a separate table (cumulated balances).
You decide the following in this step:
- which time balances should be cumulated per period
- which time types should be stored on the database in the table of day balances or cumulated balances.
Example
You want the time type "flextime balance" to be cumulated per period. Both the day balance and the period balance of the time type "flextime balance" are to be stored.
Requirements
If you want time types to be cumulated per period and their value for the period or day to be saved to the database, enter an appropriate value in the Save as day balance or Cumulate in period
balance field when you define time types.
Standard settings
Function CUMBT interprets the transfer indicators assigned to time types.
Time types which are intended for transfer to the day total are passed on to the table which is to be stored.
Time types which are to be cumulated are cumulated in the appropriate time type per period and stored in the table of cumulated balances.
Recommendation
On no account should you deactivate function CUMBT; if you do, time balances and time wage types are not saved to the database.
Activities
Check the coding of the time types wich are to be saved as day balances or cumulated balances, and modify the relevant indicators if necessary
in Define time types.
Further notes
Certain time types are only required as utility values in time
evaluation, for evaluating an individual day. Utility time types -
0000 and 0001, for example - do not have to be saved to the database.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired 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 | OHTY035 | 0 | HLA0003736 | Time Evaluation Without 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 |
| V_T555A | V - View | SM30 | 07 | Update Monthly Balances |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
