C_HCMP_2311 SAP Certified Application Associate - SAP HCM Payroll for SAP S/4HANA Question 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 PC_PAYRESULT transaction is used to display payroll results for a selected employee in SAP HCM Payroll1.
• The payroll results are stored in different tables, depending on the type of data and the payroll program. Some of the most common tables are1:
• Therefore, the correct answer is B and C, as the RT and BT tables can be found in the PC_PAYRESULT transaction, while the IT and OT tables cannot. References = 1: How to Check Payroll Results using PC_PAYRESULT in SAP - Guru99

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.

 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

Here's why these define schema attributes in SAP HCM:

• Country Grouping:SAP HCM is designed for multinational use, and schemas are intrinsically linked to specific countries to ensure calculations adhere to local payroll regulations.
• Program Class:This attribute determines whether the schema will be used within Payroll Calculations (class C) or Time Management (class T). This distinction is crucial for how the rules within the schema will be processed by the system.

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 SAP HCM Payroll for SAP S/4HANA, wage types are used for different purposes. For cumulations, the wage type /101 is used. This wage type represents the total gross amount, which flows into the final payment for the employee. Almost all of these amounts are subject to tax and social insurance contributions. A special feature for Croatia is that the wage type itself receives a CNTR2 split, which is needed to distinguish between domestic payments and work abroad. References = 1

 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

• When you change the Organizational Assignment infotype (IT0001) after a productive payroll run, the system checks whether the change affects the payroll results of the previous periods.
• If the change affects the payroll results, the system triggers a payroll retroactive calculation for the employee in the next payroll run. This means that the system recalculates the payroll results from the earliest retroactive accounting date to the current payroll period, and adjusts the differences accordingly.
• If the change does not affect the payroll results, the system does not trigger a payroll retroactive calculation, and the payroll processes normally. References =
• SAP Help Portal: Payroll Retroactive Accounting
• [SAP Help Portal: Organizational Assignment (0001)]

 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

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

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

Secondary wage types are technical wage types that are created during payroll run and start with a slash (/). They are used for various purposes such as valuation, calculation,and reporting. For average calculation, which is a method of valuing wage types according to the principle of averages, the system uses the following secondary wage types:

• /201 Average basis 01 (Time wage earner): This wage type stores the amount of the wage types that are relevant for average calculation for time wage earners.
• /202 Average basis 02 Premium amount: This wage type stores the amount of the wage types that are relevant for average calculation for premium payments.
• /203 Average basis 03 (Incentive wage earner): This wage type stores the amount of the wage types that are relevant for average calculation for incentive wage earners.
• /210 Average posit. time (day): This wage type stores the positive time in days that are relevant for average calculation.
• /211 Average posit. time (hour): This wage type stores the positive time in hours that are relevant for average calculation.
• /212 Average neg.time (day): This wage type stores the negative time in days that are relevant for average calculation.
• /213 Average neg. time (hours): This wage type stores the negative time in hours that are relevant for average calculation.
• /216 Gratuity time (day): This wage type stores the gratuity time in days that are relevant for average calculation.
• /217 Gratuity time (hours): This wage type stores the gratuity time in hours that are relevant for average calculation.
• /240 Average wage dialog (day): This wage type stores the value of the average wage due per day multiplied by 100. It can be used to override the incentive wage earners’ daily average in the infotype 0008.
• /241 Average wage dialog (hrs): This wage type stores the value of the average wage due per hour multiplied by 100. It can be used to override the incentive wage earners’ hourly average in the infotype 0008.
• /242 Aver.diff. (day) * 100!!: This wage type stores the value of the average wage difference (DIFF) due per day multiplied by 100. It can be used to override the time wage earners’ daily average in the infotype 0008.
• /243 Aver.diff. (hour) * 100!!: This wage type stores the value of the average wage difference (DIFF) due per hour multiplied by 100. It can be used to override the time wage earners’ hourly average in the infotype 0008.
• /250 Average value (Ft/day): This wage type stores the calculated value of the daily average for the reference period. It is used for evaluation with the daily average (e.g. for printing in the remuneration statement).
• /251 Average value (Ft/hour): This wage type stores the calculated value of the hourly average for the reference period. It is used for evaluation with the hourly average (e.g. for printing in the remuneration statement).
• /260 Difference comp. in payr.: This wage type stores the value of DIFF * NUM. It is used for consideration of wage types evaluated with average in bases for calculating average value.
• /261 Absence fee difference: This wage type stores the value of DIFF * NUM. It is used for consideration of wage types evaluated with absence fee in bases for calculating average value.

References = Wage types of average calculation

Average bases can be included as a condition in an adjustment rule for averages. Here's why:

• Average Bases: Average bases refer to the specific wage types you want to include in an average calculation. Adjustment rules allow you to specify conditions that filter which wage types should contribute to a particular average.

Why the other options are less likely:

• Cumulation rule: Cumulation rules control how values are accumulated across time, but they don't directly define conditions for adjusting averages.
• Time unit: This is relevant to average calculations but wouldn't be a condition within the adjustment rule itself. The adjustment rule might use different time units for its calculations.
• PCR for average formula: PCRs can be used to define the calculation logic behind averages, but they're not directly used as conditions within adjustment rules.

How do adjustments work for averages?

Adjustment rules allow you to refine average calculations by:

• Filtering Wage Types: Specifying which wage types should be included or excluded from the average.
• Conditionally Applying Rules: Define conditions that determine when a specific adjustment should take place.

 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

• To assign a constant valuation basis to the time wage type, you need to use the valuation basis indicator in the table T512W (Valuation of Wage Types).
• The valuation basis indicator determines how the system calculates the rate for the time wage type. It can be one of the following values: K, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48…

In the SAP HCM Payroll for SAP S/4HANA, the function PIT (Process Input Table) uses parameters to define its behavior. Parameter 2 is used to specify the type of access for the personnel calculation rule. The allowed values for parameter 2 in the PIT function are ‘GEN’ and ‘NOAB’. ‘GEN’ stands for Generic access of personnel calculation rule (process any wagetype). ‘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).

References = 

https://answers.sap.com/questions/8719427/reg-parameters-in-schema.html

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

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

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

 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