Technical Process of Average Processing (Old)

Prerequisites

Caution Caution

The procedure for processing averages described in this section, and in the following sections, refers to releases prior to Release 4.6B. The processing of averages as of Release 4.6B has fundamentally changed. For more information, see Old and New Processing of Averages and the Implementation Guide (IMG) under Start of the navigation path Payroll Next navigation step Time Wage Type Valuation Averages New Bases for Valuation of Averages End of the navigation path .

End of the caution.

If you been using the old version for processing averages up until now, you can now use this version. You do not have to convert your system to the new version. However, the old version for processing averages will no longer be developed. If you reconfigure, you should only use the new version for processing averages.

Process Flow

The old version of average processing takes place in the following sequence:

1. Creating Bases for Calculating Averages

Primary wage types to be included in the average bases are cumulated in one of the secondary wage types for average bases in accordance with the entries you have made. This cumulation is performed in each payroll period for each employee. The average bases are stored in internal table RT at the end of payroll, and are available for future calculations performed in accordance with the principle of averages.

2. Specifying the Wage Types to be Valuated Using the Averages Principle

The subschema XT00 ( Processing of Time Data for Payroll ) is accessed by personnel calculation schema X000. The calculation rule X015 ( Valuation of Time Wage Types ) is the first action relevant to the calculation of averages.

Note Note

In the following, the X sign represents certain personnel calculation schemas and rules. This sign stands for the international versions of the personnel calculation schemas and rules and can be replaced with a country-specific letter. For example, there is a German personnel calculation schema D000 for the international personnel calculation schema X000.

End of the note.

The personnel calculation rule X015 determines whether the internal table IT contains time wage types that should be valuated according to the principle of averages. The contents of the AMT ( Amount ), NUM ( Number ), and RTE ( Rate ) fields are checked using decision operations AMT?0, NUM?0 and RTE?0.

If the AMT field contains a value, the wage type will be transferred with the operation ADDWT ( Add Wage Type to Subsequent Wage Type ).
If the AMT field does not contain a value, but the NUM and RTE fields do contain values, the value in the NUM field will be multiplied by the value in the RTE field. The result is entered in the AMT field and the wage type is transferred with the operation ADDWT.
If only the NUM field contains a value, the operation VALBS ( Evaluate Valuation Bases ) queries whether a valuation basis has been entered in table T512W for the wage type. If this is the case, the wage type is valuated using the appropriate valuation basis. If a valuation basis has not been specified, but a specification has been entered for processing class 15, the wage type is valuated in accordance with the principle of averages. Processing is continued using operation GCY with personnel calculation rule X016 ( Special Processing for the Valuation of Time Wage Types ).

Only wage types that meet the following conditions are calculated according to the principle of averages:

Only the NUM field ( Number ) contains a value.
No valuation basis has been entered.
A specification has been entered for processing class 15.

3. Defining Calculation Rules

After defining which wage types are to be valuated according to the principle of averages, the calculation rule is defined. This is carried out by the decision operation VWTCL° 15 in the calculation rule X016. This decision operation queries processing class 15. Wage types that are to be evaluated using the principle of averages, are coded in processing class 15 with a particular specification. The operation MEANV <nn> is called for each specification. In this operation, nn stands for a calculation rule from the Calculation Rules for Averages view (V_T511A). Depending on the calculation rule, operation MEANV <nn> performs the actual calculation of average values.

Example Example

Your wage type has specification 1 in processing class 15. You have entered personnel calculation rules X017 (Relevancy Test for Averages) , X018 (Calculation of Averages after Cumulation) and the cumulation type 01 (from the Cumulation Rules for Bases for Calculating Average Values view (V_T511B)) for calculation rule 01 . You have also specified that 3 previous periods should be taken into account when the averages are calculated. In rule X016, the operation MEANV 01 is assigned to specification 1 . Using parameter 01 , calculation rule 01 is determined using personnel calculation rules X017 and X018, cumulation type 01, and 3 previous periods. Operation MEANV performs the calculation of averages on the basis of these entries.

End of the example.

4. Calculating the Averages

Operation MEANV performs the following steps when calculating averages:

The internal table MV is queried and this determines whether averages have already been calculated for the employee concerned within the current payroll period using the same average calculation rule.
– If this is the case, the value that has already been determined is entered in the RTE field (rate).

– If this is not the case, step 2 is performed.
The internal table IT is queried and determines whether the Average Value wage type exists for the employee concerned (from the Calculation Rules for Averages view (V_T511A)).
– If this is the case, the value is entered in the RTE field (rate).

– If this is not the case, step 3 is performed.
The individual periods are processed.

Each previous period to be processed is imported, starting with the current period - 1.
The relevancy test is performed.
If the period is relevant, the cumulation takes place using the cumulation rule.

The system checks whether the maximum number of periods to be taken into account has been reached.
If this is not the case, return to step 2.
The final processing of averages is performed:

The average is calculated using personnel calculation rule X016 for final processing of averages from the Calculation Rules for Averages view (V_T511A) .
The value is entered in the RTE (Rate) field for the wage type to be valuated.

When the calculation of averages has finished, an average value is entered in the RTE field (Rate) for the appropriate wage type. This average value is used to effect a valuation (usually of absences). To do this, the values in the RTE and NUM fields are multiplied.

5. Special Processing for Frozen Averages

Special processing for frozen averages is dependent on the specification of a wage type in processing class 15. If a wage type has specification A in processing class 15, the decision operation ABEVL? will be called in the calculation rule X016.

The decision operation ABEVL? determines whether an employee’s absence goes beyond the current period and returns a value ( 0, 1, 2 or 3 ) as the result of the query. Based on this value, you can trigger the following absence valuations in the personnel calculation rule X016:

Return value 0 : The absence begins and ends in the current period.

Operation MEANV calculates the average.

Return value 1 : The absence begins in the current period and ends in the next period.

In this instance, the average value is calculated for the current period and frozen for the next period.

Operation MEANV calculates the average.
Operation ZERO=NA sets the NUM (Number) and AMT (Amount) fields to zero.
Operation ELIMI deletes split indicators.
Operation ADDNAE/02A transfers the value from the RTE field (Rate) to wage type /02A and saves the value in the internal table RT. By placing the value in this wage type, the rate , in other words, the average value, is frozen and can be re-used in the next period to valuate the same absence.

Return value 2 : The absence begins in the previous period, continues through the current period, and ends in the next period.

The absence is first valuated in the current period using the frozen average value from the previous period. The average value is then frozen again for the next period.

Operation RTE=L /02A reads wage type /02A, in which the average value of the previous period was fixed, from internal table LRT.
Operation MULTI NRA multiplies the value in the Rate (RTE) field, in other words the average value, by the Number (NUM) field, in other words the number of absence hours or absence days. The result is entered and stored in the Amount (AMT) field.
Operation ZERO=NA sets the NUM (Number) and AMT (Amount) fields to zero.
Operation ELIMI deletes split indicators.
Operation ADDNAE/02A transfers the value from the RTE field (Rate) to wage type /02A and saves the value in the internal table RT. By placing the value in this wage type, the rate , in other words, the average value, is frozen and can be re-used in the next period to valuate the same absence.

Return value 3 : The absence starts in the previous period and ends in the current period.

The absence is valuated using the frozen average value of the previous period.

Operation RTE=L /02A reads wage type /02A, in which the average value of the previous period was fixed, from internal table LRT.
Operation MULTI NRA multiplies the value in the Rate (RTE) field, in other words the average value, by the value in the Number (NUM) field, in other words the number of absence hours or absence days. The result is entered and stored in the Amount (AMT) field.