C_HCMP_2311 SAP Certified Application Associate - SAP HCM Payroll for SAP S/4HANA Free Practice Exam Questions (2025 Updated)

A payroll schema is a set of rules and calculations that determine how employees are paid. A payroll schema consists of functions and parameters that define the logic and sequence of payroll processing.

The function CHECK is used to check whether certain conditions are met before executing the subsequent functions in the schema. The parameter ABR stands for aborted payroll run. It indicates that the payroll run was terminated due to an error or inconsistency.

The function/parameter combination CHECK/ABR must be activated in a productive payroll schema to ensure that the payroll run is not continued if there is an aborted payroll run for the employee. This prevents incorrect or incomplete payroll results from being posted to the database.

The other function/parameter combinations are not mandatory for a productive payroll schema. They are used for different purposes, such as:

OPT/INFT: This function/parameter combination is used to optimize the payroll run by skipping the processing of infotypes that are not relevant for the current payroll period.

OPT/TIME: This function/parameter combination is used to optimize the payroll run by skipping the processing of time data that are not relevant for the current payroll period.

PGM/ABR: This function/parameter combination is used to abort the payroll run for the employee if a certain condition is met. It is different from CHECK/ABR, which checks for an existing aborted payroll run.

References = : https://help.sap.com/doc/3044085 : https://help.sap.com/doc/3044085#section_2 : https://help.sap.com/doc/3044085#section_3 : https://help.sap.com/doc/3044085#section_4 : https://help.sap.com/doc/3044085#section_5 : https://help.sap.com/doc/3044085#section_6 : https://help.sap.com/doc/3044085#section_7 : https://help.sap.com/doc/3044085#section_8

The calculation rule XPPF is used to calculate the wage types /801 and /802, which are the gross and net pay for the current period. The operation XPPF calls the personnel calculation rules XPPO and XPP1, which perform the following steps:

XPPO: This rule calculates the gross pay (/801) by adding up all the wage types in the IT table that have the processing class 10 set to 1. The operation ADDWT&10 adds the wage types to the /801 wage type and stores it in the OT table. The operation ADDCU cumulates the /801 wage type in the CRT table.

XPP1: This rule calculates the net pay (/802) by subtracting the deductions from the gross pay. The operation SUBWT&11 subtracts the wage types in the IT table that have the processing class 11 set to 1 from the /801 wage type and stores the result in the /802 wage type in the OT table. The operation ADDCU cumulates the /802 wage type in the CRT table.

References = Payroll Schema, SAP Certified Application Associate – SAP HCM Payroll for SAP S/4HANA, SAP HCM Payroll for SAP S/4HANA - SAP Training Shop, Internal Tables for Payroll

AP (Paid Absences):Counting classes designated as 'AP' are used to track paid absences. Calculations using these counting classes will affect an employee's payroll.

AU (Unpaid Absences):Counting classes designated as 'AU' are used to track unpaid absences. Calculations using these counting classes won't generally impact payroll directly but might affect things like entitlements or reporting.

Why the other options are incorrect:

SA, KA: While 'SA' and 'KA' might be valid counting class types within a specific SAP HCM implementation, they are not standard classifications across all systems

The retroactive accounting depth of SAP payroll is the earliest date from which the payroll results can be recalculated due to changes in master or time data.

The retroactive accounting depth is determined by the following settings:

The “Earliest personal retroactive accounting date” stored in the Payroll Status infotype (0003) for the personnel number. This is the most specific setting that applies to an individual employee. It can be changed manually in the infotype or automatically by the system when certain changes are made.

The “Earliest retroactive accounting period” in the Payroll control record. This is the common setting that applies to all employees assigned to a payroll area. It can be changed in the payroll control record or by using the report RPUCTD00.

The hiring date stored for the personnel number. This is the absolute limit that cannot be exceeded by the other settings. The payroll results cannot be recalculated before the employee’s hiring date.

The system uses the latest of these three settings as the retroactive accounting depth for each personnel number. For example, if the personal retroactive accounting date is 01.01.2024, the payroll control record date is 01.02.2024, and the hiring date is 01.03.2024, then the retroactive accounting depth is 01.03.2024. References =

Retroactive Accounting | SAP Help Portal

Retroactive Accounting functionality in HCM payroll PART-I | SAP Community

Retroactive Payroll Processing | SAP Help Portal

