SAP C_HCMP_2311 Practice Test Questions Answers

 The subschemas of the payroll main schema X000 are processed in the following order:

XBDO: Edit basic data

XTOO: Gross remuneration (Time Management)

XAL9: Factoring and storage

XEND: Final processing12 References = 

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/8dde694fdfc548afb97e01051396e708/f5a1de537187424de10000000a174cb4.html

https://help.sap.com/docs/ERP_HCM_SPV/174123b1d22d4793a7d0570196ab5c23/f5a1de537187424de10000000a174cb4.html

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