Processing Class 01, "Assign wage type to a valuation basis," is the standard SAP control mechanism for determining how a wage type contributes to the formation of valuation bases like /001 and /002. To include a basic wage type in the calculation of the hourly rate stored in /001, this processing class must be configured correctly. The specification within this class dictates whether the wage type's amount and/or number (hours) are added to the cumulation wage types that are used to calculate the final rate in /001.

B. 10: Processing Class 10 ("Mark wage types for payroll run") controls the general processing of a wage type within the payroll schema, not its specific contribution to valuation bases.

C. 15: Processing Class 15 ("Valuation of time wage types") determines how a time wage type is valuated (e.g., using /001 as a rate), not how it helps form the /001 valuation basis itself.

D. 99: Processing Classes 90 through 99 are reserved for customer-specific use and have no predefined standard SAP function for wage type valuation.

1. SAP Help Portal - Wage Type Characteristics

Processing Classes: The official documentation describes the standard processing classes. For Processing Class 01

it states: "This processing class is used to form the valuation bases /001 and /002." This directly confirms its role in the scenario described. (SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> Tools -> Customizing -> Wage Type Characteristics -> Processing Classes).

2. SAP Help Portal - Calculation of Averages: This document explains the concept of valuation bases and how they are formed. It details that the payroll function X015 uses the specifications in Processing Class 01 to cumulate amounts and hours from wage types into the technical wage types /001 and /002. (SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> Basic Functions -> Calculation of Averages -> Setting up the Calculation of Averages with Valuation Bases).

In SAP Payroll the delivered variable type KAU (table T511V) is defined as “partial-period factor in work days incl. unpaid absences for all counting classes.” When you assign KAU to a wage-type valuation rule or PCR, the system determines the divisor (planned work days) and the numerator (paid work days) after first subtracting any unpaid absences, so the factor already reflects absence reduction across every counting class. Therefore it is the required variable whenever the factor must be based on work days and must always reduce for unpaid absences, irrespective of the absence counting class.

A. SAP02 Calculates factor in work days but ignores unpaid absences; therefore does not fulfil the requirement.

C. AAU Calculates factor in work hours, not work days; wrong time unit for the scenario.

D. SAP Placeholder for individual SAP0x variables; none of them include unpaid absences in work days for all counting classes.

1. SAP ERP HCM Payroll 6.0 → SAP Library → Payroll → Calculation of Payroll Results → Partial Period Factoring → “Delivered Variables SAP01-SAP04

KAU

AAU” – paragraph “KAU (Workdays incl. unpaid absences

all counting classes)”.

2. SAP Education Course HR110 (Payroll – Business Processes)

Unit 9 “Partial Period Factors”

p. 9-17: table listing “KAU – Work-day factor incl. unpaid absences”.

3. SAP Press

P. Jones

“Configuring and Customizing SAP ERP HCM Payroll”

2nd ed.

Rheinwerk

2015

ch. 6.3 “Schema Variables (T511V)”

p. 213: description of KAU variable purpose.

The function AVERA is the standard function for the new, flexible average calculation processing in SAP Payroll. It is designed to calculate average values based on wage types from previous payroll periods. This function offers enhanced configuration flexibility through processing classes, cumulation rules, and assignment rules, allowing it to handle various complex averaging scenarios for payments such as absence valuation or overtime. It supersedes the older, less flexible average calculation methods.

A. X016: This is a Personnel Calculation Rule (PCR), not a function. It is used to process and assign values for averages but is called by a function like AVERA.

B. MEANV: This is the older, now obsolete, function for calculating averages. The question specifically asks for the "new" average processing function, which is AVERA.

C. PIT X015 GEN: This represents the execution of a PCR (X015) by a general processing function (PIT). It is part of the average calculation logic but is not the name of the dedicated new average function itself.

1. SAP Help Portal - Payroll Functions and Operations: The official documentation for SAP ERP Human Capital Management describes the AVERA function as "Calculation of Averages (New)". It details its parameters and contrasts it with older methods. (See SAP Library for SAP ERP Central Component

Human Resources -> Payroll -> Payroll -> Tools -> Payroll Driver -> Functions in the Payroll Schema -> AVERA: Calculation of Averages (New)).

2. SAP Training Courseware THR12 - SAP ERP HCM: Payroll: In the unit on "Averages

" the curriculum explicitly introduces AVERA as the new function for average processing

detailing its configuration in the IMG and its use within the payroll schema. It distinguishes AVERA from the old function MEANV and the associated PCRs like X015. (Refer to THR12 course materials

Unit 7: Averages).

