SAP ABAP IMG Activity OHATHFORS050 (Example: Time Quota in Single Field)
Hierarchy
SAP_HRCTH (Software Component) Sub component SAP_HRCTH of SAP_HR
   PY-TH (Application Component) Thailand
     P26C (Package) HR customizing: Thailand
IMG Activity
ID OHATHFORS050 Example: Time Quota in Single Field  
Transaction Code S_PH9_46000238   (empty) 
Created on 19990506    
Customizing Attributes OHATHFORS050   Example: Time Quota in Single Field 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAXFORS050    

This step describes how you output an attendance or absence quota for an employee in individual fields.

Example

You want to set up an absence quota for an employee in individual fields. The information should look like this:

Leave entitlement    28,0   

Taken    12,0

Requested    2,0   

Remainder    14,0

Standard settings

  • The following tables can be used for the time quotas:
    • ZKT         Information on attendance quotas
    • ZKQ         Information on absence quotas
    • ZKX         Information from the transfer pool
    • ZKSUM         Total of 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 the period end date
    • REST     Remainder without taking ORDER and REDU2 into account
    • REST2     Remainer taking ORDER and REDU2 into account
    • ZEINH     Time unit (days or hours)

  • The identifier determines the selection of the time quotas. An identifier can have the following keys:

    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

      The identifier YDnn cannot always be used because only one value can be displayed in a single field. If there are several records for a certain quota type, then the first value is printed. The other records are not printed. You should use the identifier S*nn that contains the total of all the records of a quota or you should use a cumulation identifier to create the total for several quotas. The same applies to the identifiers PDnn and NDnn.

      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 for quota type nn
    • N***        Total of all records for all quota types

  • The cumulation of time quotas takes place at the same time as the summation of wage types. For this you must enter a cumulation identifier with its own ID and text. Then you can 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 can not add a previously created cumulation identifier to another cumulation identifier.

    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 example RT.

    It is also not advisable to add time quotas that are performed in different time units because hours are not converted to days and 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 identifier can be printed - if you call your total ZKS1, for example, the field KTART only contains tha value S1. The text of the total will, however, always be determined correctly. This restriction is only important if you print the technical key of a quota.

Activities

  1. Choose Goto -> Cumulation identifiers.
  2. Create a new cumulation identifier with an ID (for example ZKS1) and text.
  3. Choose Details and create new lines with the quotas to be cumulated from tables ZKT, ZKQ, ZKX. In this example, these are ZKQ-YD10 and ZKQ-YD12.
  4. In the Form Editor choose Individual fields -> Create.
  5. Enter four individual fields with the following data:

Page type Position Tab. Tab.field Ident. P-length Conv.

FP 16/020 ZKSUM ANZHL ZKS1 05 07

FP 16/025 ZKSUM KVERB ZKS1 05 07

FP 16/005 ZKSUM ORDER ZKS1 15 07

FP 16/030 ZKSUM REST ZKS1 05 07

Ergebnis

The entry in the Identifier field denotes that information on time quota type ZKS1 is to be printed.

The information that is to be printed for this time quota type is stored in the Table field field. Since you are dealing here with a total of absence quotas, you must specify the relevant fields from table ZKSUM (Totals of time quotas).

The conversion 07 means that the time quota is only printed with one decimal place.

The page type FP dentes that the information should only be printed on the first side of the form.

Further notes

  • For all cumulations 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
OHATHFORS050 TH Thailand
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAXFORS050 0 HLA0100669 Forms 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990506 
SAP Release Created in