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

Explanation:

To activate integration between Personnel Administration (PA) and Organizational Management (OM), two switches in table T77S0 are mandatory:

A. PLOGI ORGA
– This is the main integration switch that must contain an 'X'. Activating this switch enables the integration between Organizational Management and Personnel Administration via Infotype 0001 (Organizational Assignment), ensuring data consistency between both components .

E. PLOGI PLOGI
– This switch specifies the active plan version for integration. It functions as the central switch – if a plan version is entered, integration is active; if left blank, integration is switched off entirely .

Why other options are incorrect:

B. PLOGI EVENB
– This is an enhanced integration switch used for specific scenarios requiring company code changes during personnel moves, but it is not mandatory for basic integration activation .

C. PLOGI EVPAC
– This switch relates to master data actions for country reassignment and is not required for fundamental PA-OM integration .

D. PLOGI PRELI
– This defines a default position for employees not assigned to any position in the integrated system, serving as a fallback value rather than a mandatory integration switch .

Reference:
SAP Help Portal: "Set Up Integration with Personnel Administration"
Table T77S0 configuration documentation
SAP Learning: Organizational Management in SAP HCM

Explanation:

An Evaluation Path defines a chain of relationships between different object types in SAP Organizational Management (OM). To display a list of employees starting from an Organizational Unit and including a custom object (Object Type 99), the path must follow the logical structural hierarchy:

O (Organizational Unit): This is your starting point.

S (Position): Organizational Units do not hold employees directly; they hold Positions. Therefore, the path must move from the Org Unit to the Positions belonging to it.

P (Person/Employee): You then move from the Position to the Person (Employee) occupying that position.

99 (Custom Object): Finally, the path connects the Person to the custom Object Type 99.

This sequence (O-S-P-99) ensures that the system navigates through the standard "is described by" and "holds" relationships to reach the final custom assignment.

Why the Other Options are Incorrect

A. K-S-99-O:
This starts with a Cost Center (K). While Cost Centers are linked to Org Units or Positions, this path does not include the Person (P) object, so it cannot display a list of employees.

B. S-P-99-C:
This starts with a Position (S) and ends with a Job (C). It skips the Organizational Unit requirement mentioned in the prompt.

D. O-C-P-99:
This path attempts to go from Org Unit (O) to Job (C) and then to Person (P). In the standard SAP data model, employees are assigned to Positions (S), not directly to Jobs. Jobs describe the attributes of a position, but they are not the structural link to the person.

References
Transaction Code: OOAW (Maintain Evaluation Paths).
Table: T778W (Evaluation Paths) and T777E (Allowed Relationships).

Explanation:

When you attempt to create a time entry prior to the earliest retro accounting period on the payroll control record, the system allows the entry but limits the recalculation scope. According to SAP's time evaluation error message PG345, "You can make entries before this date, but only entries up to &V1& are recalculated" . This means:

The time entry is created - The system permits recording the data even though it falls outside the normal retroactive accounting period

Time data is recalculated only up to the earliest retro accounting date - The system recalculates from that date forward, but earlier periods remain unaffected

Why other options are incorrect:

A. The time entry is not created but time data is recalculated
– The system does not prevent creation entirely; it allows the entry with limited recalculation.

B. The time entry is created and time data is recalculated back to the earliest retro accounting period
– This overstates the recalculation scope; recalculation only goes back to the earliest retro date, not beyond it.

D. The time entry is not created and no time data is recalculated
– This is incorrect because the entry is created; it's just not fully recalculated.

Reference:
SAP message PG345: "Time evaluation: Change too far in the past, recalculation only to &" ; SAP Help documentation on retroactive accounting limits .

Explanation

Standard Employee Self-Service (ESS) is designed to allow employees to maintain their own master data that does not typically require complex payroll recalculations or organizational structural changes.

The infotypes included in option B are the core "Self-Service" pillars:

IT0002 (Personal Data): Updating names or marital status.
IT0006 (Address): Changing permanent or emergency contact addresses.
IT0009 (Bank Details): Managing direct deposit information for payroll.
IT0021 (Family Members): Adding dependents for benefits or tax purposes.

Why the Other Options are Incorrect

The presence of "Control" infotypes makes the other options incorrect for standard ESS:

IT0000 (Actions): Found in Option C.
This infotype triggers critical personnel actions (Hiring, Termination, Leaves). Allowing an employee to maintain this would bypass HR authorization and compromise data integrity.