The LGMST feature is the standard and most flexible method in SAP HCM to propose default values for the Basic Pay infotype (IT0008). The feature's return value is structured to provide the Pay scale type, Pay scale area, and the wage type model. Based on the employee's organizational assignment (e.g., Personnel Area, Employee Group), the feature's decision tree determines the appropriate values. This allows for dynamic and rule-based defaulting when a new IT0008 record is created.

A. Use the table VT510 (TARIF table).

This table defines pay scale groups and levels. It is used for validation after the pay scale type and area have already been determined, not for defaulting them.

B. Use table V001PC (Check Assignment of Pay Scale Structure to Enterprise Structure) if you do NOT use the TARIF feature.

This table assigns a pay scale structure to a personnel subarea. While it can be a fallback, the LGMST feature is the primary, more powerful tool for defaulting these values dynamically.

C. Use table V503 G (Define employee subgroup grouping for primary wage type).

This configuration is used to group employee subgroups for wage type permissibility and other settings, not for defaulting the pay scale structure (type and area) in IT0008.

1. SAP Help Portal

SAP S/4HANA

"Default Values for Basic Pay": "The system uses feature LGMST to determine the default values for an employee's basic pay. The return value of the feature determines which pay scale type

pay scale area

and wage type model are used." This document explicitly details the function of the LGMST feature for IT0008.

2. SAP Training Materials

THR12 - Management & Administration I: In the unit on "Personnel Administration

" the section covering "Basic Pay" (Infotype 0008) configuration specifies that the LGMST feature is used to default the pay scale parameters and the wage type model. (e.g.

THR12ENCol18

Unit 5

Lesson: Basic Pay).

3. SAP Knowledge Base Article 2368321 - "Default values for Pay Scale Type and Pay Scale Area in Infotype 0008": This KBA confirms that the LGMST feature is the standard procedure for defaulting the pay scale type and area in the Basic Pay infotype. It outlines the process and the structure of the feature's return value.

The initial wage type has Rate (RTE) = 10, Number (NUM) = 13, and Amount (AMT) = 0.

1. The operation MULTI RAA is processed first. This operation multiplies the Rate field (RTE) by the Number field (NUM) and places the result in the Amount field (AMT).

Calculation: 10 (RTE) 13 (NUM) = 130.

The wage type's fields are now: RTE=10, NUM=13, AMT=130.

2. The operation ADDWT adds the current wage type to the output table (OT). According to standard SAP payroll principles, once a valuation basis like the Number (NUM) field has been used to calculate an amount, it is cleared to prevent duplicate calculations or incorrect processing later. The Rate is typically retained.

Therefore, the final wage type written to the output table has Rate=10, Number=0, and Amount=130.

A. The Rate (RTE) field is not cleared by these operations; its value of 10 is preserved.

B. The Amount (AMT) is incorrectly stated as 0; the calculation results in 130. The Rate is also incorrectly cleared.

D. The Amount (AMT) is incorrectly stated as 0; the multiplication of Rate and Number results in 130.

1. SAP Help Portal

Payroll (PY)

Payroll Operations Documentation:

Operation MULTI: "The MULTI operation multiplies the contents of two fields of the current wage type and enters the result in a third field. The parameters specify the fields

for example

MULTI RAA performs the calculation RTE NUM = AMT." (This confirms the calculation part of the question).

Operation ADDWT: "The ADDWT operation adds the current wage type to an internal table. The parameter specifies that the wage type should be written to the Output Table (OT)

formerly the Results Table (RT)."

2. SAP Education Courseware

THR12 (SAP HCM Payroll):

Unit: Personnel Calculation Rules: The course materials explain the principle of wage type valuation. In standard schemas and rules (e.g.

sub-schema XAL9

rule X015)

after a wage type is valuated (e.g.

number of hours multiplied by a rate)

the valuation bases (Number and/or Rate) are often cleared using the ZERO= operation or as an implicit part of the finalization process before being stored in the results table. This prevents the wage type from being re-valuated. The question tests this fundamental processing convention. The clearing of the NUM field is standard practice.

The function WPBP (Work Place Basic Pay) is a core component of the SAP Payroll schema. Its primary role is to read and prepare fundamental employee master data for the payroll calculation period. It specifically imports data from Infotype 0001 (Organizational Assignment), Infotype 0007 (Planned Working Time), and Infotype 0008 (Basic Pay). The function creates period-specific entries (splits) in the internal WPBP table whenever there is a change in these infotypes, ensuring that payroll is calculated accurately for segments of the period with different organizational, time, or pay data.

C. 0015: Additional Payments (Infotype 0015) are processed later in the payroll schema, typically by the function PRT (Process Recurring Payments/Deductions and Additional Payments).

