C_HCMP_2311 SAP Certified Application Associate - SAP HCM Payroll for SAP S/4HANA Questions and Answers

 In SAP HCM Payroll for SAP S/4HANA, an average calculation rule is used to determine the average value for a specific wage type or set of wage types over a defined period. The average calculation rule can include several components:

• Cumulation rules: These are used to define how the wage types are cumulated over the average calculation period1.
• Relevant average period: This defines the period over which the average is calculated. It could be a fixed period (e.g., the last three months) or a variable period (e.g., the period of employment)2.
• Final processing: This is used to finalize the calculation of the average, such as rounding off the average value1.

Function PARTT and Modifier groupings are not typically included in an average calculation rule in SAP HCM Payroll for SAP S/4HANA.

References = 

The GENAU constant is available in the view V_t511K (payroll constants). It is used for accuracy purposes, specifically for rounding off in reduction formulae. This is particularly applicable in rules related to partial period factoring. References = 1

https://community.spiceworks.com/topic/2450278-factor-genau-in-payroll

In rule XPPF, the operation PPPAR checks for certain information such as whether and when the employee started a new job within the payroll period or whether and when they took unpaid leave1. If no split indicator is available the value of the partial period remains 11. Therefore, it checks for an employee’s entry or exit after the period start (Option A) and the current entry in arrears (Option D). References = 1

• 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 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

To define the time/measurement unit for a wage type, you need to maintain the Time unit / measurement field in the Wage type characteristics table (V_T511) in Customizing. This field determines the unit of measurement for the wage type, such as hours, days, or months. You also need to specify the Input combination field, which controls whether the wage type can be entered with an amount, a number/unit, or both. References = Wage Types | SAP Help Portal, Do not enter units for wagetype in an infotype15 | SAP Community

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.

When processing a wage type in SAP Payroll, if there is no requirement to differentiate between employee subgroup groupings, you would leave parameter 3 blank when function PIT calls the rule to process the wage type1. This is because parameter 3 in the PIT function is typically used for relative time unit, and if set to ‘X’, it would mean WPBP for each time unit1. However, in this case, since there is no differentiation needed for employee subgroup groupings, parameter 3 should be left blank. References = 

https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/understanding-functions-in-payroll-schemas-specific-eg-wpbp/ba-p/13270777

The valuation of a time wage type with wage type-dependent constants is often dependent on certain conditions being met. You can define different, wage type dependent constants that depend on a modifier. Different conditions are represented with different modifiers. The value of these modifiers is queried with the function RAB (Read Absences) or the operation VALBS (Valuation bases). Further conditions can be defined within the personnel calculation rule to determine whether a time wage type is valuated using a wage type-dependent constant valuation basis. In the standard system, the modifier MODIF 2 is used. You set the modifiers in personnel calculation rule XMOD ( Modifiers for Payroll ). References = https://help.sap.com/docs/r/d54170e34c6747d4a4462b963c0a6850/600_HRSP_I9/en-US/743dc2531bb9b44ce10000000a174cb4.html

The function GON (Generate Operation Number) in sub schema XBDO checks if all master data has been completely imported. It assigns a unique operation number to each employee and payroll area combination. If the master data is incomplete or inconsistent, the function GON will generate an error message and stop the payroll run for the affected employee. References =

• SAP Help Portal: Schema XBDO
• SAP Support Portal: SAP Note 3044085 - FAQ: SAP HCM Payroll for SAP S/4HANA

 The “Time wage type selection group” (MODIF W) is determined by the payroll driver to access entries from table T510S (Time Wage Type Selection) for the employee. This operation is specified by TMOD1. References = 

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/c6c3ffd90792427a9fee1a19df5b0925/e138c2531bb9b44ce10000000a174cb4.html

TheTMODpersonnel calculation rule is specifically used to determine the "Time wage type selection group" controlled by theMODIF Woperation. Here's how it works:

