SAP Certified Associate - SAP SuccessFactors Employee Central Core (C_THR81) — Questions 76–108

A business rule on Job Information that triggers on change of 'Job Classification' can perform a lookup in the custom MDF object to retrieve the associated Pay Grade and set it on the Job Information record. This automates the update based on the defined relationship, ensuring consistency and reducing manual effort. The rule must be configured with a condition and a lookup action.

This approach correctly triggers on Job Information updates, checks the Employment Type, and calculates the date using the hire date from Employment Information. Business rules can access fields from related objects, such as Employment Information, to perform calculations. The formula function can add days to a date, ensuring the Benefits Eligibility Date is set accurately.

A child MDF object with a composite association to Employee allows multiple language skill records per employee. Enabling effective dating maintains a history of changes. This configuration exactly meets the requirements of multiple skills, detailed fields, and historical tracking.

After defining the Location object in the Corporate Data Model, you must create the actual location records. This can be done through the Manage Data tool or by using Import and Export Data to upload a CSV file. These are standard methods for populating foundation object data. Without records, the Location object cannot be used in Job Information.

Business rules with an onSave trigger can validate field values and prevent saving if conditions are not met. In this case, the rule would compare the expiry date to the issue date and raise an error if the expiry is earlier. This is the standard method for implementing cross-field validation in MDF objects in Employee Central.

In business rules, the order of field updates can affect the outcome. If the Cost Center update depends on the Location being updated first, and the rule updates Cost Center before Location is set, the rule may use the old Location value. This is a common pitfall. Ensuring that the rule evaluates the new Location before updating Cost Center is crucial.

This is correct because business rules on Job Information can read related MDF objects via associations and copy values into fields. The Job Classification Foundation Object already has a Pay Grade association, so a rule triggered on Job Classification change can populate Pay Grade on Job Information, ensuring the value is derived without manual entry.

Configure Object Definitions is the correct tool for creating and modifying MDF objects, including foundation objects. It allows administrators to define the object's fields, data types, associations, and other properties. For a company car object, you would create a new object, add fields like license plate, model, and assigned employee, and configure the appropriate associations. This is the standard and correct method for creating custom foundation objects in Employee Central.

This approach uses a business rule triggered on Legal Entity change to perform a lookup in the custom MDF object and set the Company field accordingly. Business rules can access MDF objects through associations or lookups, allowing dynamic retrieval of the mapped Company. This ensures that when Legal Entity is selected, the Company is automatically populated based on the mapping, meeting the requirement accurately.

A Generic Object with a composite association to Employee Profile allows multiple project assignment records per employee, each with its own start date, end date, and role. These records can be displayed in the profile and are reportable via MDF reporting. This is the standard pattern for repeatable employee-specific data.

Role-Based Permissions define what a role can do, and the permission role can be scoped to a dynamic group so only the recruiters matching that group's criteria gain read access to Compensation Information. This meets the requirement without business rules, because the group membership automatically determines which employees each recruiter can view.

The 'Add New Employee' wizard starts by prompting for the hire date and event reason (e.g., 'New Hire'). Then it guides you through entering the employee's biographical data (name, date of birth, etc.), followed by job information (position, department, manager), and compensation details. Finally, you review and submit the record.

OnChange triggers when a specified field changes, allowing the rule to set another field's value dynamically. Here, when Company or Business Unit changes, the rule can set Employee Class. This meets the requirement to automatically populate based on selections. OnChange is the correct trigger for dependent defaulting.

Setting a Foundation Object record to inactive removes it from selection lists for new entries while preserving it for existing and historical records. This satisfies the requirement that the value remains valid for historical reporting but cannot be chosen for new hires. Inactivation is the standard lifecycle mechanism for Foundation Object records in Employee Central.

A Picklist field type allows users to select from a predefined list of values that are maintained in a picklist. This ensures data consistency and restricts input to only the allowed certifications. Picklists can be configured with values and can be associated with the MDF object. This is the standard way to provide a dropdown of predefined options in MDF objects, meeting the requirement exactly.

Pay Group determines the payroll processing rules, and Currency defines the payment currency. For an employee paid in US dollars, setting the Currency to USD and assigning an appropriate Pay Group is essential for correct payroll processing. These fields are standard in Job Information and are critical for compensation. This option correctly identifies the necessary fields.

