Explanation:

Infotype 0007 (Planned Working Time) stores time management control data for employees. The two correct pieces of information maintained here are:

A. Assignment of public holiday calendar
– This is correct. In IT0007, you assign a public holiday calendar (field HKTID) to determine which holidays apply to the employee and how they are treated for time evaluation and pay.

D. Work schedule rule
– This is correct. The work schedule rule (field SCHKZ) is the most critical field in IT0007. It defines the employee's planned working hours, including daily work schedules, break rules, and rotation patterns.

Why the other options are incorrect:

B. Dynamic assignment based on clock-in entries
– This is incorrect. Dynamic work schedules based on actual clock-in times are handled through time recording configurations (e.g., CATS, PCRs) and dynamic daily work schedule determination in time evaluation, not maintained in IT0007.

C. Status of employee participation in time evaluation
– This is incorrect. The time evaluation status (whether an employee is included in time evaluation runs) is maintained in Infotype 0208 (Time Management Status), not in IT0007.

Reference:
SAP Training THR12 (Management Administration 2)
SAP Online Help: Infotype Planned Working Time (0007)
SAP Table T508A (Work Schedule Rules) and T5495 (Public Holiday Calendar)

Explanation:

In SAP HCM, a Feature is a decision tree used to determine default values. For a feature to function, it must know which data fields it is allowed to evaluate (e.g., Company Code, Employee Subgroup, or Personnel Area). These allowable fields are defined in the PME (Personnel Management Entity) Structure associated with that feature.

When you are in transaction PE03, clicking on the Structure button reveals the technical dictionary (such as PME01 for feature PINCH) that lists every field available for use as a decision node. If a field is not in this structure, it cannot be used in the logic.

Why the Other Options are Incorrect

A. In the Documentation:
This is a text-based help file. While it describes the feature’s purpose, it is not a technical source for the data fields used in the decision-making process.

B. In the Country Assignment:
This attribute only defines which MOLGA (Country Grouping) the feature applies to. It limits the scope of the feature but does not provide the fields used for its logic.

C. In the Administrative Data:
This section contains the "audit trail," such as the name of the person who last changed the feature and the date of the change. It contains no technical data regarding field selection.

References

Transaction Code: PE03 (Maintain Feature) -> Attributes Tab -> Structure Field. SAP Tables: T549B (Features) and T549D (Fields for Features).

Explanation:

The Relationship infotype (1001) in Organizational Management determines the life cycle relationship period that an organizational unit can have with all other infotypes. This infotype stores the relationships between organizational objects (such as organizational units, positions, jobs, and persons) and defines the time frame during which these relationships are valid.

Why other options are incorrect:

A. Vacancy infotype
– This is incorrect. The Vacancy infotype (1005) is used specifically to mark positions as vacant or occupied. It does not control relationship life cycles between organizational units and other infotypes.

C. Obsolete infotype
– This is incorrect. The Obsolete infotype (1007) is used to flag organizational objects as obsolete or archived. It does not manage relationship periods.

D. Object infotype
– This is incorrect. The Object infotype (1000) stores basic information about organizational objects (such as name and validity). While it defines the object's own validity period, it does not determine relationship periods with other infotypes.

Reference:
SAP Training HR505 (Organizational Management)
SAP Online Help: Infotype 1001 (Relationships) SAP Documentation: Organizational Management - Relationship Infotype

Explanation

In SAP Organizational Management (OM), relationships are reciprocal. To ensure the system maintains data integrity between a custom object (e.g., Object Z1) and a standard SAP object (e.g., Position 'S' or Org Unit 'O'), you must perform specific configuration steps in the Implementation Guide (IMG).

B. Configure both the A and B relationships:
In SAP, relationships are always created in pairs. The 'A' relationship represents the "bottom-up" or passive side (e.g., "reports to"), while the 'B' relationship represents the "top-down" or active side (e.g., "is line manager of"). Even if you only intend to use one direction, SAP technical logic requires both directions to be defined in table T777V (Relationships) to maintain the link correctly.

C. Create an allowed relationship between objects:
Simply defining the relationship type (A/B) isn't enough. You must also define which Object Types are permitted to use that relationship. This is done in the "Allowed Relationships" table (T777E). For example, you must explicitly state that "Object Z1" is allowed to have relationship "A002" with "Object O." Without this step, the system will trigger an error when you try to create the record in PP01.