E. 2001: Absences (Infotype 2001) are processed by time management functions within the payroll schema, such as P2001, and are valued by functions like PAB.

1. SAP Help Portal

SAP ERP Central Component

Functions for the Payroll Schema: The official documentation for the WPBP function explicitly states its purpose. It reads data from the infotypes Actions (0000)

Organizational Assignment (0001)

Planned Working Time (0007)

Basic Pay (0008)

and Cost Distribution (0027) to create the work center/basic pay table. This table forms the basis for remuneration. (Accessed under SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> Tools -> Payroll Driver -> Functions for the Payroll Schema -> WPBP: Read Basic Personal Data).

2. SAP Help Portal

Processing Steps of the Payroll Run: The documentation outlines the sequence of a payroll run. It describes that initial processing involves reading basic data (WPBP) before moving on to processing time data (like absences from IT2001) and then processing recurring and additional payments (like IT0015). This confirms the separation of duties between WPBP and other functions. (Accessed under SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> The Payroll Process -> Processing Steps of the Payroll Run).

3. Glynn

D.

& De Torres

I. (2009). SAP ERP HCM Payroll. SAP PRESS. Chapter 4

"The Payroll Schema

" details the structure and key functions of the payroll process. It describes the function WPBP and confirms that it processes infotypes 0000

0001

0007

and 0008 to build the basic data for the payroll run. It also explains that other infotypes like 0015 are handled by subsequent functions. (Specific reference: Chapter 4

Section 4.2.2 "Function WPBP").

In SAP Payroll, the standard personnel calculation rule XMOD is used to set various employee groupings, known as modifiers, for subsequent processing. The modifier MODIF 2 is specifically designated as the "Valuation Basis Grouping". This grouping is used by payroll functions and operations to read constant values, such as amounts or numbers, from the "Constants for Valuation" table (VT510J). Rule XMOD typically sets this modifier based on the employee's pay scale area, allowing for different constant valuations for different employee groups.

A. MODIF T: This modifier is used for the Time Wage Type Selection grouping, which determines wage type generation based on time data (Table T510S).

B. MODIF D: This modifier is used for the "Differentiation of Payments" grouping, which controls how payments are processed (Table T510C).

C. MODIF 1: This modifier is the "Pay Scale Grouping for Allowances," used to determine wage type permissibility and valuation based on pay scale structure (Table T510A).

---

1. SAP Help Portal

Payroll (PY-XX)

Standard Personnel Calculation Rule XMOD:

Reference: In the documentation for the standard rule XMOD

it is explicitly stated: "The system sets modifier 2 for the valuation of constants (table T510J)." This directly links MODIF 2 to the VT510J table.

Source: SAP Help Portal

Payroll -> Payroll: International -> Basic Settings -> Personnel Calculation Schemas and Rules -> Standard Personnel Calculation Rule XMOD.

2. SAP Help Portal

Payroll (PY-XX)

Valuation Bases:

Reference: The documentation on valuation bases explains that constants from table T510J are read using a specific grouping. This grouping is set in the personnel calculation schema using rule XMOD with the parameter MODIF 2.

Source: SAP Help Portal

Payroll -> Payroll: International -> Basic Settings -> Valuation Bases -> Constants for Valuation.

3. SAP Customizing Implementation Guide (IMG):

Reference: Within the SAP system

the documentation for the IMG activity Payroll -> Payroll: International -> Basic Settings -> Valuation Bases -> Define Constant Valuations describes the configuration of table VT510J. The documentation for the "Constant val. grouping" field (KONST) specifies that its value is determined by the employee grouping for valuation bases

which corresponds to MODIF 2 set in rule XMOD.

Path: SPRO -> Payroll -> [Country] -> Basic Settings -> Valuation Bases -> Define Constant Valuations.

The function GON (Go On / No Action) is used within the payroll schema to check if an employee has been rejected during the initial data import phase. An employee is typically rejected if essential master data infotypes, such as Actions (0000), Organizational Assignment (0001), Personal Data (0002), or Payroll Status (0003), are missing or incomplete. By checking for this rejection status, the GON function effectively serves as a gatekeeper, ensuring that the payroll driver does not proceed with calculations for an employee whose master data is incomplete. It stops further processing for the rejected personnel number.

A. UPD: This function is used to update internal tables, such as the results table (RT), not to check the completeness of master data.

C. ENAME: This function's specific purpose is to read the employee's name from infotype 0001 (Organizational Assignment) into the header of the remuneration statement.

D. WPBP: This function reads and processes data from the Work Center Basic Pay (WPBP) table, which is populated from infotypes like Organizational Assignment (0001) and Basic Pay (0008).

