SAP ABAP IMG Activity OHAGB_AV001 (Bases for Valuation of Averages)
Hierarchy
SAP_HRCGB (Software Component) Sub component SAP_HRCGB of SAP_HR
   PY-GB (Application Component) United Kingdom
     PC08 (Package) HR accounting: GB
IMG Activity
ID OHAGB_AV001 Bases for Valuation of Averages  
Transaction Code S_L9C_94000703   s_l9c_94000703 
Created on 20010829    
Customizing Attributes OHAGB_AV001   Bases for Valuation of Averages 
Customizing Activity OHAXAV001   Bases for Valuation of Averages 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAXAV001    

Collective agreements often contain rules stating that absences are to be remunerated using an average from past months. In the following activities, you set the rules required. To carry out valuation by the principle of averages, you must first decide the following:

  • How many periods are to be used to calculate the average value?
  • Can a period be irrelevant to mean value analysis? (for example if an employee has unpaid leave for the entire period).
  • What is the maximum number of periods to be used to calculate averages in such cases?
  • What types of absence are to trigger average pay?
  • What does the form for the calculation of averages values look like?
  • Which values should be calculated for the new employees in the first month, if no historical value for the calculation of an average value is available?
  • Should an average value be adjusted when pay is changed (for example after a standard pay increase)?
  • Which wage types are included in an average value?

Standard settings

Three model entries are delivered:

These entries can be found in client 000. Other entries are also planned for further functions in HR.

  • Amounts and hours are collected from 3 previous periods for calculation rule 1. In the final processing, the average value is calculated by dividing the amount by the hours. All of the periods are relevant.
  • The calculation is extended to 6 previous periods in calculation rule 2.
  • The same data is used in calculation rule 10 as in rule 1. This calculation rule is accessed with specification A, in processing class 15 which is part of the rule Special processing for the valuation of wage types. This specification leads to a special processing in this rule. A check is run to see whether the absence started in the previous period or whether it extends into the following period. In this case the average value already calculated is used from the previous period, or the average value which is calculated in the period is stored in the results table in order to be used in the following period.

Activities

Familiarise yourself with the overview about the possibilities of how to create the pay scale rules in the system. Please refer to a description of individual and essential activities in the following chapters.

You can edit this part either according to wage types or as a whole. When editing each infotype separately please perform all activities until adjusting each wage type in the payroll procedure. The adjustment should occur altogether.

You can create the personnel rules and the rules (calculation, cumulation, adjustment) for all wage types in all chapters if you process all data at the same time.







Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHAGB_AV001 GB United Kingdom
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAXAV001 0 HLA0100668 Bases 
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
VC_T511ABC C - View cluster OH02 01 99 Rules for calculation of averages 
History
Last changed by/on SAP  20020405 
SAP Release Created in 46C