• Time Wage Type Selection: SAP uses time wage type selection to link time data (attendances, absences, etc.) with corresponding wage types for payment calculation.
• MODIF W: This operation within PCRs lets you specify groupings of employees that share specific time wage type selection rules.
• TMOD Rule: The TMOD rule allows you to customize how the MODIF W grouping will be determined. You can configure it based on factors like:

In SAP HCM Payroll for SAP S/4HANA, WPBP is both a function and a table. As a function, WPBP (Import work center and basic pay data) is used to transfer master data on the work center and basic pay for the payroll period to internal table WPBP1. The basic pay wage types are stored in the internal table IT1. If all the fields of the table WPBP are the same during the entire payroll period, this table will contain one record1. As a table, WPBP is filled by the infotypes Actions (0000), Organizational Assignment (0001), Planned Working Time (0007), Basic Pay (0008), and Cost Distribution (0027). It contains important organizational and payment-relevant data, and different partial period parameters2.

References = Understanding functions in Payroll Schemas - SAP Community, Internal Tables for Payroll - SAP Help Portal

 The calculation rule X018 is used to calculate the average of the wage type based on the cumulative values stored in the AMT and NUM fields. The operation X018 divides the AMT field by the NUM field and stores the result in the RTE field. This operation is usually performed after the cumulation of the wage type values using the ADDCU operation. The X018 operation is relevant for the valuation of time wage types according to the principle of averages, which is used for payroll and leave valuation. References = Payroll Operations, Payroll Schema, SAP HCM Payroll for SAP S/4HANA, Free SAP HCM Payroll for SAP S/4HANA Certification Sample Questions and Answers, Work Schedule Rule

• Executable Schemas:Executable schemas are designed to be run directly on employee data during the payroll process. They contain the complete set of rules and functions necessary to execute all aspects of payroll calculations. X000 is a standard international executable schema provided by SAP.
• Non-executable/Subschemas:Other schemas like XPPF, X010, and XT00 serve as components or building blocks within an executable schema. They might contain functions or calculations, but they cannot be run directly on their own.

The XIN0 subschema is specifically designed to initiate the payroll process within SAP HCM. It's responsible for a series of crucial initialization tasks, including:

• Reading employee master data
• Fetching relevant time data
• Initializing cumulation wage types
• Setting up data for processing within the payroll run.

 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

 In SAP HCM Payroll for SAP S/4HANA, time wage types are selected during the payroll process. This selection is performed in the payroll subschema using the function GWT (Generate Wage Types). The time wage types are selected based on the processing type of a TIP entry1. Specifically, the TC00 schema (Wage Type Generation International) is used for this purpose2. References = 2, 1

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

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/c6c3ffd90792427a9fee1a19df5b0925/e138c2531bb9b44ce10000000a174cb4.html

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

 In SAP HCM Payroll for SAP S/4HANA, processing classes determine how wage types are processed during the payroll run. Each processing class has its own specifications, with which each wage type is processed in a different way1. Specifically, processing class 10 is used to determine whether and how wage type amounts are to be reduced2. This means that if a wage type should be considered for factoring, it would be associated with processing class 10. References = 

https://help.sap.com/docs/ERP_HCM_SPV/659325223d7d437388161c0c4da88ef6/12af7053e4960150e10000000a44176d.html

https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/understanding-processing-classes-in-sap-hr/ba-p/13250375

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.

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

A Personnel Calculation Rule (PCR) is called within a schema for executing subtasks using various operations. Each step within a PCR corresponds to an operation and there can be sub PCRs too. A PCR will be processed by a function1. The attributes section of a PCR displays the text of the PCR, program class (T – Time Management, C – Payroll), Country Grouping, Person Responsible, Changes only by Person Responsible Checkbox, Created On and Last Change By date1. Therefore, in the attributes of a PCR, you must define the Processing class (A) and Program class (B). References = 1