SAP ABAP IMG Activity OHTY013 (Assign Time Types and Processing Types)
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 OHTY013 Assign Time Types and Processing Types  
Transaction Code S_AHR_61009713   IMG Activity: OHTY013 
Created on 19981221    
Customizing Attributes OHTY013   Assign time types and processing types 
Customizing Activity OHTY013   Assign Time Types and Processing Types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHTY013    

Function TYPES reads the processing type and time type table and assigns a time type and processing type to the imported time data. The assignment is made according to the processing type/ time type class and the pair type allocated to the imported times.

The time types are the smallest units used later to cumulate the main time balances in the section on balance formation.

Various different time wage types can be formed from the recorded times in time wage type selection, according to the processing type.

Example

  • Separate balances should be formed for
    - Periods of leave
    - Periods of illness
    - Other absences
    The absence types included in the various categories can be grouped together via the processing type/time type class. Class '02' is assigned to the absence types 'doctor's appointment', 'sickness of up to 2 days', 'sickness of longer than 2 days', 'health spa stay', for example. Absences are allocated pair type 2. TYPES can be used to assign the time type 1202, which then takes these periods of illness into account.
  • Overtime should not be detected (exclusively) via personnel calculation rules, but recorded explicitly using special attendance types in infotype 2002. An attendance type is set up for 'overtime' with a processing type/time type class which is assigned the processing type 'M' via the processing type and time type table. Overtime wage types are generated on the basis of this attendance type.

Requirements

The valid time type determination group for reading the processing type and time type table has been defined in Set groupings.

Standard settings

The following pair types are assigned when time data is imported:

  • '1' (at work), function P2000 or P2011
  • '2' (recorded absence), function P2001
  • '3' (recorded attendance), function P2002.

In the standard system, one of the following processing types is assigned to all recorded times using function TYPES:

  • 'S' for planned work
  • 'M' for overtime

All recorded times are acknowledged as time worked in the standard system, and are included in time wage type selection.

Processing type/time type classes '01' - '05' are evaluated in the standard. This class is assigned to each absence/attendance type. The specifications of classes '01' to '05' in the standard system are:

  • '01' leave types or general attendance hours
  • '02' periods of illness
  • '03' time off for overtime
  • '04' other absences
  • '05' overtime

The value '00' is used for time data with an initial processing type/ time type class.

The naming convention for time types is 1yzz, where y is the pair type and zz is the processing type/time type class.

Recommendation

Activities

  1. Decide which absence and attendance types in infotype 2001 or 2002 you want to differentiate for balance formation and wage type generation.
  2. Group the absence/attendance types by assigning them appropriate values in the processing type/time type class.
  3. If new time types are required, they have to be defined in Define time types. 9yzz is recommended as a naming convention, where y is the pair type and zz is the processing type/time type class.
  4. If you have to make modifications to the processing type and time type table, copy the standard entries for time type determination group '02' to a value in the customer range - '99' for example. Make all modifications in the customer range. Use operation MODIF T to change the time type determination group in the section Set groupings.
  5. Customize the assignment of processing type and time type in the customer range, using the standard entries for reference.
  6. If new time types are created, time type cumulation should be enhanced in Form daily balances.
  7. The value '00' is used for times with an initial processing type/ time type class. A different default value can be assigned by changing the second parameter of function TYPES.

Further notes

If there is no time type stored in the processing type and time type table, function TYPES deletes the corresponding time data for further processing. If the processing type is '*', the present processing type of the time pair is retained.

Some of the processing types assigned using function TYPES are only provisional and are changed in the further course of time evaluation using personnel calculation rules. This is necessary to determine overtime subject to bonuses, which is not recorded explicity, but should be detected by the system by analyzing all times according to special overtime rules.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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 OHTY013 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 Define Time Types 
V_554S_E V - View SM30 03 Determine Processing Type/Time Type Class for Absence 
V_554S_F V - View SM30 01 Determine Processing Type/Time Type Class for Attendance 
T555Y S - Table (with text table) SM30 01 Assign Processing Type and Time Type 
History
Last changed by/on SAP  19990616 
SAP Release Created in