An Association field type creates a relationship to another MDF object or a standard object like Job Information. It stores a reference to the target record, allowing the 'Company Car' object to link directly to the employee's Job Information record for seamless data retrieval.

In MDF, to associate a custom object with an employee, you must include a field of type 'Employee' (or 'User') and configure it as an association. This creates a link between the MDF record and the employee, allowing the visa information to be stored per employee.

An onSave rule on Job Information executes when the record is saved. By adding a condition that evaluates the Event Reason field, the rule only proceeds when the event reason is Promotion. This satisfies the requirement to trigger only for promotions and to send the notification.

Employment Type is the correct object because it defines the legal relationship between the employee and the company, such as Employee, Contingent Worker, or Trainee. During the hire process, the Employment Type field on the Job Information block determines whether the system creates an Employee or Contingent Worker record. Configuring this object correctly ensures the proper record type is assigned.

This option correctly sets Effective Dating to 'Date Range' to meet the effective date range requirement. Adding an association field to the Employee entity links the certification records to the employee. Configuring a portlet in the Employee Profile using the MDF object is the standard way to display the records. This combination satisfies all stated requirements.

An MDF object with a composite association to the Employee object is the correct choice because it allows multiple records per employee, each with its own set of fields (language, proficiency, primary flag). MDF objects are designed for custom data tracking and support the necessary associations and validations. This approach is standard for employee skills, certifications, and similar data.

To apply a default value for Employment Type when hiring, the default must be configured on the Employment Type field in the Job Information object definition. If it is not set there, no default will be applied. This is the most common reason for defaults not working. The field configuration allows specifying a default value from the associated foundation object.

The Global Assignment object is designed to capture host-country assignments with their own dates, pay scale, and related data while the home assignment remains in Job Information. This preserves the primary record and provides a structured place for each country assignment, matching the requirement precisely.

A business rule triggered on the Job Information object when Employee Class changes can conditionally set the Bonus Plan field. This is the standard, low-maintenance approach because it centralizes the logic and automatically applies to all employees without manual intervention. It leverages the platform's rule engine and is easily adjustable if the mapping changes.

This approach correctly models the one-to-many relationship between employees and licenses using a custom MDF object with a many-to-one association to Employee. The fields for license type, issue date, and expiry date are included. A report can then filter on the expiry date to identify licenses expiring within 30 days. This is the standard, scalable way to track multiple licenses per employee and enables reporting.

A business rule on the MDF object can evaluate the Medical Plan value on save and raise an error if Dependent Coverage is empty. This enforces the conditional dependency exactly as required. MDF business rules support onSave validation, making this the appropriate configuration to ensure data integrity without over-constraining other scenarios.

Time Accounts hold the balance, and accrual rules define how and when the balance increases, including tiered rates based on service length. Configuring the accrual rule with service-based tiers and a posting schedule meets the automatic, scheduled accrual requirement for the specified country.

A separate MDF object for Project Assignment with an association to Employee allows multiple records per employee. Enabling effective dating maintains a history of assignments with start and end dates. This configuration supports multiple simultaneous assignments and historical tracking, meeting all requirements. The association links each assignment to an employee.

Business rules on MDF objects can be configured to trigger on save and perform validations. By creating a rule that checks if the expiry date is after the issue date and raises an error if not, the administrator ensures data integrity. This is a standard approach for cross-field validation within MDF objects and is fully supported in Employee Central.

To make a Foundation Object selectable in Job Information, you must create a picklist that references the Foundation Object and then associate that picklist with the appropriate field in the Job Information portlet. This is done in Picklist Management and Field Configuration. The picklist provides the list of valid values from the Foundation Object, enabling selection during employee data maintenance.

A business rule can be configured to copy the country from the Location object to the National ID portlet when the Location is changed or on save. This dynamic data propagation is a common use case for business rules in Employee Central, allowing automatic population based on related data.

Using a picklist for the certification name field ensures that users can only select from a predefined list of valid certifications. This is the standard way to enforce data consistency for a field that should have a limited set of values. The picklist can be configured with the allowed certification names, and the field type would be Picklist.