The status of the payroll run can be viewed using the payroll control record. The payroll control record is used to control individual stages of the payroll run, including the release of the payroll, the correction phase, and the exit of the payroll run. During a payroll run, the payroll control record status prohibits changes to master data and time data that affect the payroll past or present1. References = SAP Help Portal, SAP Learning

Operation MULTI RAA is used to multiply the value of the rate field by the value of the amount field and store the result in the amount field. This operation is useful for calculating the total amount of a wage type based on its rate and quantity. For example, if the wage type is hourly pay, the rate field contains the hourly rate and the amount field contains the number of hours worked. By using MULTI RAA, the amount field will be updated with the total pay for that wage type. References = SAP Help Portal: MULTI RAA

 In SAP HCM Payroll for SAP S/4HANA, wage types are used for different purposes. For cumulations, the wage type /101 is used. This wage type represents the total gross amount, which flows into the final payment for the employee. Almost all of these amounts are subject to tax and social insurance contributions. A special feature for Croatia is that the wage type itself receives a CNTR2 split, which is needed to distinguish between domestic payments and work abroad. References = 1

Constant Valuation (V_T510J):This table in SAP HCM stores specific rules for valuing various wage types. MODIF 2 is how you group employees for consistent valuation purposes in this table.

XMOD Rule:The XMOD Personnel Calculation Rule (PCR) is often used to set the value of modifier T (MODIF T) which is used by the time evaluation module.

Why other options are less suitable:

MODIF T While used frequently in PCRs, MODIF T typically deals with grouping employees for time wage type selection purposes.

MODIF D: This modifier serves a specific function in day processing but isn't directly related to constant valuation.

MODIF 1 This might be a valid modifier within your specific SAP system, but it doesn't have a standard definition for constant valuation.

 The processing class 01 is used to determine into which valuation basis (for example mzd /001) the wage type is to be read1. This is done in rule CZ101. At the moment of processing, wage types from IT 0008 areavailable1. References = https://help.sap.com/docs/ERP_HCM_SPV/659325223d7d437388161c0c4da88ef6/12af7053e4960150e10000000a44176d.html

Here's a breakdown of why these are applicable to retroactive accounting:

A. "Forced retro.accounting" data field:This field allows you to manually trigger a retroactive calculation for a specific employee. This is useful in cases where normal retroactive processes might not be sufficient.

D. Customizing changes:Changes to system configuration data that impact payroll calculations (such as tax tables, deductions, etc.) will trigger retroactive accounting to ensure past payrolls are correctly aligned with the new settings.

Why the other options are incorrect:

B. Every change to customizing data...:While some changes to customizing data are payroll-relevant, not every single change will necessarily trigger a retroactive calculation.

C. A change to master data...:A change to master data in the current period won't automatically trigger retroactive accounting. For retroactive calculations, changes to master data in previous periods are typically required.

 The function DAYMO (Day Grouping for Time Wage Type Selection) can use four parameters: PAR1, PAR2, PAR3, and PAR4. These parameters are used to specify the day grouping for time wage type selection, which determines how the entries of table T510S (Time Wage Type Selection) are checked for different types of days, such as working days, Sundays, and public holidays. The parameters are defined as follows:

PAR1: Day grouping for working days

PAR2: Day grouping for Sundays

PAR3: Day grouping for public holidays

PAR4: Day grouping for other days

The values of the parameters are numerical codes that correspond to the entries in table T510S. For example, if PAR1 is set to 1, then the function DAYMO will check the entries of table T510S that have the value 1 in the field Day grouping for time wage type selection. If no entry is found, then the function DAYMO will check the entries that have the value 0 in the same field. If PAR1 is set to 0, then the function DAYMO will check only the entries that have the value 0 in the field Day grouping for time wage type selection.

The function DAYMO is usually called in the subschema TC00 (Wage Type Generation: International) or TC04 (Wage Type Generation International for Time Evaluation Without Clock Times) before the function ZLIT (Cumulate Time Wage Types), which reads the time wage types from table ZL (Time Wage Types) and cumulates them according to the cumulation class and the cumulation wage type. References =

SAP Help Portal: Function DAYMO

SAP Community: function daymo

 The following infotypes are evaluated for factoring in payroll: Actions infotype (0000), Organizational Assignment infotype (0001), and Absences infotype (2001). These infotypes are used to determine an employee’s exact remuneration, the remuneration amount is multiplied by a partial period factor1. References = 