Why the Other Options are Incorrect

A. Configure either the A or B relationship:
SAP does not allow "one-way" relationships for standard object linking. If you define only one side, the reciprocal record will not be created, leading to inconsistent reporting and structural gaps.

D. Add your new object type to the customer specific table:
While you do define the custom object itself in a customer-specific range (typically starting with 9, Y, or Z), simply adding it to a table does not establish the logic for how it interacts with other objects. Relationships are governed by the relationship and allowed-relationship tables mentioned above.

References
Transaction Code: OOAW (Evaluation Paths) and OOV (Relationship Maintenance).
IMG Path: Personnel Management > Organizational Management > Basic Settings > Data Model Enhancement > Relationship Maintenance.

Explanation:

To assign different leave entitlements based on union groups or contracts, you must configure quota type selection rule groups. The QUOMO feature determines which quota type selection rule group applies to an employee based on organizational assignment (such as employee subgroup or personnel subarea). Once assigned, you define selection rules for these groups that specify:

Base entitlement amounts
Accrual periods
Reduction and rounding rules
Validity intervals
Absence quotas are then generated either manually via report RPTQTA00 or automatically through time evaluation.

Why other options are incorrect:

A. By creating different absence types and assigning them to employee subgroups
– Absence types (IT2001) record actual time off, not entitlements. Leave entitlements are stored as absence quotas (IT2006), which require generation rules based on quota type selection rule groups.

B. By creating a dynamic action on IT2001
– Dynamic actions trigger events based on infotype changes. They cannot configure leave entitlement rules or generate quota amounts.

C. By assigning a base entitlement rule to the Work Contract field
Base entitlement rules are assigned to quota type selection rule groups, not directly to the Work Contract field on IT0001.

Reference:
SAP Training: Time Management in SAP HCM (S4HR36/HR306)
SAP Note: QUOMO feature determines quota type selection rule group based on organizational assignment

Explanation:

In SAP Time Management, the system handles "collisions" (two time records occurring simultaneously) through a specific logic check. To prevent an employee from booking overtime while on vacation, the following must be configured:

B. The absence/attendance class:
This is a grouping mechanism (usually a value from 0-9) assigned to each Absence or Attendance type in table T554S. It acts as a "behavioral label" for the record. For example, you might assign all "Paid Vacations" to Class 01. The system uses this class to look up how it should interact with other types of time data.

C. The time constraint class:
This is the most critical element for collision logic. It is assigned to Infotypes (like IT2001 or IT2005) or specific subtypes in table T554S. The Time Constraint Class determines the "severity" of the collision.

When a collision occurs, the system checks the Collision Check table (T554Y). This table uses the Time Constraint Class of the new record against the Absence/Attendance Class of the existing record to decide the outcome (e.g., give an error, a warning, or split the record).

Why the Other Options are Incorrect

A. The reaction indicator:
This is the result of the configuration (e.g., 'E' for Error, 'W' for Warning), but it is not a standalone "element" you configure to define the logic; it is a value defined within the Collision Check table mentioned above.

D. The collision class:
This is often confused with the "Time Constraint Class." While "collision" describes the event, "Collision Class" is not the standard technical term used in the T554Y configuration table.

E. The availability indicator:
This is used primarily in Manual Check or specific On-Call/Availability (IT2004) scenarios to indicate if an employee is reachable, but it does not govern the hard logic of blocking overlapping absences and overtime.

References
IMG Path: Personnel Time Management > Time Data Recording and Administration > Absences > Absence Catalog > Determine Entry Screens and Time Constraint Classes.

Explanation:

In SAP HCM Payroll, you can valuate certain absences as if the employee had worked. This is achieved through valuation methods configured in the Absence Valuation view (V_T554C) and implemented in payroll schema using functions such as VALBS (Valuation of Absences) and ADDWTI (Process Absences as Worked Time).

When an absence is valuated "as if worked," the system:
Calculates the payment for the absence period using the same wage types and rates as for actual work time
Ensures the employee receives full pay during qualified absences (e.g., paid leave, public holidays)
Treats the absence time as attended time for the purpose of generating additional payments, allowances, or premiums
This functionality is particularly important for complying with labor laws and collective agreements that require certain absences to be paid at regular work rates.

Reference:
SAP Training HR400 (Payroll Configuration)
SAP Payroll Documentation: Absence Valuation

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