1. SAP Help Portal - Payroll Functions and Operations:

Function GON (Go On / No Action): "The function checks whether the employee has been rejected during the data import phase. If so

processing is terminated for this employee." This directly supports the answer

as rejection is a consequence of incomplete master data.

Function WPBP (Read Basic Data): "The function reads the infotypes Organizational Assignment (0001) and Basic Pay (0008) and makes the data available for the payroll run."

Function ENAME (Read Name): "The function reads the employee's name in the infotype Organizational Assignment (0001)."

Reference Location: SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> Tools -> Payroll Driver (RPCALCx0) -> Functions and Operations in the Payroll Schema. (This structure is consistent across SAP documentation versions).

2. SAP Training Courseware - HR400 (Payroll Configuration):

Unit: Payroll Schema: This course material details the structure of standard schemas like X000 and sub-schemas like XBDO. It explains that the initial block is for data retrieval and validation. The function GON is explicitly identified as the check to see if the employee should be processed further or skipped due to missing core data. (e.g.

Section on "Basic Data Processing").

The PIT (Process Input Table) function in a Personnel Calculation Rule (PCR) uses parameters to control how it processes wage types. The second parameter dictates the processing type.

- GEN (Generate): This parameter instructs the function to place the specified wage type into the Output Table (OT), even if it does not exist in the Input Table (IT). This is a direct method of controlling wage type creation.

- NOAB: This parameter prevents the function from reading wage types from the old results table (ORT) of the previous payroll period. This controls the source of wage types being accessed, ensuring only current period data is processed.

A. Pnn: This is not a valid parameter for the PIT function. It resembles a naming convention for infotypes (Pnnnn) but does not control wage type access within this function.

D. ABART: This refers to a payroll area type, which is a field used in other contexts like absence valuation, but it is not a parameter for the PIT function.

1. SAP Help Portal - Payroll Functions and Operations: The documentation for the PIT function details its parameters. It explicitly lists GEN and NOAB as valid entries for the second parameter (par2) to control processing behavior.

Source: SAP Help Portal

Functions and Operations (PY-XX-TIM)

Section: "Function PIT: Process entries in the Input Table".

Details: The documentation specifies: "par2 = GEN: The wage type is to be added to the OT even if it is not in the IT." and "par2 = NOAB: The wage types are not to be read from the tables of the last payroll result (LRT

ORT)."

2. SAP ERP Human Capital Management - Payroll Configuration: Standard SAP training materials and configuration guides for payroll schemas explain the syntax and usage of common functions like PIT.

Source: SAP Education Courseware

HR400 - Payroll Configuration.

Details: Chapter on "Personnel Calculation Rules"

Unit on "Functions in Schemas". This section details the PIT function and its parameters

including GEN and NOAB

as fundamental controls for wage type processing.

To reduce a wage type's amount by 10%, you must multiply the current amount by 0.90. The operation AMT 0.90 correctly performs this calculation. The requirement to "retain it for further processing" means the modified wage type must be placed back into the Input Table (IT) so it can be processed again by subsequent operations or rules within the same schema loop. The operation ADDWTI (Add Wage Type to Input table) achieves this. Therefore, the combination AMT 0.90 ADDWTI is the correct sequence of operations.

A. AMT 0.90 ADDWT: This is incorrect because AMT 0.90 sets the amount to a fixed value of 0.90, it does not multiply. ADDWT sends the wage type to the Output Table (OT), not retaining it in the Input Table (IT).

C. AMT 0.10 ADDWT: This is incorrect as AMT 0.10 sets the amount to 0.10. Furthermore, ADDWT sends the wage type to the Output Table (OT), which does not meet the retention requirement.

D. AMT 0.10 ADDWTI: While ADDWTI correctly retains the wage type in the Input Table (IT), the operation AMT 0.10 incorrectly sets the amount to a fixed value of 0.10 instead of performing the required percentage reduction.

1. SAP Help Portal - Payroll Operations Documentation: The official documentation for SAP ERP Human Capital Management outlines the functions of personnel calculation rule operations.

Operation AMT: The documentation specifies that AMTK multiplies the amount field by a constant. To reduce by 10%

the multiplication factor is 0.90. (Reference: SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> Tools -> Personnel Calculation Schemas -> Operations -> AMT).

Operation ADDWTI: The documentation states that this operation adds the current wage type to the internal Input Table (IT)

making it available for further processing within the current sub-schema. (Reference: SAP ERP Central Component -> Human Resources -> Payroll -> Payroll -> Tools -> Personnel Calculation Schemas -> Operations -> A -> ADDWTE/ADDWTI/ADDWT).