Free SAP C_HCMP_2311 Practice Exam with Questions & Answers | Set: 2

 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

To create a new personnel calculation rule, you need to use transaction PE01. This transaction allows you to access the rule editor, where you can define the rule type, the variable key, and the operations for the rule. You can also assign the rule to a payroll schema or a sub-schema using transaction PE02. The other transactions are not relevant for creating a new personnel calculation rule. PA30 is used to maintain employee master data, PA03 is used to display payroll control records, and PE02 is used to maintain payroll schemas and sub-schemas. References = Payroll Operations, Payroll Schemas and Personnel Calculation Rules PCR SAP HCM (HR), Personnel Calculation Rules

• AVERA function: This function is the core of the new average processing in SAP HCM. It's designed to calculate various averages (like gross averages, taxable averages, etc.) that can be used in subsequent payroll calculations.expand_more

Why the other options are incorrect:

• X016 This might be a valid Personnel Calculation Rule (PCR) in your SAP system, but it doesn't directly represent the AVERA function.
• MEANV This operation is used to assign average processing results to wage types but is not the central function performing the averaging.exclamation
• PIT X015 GEN: These are common commands, but they don't specifically represent the new average processing functionality.

The personnel calculation rules used in the subschema of XAL9 for factoring and storage are typically designed to handle specific country-related factoring and valuation scenarios. While the exact rules can vary based on the country and the specific requirements of the payroll system, generally, rules like XVAL (for valuation) and XPPF (for partial period factoring) could be involved in such processes1.

Therefore, the correct answers could be: C. XPPF D. XVAL

These rules help in calculating the correct pay for periods where employees have variable pay due to factors like absences or changes in work schedule. It’s always best to refer to the specific system documentation or configuration for the precise rules used in a given scenario.

 In SAP HCM Payroll for SAP S/4HANA, the calculation rules MULTI RAA and ADDWT * are used to process wage types. The MULTI operation multiplies two fields of the current entry of table OT and stores the result in a third field1. The ADDWT operation adds the wage type affected to an internal table1. Given the wage type 5000 with Rate = 10, Number = 0, and Amount = 13, if it only runs through the MULTI RAA and ADDWT * calculation rules, the result in the output IT would be Rate = 10, Number = 0, and Amount = 130. This is because the MULTI operation would not change the Rate or Number as they are multiplied by 0, and the ADDWT operation would not change the Amount as it is added to an internal table without any modification1. References = 1

Operation ADDWTE* is used to add a wage type to the results table (RT) with a specified amount and number. The wage type can be either a constant value or a variable from the input table (IT). The operation can also be used to modify an existing wage type in the RT by adding or subtracting the amount and number. The operation has the following syntax:

ADDWTE*nnnnnAmmmmmB

where nnnnn is the wage type, A is the operator (+ or -), mmmmm is the amount or variable, and B is the number or variable. For example:

ADDWTE*1000+1000.00

This operation adds wage type 1000 to the RT with an amount of 1000.00 and a number of 1.

ADDWTE*1000+VARGB

This operation adds wage type 1000 to the RT with an amount of VARGB and a number of 1.

ADDWTE*1000+1000.00-2

This operation adds wage type 1000 to the RT with an amount of 1000.00 and a number of -2.

ADDWTE*1000-VARGB

This operation subtracts VARGB from the amount of wage type 1000 in the RT and leaves the number unchanged.

References = 1 (SAP HCM Payroll for SAP S/4HANA, page 52) 2 (SAP Note 3044085 - FAQ: SAP HCM Payroll for SAP S/4HANA, question 13)

• 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 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 operation ADDWT is used to transfer wage types to an internal table. An internal table is a data structure that can store multiple records of the same type. The operation ADDWT can be used in personnel calculation rules (PCRs) or schemas to manipulate wage types. The syntax of the operation is:

ADDWT&XXXX

where XXXX is the four-digit wage type number. The operation will add the wage type XXXX to the internal table IT, which is a predefined table that contains all the wage types for the current payroll period. The operation will also perform some checks and validations, such as:

• If the wage type XXXX does not exist in the payroll cluster, the operation will create it with the default attributes from the wage type table T511.
• If the wage type XXXX already exists in the internal table IT, the operation will add the amount and number fields of the new wage type to the existing one, unless the wage type is cumulative or additive.
• If the wage type XXXX is cumulative or additive, the operation will create a new line in the internal table IT with the same wage type number, but with a different line counter.
• If the wage type XXXX has a time unit, the operation will convert the time unit to the payroll period unit, using the conversion factors from the table T510S.

The operation ADDWT can also be used with modifiers, such as:

• N: to suppress the creation of a new wage type if it does not exist in the payroll cluster.
• K: to keep the original attributes of the wage type from the payroll cluster, instead of using the default attributes from the wage type table T511.
• A: to add the wage type to the internal table IT without any checks or validations.

References = Working with Simple Internal Tables, SAP C_HCMPAY2203 Exam Practice Test Instant Access - CertsHero

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