https://help.sap.com/docs/ERP_HCM_SPV/ae31cd7e808241afb6cc47a420f059af/ae5bdd5321e8424de10000000a174cb4.html?locale=en-US &state=PRODUCTION&version=EHP8_HRSP_90

This operation is used within SAP HR to retrieve the personnel area which is part of an employee’s organizational assignment. Personnel areas are used to structure an enterprise from a personnel perspective and are unique to each company code.

In the payroll period in which the absence begins (B): The system compares the cut-off day with the start date and the end date of an absence record1. If the cut-off day is later than the end date, the system continues with the standard absence valuation process1.

On the actual dates in each affected payroll period ©: If the cut-off day is earlier than the start date, the system transfers the absence to the corresponding carry-over wage type, which is saved in an internal table for absence valuation in the next payroll period1.

In the payroll period in which the absence ends (E): If the cut-off day is between the start date and the end date, the system splits the absence into two records: One record is from the start date to the cut-off day, for which the system continues with the standard absence valuation. The other record is from the cut-off day to the original end date, which the system saves in the carryover wage type and will evaluate in the next payroll period1. References = 

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/7aff27bde57a4bd7b89e8cce540e110e/dede391612cc4bf0831329b9138f360c.html

 When you want to use a wage type in infotype 8 (Basic Pay) that valuates your amounts indirectly from the pay scale table, you use the TARIF module. The TARIF module is used for indirect evaluation of wage types. Indirect evaluation defines the actual amounts for each wage type that the employee is eligible for according to his or her Pay Scale Grouping for Allowances1. When using pay grades for basic pay wage types, you will use indirect evaluation module 58710 to retrieve pay grade level and store it into AMT field of the wage type2. References = 2, 1

 The Payroll Status infotype (IT0003) stores data on the Payroll status and Time Management status of an employee. It is created and updated automatically by the system during the hiring action, time evaluation, payroll run, or changes to the payroll past. The infotype contains fields that control the retroactivity of an employee’s time evaluation and payroll runs, such as:

Earl.pers. RA date: Sets the exact date back to which the system can run retroactive accounting.

Earliest MD Change: The program recognizes whether and when payroll must be repeated to take master data changes into account.

MD Change Bonus: To perform retroactive Accounting in connection with bonus accounting.

Payroll Correction: If the personnel number has been rejected or data has been changed in the correction phase. These fields determine how far back the system can go to recalculate the employee’s payroll results based on the changes made to the master data, time data, or payroll data. Data stored in this infotype should be changed only in exceptional cases, as these changes will affect the employee’s payroll processing and/or retroactive accounting. References =

Payroll Status (Infotype 0003) | SAP Help Portal

All About Infotype 0003 Payroll Status in SAP - Guru99

AMT 0.90: This multiplies the amount of the current wage type by 0.90, effectively reducing it by 10%.

ADDWT*: This adds the reduced wage type amount (along with its number) back to the input table (IT), making it available for subsequent calculations or processing.

Why other options are incorrect:

AMT 0.90 ADDWTI:* The 'I' at the end signifies that the result will be stored in the internal table, but not passed back to the input table (IT) for further processing in the current schema.

AMT 0.10 ADDWT* / AMT 0.10 ADDWTI*:** These would reduce the wage type by only 1%, not 10%.

The rules used to determine hourly rates for all employees in SAP HCM Payroll for SAP S/4HANA are X010 and X013. Rule X010 is used for the determination of valuation bases. In this step, all the wage types which should be included in the rate of pay are added1. Rule X013 is used for the division of valuation bases. In this step, /0 series wage types (/001,/002) are divided with calendar days, working hours, working days, or with a fixed value. We arrive at the rate of pay1. References = SAP Community

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/85346b7b83c8474e993429d934f77cc0/de38c2531bb9b44ce10000000a174cb4.html

 Wage types in SAP HCM Payroll are used to assign payments and deductions as well as to control the payroll program. They are the building blocks of the payroll module and areessential to compensate the employees1. In the case of an hourly wage type, the hourly rate, which should be multiplied by the number of hours performed by the employee, during the payroll run2. Therefore, wage types /001 and /002 can be used to calculate the hourly base rate for salaried employees. References = 

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/e533a9d0e7e547818964b2fd3226924b/953ac2531bb9b44ce10000000a174cb4.html

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/21a0a960d9b44ccaa6ac02f87e100f2f/37cade537187424de10000000a174cb4.html