Free Practice Questions for SAP C_HCMP_2311 Exam

 In SAP HCM Payroll for SAP S/4HANA, the function that generates time wage types on the TIP table is GWT (Generate Wage Types). This function processes the entries of table T510S (Time Wage Type Selection), which contains the wage types that can be selected and the conditions that must be met for the selection of a wage type1. References = 

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

When processing a wage type in SAP Payroll, if there is no requirement to differentiate between employee subgroup groupings, you would leave parameter 3 blank when function PIT calls the rule to process the wage type1. This is because parameter 3 in the PIT function is typically used for relative time unit, and if set to ‘X’, it would mean WPBP for each time unit1. However, in this case, since there is no differentiation needed for employee subgroup groupings, parameter 3 should be left blank. References = 

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

To define the time/measurement unit for a wage type, you need to maintain the Time unit / measurement field in the Wage type characteristics table (V_T511) in Customizing. This field determines the unit of measurement for the wage type, such as hours, days, or months. You also need to specify the Input combination field, which controls whether the wage type can be entered with an amount, a number/unit, or both. References = Wage Types | SAP Help Portal, Do not enter units for wagetype in an infotype15 | SAP Community

 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

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

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

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