Hierarchy
SAP_HRCDK (Software Component) Sub component SAP_HRCDK of SAP_HR⤷
PY-DK (Application Component) Denmark⤷
P09C (Package) HR Customizing: Denmark
IMG Activity
| ID | OHAMFORS060 | Example: Time quota in window |
| Transaction Code | S_PH9_46000477 | (empty) |
| Created on | 19990519 | |
| Customizing Attributes | OHAMFORS060 | Example: Time Quota in Window |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAXFORS060 |
This step outlines how you output an attendance or absence quota for an employee in a window.
Example
You want to set up the absence quota for an employee in a window. The information in the window should look like this:
Quota Entitlment Taken Requested Remainder
Leave 28,0 12,0 2,0 14,0
Training 6,0 0,0 1,0 5,0
Total 34,0 12,0 3,0 19,0
Standard settings
- The following tables can be used for the time quotas:
- ZKT Information about attendance quotas
- ZKQ Information about absence quotas
- ZKX Information about the transfer pool
- ZKSUM Totals of the above quotas
- ZK Place holder for one of the above tables in line layout
- The following fields from table ZK can be used:
- ANZHL Entitlement at period end date
- BEGDA Deduction start date
- ENDDA Deduction end date
- KTART Quota type (Conversion 01 -> Text)
- KVERB Used up to period end date
- ORDER Requested for the future after the period end date
- REDU Compensated up to period end date
- REDU2 Compensated after period end date
- REST Remainder without taking ORDER and REDU2 into account
- REST2 Remainder taking ORDER and REDU2 into account
- ZEINH Time unit (days or hours)
- The identifier determines the selection of time quotas. The following keys exist for the identifier:
In the case of these identifiers, quota records are only selected if they are deductible in the current payroll period.
- YDnn Record for quota type nn
- S*nn Total of all records for quota type nn
- S*** Total of all records for all quota types
In the case of these identifiers, quota records are only selected if they were deductible in the past, but can now only be compensated, and have a remainder other than 0.
- PDnn Record for quota type nn
- P*nn Total of all records for quota type nn
- P*** Total of all records for all quota types
In the case of these identifiers, quota records are only selected if they cannot be deducted and compensated until sometime in the future, that is, quotas that have already been entered for the future.
- NDnn Record for quota type nn
- N*nn Total of all records of quota nn
- N*** Total of all records for all quota types
- The summary of time quotas takes place at the same time as the summation of wage types. For this you should create a cumulation identifier with its own ID and text. Then add time quotas from tables ZKQ, ZKT and/or ZKX to this cumulation identifier.
Note that totals within totals are not allowed. This means that you cannot add a previously created cumulation identifier to another one.
Note that it is not possible to create totals from wage types and time quotas. A cumulation identifier cannot contain entries from tables ZKQ, ZKT, ZKX and, for examaple, RT.
It is not advisable to add time quotas that were performed in different time units because hours are not converted into days or vice versa. In such a case, hours would be added to days.
As the quota type (KTART) has two characters, and the cumulation identifier has four characters, only the last two characters of the selected identifer can be printed. If, for example, you call your total ZKS1, the field KTART only contains the value S1. The text of the total will, nevertheless, always be determined correctly. This restriction is only important if you want to output the technical key of a quota.
Activities
- In the Form Editor, choose Line layout -> Change.
- Create a line layout:
- In the field line type enter a two digit number, for example, 10.
- In the field column type enter X.
- For the line layout, enter the following individual fields:
Column Table Table field Conversion
001 ZK KTART 01
027 ZK ANZHL 07
037 ZK KVERB 07
047 ZK REST 07
Choose table ZK here in order that tables ZKT, ZKQ, ZKX and ZKSUM have the same line layout in the window. ZK is only a place holder for the other tables. For this reason, table ZK can only be used for the fields of the line layout and not as an individual field.
- Choose Goto -> Cumulation identifier.
- Create a new cumulation identifier with ID (for example, ZKS1) and text.
- Choose Details and create new lines with the quotas to be cumulated from tables ZKT, ZKQ, ZKX. In our example this would be ZKQ-YD10 and ZKQ-YD12.
- Choose Goto -> Window.
- Create a new group.
- Here you should define three subgroups 01, 02, and 03 with the following data:
Subgroup Table Identifier LType CType
01 ZKQ YD10 10 X
02 ZKQ YD12 10 X
03 ZKSUM ZKS1 10 X
Further notes
- For all totals using time quotas, the field's start and end dates are not important because they are not filled.
- For time quotas from the transfer pool, the fields KVERB, ORDER, REDU, and REDU2 are not filled because a quota in the transfer pool cannot be used or paid out. This means that the value in fields REST and REST2 is always the same as the value in field ANZHL.
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 |
|---|---|---|
| OHAMFORS060 | DK | Denmark |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAXFORS060 | 0 | HLA0100669 | Forms |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990519 |
| SAP Release Created in |
