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

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

• 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

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

 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

 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

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

 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 LGMST feature is used to propose a default value for the Pay scale type and Pay scale area (IT 0008) data fields based on the country grouping, personnel area, and employee subgroup of the employee.
• To use the LGMST feature, you need to define the feature in the Customizing activity Define Features for Personnel Administration under Personnel Management > Personnel Administration > Basic Settings.
• In the feature, you can specify the pay scale type and pay scale area for each combination of country grouping, personnel area, and employee subgroup. You can also use wildcards (*) to cover multiple values.
• After defining the feature, you need to activate it in the Customizing activity Activate Pay Scale Type and Area Determination under Personnel Management > Personnel Administration > Payroll Data > Basic Pay.
• Once the feature is activated, the system will automatically propose the pay scale type and pay scale area for the employee when you create or change the IT 0008 infotype record. References =
• SAP Help Portal: Define Features for Personnel Administration
• SAP Help Portal: Activate Pay Scale Type and Area Determination
• SAP Community: SAP HCM Payroll for SAP S/4HANA - FAQ

 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

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)

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.

 Absences are processed during regular payroll runs using country-specific schemas. The absence valuation is carried out by the rule I015. This procedure consists in the multiplication of the number of the wage types generated from the function PAB by their amount per unit and it is showed in the internal table of the IT payroll1. Therefore, to include absence hours in the PARTA table, the wage type must be defined in absence valuation rules. References = 

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

https://help.sap.com/docs/SAP_S4HANA_ON- PREMISE/bb31338348194291925625f5e965ac94/7df5dd5321e8424de10000000a174cb4.html

 In SAP HCM Payroll for SAP S/4HANA, wage type selection rules are built using several elements. These elements are grouped into a rule group, forming different regulations for the selection of time wage types1. Each individual rule within a rule group contains the wage type to be selected1. The selection of a wage type is determined by whether the conditions specified in an individual rule are fulfilled1. Two of these elements are the Processing type and Conditions for the day1. References = 1

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

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

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

• Run Payroll up to Date: This crucial field in IT0003 determines the final payroll period for which an employee has already been paid. By updating this date to a period after the employee's termination date, you signal to the payroll system that a final off-cycle payroll run is needed.

Why the other options are less suitable:

• Qualified advance payment, Advance payment from master data:These might be relevant if you need to issue a payment before the final payroll run, but they don't directly trigger the payroll calculation for a terminated employee.
• Earliest MD Change Date:This field helps control retroactive pay calculations, but it's not the primary method for processing payroll for terminated employees.

Important Considerations

• Off-Cycle Payroll Runs: Processing payroll for terminated employees often requires a specific off-cycle payroll run to ensure proper calculations.
• Data Consistency: Ensure the employee's termination date and the "Run Payroll up to Date" align for accurate calculations.

In the SAP HCM Payroll for SAP S/4HANA, the function PIT (Process Input Table) uses parameters to define its behavior. The PIT function is used to process all wage types in the input table (IT) using a specific personnel calculation rule, in this case, Z123. The parameters ‘GEN’ and ‘NOAB’ are used in the PIT function to accomplish this. ‘GEN’ stands for Generic access of personnel calculation rule (process any wage type). ‘NOAB’ stands for Employee subgroup grouping personnel calculation from table employee group/employee subgroup (T503) without payroll type (Process for any EE sub-group groupings). Therefore, the correct configuration to process all wage types in the input table (IT) using personnel calculation rule Z123 and considering the employee subgroup grouping for the personnel calculation rule is ‘PIT Z123 GEN NOAB’.

References = 1, 2

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

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ff854a903cbf4c10910a5825d787693f/253ec2531bb9b44ce10000000a174cb4.html

In SAP HCM Payroll for SAP S/4HANA, wage type fields rate and number can be multiplied in a calculation rule using the MULTI ARN operation. The result of this operation will be stored in the amount field. To set the values in the rate and number fields to zero after the multiplication, the operations ZERO=N and ZERO=A are used1. References = 

https://answers.sap.com/questions/9074890/wage-type-for-multiplying-a-rate-with-amount-and-d.html

 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: