Suppose we have a business requirement which is necessary to discount, from employee’s payroll, values regarding benefits only on the next payroll period. This kind of discount needs to be possible independent the number of off-cycles calculation between regular payroll first period (benefit) and second period (discount).
~ On regular payroll and period 201605, was paid a benefit for the employee and calculated the corresponding discount; on the next regular payroll – period 201606, is applied the benefit’s discount independent the number of off-cycles between regular payrolls:
To calculate the discount mentioned in a regular payroll’s period and apply it only on the next one, is necessary to configure the wage type related to be cumulated or not on table responsible to cumulate values on SAP HCM Payroll – CRT (Cumulated Results Table). Using the Processing Class 30, is possible to set the way that the wage type mentioned will be cumulated.
Processing Class ~ Cumulation Maintenance
Rules of Processing Class 30:
~ If the wage type was configured with the specification 0, then this wage type must not be cumulated;
~ If the wage type was configured with the specification 1, then the fields amount and number of this wage type must be cumulated in current year;
~ If the wage type was configured with the specification 2, then the field amount of this wage type must be cumulated in current year;
~ If the wage type was configured with the specification 3, then the field number of this wage type must be cumulated in current year;
~ If the wage type was configured with the specification T, then this wage type must be cumulated according to rules of the table T54C3;
Table ~ T54C3
Rules of Table T54C3 (Most used):
~ If the wage type was configured with the cumulation type field U, then this wage type will be cumulated until something clear it;
~ If the wage type was configured with the cumulation type field Y, then this wage type will be cumulated annually;
~ If the wage type was configured with the cumulation type field M, then this wage type will be cumulated monthly;
Function ~ SETCU
This function is responsible to processes the cumulations values from previous period to current period, importing wage types from OCRT (Old Cumulated Results Table) to CRT, respecting the rules of all entries of OCRT (whether a new cumulation interval starts or whether the cumulation continues).
Is important to say that is mandatory to process function IMPRT (see more about it: https://viniciustavanoferreira.wordpress.com/2016/12/12/sap-payroll-import-last-result-table-pcr-x006/) before function SETCU – like standard schema XLR0, because the cumulations of the previous period must be available on memory (OCRT) and also the old results. If your system uses Concurrent Employment, the flow payroll process consider CRT_PERSON and RT_PERSON tables too.
Wage type /101 from OCRT (Input)
~ If the current period was 01/2017 (next year), this cumulation was not considered, because the configuration is setting to value ‘Y’ (annually);
Wage type /101 from CRT (Output)
Function ~ ADDCU
This function is responsible to cumulate values from RT (Results Table) in CRT, respecting all configuration of Processing Class 30 and (when specification field is equals the value ‘T’) of the Table T54C3, to update cumulation values. Is important to say that if the perspective of this configuration is about Average Bases, this function will create the corresponding Average Bases based on configuration of the View V_T51AV_2W. When your system uses Concurrent Employment, the relevant wage types of table RT_PERSON are stored in table CRT_PERSON.
Wage type /101 from RT (Input)
Wage type /101 from CRT (Input)
Processing – accumulation according specifications in PC30
PC30 (specification 02 – Cumulate wage type amount in current year) ~ Wage type /101
Wage type /101 from RT (Output)
Wage type /101 from CRT (Output) ~ $338.836,94 (CRT Input) + $2.603,11 (RT Input) = $341.440,05 (CRT Output)
Vinicius T. Ferreira