C_HCMP_2311 Sample Questions Answers

• 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

 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

•  Conditions Day: This section specifies the days when the rule applies. Weekdays are highlighted, indicating the rule applies on weekdays. Public holidays (PH) are not highlighted, meaning the rule is not applicable on public holidays.
• Conditions Time: This section doesn't have any selections, so there are no time-based conditions for selecting the time wage type.

Therefore, considering weekdays are highlighted and public holidays are not, the only condition that aligns with selecting the time wage type isNOT on a public holiday.

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

 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:

 The internal table ZML (Cumulated Time Wage Types) contains the cumulated time wage types for the current payroll period. It is filled by the function ZLIT (Cumulate Time Wage Types) in the schema XT00 (Time Data Processing). The function ZLIT reads the time wage types from table ZL (Time Wage Types) and cumulates them according to the cumulation class and the cumulation wage type. The cumulation class and the cumulation wage type are defined in table T510S (Time Wage Type Selection). The cumulation class is a grouping of wage types that have the same valuation basis, such as total gross, total net, or total hours. The cumulation wage type is a technical wage type that stores the cumulated amount or number for each cumulation class. For example, the cumulation class 1 (total gross) corresponds to the cumulation wage type /101, which is stored in table ZML. References =

• SAP Help Portal: Internal Tables for Payroll
• SAP Help Portal: Time Wage Type Selection
• SAP Community: cumulation class, cumulation wage types

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.

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

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

The correct answers are:

• B. Rule X015
• C. Rule X010

In the standard XT00 subschema, functions and rules are processed in a specific order. Here's why X015 and X010 come before the MOD function:

• Personnel Calculation Rules (PCRs): Generally, PCRs (like X015 and X010) are processed to perform calculations, determine values, and can be used to set up variables for later use by other functions.
• MOD function: The MOD function acts upon calculations or variables established earlier by PCRs. It often deals with things like:

Why the other options are less likely:

• GENPS: This function is typically used much earlier in the subschema during payroll initialization, not directly before the MOD function.
• AVERA: This function focuses on average calculations and is often processed later, potentially after the MOD function.

Note:The exact order of functions and PCRs within subschemas can be customized to a degree, so this explanation is based on common SAP HCM practices.

 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

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

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

 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

• Employee Subgroup Groupings for PCRs:This setting allows you to categorize employees into groups to apply different payroll rules. SAP reserves values below 10 (00 - 09) for its use.
• Customer-Specific Values:You can use the range 00 to 99, excluding the fixed SAP values of 5 to 9, to create your custom groupings. This flexibility allows you to tailor payroll rules according to your company's specific needs.

 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

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