IT0001 (Organizational Assignment): Found in Option D.
This links an employee to their Position, Org Unit, and Cost Center. These are managed by HR/Managers to ensure budget and structural alignment.

IT0007 (Planned Working Time): Found in Options A and C.
This defines an employee’s work schedule (Work Schedule Rule). Changing this affects payroll capacity and time evaluation, which is strictly an HR or Managerial function.

References
SAP Library: Employee Self-Service (WDA) > Service Development > International Services > Personal Information.

Explanation:

Indirect valuation in SAP HCM allows wage types to be valued automatically based on configured rules rather than manual entry. The three infotypes that can use indirect valuation are:

IT0008 (Basic Pay) – Uses indirect valuation through the Wage Type Model (LGMST) feature and valuation table V_512W_D

IT0014 (Recurring Payments/Deductions) – Uses indirect valuation via the same wage type valuation tables

IT0015 (Additional Payments) – Uses indirect valuation for one-time payments through the same mechanism

Why other options are incorrect:

B. IT2010 Employee Remuneration Info
– This infotype is used for displaying wage type information from other infotypes, not for indirect valuation configuration.

C. IT0057 Membership Fees
– This infotype handles union dues and membership fees through membership fee rules, not indirect valuation.

D. IT0083 Leave Compensation and IT0416 Quota Compensation
– These are specific compensation infotypes that do not support indirect valuation.

Reference:
SAP Note 394820 - "Indirect valuation of wage types"
SAP Training HR305 - Configuration of HR Master Data
Table V_512W_D - Indirect Valuation of Wage Types

Explanation

Infotype 0105 (Communication) is a critical technical bridge in SAP HCM that links a physical person (Personnel Number/PERNR) to various communication channels and system IDs.

B. To store employee telephone numbers and e-mail addresses:
This is the primary functional use of IT0105. By using different Subtypes, you can store various contact methods. For example, Subtype 0010 is typically used for the E-Mail address, and Subtype CELL or 0005 might be used for mobile numbers. This data is often pulled into the SAP Global Address Book or used for automated notifications.

D. To assign system user names to personnel numbers:
This is the primary technical use of IT0105, specifically Subtype 0001 (System User Name). By entering the SAP User ID (from transaction SU01) into this subtype, you create a 1:1 link between the employee's HR record and their system login. This link is mandatory for Employee Self-Service (ESS), Manager Self-Service (MSS), and Workflow routing, as it tells the system which PERNR belongs to the logged-in user.

Why the Other Options are Incorrect

A. To determine the default language:
This is handled in Infotype 0002 (Personal Data) under the "Language" field or via the user's fixed values in their System User Profile (SU01). IT0105 is used for communication addresses, not the language of the communication.

C. To activate functions in the Business Workplace:
The Business Workplace (SBWP) is a standard SAP tool available to all users with a system ID. While IT0105 helps route workflow mail to the workplace by linking the PERNR to a User ID, it does not "activate" the functions of the workplace itself. Activation is handled through basis configurations and organizational assignment.

References
Transaction Code: PA30 (Maintain Master Data) -> Infotype 0105.
Common Subtypes: 0001 (System User Name), 0010 (E-Mail), 0020 (First Telephone No).

Explanation:

An existing work schedule rule can be used as the basis for a part-time work schedule without additional configuration when the only change required is a proportional reduction of daily working hours while maintaining the same weekly work pattern. This is achieved through the part-time factor in the work schedule rule.

In option B, the employee still works Monday through Thursday (same distribution pattern), but daily hours are reduced from 10 to 6. The system can apply a part-time percentage to an existing full-time work schedule rule without creating a new rule.

Why other options are incorrect:

A. Change in distribution pattern
– Changing from Monday-Thursday + Friday to Monday-Friday requires a new work schedule rule because the work distribution across days has fundamentally changed.

C. Change in distribution pattern
– Moving from Monday-Thursday (9h) + Friday (4h) to Monday-Friday (4h) changes the pattern completely, requiring a new rule.

D. Change in distribution pattern
– Reducing from 5 days to 3 days while keeping 8-hour days changes the work pattern, requiring a new rule.

Reference:
SAP Training: Time Management (HR306)
SAP Help: Work Schedule Rules and Part-Time Factor
Table T508A - Work Schedule Rules