Learn, Practice, and Improve with SAP C_HCMP_2311 Practice Test Questions

Explanation:

The TC00 (Time Data Processing, Wage Type Selection) subschema is specifically designed for processing time data within the payroll run. Its core function includes selecting the relevant time wage types from the Time Information Packet (TIP) table (populated by Time Evaluation) and preparing them for payroll calculation.

Why the other options are incorrect:

A. TM00 Time Evaluation with Clock Times & B. TM04 Time Evaluation Without Clock Times:
These are time evaluation schemas, not payroll subschemas. They are executed in transaction PT60 or PT61 to process raw time data and produce the TIP. They perform attendance/absence recording and quota deduction, but the selection of time wage types for payroll is a subsequent step handled by the payroll subsystem (TC00).

D. XINO Initialization of payroll (INTERNATIONAL):
This is a Payroll International (PI) subschema used for country-specific initialization steps at the very start of a payroll run. It handles preparatory tasks like reading specific international infotypes or setting global variables, but it does not process or select time wage types.

Reference:
The payroll schema follows a clear sequence of subschemas:
XINO (Initialization - International)
CINO (Initialization - Country)
TC00 (Time Data Processing, Wage Type Selection)
PC00 (Basic Pay Processing)
... (other subschemas for deductions, taxes, etc.)

Explanation:

The OUTWP operation in a payroll schema is used in conjunction with functions starting with 'P' (like P0014, P0015, P0008, P0167, etc.) to read and process specific Human Resources master data into the payroll results. Essentially, OUTWP calls a function module that reads the specified data.

C. Infotypes:
This is the primary and most common use. Each Pxxxx function corresponds to a specific HR Infotype (e.g., P0008 reads Basic Pay (Infotype 0008), P0009 reads Bank Details (Infotype 0009)). OUTWP is the operation used to execute these read functions.

D. Wage types:
Master data wage types (like those from Basic Pay Infotype 0008 or Recurring Payments/Deductions Infotype 0014) are queried via their respective Infotypes. Therefore, reading wage types is done through the Infotype read operations (e.g., OUTWP P0014).

E. Cost centers:
Cost assignment data (like Cost Center, Internal Order) is stored in Infotype 0001 (Organizational Assignment) and related Infotypes (e.g., 0027 for Cost Distribution). To access the employee's cost center within payroll, you use an operation like OUTWP P0001 to read the relevant infotype data.

Why the other options are incorrect:

A. Personnel areas:
While Personnel Area is a key organizational attribute, it is not directly queried using a specific Pxxxx function called by OUTWP in the standard payroll context for calculation purposes. It is a field within Infotype 0001. The payroll driver automatically provides the personnel area (via the PERNR-AWART relationship) for basic control, but you don't typically use OUTWP to "query" it as a separate operation. For detailed reporting, you would read Infotype 0001.

B. Pay scales:
Pay scale data (Pay Scale Group, Level, etc.) is stored within the Basic Pay Infotype (0008). It is not a separate entity read by its own Pxxxx function. You access it by reading Infotype 0008 (OUTWP P0008), and the pay scale information is part of that data structure. The option is incorrect because OUTWP does not query "Pay scales" as a distinct object separate from the infotype that contains them.

Reference:
The OUTWP operation is fundamental for data retrieval in payroll schemas. The naming convention Pxxxx directly corresponds to the Infotype number.

Explanation:

The TARIF wage type module is specifically designed for indirect valuation from pay scale tables (T5* tables, like T51* for wage types or T52* for salary scales). When you assign a wage type with module TARIF in Infotype 0008, the system does not store a fixed monetary amount. Instead, it stores a pay scale grouping (pay scale group, level, step, etc.). During payroll processing, the system uses this grouping to look up the current monetary value from the active pay scale table, ensuring the basic pay is always up-to-date with the latest salary agreements.

Core Function: It links the wage type to the organizational pay structure, enabling automatic valuation based on the employee's assigned pay scale data.

Why the other options are incorrect:

A. SUMME:
This is the summation module. It is used for wage types where a fixed monetary amount is directly entered and stored in Infotype 0008. This is the opposite of indirect valuation.

B. PRZNT:
This is the percentage module. It is used for wage types where the amount is calculated as a percentage of another wage type (e.g., a 10% bonus of basic pay). It does not perform pay scale table lookups.

C. ARBPL:
This is not a valid wage type module. ARBPL is an abbreviation for Work Center, which is a field in organizational planning and time management, not a module for wage type valuation.

Reference:
Wage type modules in the V_T512W (Wage Type Characteristics) table define how a wage type's amount is determined. Key modules for Infotype 0008 include:

Explanation:

