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, employees are grouped for use in personnel calculation rules (PCRs) using the customizing table V_001P_K. This table is used to set the employee subgroup grouping for personnel calculation rules regardless of its current value

https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/payroll-operations/ba-p/13241690

• Pnn:This option lets you specify a particular wage type using its number (e.g., P0008 for basic pay). This gives you precise control over which wage type the PCR will process.
• GEN:This option tells the PCR to process all wage types found in the Input Table (IT). It's useful when you need the rule to work with a range of wage types without specifying them individually.

Why the other options are incorrect:

• NOAB:This is a valid parameter but its primary function is to prevent a PCR from running multiple times for the same employee subgroup. It doesn't directly control which wage types can be accessed.
• ABART:This represents the Wage Type (Lohnartin German). While wage types are a core part of payroll processing, the ABART parameter itself doesn't directly specify which wage types the PIT function will access.

 Factoring in SAP HCM Payroll for SAP S/4HANA is used when an employee did not work for the whole payroll period, then a partial remuneration is calculated during the payroll run1. Factoring is used in the following cases: To reduce payments made to an employee because he or she joins, leaves, or is absent from the company during a period. To calculate remuneration for an exact period because of substitutions, changes in basic pay, organizational reassignments, or changes in the personal work schedule1. Therefore, the scenarios that cause factoring to occur when they happen in the middle of a pay period are when an employee has a basic pay change (Option B) and when a different work schedulerule is assigned (Option D). References = 1

• When a personnel number is rejected in the payroll run, the system sets the Payroll Correction indicator in infotype 0003 (Payroll Status) for that employee1.
• When a personnel number is subject to master data changes in the correction phase, the system also sets the Payroll Correction indicator in infotype 0003 (Payroll Status) for that employee2.
• The Payroll Correction indicator means that the payroll results of the employee need to be recalculated in the next payroll run3.
• Therefore, the system uses the Payroll Correction indicator in infotype 0003 (Payroll Status) to identify the personnel numbers whose payroll results need to be recalculated in the next payroll run. References =
• 1: SAP Help Portal, Payroll Control Record, section “Rejected Personnel Numbers”.
• 2: SAP Help Portal, Payroll Control Record, section “Master Data Changes in the Correction Phase”.
• 3: SAP Help Portal, Payroll Control Record, section “Payroll Correction”.
• 4: SAP Help Portal, [Payroll Control Record].

 To import an employee’s actual planned working time for each partial period, you need to use the variable ASOLL. This variable contains the planned working time in hours for the current partial period. The system calculates this value based on the work schedule rule and the employment percentage entered in the Planned Working Time infotype (0007). The variable ASOLL is used to determine the partial period factor, which is the ratio of the employee’s actual planned working time to the full-time planned working time for the same period. The partial period factor is used to prorate the employee’s pay and benefits for the partial period. References = Planned Working Time Infotype (0007), Time Evaluation

 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

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

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

 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 = 

 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

To calculate partial period factors including unpaid absences in work days for all counting classes, you need to use the variable AAU**. This variable represents the absence in work days for all counting classes. The formula for the partial period factor is:

Partial period factor=DivisorPlanned working time or flat rate period working time−Absence​

The divisor is the number of work days in the period. The planned working time or flat rate period working time and the absence are both in work days. Therefore, you need to use the same calculation unit (A) for both parameters. The variable AAU** contains the value for absence in work days for all counting classes. The variable ASOLL contains the value for planned working time or flat rate period working time in work days. Therefore, the partial period factor can be calculated as:

Partial period factor=DivisorASOLL−AAU**​

References=Partial Period Factor,Partial Period Remuneration (Factoring)

 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

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

 Before running a payroll in SAP HCM Payroll for SAP S/4HANA, you need to perform certain activities. These include:

• Generate Payroll Periods: Payroll periods are essential as they define the frequency of payroll runs. They could be weekly, bi-weekly, monthly, etc., depending on the organization’s policies.
• Create Control Records: Control records in SAP HCM Payroll are used to control the payroll status of an employee or a group of employees. They ensure that no changes can be made to master data or time data affecting the payroll past or present during a payroll run1.

Creating organizational units and assigning cost centers to positions are not directly related to the configuration needed before running a payroll. They are more related to the organizational structure and cost accounting respectively.

References = 

https://learning.sap.com/learning-journeys/get-started-with-sap-hcm-payroll/running-payroll_e1629f8b-5236-4a89-af07-6531cb316d9b

 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

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.

When you want to create live posting documents in SAP HCM Payroll for SAP S/4HANA, the status of the payroll control record should be “Exit payroll”. This is because the “Exit payroll” status indicates that the payroll process is over and the record can be updated in the account12. References = https://answers.sap.com/questions/4028753/payroll-control-record-status-while-posting.html

https://community.sap.com/t5/enterprise-resource-planning-q-a/how-to-best-unlock-locked-records-for-payroll/qaq-p/5503356

 In SAP HCM Payroll for SAP S/4HANA, the operation TSDIVP (Time Schedule Division Period) is used to query the average working hours per pay period for each partial period in table PARTT. This operation calculates the average working hours by dividing the total working hours by the number of pay periods. It takes into account the specific time schedule and partial periods to provide an accurate calculation.

References = 

https://stackoverflow.com/questions/35907459/how-to-get-the-total-working-hours-for-employees-with-sql-server

https://stackoverflow.com/questions/20004156/hours-and-average-hours-worked-per-day-by-department

 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%.

 In the process of Absence Valuation in SAP HCM Payroll for SAP S/4HANA, the system uses the employee grouping for absence valuation in the Valuation of Absences table (T554C) to select an absence valuation rule. This employee grouping is determined by the operation MODIF A in personnel calculation rule XMOD1. Therefore, MODIF A and the Absence Valuation Rule play an important role in Absence Valuation (v_T554C) in Customizing. References = 

https://help.sap.com/docs/r/97b4732247c048ef80ca97c92555e703/2.5.latest/en-US/ae17dd5321e8424de10000000a174cb4.html