C-THR12-67 Sample Questions & Answers

Ad Hoc Query is the primary tool for HR analysts to create flexible reports without programming. It leverages logical databases like PNPCE, which provides built-in authorization checks and time-based data retrieval. The user can easily select the required infotypes (Addresses, Org. Assignment), choose the output fields (address data, cost center), and use the selection screen to filter by the change date of IT0006.

This statement is true. The PLOGI ORGA switch is the main integration switch between Organizational Management (OM) and Personnel Administration (PA). Setting it to 'X' or 'A' activates the integration, which ensures that when a person is assigned to a position in IT0001, data such as job, organizational unit, and cost center are defaulted from the OM position.

Dynamic Actions are designed to trigger follow-up actions automatically when an infotype is maintained. In this scenario, a dynamic action on IT0007 can be configured to trigger when the Work Schedule Rule (SCHKN) field is changed. The action can then call a routine (using the 'F' command) or directly maintain IT0008 (using the 'I' command) to update the capacity utilization and working hours fields based on the new schedule.

This is a classic use case for a dynamic action. It should be configured on the infotype that holds the condition data, which is IT0001 (Org Assignment) for the personnel area, typically saved after IT0000 in a hiring action. The dynamic action would have a check (P command) for P0001-WERKS = 'Global Mobility Personnel Area'. If true, it would execute an Insert command (I) for infotype 0016. This makes the action conditional based on organizational data.

The Counting Rule provides conditions to determine if an absence should be counted and if it should reduce a quota. You can set a condition based on 'Length of service'. By creating two sequence numbers in the counting rule, one for ' = 1 year' (with quota deduction enabled), the system can automatically handle this requirement for the same absence type.

This is the primary infotype for recording employee absences like vacation or sick leave, which are then deducted from the relevant quota.

Overtime can be compensated either by payment or by time off. If compensated by time off, the hours recorded in IT2005 can be configured to be deducted from a time-off quota.

SAP's retroactive accounting functionality automatically detects master data or time data changes that affect past, already calculated payroll periods. When the April payroll is run, the system identifies the change relevant to March, recalculates the March payroll internally, determines the difference (the overpayment), and carries this difference forward to be processed and adjusted in the current (April) payroll period.

The switch PLOGI PLOGI in group PLOGI defines the active plan version for integration. Reports like RHCHECK0 use the value of this switch to determine which plan version's OM data should be compared against the PA data in infotype 0001.

The Employee Subgroup Grouping for Personnel Calculation Rules (PCRs) allows the system to branch its logic within a PCR. The operation VWTST (Variant Where-used list TeST) can query this grouping. This enables a single PCR to perform different calculations (e.g., for hourly vs. salaried employees) by checking the employee's grouping and following the appropriate processing path, thereby increasing the reusability and flexibility of the payroll schema.

Time Constraint 1 enforces that an infotype record must exist for the entire time the employee is active, with no gaps. It also ensures that only one record can exist at any point in time. This perfectly matches the requirement for a single, continuous main bank record.