In SAP HCM Payroll, secondary wage types are used for internal calculations and processing. They are organized into specific number ranges with designated purposes. The range /801 to /816 is exclusively reserved for average value calculations.

Why the other options are incorrect:

A. /840 to /845:
This range is typically used for cumulations and running totals (e.g., year-to-date totals), not specifically for average calculations.

B. /201 to /232:
This is a common range for statutory deductions (like taxes, social insurance contributions). These are wage types for final calculated amounts, not internal averaging work areas.

C. /001 to /002:
These are extremely common wage types, but they are usually primary wage types for gross pay components (like base salary) or are used in time management. They are not designated for average processing.

Reference:

SAP HCM uses a structured numbering system for wage types:
Primary Wage Types (e.g., 1000, 2000): Represent earnings and deductions from master data.
Secondary Wage Types (e.g., /101, /801): Used for internal payroll operations.

Explanation:

The ADDWT (Add Wage Type) operation is specifically designed to transfer wage types to an internal table during payroll processing. It takes a wage type from a specified source (like the results table - RT) and copies it into a different internal table (often the input table - IT or another processing table) so it can be used in subsequent calculations.

Why the other options are incorrect:

A. XINO (Initialization of Payroll - International):
This is a subschema, not a data transfer operation. It is called at the beginning of a payroll run for country-specific initialization tasks and does not move individual wage types between tables.

B. PIT (Payroll International):
This is a category or prefix for a suite of functions and operations designed for country-specific requirements. By itself, PIT is not an operation that transfers wage types. You would use a specific PIT function (like PIT X015 for averages), but the transfer of the wage type to a table beforehand would be done by another operation like ADDWT.

D. OUTWP (Output Work Process):
As discussed in a previous question, this operation is used to read data from HR master data (Infotypes) into the payroll context. It queries and retrieves data from the database, but it does not transfer wage types between internal tables that already exist in memory during the payroll run.

Reference:
Understanding the role of different schema operations is essential:
ADDWT: Moves/copies wage types between internal tables (e.g., from RT to IT).
OUTWP: Reads data from master data infotypes into the payroll run. ELIMI: Removes/deletes wage types from an internal table.

Explanation:

In SAP HCM Payroll, variables prefixed with SOLL refer to planned (or scheduled) working time. These variables are used to import the employee's contractual or planned working hours for a given period.

KSOLL: Provides the planned working time for the current payroll period (e.g., monthly planned hours).
ASOLL: Provides the planned working time per day.
SSOLL: Provides the planned working time for a partial period (e.g., a specific week or a day within the payroll period). This is the most direct answer to "actual planned working time for each partial period."

Why the other options are incorrect:

A. KDIVP, ADIVP, SDIVP:
These variables with the DIVP suffix are used for dividing values for payment. They are related to pro-rating payments (like splitting a monthly salary across different cost centers or pay scales), not for retrieving planned working time.

C. KDIVI, ADIVI, SDIVI:
Variables with the DIVI suffix are used for time proportionality in averaging. They are involved in calculating averages over partial periods, not for directly importing the planned working time figure.

D. KAU**, AAU**, SAU**:
Variables with the AU prefix are used for actual working time (e.g., KAUFW for actual hours worked, KAUMF for actual absence hours). They retrieve attended or absent hours from time evaluation results, not the planned schedule.

Reference:

Payroll variables are essential tools in payroll schemas and wage type calculations. The prefixes are key:

K = Period (e.g., monthly)
A = Day
S = Partial Period
SOLL = Planned working time (from the employee's work schedule) IST / AU = Actual working/absence time (from time evaluation)

Explanation:

Infotype 0003 (Payroll Status) is the master control record for an employee's payroll processing. Its primary purpose is to manage the payroll accounting status and, critically, to control retroactive accounting.

Why the other options are incorrect (they describe functions of other infotypes):

A. To control an employee's assignment to a payroll area:
This is controlled by Infotype 0001 (Organizational Assignment), specifically the "Payroll Area" field.

B. To determine the assigned payroll schema:
The payroll schema is determined by the employee subgroup (ESG) and payroll area combination, configured in table T52B9. The schema is not stored directly in an employee's infotype 0003.

C. To determine the assigned current payroll period:
The "current payroll period" is a characteristic of the payroll area itself (defined in table T549A), not stored in an individual's IT0003. The payroll driver uses the payroll area from IT0001 to find the current period from the payroll area definition.

Reference
Infotype 0003 is transactional in nature. It is not static master data but a processing log that is updated by the system after each payroll run. It holds the keys to understanding an employee's payroll history and controlling future calculations, making it the central infotype for payroll administrators when troubleshooting retroactive runs or locks.