Courseiva

SAP Certified Associate - SAP SuccessFactors Employee Central Core (C_THR81) — Questions 1–75

108 questions total · 2pages · All types, answers revealed

Take a mock examExam hub

Page 1 of 2

Page 2
1
MCQeasy

An administrator needs to create a new foundation object to track employee job grades. The object must include fields for grade name, grade code, and a description. The administrator wants to ensure that the grade code is unique and that the object can be used in Job Information. What is the correct first step?

A.Add a new picklist to the Job Information portlet for job grades.
B.Import job grade data using the Import and Export Data tool with a new object definition.
C.Create a new MDF object via Configure Object Definitions and set the object type to 'Foundation Object'.
D.Configure a business rule to validate job grade entries in the Job Information portlet.
AnswerC

To create a new foundation object, the administrator must use Configure Object Definitions and define a new MDF object with the type 'Foundation Object'. This allows the object to be used across Employee Central, including in Job Information. It is the foundational step for creating any custom foundation object.

Why this answer

Creating a new foundation object requires using Configure Object Definitions to define an MDF object of type 'Foundation Object'. This provides the structure for fields such as grade name, grade code, and description, and makes the object available for use in Job Information and other areas. Once defined, data can be imported and business rules can be applied.

Exam trap

The trap here is thinking that a picklist or business rule can substitute for a foundation object, but they lack the necessary structure and reusability.

Full explanation →
2
MCQhard

A company uses Employee Central with Position Management. An HR administrator needs to create a new position for a senior engineer. The position must be linked to the existing job classification 'Senior Engineer' and must inherit the job classification's pay grade. However, the administrator notices that the pay grade field on the position is not automatically populated. What is the most likely reason for this issue?

A.The pay grade field on the position is not configured to be derived from the job classification.
B.The job classification must be associated with a legal entity for the pay grade to be inherited.
C.The position's pay grade field is not included in the position object's field configuration.
D.The job classification 'Senior Engineer' does not have a pay grade assigned to it.
AnswerD

If the job classification does not have a pay grade defined, the position cannot inherit it. The position's pay grade field is populated based on the job classification's pay grade. Therefore, the administrator must first ensure that the job classification has a pay grade assigned in its configuration.

Why this answer

The most likely reason is that the job classification 'Senior Engineer' does not have a pay grade assigned. In Employee Central Position Management, the position inherits the pay grade from the job classification. If the job classification lacks a pay grade, the position's pay grade field remains empty.

The administrator should first assign a pay grade to the job classification.

Exam trap

The trap here is assuming that the position's pay grade is derived from another source, such as the legal entity or the position's own configuration, rather than from the job classification.

Full explanation →
3
MCQhard

A global company uses Employee Central and needs to configure a business rule that assigns a specific 'Works Council' based on the employee's 'Location' and 'Legal Entity'. The rule must run when either Location or Legal Entity changes, and it should set the Works Council field on the Job Information record. Which approach is most appropriate?

A.Create an OnSave rule on Job Information that evaluates Location and Legal Entity
B.Create a business rule on the Location object that updates the Works Council on Job Information
C.Create two separate OnChange rules: one on Location and one on Legal Entity
D.Create an OnChange rule on Job Information with trigger fields Location and Legal Entity
AnswerD

An OnChange rule on Job Information can have multiple trigger fields. When either Location or Legal Entity changes, the rule fires and sets the Works Council field. This provides immediate update and meets the requirement of reacting to changes in both fields.

Why this answer

A single OnChange rule on Job Information with both Location and Legal Entity as trigger fields is the most appropriate. It fires whenever either field changes, setting the Works Council accordingly. This avoids redundancy and ensures immediate updates, unlike separate rules or OnSave rules that do not trigger on field changes.

Exam trap

The trap here is assuming that you need separate rules for each trigger field, or that an OnSave rule will provide the same immediate behavior.

Full explanation →
4
MCQeasy

An administrator is setting up a new MDF object to track employee language skills. The object must allow employees to specify the language, proficiency level, and whether they are a native speaker. The administrator wants to ensure that the proficiency level is selected from a predefined list of values. Which of the following should the administrator do to meet this requirement?

A.Define the proficiency field as a 'String' data type and manually enter the allowed values in the field's description.
B.Create a new picklist for proficiency levels and assign it to the 'Proficiency' field of the MDF object.
C.Create a new Foundation Object for proficiency levels and reference it as a 'Composite' field in the MDF object.
D.Use a business rule to validate the proficiency field against a list of allowed values stored in a custom MDF object.
AnswerB

MDF objects support fields of type 'Picklist' where the values are defined in a Picklist object. By creating a picklist for proficiency levels and assigning it to the field, the administrator ensures that users can only select from the predefined list. This is the standard way to enforce a predefined list of values in an MDF object.

Why this answer

In MDF, a picklist field type is designed to present a predefined list of values. By creating a picklist for proficiency levels and assigning it to the field, the administrator ensures data consistency and meets the requirement. This is the standard and most efficient method for enforcing a list of allowed values in a custom MDF object.

Exam trap

The trap here is thinking that a business rule or a string field with documented values can replace a picklist for enforcing predefined selections in an MDF object.

Full explanation →
5
MCQhard

A company uses Employee Central and needs to ensure that when an employee's 'Job Classification' changes, the 'Pay Grade' is automatically updated according to a mapping table. The mapping table is maintained in an MDF object called 'JobClassToPayGrade'. Which approach should the administrator use?

A.Configure a picklist dependency between Job Classification and Pay Grade using the Picklist Management tool.
B.Create an OnSave business rule on Employee Information that reads the Job Classification and updates Pay Grade.
C.Use a Scheduled business rule that runs nightly to synchronize Pay Grade based on Job Classification.
D.Create an OnChange business rule on Job Information that looks up the JobClassToPayGrade MDF object and assigns the corresponding Pay Grade.
AnswerD

An OnChange rule on Job Information triggered by the Job Classification field can query the MDF mapping object and set the Pay Grade field. This is the standard way to implement dependent field updates based on a lookup table, and it ensures the update occurs immediately when the triggering field changes.

Why this answer

An OnChange rule on Job Information triggered by Job Classification is the correct mechanism because it fires immediately when the field changes, can look up the MDF mapping object, and assign the corresponding Pay Grade. This ensures data consistency in real time and leverages the MDF object as a lookup source, which is a common pattern in Employee Central.

Exam trap

The trap here is assuming that picklist dependencies can set values, when they only filter available options; actual value assignment requires a business rule.

Full explanation →
6
Multi-Selectmedium

An administrator is configuring the Employee Central 'Employment Details' object. The company wants to track the employee's original hire date, which should never change, and also a 'Seniority Date' that is calculated based on the original hire date and any breaks in service. Which two configurations are required to meet these requirements? (Choose two.)

Select 2 answers
A.Configure a picklist for 'Seniority Date' with predefined values.
B.Create a business rule that calculates 'Seniority Date' based on 'Original Hire Date' and service breaks.
C.Create a custom field for 'Original Hire Date' and set it as read-only after initial entry.
D.Use the standard 'Hire Date' field and configure it as read-only.
E.Use a standard field for 'Seniority Date' and set it as a calculated field via the Data Dictionary.
AnswersB, C

A business rule is required to calculate the Seniority Date dynamically, considering the Original Hire Date and any breaks in service. This allows the system to automatically compute the date whenever relevant data changes, ensuring accuracy and reducing manual effort. The rule can incorporate complex logic for service breaks.

Why this answer

To track an immutable original hire date, a custom read-only field is needed because standard fields can change. For Seniority Date, a business rule is the correct tool to calculate it based on the original hire date and service breaks. Together, these configurations meet the requirements without relying on inappropriate mechanisms like picklists or Data Dictionary calculations.

Exam trap

The trap here is assuming standard fields like Hire Date can serve as immutable original hire date, or that picklists can handle date calculations.

Full explanation →
7
MCQeasy

An HR administrator needs to add a field to the Employment Information portlet that captures an employee's previous employer name as free text. The field must be available on the employee's record and in reporting. What is the correct approach in Employee Central?

A.Use a picklist field on Job Information and populate the picklist with common employer names.
B.Add a custom String field to the Employment Information object via Configure Object Definitions, then place it in the portlet layout.
C.Create a new Foundation Object called 'PreviousEmployer' and reference it from Employment Information.
D.Create a business rule that writes the employer name into the 'Comment' field of the employment record.
AnswerB

Employment Information is an MDF-based object, so custom fields are added through Configure Object Definitions, where you create a field of type String. After adding the field, it must be placed on the portlet layout so users can enter data. Because it is a standard object field, it is automatically available for reporting, which satisfies both requirements with a straightforward configuration.

Why this answer

Employment Information is an MDF object, so a custom free-text field is created through Configure Object Definitions as a String type and then added to the portlet layout. Once configured, the field is part of the object model and is therefore reportable. Foundation Objects, picklists, and repurposed comment fields do not provide a dedicated, reportable free-text field on the correct portlet.

Exam trap

The trap here is reaching for a Foundation Object or picklist for free-text data, when a custom String field on the MDF object is the correct and reportable choice.

Full explanation →
8
MCQmedium

An administrator is configuring the 'Employment Type' field in the Job Information portlet. The company requires that the field be mandatory for all new hires but optional for existing employees. The administrator needs to enforce this requirement without affecting existing employee records. Which of the following configurations should the administrator apply?

A.Use a business rule to validate on save that the 'Employment Type' field is populated for new hires (based on hire date) and allow it to be empty for existing employees.
B.Configure the 'Employment Type' field as required in the Job Information portlet, but create a custom MDF object to store the employment type for existing employees and leave the portlet field empty.
C.Use a business rule that triggers on hire and sets the 'Employment Type' field as required, and another rule that triggers on job information change to make it optional for existing employees.
D.Set the 'Employment Type' field as required in the Job Information portlet configuration, and then use a business rule to make it optional for existing employees based on their hire date.
AnswerA

A business rule can be configured to trigger on save of the Job Information portlet and check if the employee is a new hire (e.g., hire date is within a certain range) and if the Employment Type field is empty. If so, it can raise an error, effectively making the field mandatory for new hires while allowing existing employees to leave it empty. This meets the requirement without changing the field's required property globally.

Why this answer

To conditionally enforce a field as mandatory, a business rule can be used to validate on save. The rule can check the employee's hire date or other criteria to determine if the field must be populated. This allows the field to be required for new hires while remaining optional for existing employees, without affecting the portlet configuration for all users.

Exam trap

The trap here is assuming that setting a field as required in the portlet configuration applies only to new hires, or that a business rule can dynamically change the required property of a field in the UI.

Full explanation →
9
MCQmedium

An employee transfers from a position in the United States to a new position in Germany. The administrator must ensure that the employee's Job Information record reflects the new legal entity, pay scale, and work location, and that the change is effective on the transfer date. Which action should the administrator take?

A.Edit the existing Job Information record directly and change the legal entity, pay scale, and work location fields to the new values.
B.Create a new Employment Info record with the new legal entity and work location, and set the original record's end date to the day before the transfer.
C.Use the 'Transfer' action in the Take Action menu on the Job Information portlet to create a new record with the new legal entity, pay scale, and work location, effective on the transfer date.
D.Create a new Job Information record using the 'Add New Employee' function, and then terminate the original record.
AnswerC

The Transfer action creates a new Job Information record with the updated legal entity, pay scale, and work location while maintaining the employee's continuous history. It automatically sets the effective date and ends the previous record appropriately, ensuring accurate reporting and compliance.

Why this answer

The Transfer action is the standard method to move an employee to a new position, legal entity, or location while preserving their employment history. It creates a new effective-dated Job Information record with the updated data and automatically ends the previous record. This ensures accurate historical reporting and seamless integration with payroll and benefits.

Exam trap

The trap here is thinking that editing the existing Job Information record is acceptable, but Employee Central requires effective-dated records to maintain a complete audit trail.

Full explanation →
10
MCQhard

A consultant is configuring the Employee Central 'Job Information' portlet. The company requires that when an employee's 'Employee Class' is set to 'Executive', the 'Bonus Plan' field becomes mandatory. The consultant decides to use a business rule on the Job Information object. Which trigger event should the business rule use to enforce this requirement?

A.OnChange
B.OnSave
C.OnPostSave
D.OnInit
AnswerA

The OnChange event triggers when a specified field changes, such as 'Employee Class'. This allows the business rule to immediately set the 'Bonus Plan' field as mandatory when 'Employee Class' becomes 'Executive'. This dynamic behavior ensures the user is prompted to fill the field before saving, which is exactly what the scenario requires.

Why this answer

To conditionally make a field mandatory based on another field's value, the business rule should trigger on the change of the controlling field. The OnChange event on the 'Employee Class' field allows the rule to set the 'Bonus Plan' field as required immediately, ensuring the user cannot save without providing the bonus plan when the employee class is executive.

Exam trap

The trap here is assuming that OnSave is the correct event for all validations; however, conditional mandatory fields require OnChange to react dynamically as the user edits the record.

Full explanation →
11
MCQhard

A company has a business rule that triggers on the Job Information object when the Event Reason is 'Promotion'. The rule must update the employee's Pay Grade based on the new Job Classification. However, the rule is not firing when a promotion is processed via the 'Promote' action. What is the most likely cause?

A.The rule's trigger condition is set to fire only on the 'Save' event, but the 'Promote' action uses a different event or the rule is not associated with the correct event reason.
B.The Pay Grade field is not enabled for business rule updates in the Employee Central configuration.
C.The business rule requires a scheduled job to run after the promotion is saved, but no job has been scheduled.
D.The business rule is configured on the wrong object; it should be on the Employment Info object.
AnswerA

Business rules on Job Information can be triggered on save or on specific actions. The 'Promote' action may use a different trigger event or require the rule to be explicitly associated with the promotion event reason. If the rule is not configured to fire on that action or event reason, it will not execute.

Why this answer

Business rules in Employee Central can be triggered by specific actions or events. The 'Promote' action may not automatically trigger a rule configured only for the 'Save' event. The rule must be associated with the correct event reason or action, and the trigger condition must include that action.

This ensures the rule fires when the promotion is processed.

Exam trap

The trap here is assuming that any save on Job Information triggers all business rules, but rules can be scoped to specific actions or event reasons.

Full explanation →
12
MCQhard

An administrator is configuring the MDF object 'Job Classification' and needs to ensure that when a new record is created, the 'Job Family' field is automatically populated based on the selected 'Job Function'. The 'Job Function' field is a picklist, and the mapping between Job Function and Job Family is maintained in a separate MDF object called 'Job Function Mapping'. Which configuration should the administrator implement?

A.Use a Propagation rule on the Job Function field to copy the value to Job Family.
B.Configure a picklist dependency between Job Function and Job Family using the Picklist Center.
C.Create an onSave business rule on Job Classification that reads the selected Job Function and looks up the corresponding Job Family in the Job Function Mapping object, then sets the Job Family field.
D.Set up a default value on the Job Family field using a 'Rule' as the source, referencing the Job Function field directly.
AnswerC

An onSave rule can access the Job Function value, query the Job Function Mapping object using a lookup, and assign the returned Job Family to the field. This is the standard pattern for cross-object dependent picklist behavior in MDF, and it runs at the right moment to persist the value.

Why this answer

Cross-object dependent picklist behavior in MDF requires a business rule that performs a lookup into the mapping object. An onSave rule can read the selected Job Function, query the Job Function Mapping object, and write the corresponding Job Family. Other mechanisms such as picklist dependencies, propagation, or default values lack the ability to query another object, so they cannot resolve the mapping.

Exam trap

The trap here is assuming that standard picklist dependencies or default values can span separate MDF objects, when only a business rule with a lookup can resolve cross-object mappings.

Full explanation →
13
MCQhard

A consultant is configuring the 'Job Information' portlet in Employee Central. The company requires that when an employee's 'Job Classification' is set to 'Manager', the 'Manager' field must be populated with a valid employee ID. The consultant needs to ensure that the system prevents saving the record if the 'Manager' field is empty. Which configuration should the consultant use to meet this requirement?

A.Create a workflow rule that sends a notification to the HR administrator if the Manager field is empty for a Manager.
B.Create a business rule on the Job Information object that triggers on save and checks if Job Classification is 'Manager' and Manager is empty, then throws an error.
C.Configure the 'Manager' field as a required field in the Job Information portlet configuration.
D.Set up a picklist dependency so that the Manager field becomes mandatory when Job Classification is 'Manager'.
AnswerB

A business rule on the Job Information object can evaluate the Job Classification field and conditionally require the Manager field. By triggering on save and raising an error if the condition is not met, the rule prevents saving the record. This is the standard approach for conditional mandatory fields in Employee Central, as it allows dynamic validation based on other field values.

Why this answer

A business rule on the Job Information object can dynamically enforce conditional mandatory fields. By evaluating the Job Classification and checking the Manager field, the rule can raise an error on save if the condition is violated. This ensures data integrity without making the Manager field universally required, which would be inappropriate for employees who do not have managers.

Exam trap

The trap here is confusing conditional mandatory validation with static required fields or workflow notifications, which do not prevent saving invalid data.

Full explanation →
14
Multi-Selectmedium

An administrator is configuring the Employee Central Foundation Object 'Business Unit' and needs to ensure that the 'Parent Business Unit' field only allows selection of business units that are not already children of the current business unit. The administrator plans to use a business rule to validate this. Which two trigger types can be used to enforce this validation? (Choose two.)

Select 2 answers
A.OnDelete
B.OnChange
C.OnPostSave
D.OnSave
E.OnInit
AnswersB, D

OnChange triggers when the Parent Business Unit field value changes. It can immediately validate the selection and display an error, preventing the user from saving an invalid hierarchy. This provides real-time feedback and is appropriate for field-level validation.

Why this answer

Both OnSave and OnChange can be used to validate the Parent Business Unit field. OnSave ensures validation at save time, while OnChange provides immediate feedback when the field is modified. Using either or both can enforce the rule, but they serve different purposes in the user experience.

Exam trap

The trap here is assuming that only OnSave is needed for validation, but OnChange can also validate and provide immediate feedback.

Full explanation →
15
MCQmedium

An administrator is configuring a new custom field on the Job Information block that must derive its valid options dynamically based on the company code selected in the preceding field. Which tool and configuration path must the administrator utilize to achieve this dependency?

A.Configure business rules using the 'Set' rule type to alter the field visibility dynamically.
B.Define parent-child picklist associations in Picklist Center and reference them in data model field definitions.
C.Utilize Dynamic Forms for Employee Central to write a direct SQL query joining the two picklist tables.
D.Create a generic object with a custom MDF association and link it via Configure Object Definitions.
AnswerB

Establishing parent-child relationships directly within the Picklist Center links the dependent picklist to the controlling picklist. Referencing these associations in the data model ensures the user interface dynamically restricts choices based on the parent field selection.

Why this answer

Configuring cascading picklists requires defining the parent-child relationship in the Picklist Center and subsequently mapping the fields in Succession Data Model or Corporate Data Model. This ensures data integrity by filtering dropdown values based on prior selections, which is critical for compliance and reporting accuracy across global subsidiaries.

Exam trap

Candidates often confuse cascading picklist dependencies with standard business rules, selecting rule configuration paths instead of defining parent-child picklist associations in the Picklist Center and updating the data model.

Full explanation →
16
Multi-Selectmedium

An administrator is configuring the 'Job Information' portlet in Employee Central. The organization requires that when an employee's 'Employee Class' is changed to 'Executive', the 'Pay Grade' field must be automatically set to a specific value based on the executive level. The administrator plans to use a business rule to achieve this. Which two actions must the administrator perform to ensure the business rule correctly sets the Pay Grade? (Choose two.)

Select 2 answers
A.Create a workflow that routes the Pay Grade change for approval.
B.Configure the 'Pay Grade' field as a read-only field in the Job Information configuration.
C.Add a 'Valid When' condition to the Pay Grade field to ensure it matches the Employee Class.
D.Create a business rule on the Job Information object that triggers on the 'Employee Class' field change.
E.Use a 'Set' rule action to assign the appropriate Pay Grade based on the Employee Class value.
AnswersD, E

The business rule must be associated with the Job Information object and configured to trigger when the 'Employee Class' field is changed. This ensures that the rule evaluates and sets the Pay Grade whenever the employee class is updated to 'Executive' or any other value.

Why this answer

The administrator must create a business rule on the Job Information object that triggers on the 'Employee Class' field change and includes a 'Set' action to assign the Pay Grade. These two actions ensure that when the Employee Class is updated, the rule evaluates and automatically populates the Pay Grade field with the correct value.

Exam trap

The trap here is confusing validation with automation; 'Valid When' conditions validate data, while 'Set' actions populate data. The requirement is to set the value automatically.

Full explanation →
17
MCQhard

A company has configured a business rule on the 'Job Information' object that triggers on the 'onSave' event to validate that the 'Employment Type' field is not empty. During testing, the rule works for regular employees but fails to trigger for employees on a leave of absence. What is the most likely reason for this behavior?

A.The 'onSave' event does not trigger for employees with a leave of absence status because the record is not saved.
B.The rule is scoped to exclude employees with a leave of absence status.
C.The 'Employment Type' field is not available on the Job Information portlet when an employee is on leave.
D.The rule's trigger condition checks for a specific employment status that is not present for employees on leave.
AnswerD

If the rule includes a condition that checks for a specific employment status (e.g., 'Active') and employees on leave have a different status (e.g., 'Leave'), the condition evaluates to false, and the rule does not execute its validation. This is a common oversight: the rule may be triggered onSave, but its internal condition restricts it to certain statuses. To fix this, the condition should be adjusted to include leave statuses or removed if the validation should apply universally.

Why this answer

The rule fails for employees on leave because its trigger condition likely includes a check for a specific employment status that does not match the leave status. Even though the onSave event fires, the condition evaluates to false, preventing the validation from running. To resolve this, the administrator should review the rule's condition and ensure it applies to all relevant employment statuses or remove the status check if the validation is required for all employees.

Exam trap

The trap here is assuming that an onSave rule always executes its actions, when in fact a conditional trigger can prevent execution if the condition is not met.

Full explanation →
18
MCQhard

A consultant is designing a business rule to calculate an employee's bonus eligibility based on their hire date and employment type. The rule must trigger when either the hire date or employment type changes in Job Information. Which rule scenario and trigger should be used to ensure the rule evaluates both fields?

A.OnInit rule on Job Information
B.OnPostSave rule on Job Information
C.OnChange rule on Job Information with trigger fields Hire Date and Employment Type
D.OnSave rule on Job Information
AnswerC

An OnChange rule on Job Information can be configured with multiple trigger fields. When either Hire Date or Employment Type changes, the rule fires and recalculates bonus eligibility. This ensures both fields are monitored and the rule executes appropriately.

Why this answer

An OnChange rule on Job Information with both Hire Date and Employment Type as trigger fields ensures the rule fires whenever either field is modified. This allows immediate recalculation of bonus eligibility, providing dynamic behavior as required. Other rule types either do not trigger on field changes or run at inappropriate times.

Exam trap

The trap here is assuming that an OnSave rule will suffice because it ultimately saves the changes, but it does not provide the immediate evaluation upon field change that the scenario implies.

Full explanation →
19
MCQmedium

An Employee Central administrator at a multinational company needs to set up a new association between the 'Job Information' portlet and the 'Position' MDF object so that when a position is selected, the corresponding 'Cost Center' from the position record is automatically populated into Job Information. The administrator creates a rule on the Job Information object that triggers on save and uses the 'Position' field to look up the 'Cost Center' from the Position object. However, during testing, the Cost Center is not populated. What is the most likely cause?

A.The 'Position' field in Job Information is not configured as an association to the Position MDF object.
B.The 'Cost Center' field in the Position object is not set as a required field.
C.The rule must be configured as an onChange rule instead of onSave to populate the field.
D.The rule needs to use the 'Position' field as a source and then a 'Lookup' function to retrieve Cost Center.
AnswerA

For a rule to look up a value from the Position object using the Position field, that field must be defined as an association (e.g., 'Position' association) pointing to the Position MDF object. If it is a simple text or picklist field, the rule cannot traverse to the related object. Thus, the Cost Center cannot be retrieved, causing the failure. This is the most likely cause.

Why this answer

For a business rule to retrieve data from a related MDF object via a field on Job Information, that field must be defined as an association to that object. Without the association, the rule cannot navigate to the Position record to read Cost Center. Thus, the absence of the association on the Position field is the fundamental issue preventing the automatic population.

Exam trap

The trap here is assuming that any field can be used to look up values from another object, when in fact the field must be configured as an association to enable that navigation.

Full explanation →
20
MCQmedium

A SuccessFactors administrator needs to configure the 'Job Information' portlet so that when an employee's 'Employee Class' is changed to 'Executive', the 'Bonus Plan' field becomes mandatory. Which tool should the administrator use to achieve this?

A.Use a workflow to require approval if Employee Class is 'Executive' and Bonus Plan is empty.
B.Configure a business rule on Job Information that triggers on change of Employee Class and sets the Bonus Plan field as required.
C.Create a custom MDF object to track executive bonus plans and associate it with Job Information.
D.Set the Bonus Plan field as required in the Job Information object definition.
AnswerB

Business rules can be configured to trigger on field changes and dynamically set other fields as required. This is the standard way to enforce conditional mandatory fields in Employee Central. The rule would evaluate the Employee Class value and, if 'Executive', mark Bonus Plan as required, preventing save without a value.

Why this answer

A business rule on Job Information can dynamically set the Bonus Plan field as required when Employee Class is 'Executive'. This is the correct way to enforce conditional mandatory fields. The rule triggers on change and ensures data completeness for executives without affecting other employees.

Exam trap

The trap here is using a workflow or making the field always required; conditional mandatory fields require a business rule.

Full explanation →
21
MCQeasy

An HR administrator needs to ensure that when an employee's date of birth is entered in Employee Central, it is automatically validated to be at least 18 years before the current date. Which feature should the administrator use?

A.Workflow that requires manager approval if the employee is under 18.
B.Business rule with a date validation on the Date of Birth field in the Personal Information portlet.
C.Custom MDF object to store birth dates and a scheduled job to validate age daily.
D.Field-level picklist restriction on the Date of Birth field to only allow dates before a certain year.
AnswerB

Business rules can be configured to validate the Date of Birth field against the current date, ensuring the employee is at least 18 years old. The rule can trigger on save and display an error if the condition is not met. This is the standard approach for field-level validation in Employee Central.

Why this answer

A business rule on the Date of Birth field is the correct way to enforce age validation. It can dynamically compare the entered date to the current date and block saving if the employee is under 18. This ensures data accuracy at the point of entry without additional workflows or objects.

Exam trap

The trap here is confusing validation with approval; workflows do not enforce data constraints, only business rules do.

Full explanation →
22
MCQhard

An administrator needs to create a business rule that calculates an employee's 'Service Date' based on the 'Original Hire Date' and the 'Employment Type'. The rule must run when the employee record is saved and must write the result to the 'Service Date' field on the Employment Information object. Which rule configuration is required?

A.An onChange rule on the Original Hire Date field that calculates Service Date and writes it to the Employment Information object.
B.An onInit rule on the Employment Information object that calculates Service Date when the record is loaded.
C.An onSave rule on the Employment Information object with a condition based on Original Hire Date and Employment Type, and an assignment to the Service Date field.
D.An onSave rule on the Job Information object that calculates Service Date and writes it to the Employment Information object.
AnswerC

An onSave rule on Employment Information can evaluate the Original Hire Date and Employment Type, then assign the calculated result to the Service Date field. This is the correct object and scenario for writing calculated values on save, meeting the requirement precisely.

Why this answer

To calculate and persist a value on save, the rule must be an onSave rule on the object containing the target field. Employment Information holds the Service Date field, so the rule belongs there, with conditions using Original Hire Date and Employment Type and an assignment to Service Date. This ensures the value is written whenever the record is saved.

Exam trap

The trap here is placing the rule on the wrong object or using onChange/onInit, when writing to a field requires an onSave rule on the object that owns the target field.

Full explanation →
23
MCQmedium

An administrator is configuring the 'Job Information' portlet and needs to ensure that the 'Employee Class' field is required for all employees except those with the 'Employment Type' of 'Intern'. Which configuration should the administrator use to achieve this?

A.Set the 'Employee Class' field as required in the Job Information portlet configuration, and then create a business rule to make it optional when Employment Type is 'Intern'.
B.Configure a picklist for Employee Class that excludes 'Intern' and set the field as required.
C.Create a workflow rule that checks if Employee Class is populated for non-interns and routes the record for correction if not.
D.Use a business rule on the 'Job Information' object that triggers on save and validates that Employee Class is populated unless Employment Type is 'Intern'.
AnswerD

A business rule can enforce conditional requiredness by checking if Employee Class is empty and Employment Type is not 'Intern'. If the condition is met, the rule raises an error, preventing save. This allows interns to bypass the requirement while enforcing it for others.

Why this answer

To conditionally require Employee Class, a business rule on Job Information is needed. The rule can check if Employee Class is empty and Employment Type is not 'Intern', then throw an error. This enforces the requirement only for non-interns, allowing interns to save without the field.

It is a standard use of business rules for dynamic validation.

Exam trap

The trap here is assuming that portlet-level required settings can be conditionally overridden by business rules, when in fact conditional requiredness must be implemented entirely through business rules.

Full explanation →
24
Multi-Selectmedium

An administrator is configuring the 'Job Information' portlet in Employee Central. The organization wants to ensure that when an employee's 'Employment Type' is changed to 'Part-Time', the system automatically adjusts the 'Standard Weekly Hours' field to a value of 20, and also requires that the 'Full-Time Equivalent' (FTE) field is recalculated based on the new hours. The administrator plans to use a business rule triggered on the change of 'Employment Type'. Which two actions must the rule perform to meet these requirements? (Choose two.)

Select 2 answers
A.Configure a workflow to send an email to the HR administrator to update the FTE field.
B.Trigger a recalculation of the 'Full-Time Equivalent' field using a Set operation with a formula.
C.Set the 'Employment Type' field to 'Part-Time' again to trigger the rule recursively.
D.Use a 'Raise Error' operation to force the user to manually update the FTE field.
E.Set the 'Standard Weekly Hours' field to 20 using a Set operation.
AnswersB, E

The 'Full-Time Equivalent' field must be recalculated based on the new hours. A Set operation can assign a calculated value, such as dividing the new hours by the full-time hours (e.g., 40). This ensures the FTE reflects the change. It is a necessary action to meet the requirement.

Why this answer

To meet the requirements, the rule must set the 'Standard Weekly Hours' to 20 and recalculate the 'Full-Time Equivalent' based on the new hours. Both actions are performed using Set operations: one to assign the fixed value, and another to calculate the FTE. These ensure the fields are updated automatically upon the change of 'Employment Type'.

Exam trap

The trap here is thinking that a workflow or error message is needed for automatic updates, when in fact business rules can directly set field values.

Full explanation →
25
MCQhard

A consultant is configuring a business rule on the Job Information portlet that must trigger only when the 'Employee Status' field changes from 'Active' to 'Terminated'. The rule should also consider that the change might occur due to a termination event or a manual edit. Which rule scenario and trigger condition should be used to ensure the rule fires only when the status changes to 'Terminated'?

A.Use the 'OnInit' rule scenario with a condition that checks if Employee Status equals 'Terminated'.
B.Use the 'OnChange' rule scenario with a condition that checks if the previous value of Employee Status was 'Active' and the new value is 'Terminated'.
C.Use the 'OnSave' rule scenario with a condition that checks if Employee Status equals 'Terminated'.
D.Use the 'OnSave' rule scenario with a condition that checks if the previous value of Employee Status was 'Active' and the new value is 'Terminated'.
AnswerB

The OnChange rule scenario is designed to fire when a specific field's value changes. By checking that the previous value was 'Active' and the new value is 'Terminated', the rule triggers only on that exact transition. This works whether the change comes from a termination event or a manual edit, because the rule evaluates the field change regardless of the source. This is the precise way to detect a status transition.

Why this answer

The OnChange rule scenario is specifically designed to trigger when a field value changes. By comparing the previous value and the new value of Employee Status, the rule can detect the exact transition from 'Active' to 'Terminated'. This ensures the rule fires only when that change occurs, regardless of whether it is from a termination event or manual edit, and avoids triggering on unrelated saves.

Exam trap

The trap here is assuming that an OnSave rule with a condition on the new value is sufficient, but it would fire even when the status was already 'Terminated' and another field changes.

Full explanation →
26
MCQmedium

An HR administrator needs to grant a specific group of users the ability to view and edit the 'Job Information' portlet for employees in their department, but not for employees in other departments. Which Employee Central security mechanism should be used to achieve this?

A.Create a new Permission Group for the department and add the users to it.
B.Assign the users to a Permission Role with Job Information edit permission and a target population limited to their department.
C.Grant the users the 'Administrator' permission role and rely on their department assignment.
D.Configure a business rule that blocks edits to Job Information for employees outside the department.
AnswerB

Permission Roles in Employee Central combine functional permissions with a target population. By granting Job Information edit permission and scoping the target population to the users' department, the administrator ensures they can only act on employees within that department. This is the standard way to implement department-based access control in Employee Central.

Why this answer

Department-scoped editing access is achieved by pairing functional permissions with a target population. A Permission Role that grants Job Information edit rights and limits the target population to the relevant department ensures users can only act on employees in that department. Permission Groups, broad administrator roles, and business rules do not provide this scoped access control.

Exam trap

The trap here is assuming that adding users to a Permission Group or relying on department assignment automatically limits access, when the restriction must come from the role's target population.

Full explanation →
27
MCQmedium

An Employee Central administrator is configuring the 'Job Information' portlet. The company requires that when an employee's 'Employee Class' is set to 'Regular', the 'Standard Weekly Hours' field must be populated and cannot be left blank. The administrator creates a business rule on the Job Information object to validate this. Which trigger type should be used for this business rule?

A.OnPostSave
B.OnInit
C.OnChange
D.OnSave
AnswerD

The OnSave trigger fires when the user saves the Job Information record, allowing validation of required fields based on other field values. It can block the save if validation fails, ensuring data integrity. This is appropriate for enforcing conditional mandatory fields during data entry.

Why this answer

To enforce conditional mandatory fields during save, the business rule must trigger on save so that it can validate and block the save if necessary. OnSave is the correct trigger for validation logic that must run before the data is committed. Other triggers either run at different times or are used for different purposes.

Exam trap

The trap here is assuming that OnChange is sufficient because the field value changes, but OnChange does not block save and is used for dynamic UI behavior.

Full explanation →
28
Multi-Selecthard

An administrator is configuring the Employee Central 'Job Information' portlet for a company that uses multiple employment types (e.g., Regular, Temporary, Intern). The company needs to ensure that when an employee's Employment Type is changed to 'Temporary', the system automatically sets the 'Probation End Date' to exactly 90 days from the start date, and also requires that the 'Contract End Date' be entered. Which two configuration steps are required to meet these requirements? (Choose two.)

Select 2 answers
A.Configure a Business Rule on the Job Information object that triggers on the 'onSave' event and validates that the Contract End Date is not empty when Employment Type is 'Temporary'.
B.Configure a Business Rule on the Job Information object that triggers on the 'onInit' event to set the Probation End Date when the record is loaded.
C.Create a Propagation rule on the Job Information object to copy the Employment Type value to the Probation End Date field.
D.Use a Picklist Center configuration to make the Contract End Date field mandatory when Employment Type is 'Temporary'.
E.Create a Business Rule on the Job Information object that triggers on the 'onChange' event of the Employment Type field and sets the Probation End Date using the 'addDays' function.
AnswersA, E

To enforce that Contract End Date is entered when Employment Type is Temporary, a validation Business Rule on the onSave event is needed. This rule checks if Employment Type equals Temporary and if Contract End Date is empty, then raises an error. This prevents saving the record without the required contract end date, ensuring data completeness.

Why this answer

The requirements are twofold: automatically calculate Probation End Date when Employment Type changes to Temporary, and enforce that Contract End Date is entered. A Business Rule on the onChange event of Employment Type can set the Probation End Date using date arithmetic. A separate validation Business Rule on the onSave event can check for Contract End Date when Employment Type is Temporary.

These two rules together satisfy both conditions.

Exam trap

The trap here is confusing Propagation rules with Business Rules for date calculations and conditional validation, when Propagation only copies values and cannot perform calculations or enforce mandatory fields.

Full explanation →
29
MCQeasy

A new HR administrator needs to add a custom field to the Employment Information portlet to capture an employee's prior years of service. The field should be available for data entry and reporting. Which action should the administrator take first?

A.Create a new MDF object named 'Prior Service' and associate it with the Employment Information portlet.
B.Create a business rule that writes the prior years of service into an existing unused field on the Employment Information portlet.
C.Add the field to the Employment Information object via Configure Object Definitions, then add it to the portlet layout and permissions.
D.Use the Import and Export Data tool to upload a CSV that defines the new field on the Employment Information portlet.
AnswerC

Custom fields on standard portlets are added by extending the underlying object through Configure Object Definitions, then exposing the field on the portlet layout and granting permissions via RBP. This is the standard, supported method for capturing and reporting on a new Employment Information field.

Why this answer

To capture a new attribute on Employment Information, the administrator extends the Employment Information object in Configure Object Definitions, adds the field to the portlet layout, and configures role-based permission so the field is visible and editable. This is the standard configuration path and ensures the field is available for data entry and reporting.

Exam trap

The trap here is assuming a new MDF object or a data import is needed to add a field, when the correct first step is extending the existing object definition.

Full explanation →
30
MCQeasy

A company uses SAP SuccessFactors Employee Central. The HR team needs to track the number of vacation days an employee has accrued and allow managers to adjust this balance. The data must be visible on the employee's profile and must support reporting. Which object type should the administrator use to store this information?

A.A Picklist, because it allows the administrator to define a list of vacation day values that can be assigned to employees.
B.A Business Rule, because it can calculate and store the vacation balance directly on the employee record.
C.A Foundation Object, because it is a standard SAP-delivered object that can be extended with custom fields.
D.An MDF (Metadata Framework) object, because it supports custom fields, associations to Employee, and can be reported on.
AnswerD

MDF objects are custom objects that can be created to store employee-specific data. They support fields, associations to the Employee object, and are reportable. This makes them ideal for tracking vacation balances per employee, with the ability for managers to adjust values and for reporting.

Why this answer

An MDF object is the correct choice because it allows the creation of custom fields, including numeric fields for vacation days, and supports associations to the Employee object. This enables per-employee storage, manager adjustments, and reporting. Foundation Objects are for predefined corporate structures, picklists for value lists, and business rules for logic, not storage.

Exam trap

The trap here is confusing the role of business rules or picklists with data storage, when only an MDF object can persist employee-specific custom data with associations and reporting support.

Full explanation →
31
MCQmedium

A SuccessFactors administrator is defining a new MDF object called 'CompanyVehicle' to track the vehicles assigned to employees. Each vehicle must be linked to exactly one employee, and an employee may be assigned several vehicles over time. The administrator wants the association field on the CompanyVehicle object to reference the Employee object. Which association type must be configured on the CompanyVehicle object to meet this requirement?

A.Many-to-One association from CompanyVehicle to Employee
B.Composite association
C.Valid When association
D.One-to-Many association from CompanyVehicle to Employee
AnswerA

A many-to-one association defined on CompanyVehicle pointing to Employee allows many vehicle records to reference the same employee while each vehicle record references only one employee, exactly matching the stated cardinality. This is the standard way in MDF to model a lookup to a parent object such as Employee from a child object like CompanyVehicle.

Why this answer

The requirement is that each vehicle record points to exactly one employee, while an employee can be referenced by many vehicle records. In MDF, that cardinality is modelled with a many-to-one association placed on the child object (CompanyVehicle) and pointing to the parent object (Employee). The other association types either reverse the ownership, filter values without storing a link, or impose the wrong cardinality.

Exam trap

The trap here is confusing the direction of the association and assuming that a one-to-many association should be created on the object that has many records, when the many-to-one association belongs on the child object that references the single parent.

Full explanation →
32
Multi-Selecthard

A SuccessFactors administrator is configuring the 'Job Information' portlet and needs to ensure that when an employee's 'Job Title' changes, the system automatically updates the 'Job Code' based on a predefined mapping. The mapping is maintained in an MDF object called 'JobTitleMapping' with fields 'JobTitle' and 'JobCode'. Which two steps must the administrator perform to achieve this? (Choose two.)

Select 2 answers
A.Create a business rule on the Job Information object that triggers on change of Job Title, looks up the JobTitleMapping object to find the corresponding Job Code, and sets the Job Code field.
B.Create a workflow that triggers when Job Title changes and routes a task to the HR administrator to manually update the Job Code.
C.Use a data import to update the Job Code field in Job Information whenever Job Title changes.
D.Configure a propagation rule to copy the Job Title from Job Information to the JobTitleMapping object to trigger the mapping.
E.Ensure that the JobTitleMapping MDF object is configured with the appropriate associations or fields so that the business rule can query it effectively.
AnswersA, E

A business rule on Job Information is necessary to detect the change in Job Title and perform the lookup in the JobTitleMapping object. The rule can use a 'Lookup' function or a 'Rule' to query the MDF object and retrieve the Job Code. Then, it sets the Job Code field on Job Information. This automates the update in real-time, ensuring data consistency. This is a core step in the solution.

Why this answer

The two required steps are to create a business rule on Job Information that triggers on Job Title change and performs a lookup in the JobTitleMapping object to set Job Code, and to ensure the JobTitleMapping MDF object is properly configured with the necessary fields for the lookup. These steps together enable automatic, real-time update of Job Code based on the mapping, fulfilling the requirement without manual intervention.

Exam trap

The trap here is considering propagation rules or workflows, which do not perform dynamic lookups or mappings, instead of a business rule with MDF lookup.

Full explanation →
33
MCQmedium

An Employee Central administrator is configuring the 'Event Reason' foundation object. The company wants to derive the event reason automatically when an employee's Job Information is updated, based on the type of change (e.g., promotion, transfer, termination). Which configuration approach should the administrator use to meet this requirement?

A.Use a workflow rule to send a notification to the HR team to manually update the event reason after the job change.
B.Set up a scheduled job that runs nightly to update event reasons based on the latest job information changes.
C.Configure the Event Reason object with a picklist that filters values based on the employee's country.
D.Create a business rule on the Job Information object that sets the event reason based on the change type, and associate it with the 'onSave' event.
AnswerD

A business rule on Job Information triggered on save can evaluate the changed fields and assign the appropriate event reason. This is the standard way to derive event reasons dynamically during job data changes, ensuring accuracy and reducing manual selection. It leverages the rule engine's ability to inspect previous and current values.

Why this answer

The correct approach is to use a business rule on the Job Information object that triggers on save. This allows the system to evaluate the changed fields and automatically set the appropriate event reason. It ensures real-time, accurate derivation without manual intervention, meeting the requirement for automatic determination based on the type of change.

Exam trap

The trap here is assuming that event reasons can be automatically derived through picklist filtering or scheduled jobs, when in fact they require a business rule to evaluate the change context.

Full explanation →
34
MCQeasy

An administrator is setting up the Employee Central 'Employment Details' portlet for a new legal entity. The company wants to record whether each employee is full-time or part-time and to capture the standard weekly working hours. Which two fields should the administrator configure on the Employment Details portlet to meet this requirement?

A.Employee Class and Pay Grade
B.Employment Type and FTE
C.Is Full Time and Standard Weekly Hours
D.Job Title and Position
AnswerC

The Employment Details portlet includes the Is Full Time indicator to distinguish full-time from part-time employees and the Standard Weekly Hours field to capture the contractual weekly hours. Configuring these two fields directly satisfies the requirement to record employment status and standard weekly working hours for the legal entity.

Why this answer

Employment Details in Employee Central provides the Is Full Time indicator and the Standard Weekly Hours field, which together capture whether an employee is full-time or part-time and the contractual weekly hours. Other field pairs such as Employee Class with Pay Grade, Employment Type with FTE, or Job Title with Position describe different aspects of the employment relationship and do not satisfy the stated requirement.

Exam trap

The trap here is confusing FTE with Standard Weekly Hours, when FTE expresses a fraction of full-time equivalence rather than the actual contractual weekly hours value the business wants to record.

Full explanation →
35
MCQhard

A company wants to track employee dependents for benefits purposes. Each employee can have multiple dependents, and each dependent must store name, date of birth, relationship, and a flag indicating whether they are covered under the employee's health plan. The data must be reportable and editable from the employee's profile. Which configuration approach should the administrator use?

A.Create a new foundation object 'Dependent' and assign it as a picklist to the Personal Information portlet.
B.Add multiple sets of dependent fields directly to the Personal Information portlet as repeating fields.
C.Use the Employee Profile portlet's built-in Dependents section and enable the health plan coverage flag through a business rule.
D.Create a new MDF object 'Dependent' with a composite association to Employee, and add a 'Dependents' portlet or section to the employee profile.
AnswerD

A custom MDF object with a composite association to Employee supports multiple dependent records per employee, stores the required fields, and can be surfaced on the profile for editing and reporting. This is the standard pattern for one-to-many custom data in Employee Central.

Why this answer

The appropriate approach is a custom MDF object with a composite association to Employee, which naturally supports multiple records per employee and stores all required attributes. Surfacing it on the employee profile enables editing and reporting. The other options either cannot handle one-to-many data or misuse foundation objects and standard portlets.

Exam trap

The trap here is choosing a foundation object or standard portlet for employee-specific one-to-many data, when a custom MDF object with a composite association is the correct pattern.

Full explanation →
36
MCQmedium

An EC administrator is configuring a new MDF object called 'Employee Recognition' that must allow multiple records per employee AND be associated to a specific employee via a field. Which configuration should be used to ensure proper linkage to the employee?

A.Create a field of type 'String' and manually enter the employee ID.
B.Create a field of type 'Association' and set the 'Valid Values' to the Employee object.
C.Create a field of type 'User' and set the 'Valid Values' to the employee's user ID.
D.Create a field of type 'Number' and store the employee's numeric ID.
AnswerB

An 'Association' field type is specifically designed to link one MDF object to another, such as Employee. By setting Valid Values to the Employee object, the field will reference employee records. This ensures the recognition record is associated with the correct employee, and multiple records can be created per employee because the object is configured as a detail object.

Why this answer

The correct approach is to use an Association field type with Valid Values set to the Employee object. This creates a proper linkage between the 'Employee Recognition' MDF object and Employee Central employee records, ensuring data integrity and enabling multiple recognition entries per employee. Other field types do not establish the necessary object relationship.

Exam trap

The trap here is assuming that any field that can store an employee identifier, such as a String or Number field, is sufficient for linking to the Employee object, when only an Association field provides the required referential integrity.

Full explanation →
37
Multi-Selecthard

A SuccessFactors administrator is configuring the 'Job Information' portlet and needs to ensure that when an employee's 'Employee Class' changes from 'Regular' to 'Temporary', the system automatically updates the 'Probation End Date' to be 90 days from the change date. The administrator plans to use a business rule. Which two configurations are required to achieve this? (Choose two.)

Select 2 answers
A.Use a scheduled job to run daily and update the Probation End Date for all employees whose Employee Class is 'Temporary'.
B.Create a workflow that sends an email notification to the HR administrator whenever Employee Class changes.
C.In the business rule, set the 'Probation End Date' field to the current date plus 90 days using a calculated expression.
D.Configure a field-level validation rule on the 'Employee Class' field to restrict values to 'Regular' and 'Temporary'.
E.Create a business rule on the Job Information object that triggers on the 'onChange' event of the 'Employee Class' field.
AnswersC, E

The rule must calculate the new probation end date as the current date plus 90 days. Using a calculated expression with the 'addDays' function or similar date arithmetic ensures the correct value is set. This action directly fulfills the requirement to update the field when the condition is met.

Why this answer

To automatically update Probation End Date when Employee Class changes, you need a business rule that triggers on the onChange event of the Employee Class field. The rule must then calculate the new date as current date plus 90 days and set the Probation End Date field. These two configurations together ensure the field is updated precisely when the triggering change occurs.

Exam trap

The trap here is confusing notification or validation with automated field updates, or thinking a scheduled job would suffice, when the requirement demands an immediate, event-driven calculation.

Full explanation →
38
MCQhard

An administrator needs to configure the Employee Central Foundation Object 'Event Reason' to support a new business process. The company requires that when an employee is terminated, the event reason 'Resignation' triggers a specific workflow and updates the employee's status to 'Terminated'. The administrator must ensure that the event reason is only available for the Termination event and that it is mapped to the correct employee status. Which configuration is required to achieve this?

A.Create a new Event Reason with Event Type 'Termination', map it to Employee Status 'Terminated', but do not assign a workflow.
B.Create a new Event Reason with Event Type 'Resignation', map it to Employee Status 'Terminated', and assign the workflow.
C.Create a new Event Reason with Event Type 'Termination', map it to Employee Status 'Terminated', and assign the workflow.
D.Create a new Event Reason with Event Type 'Termination', map it to Employee Status 'Resignation', and assign the workflow.
AnswerC

This is correct because Event Reason must be associated with an Event Type, such as Termination, to control when it is available. Mapping it to the Employee Status 'Terminated' ensures the employee's status is updated correctly. Assigning the workflow ensures the business process is triggered. This configuration meets all the requirements.

Why this answer

The Event Reason must be associated with the Event Type 'Termination' to ensure it is only available for termination events. Mapping it to Employee Status 'Terminated' ensures the employee's status is updated correctly. Assigning the workflow triggers the required business process.

This combination fulfills all the stated requirements for the new business process.

Exam trap

The trap here is confusing Event Type with Event Reason; Event Type defines the category of the event, while Event Reason is the specific reason selected within that category.

Full explanation →
39
Multi-Selecthard

A consultant is configuring the Employee Central 'Job Information' portlet for a client that uses position management. The client wants to ensure that when a position is changed, the 'Job Code' and 'Cost Center' fields are automatically updated based on the new position. The consultant needs to implement this. Which two configurations are required? (Choose two.)

Select 2 answers
A.Create a business rule on Job Information that triggers on change of the Position field and sets Job Code and Cost Center from the Position object.
B.Ensure that the Position object contains the Job Code and Cost Center fields and that they are populated for each position.
C.Set up a picklist dependency to filter Job Code values based on the selected Position.
D.Use a workflow rule to update Job Code and Cost Center after the Job Information record is saved.
E.Configure the Job Code and Cost Center fields as required fields in the Job Information portlet.
AnswersA, B

A business rule on Job Information can detect when the Position field changes and then retrieve the Job Code and Cost Center from the associated Position record. This automatically updates the fields as required. This is the standard method for synchronizing data from a related object upon change.

Why this answer

To automatically update Job Code and Cost Center when Position changes, a business rule on Job Information is needed to fetch values from the Position object. Additionally, the Position object must contain those fields and have them populated. Together, these ensure the data is available and the rule can apply it.

Other options do not provide automatic synchronization.

Exam trap

The trap here is assuming that making fields required or using workflow rules will automatically update them, but only a business rule can perform the dynamic lookup and set values.

Full explanation →
40
MCQmedium

An Employee Central administrator is setting up a new association on a custom MDF object 'EmployeeProjectAssignment'. The association must link each project assignment record to exactly one employee record in the Employee Central 'Employee' object. The administrator needs to ensure the association is configured so that an employee can be linked to many project assignment records, but each project assignment record references only one employee. Which association type should be configured on the 'EmployeeProjectAssignment' object to the 'Employee' object?

A.Many-to-Many association with the Employee object as the target
B.One-to-One association with the Employee object as the target
C.Many-to-One association with the Employee object as the target
D.One-to-Many association with the Employee object as the source
AnswerC

A many-to-one association from the custom object to the Employee object allows many project assignment records to reference the same employee, while each assignment record holds a single employee reference. This matches the requirement exactly: an employee can have multiple assignments, but each assignment points to only one employee. The association is configured on the custom object with Employee as the target.

Why this answer

The requirement is that many project assignment records can point to one employee, while each assignment record points to exactly one employee. In MDF, this is modeled as a many-to-one association on the custom object with Employee as the target. This allows multiple records on the custom object to reference the same employee record without allowing a single assignment to reference multiple employees.

Exam trap

The trap here is confusing the direction of the association and assuming that many-to-one on the custom object means many employees to one assignment, when it actually means many assignments to one employee.

Full explanation →
41
MCQmedium

A company uses Employee Central and needs to track employee participation in internal training programs. Each employee can attend multiple trainings, and each training can have multiple employees. The administrator must create an MDF object to store this information. Which object type should the administrator create?

A.A MDF object with a multi-select picklist field that lists all available trainings, and assign it to the Employee object.
B.A generic object with a many-to-many relationship to the Employee object via a composite association.
C.A child object of the Employee object with a field for training name, allowing multiple records per employee.
D.A junction object that has a many-to-one association to both the Employee object and a Training object.
AnswerD

A junction object is the standard way to model many-to-many relationships in MDF. By creating an object with many-to-one associations to both Employee and Training, each record represents a unique employee-training pair. This allows an employee to have multiple training records and a training to have multiple employee records, accurately capturing the many-to-many relationship.

Why this answer

To model a many-to-many relationship between employees and trainings in MDF, a junction object is required. This object has many-to-one associations to both Employee and Training, with each record representing a unique pairing. This allows efficient tracking of participation and any additional attributes per employee-training combination.

Exam trap

The trap here is assuming that a child object or a multi-select picklist can handle many-to-many relationships, when they actually lead to data duplication or limited functionality.

Full explanation →
42
MCQhard

A company uses SAP SuccessFactors Employee Central and has a requirement that when an employee is terminated, their 'Job Information' record should be updated to set the 'Employee Status' to 'Terminated' and the 'Termination Date' should be populated. The termination process is initiated via the 'Terminate' action in the UI. Which configuration ensures that the Employee Status is automatically set to 'Terminated' when the termination is completed?

A.Use the standard 'Terminate' action, which automatically sets the Employee Status to 'Terminated' and populates the Termination Date based on the event reason configuration.
B.Create a custom MDF object to track terminations and use a business rule to update the Job Information record when a termination record is created.
C.Configure a workflow that triggers on termination and uses a business rule to set the Employee Status to 'Terminated' after approval.
D.Configure a business rule on the Job Information object with the 'onSave' event that checks if Termination Date is populated and sets Employee Status to 'Terminated'.
AnswerA

The standard termination process in Employee Central is designed to handle all necessary updates, including setting Employee Status to 'Terminated' and recording the Termination Date. The event reason selected during termination determines the resulting Employee Status. This is the correct and standard approach, requiring no custom configuration beyond ensuring event reasons are properly set up.

Why this answer

The standard termination process in Employee Central automatically updates the Employee Status and Termination Date based on the event reason selected. No custom business rules or workflows are needed for this core functionality. Ensuring that event reasons are correctly configured to map to the 'Terminated' status is the only necessary setup.

Exam trap

The trap here is assuming that custom business rules are needed to set Employee Status during termination, when the standard process handles it automatically.

Full explanation →
43
MCQeasy

An administrator is setting up the Employee Central 'Employment Details' portlet and needs to ensure that the 'Original Start Date' is captured for all employees. The company wants this field to be automatically populated with the employee's first hire date and then remain unchanged even if the employee is rehired. Which field should be used to store this information?

A.Service Date
B.Original Start Date
C.Start Date
D.Hire Date
AnswerB

The 'Original Start Date' field in Employment Details is specifically designed to capture the employee's very first hire date. It is typically set automatically when the employee is first hired and remains unchanged through rehires or other job changes. This field is standard in Employee Central and serves exactly the purpose described, ensuring a permanent record of the initial hire date.

Why this answer

The 'Original Start Date' field is specifically designed to store the employee's first hire date and remains unchanged through rehires. Other date fields like 'Start Date' or 'Hire Date' may be updated upon rehire or reflect the current employment segment. Therefore, 'Original Start Date' is the correct choice to meet the requirement.

Exam trap

The trap here is assuming that 'Hire Date' always remains the original hire date, when in fact it can be updated on rehire in many configurations.

Full explanation →
44
MCQeasy

A company uses SAP SuccessFactors Employee Central. An HR administrator needs to update an employee's home address. Which portlet in the Employee Profile should the administrator use?

A.Personal Information
B.Employment Information
C.Job Information
D.Compensation Information
AnswerA

The Personal Information portlet in the Employee Profile contains personal data including home address, contact information, and personal details. This is the correct portlet to update an employee's home address. It is typically accessible to HR administrators and employees themselves based on permissions.

Why this answer

To update an employee's home address in SAP SuccessFactors Employee Central, the HR administrator should use the Personal Information portlet in the Employee Profile. This portlet is designed to store and manage personal data, including addresses, and is the standard location for such updates.

Exam trap

The trap here is confusing personal data with job or employment data, as home address is personal information, not job-related.

Full explanation →
45
MCQmedium

A company uses SAP SuccessFactors Employee Central. An administrator needs to create a new position for an employee. The position must be linked to a specific legal entity and must have a maximum headcount of 1. Which object should the administrator use to create the position?

A.Job Information
B.Position
C.Employee Profile
D.Legal Entity
AnswerB

The Position object in Employee Central is used to create and manage positions. It allows configuration of attributes such as legal entity, headcount, and other position-specific details. Creating a position here ensures it can be assigned to employees via Job Information. This is the correct object for the task.

Why this answer

To create a new position with specific attributes like legal entity and maximum headcount, the administrator must use the Position object in Employee Central. This object allows defining all necessary position details, which can then be assigned to employees through Job Information.

Exam trap

The trap here is confusing the creation of a position with the assignment of a position, as Job Information is used for assignment, not creation.

Full explanation →
46
MCQmedium

An HR administrator at a global company needs to set up a new Employee Central instance. The company operates in multiple countries, and employees in different legal entities must follow distinct time-off policies. The administrator wants to ensure that time-off accruals and eligibility are automatically determined based on the employee's legal entity and country. Which of the following should the administrator configure to achieve this requirement?

A.Create a business rule that updates the employee's Time Off plan field in Job Information based on legal entity.
B.Create a Time Off plan and assign it to employees via the Employment Details block.
C.Set up Time Off plans and link them to employee groups based on legal entity and country.
D.Configure Time Off calendars with country-specific holidays and assign them to employees.
AnswerC

In Employee Central, Time Off plans define accrual rules and eligibility, and they are assigned to employees through employee groups. Employee groups are defined by rules that can reference legal entity and country. This ensures that employees in different legal entities and countries automatically receive the correct time-off plan. This is the standard configuration to meet the requirement.

Why this answer

Time Off plans in Employee Central are assigned to employees via employee groups, which are determined by rules that can use legal entity and country as criteria. This automatically ensures that employees in different legal entities and countries receive the appropriate time-off policy. Configuring plans and linking them to employee groups is the correct approach to meet the global time-off policy requirement.

Exam trap

The trap here is assuming that time-off plans are assigned directly on the employee record or via Job Information, rather than through employee groups derived from legal entity and country.

Full explanation →
47
MCQeasy

An HR administrator needs to create a new MDF object to track employee visas. The object must store the visa type, issue date, expiry date, and a copy of the visa document. Which field type should be used to store the visa document?

A.Date
B.Attachment
C.String
D.Picklist
AnswerB

The Attachment field type in MDF allows uploading and storing files, such as PDFs or images, directly in the object record. It is specifically designed for document storage and supports versioning and access control. For a visa document, this is the appropriate field type because it enables users to attach the scanned visa file. Other field types like String or Date cannot store binary files.

Why this answer

To store a document such as a visa copy, the MDF object must use the Attachment field type. This field allows users to upload and associate files with the record. Other field types like String, Date, or Picklist cannot handle binary file data.

The Attachment field is the standard and correct choice for document storage in MDF objects.

Exam trap

The trap here is confusing a String field, which might store a URL, with an Attachment field that actually stores the file within the system.

Full explanation →
48
MCQmedium

An administrator is configuring the Employee Central 'Job Information' portlet. The company requires that when an employee's 'Employee Class' is changed to 'Executive', the 'Pay Grade' field must be automatically set to a specific value and then made read-only. Which tool should the administrator use to implement this requirement?

A.Configure Object Definitions to set a default value for Pay Grade based on Employee Class.
B.Picklist management to restrict the Pay Grade values available when Employee Class is Executive.
C.Business Rules to trigger on Job Information save, set Pay Grade, and set the field as read-only.
D.Workflow configuration to route the Job Information change for approval when Employee Class is Executive.
AnswerC

Business Rules can be triggered on save or change of Job Information. A rule can check if Employee Class equals 'Executive', then set the Pay Grade to the required value and set the field to read-only using the 'Set Field Read-Only' action. This provides the conditional logic and dynamic behavior needed, ensuring the field is both populated and locked from further editing.

Why this answer

Business Rules are the appropriate tool to implement conditional logic that sets a field value and makes it read-only based on another field's value. Triggering on Job Information save allows the rule to evaluate Employee Class and perform the necessary actions on Pay Grade.

Exam trap

The trap here is assuming that object definition settings or picklist management can enforce dynamic field behavior, when they only handle static configuration.

Full explanation →
49
MCQhard

An administrator needs to configure a business rule on the Job Information object that prevents saving a record when the employee's 'Employment Type' is 'Regular' and the 'Standard Weekly Hours' field is empty. The rule must evaluate on save and block the save with a custom error message. Which rule scenario and configuration should the administrator use?

A.Create an onSave rule on the Job Information object with a condition checking Employment Type = Regular and Standard Weekly Hours is empty, and add a message with severity 'Error'.
B.Create an onInit rule on Job Information that checks the fields and displays a warning message when Standard Weekly Hours is empty for Regular employees.
C.Create an onChange rule on the Standard Weekly Hours field that raises an error when the field is cleared, regardless of Employment Type.
D.Create an onSave rule on the Employment Type field with a condition checking Standard Weekly Hours is empty, and configure the rule to trigger a workflow instead of an error message.
AnswerA

An onSave rule on Job Information evaluates when the record is saved. A condition matching Employment Type = Regular and empty Standard Weekly Hours, combined with an error-severity message, blocks the save and displays the custom message. This is the supported pattern for validation on save in Employee Central.

Why this answer

To block a save based on field values, an onSave rule on the Job Information object is required. The condition must combine the Employment Type check with the empty Standard Weekly Hours check, and the message must have error severity so the save is prevented and the custom message is shown to the user.

Exam trap

The trap here is confusing onChange or onInit rule timing with onSave, when only an onSave rule with error severity can block the save and display the validation message.

Full explanation →
50
MCQhard

A company uses SAP SuccessFactors Employee Central with a complex organizational structure. An HR administrator needs to create a new position for a senior manager. The position must be linked to a specific job classification, a cost center, and a location. The administrator also wants to ensure that the position is available for succession planning. Which object should the administrator configure to meet these requirements?

A.Position
B.Cost Center
C.Job Classification
D.Job Information
AnswerA

Position is the correct object because it represents a specific role within the organization that can be linked to a job classification, cost center, and location. Creating a position allows the administrator to define these attributes and make the position available for succession planning. Once the position is created, it can be assigned to an employee in Job Information, ensuring proper organizational structure and planning.

Why this answer

The Position object represents a specific role within the organization and can be linked to a job classification, cost center, and location. Creating a position allows the administrator to define these attributes and make the position available for succession planning. Once created, the position can be assigned to an employee in Job Information, ensuring accurate organizational structure and enabling talent management processes.

Exam trap

The trap here is assuming that Job Information is used to create positions; in reality, Job Information only stores the assignment of an existing position to an employee, while the Position object itself must be configured separately.

Full explanation →
51
MCQmedium

An Employee Central administrator is creating a new event reason for the 'Termination' event. The company requires that when an HR administrator selects this event reason during termination, the system must automatically set the employee's 'Employee Status' to 'Terminated' and 'Employee Class' to 'Inactive'. Which configuration should the administrator perform to meet this requirement?

A.Create a 'Event Reason' record with the 'Employee Status' and 'Employee Class' fields populated, and configure the event reason to derive these values during the termination process.
B.Configure a workflow rule on the Termination portlet that updates the Employee Status and Employee Class fields upon approval.
C.Configure a business rule on the 'Event Reason' object that triggers on save and sets the Employee Status and Employee Class fields.
D.Create a business rule on the 'Employment Information' object that triggers when the event reason is 'Termination' and sets the Employee Status and Employee Class fields.
AnswerA

Event Reason configuration includes fields for Employee Status and Employee Class that are automatically applied when the event reason is used in a termination. By setting these fields on the event reason record, the system derives the correct status and class without additional business rules. This is the standard configuration for termination event reasons.

Why this answer

Event reasons in Employee Central can be configured with specific Employee Status and Employee Class values that are automatically applied when the event reason is selected. This ensures consistency and reduces manual entry. For termination, setting these fields on the event reason record is the standard approach, eliminating the need for complex business rules or workflows.

Exam trap

The trap here is confusing event reason derivation with business rules, assuming that a business rule is required to set Employee Status and Employee Class during termination, when the event reason configuration itself can handle it.

Full explanation →
52
MCQhard

A company uses Employee Central and has a requirement that when an employee's 'Job Information' record is created, the 'Cost Center' field must be populated based on the employee's 'Location'. The administrator has created a business rule with an OnSave trigger on Job Information. However, during testing, the Cost Center is not being set. What is the most likely cause?

A.The rule should be triggered on OnInit instead of OnSave.
B.The rule is missing a condition to check if the record is new.
C.The 'Cost Center' field is not included in the rule's target field list or the rule is not active.
D.The rule must be created on the 'Location' object instead of Job Information.
AnswerC

If the rule is not active or the Cost Center field is not specified as a target, the rule will not set it. This is a common configuration oversight. The administrator should verify the rule is active and that the target field is correctly mapped in the rule action.

Why this answer

The most common reasons a business rule does not set a field are that the rule is inactive or the target field is not properly configured in the rule's action. The administrator should check the rule's status and ensure the Cost Center field is selected as the target in the 'Set' action. Other factors like trigger type or base object are likely correct given the scenario.

Exam trap

The trap here is assuming the trigger or base object is wrong, but often the rule is simply inactive or the target field is not mapped.

Full explanation →
53
MCQeasy

An HR administrator needs to create a new position in Employee Central. The position must be assigned to a specific department and location. Which object should the administrator use to create the position record?

A.Position
B.Job Information
C.Department
D.Location
AnswerA

The Position object is the standard MDF object used to create and manage positions in Employee Central. It includes fields for Department, Location, and other attributes. Creating a position record here allows assignment to employees and integration with Job Information. This is the correct object for this requirement.

Why this answer

The Position object is specifically designed for creating and managing positions. It contains the necessary fields to assign a department and location. Job Information is for employee assignments, while Department and Location are Foundation Objects used for categorization.

Therefore, the administrator should use the Position object.

Exam trap

The trap here is confusing the object used to define a position with the object used to assign a position to an employee, leading to selection of Job Information instead of Position.

Full explanation →
54
MCQhard

An administrator needs to configure the Employee Central 'Job Information' portlet to enforce that the 'Employee Class' field is mandatory only for employees in the United States, while for other countries it remains optional. The company uses Country-specific field configurations. Which configuration should the administrator use to achieve this?

A.Set the 'Employee Class' field as required in the global field configuration and then use a business rule to bypass the requirement for non-US employees.
B.Create a country-specific field configuration for the United States where the 'Employee Class' field is set as required, and another configuration for other countries where it is optional.
C.Use a business rule on Job Information that checks the employee's country and raises an error if Employee Class is empty for US employees.
D.Configure a custom validation rule on the 'Employee Class' field in the Job Information portlet that makes it required based on the employee's country.
AnswerB

Country-specific field configurations allow different field properties per country. By setting up a configuration for the United States where Employee Class is required, and a default configuration for other countries where it is optional, the administrator meets the requirement. This is the standard method to apply country-specific field rules in Job Information.

Why this answer

Country-specific field configuration allows the administrator to set different properties for fields based on the employee's country. By configuring Employee Class as required for the United States and optional for other countries, the requirement is met without complex business rules. This is the standard, supported method for country-specific field behavior in Job Information.

Exam trap

The trap here is thinking that a business rule is needed to conditionally enforce a field, when country-specific field configuration can directly set the field as required per country.

Full explanation →
55
MCQmedium

An administrator needs to configure a custom field in the Job Information block that dynamically populates based on the selection of the Department field. Which feature must be utilized to achieve this dependency mapping efficiently?

A.Employee Central Data Models via Succession Data Model XML upload
B.Business Rules triggered onOnChange of the Department field
C.Workflows configured in Corporate Data Model
D.UI Master Configuration via Configure Employee Files
AnswerB

Configuring a business rule with an OnChange event on the Department field allows the system to instantly evaluate conditional logic and set the value of the target custom field dynamically on the user interface before the transaction is saved.

Why this answer

Business Rules are the standard configuration mechanism in SAP SuccessFactors Employee Central to establish field-to-field dependencies, trigger dynamic UI changes, and enforce data validation across MDF and legacy blocks. Utilizing a business rule ensures seamless user experience and maintains data integrity during hire and job change processes without requiring custom client-side script interventions.

Exam trap

Candidates frequently select generic UI rules or MDF object triggers instead of specifically utilizing Business Rules triggered on the onChange event of the Department field.

Full explanation →
56
MCQmedium

An Employee Central administrator at a multinational company needs to ensure that when an employee's Job Information record is created, the 'Company' field automatically defaults to the legal entity associated with the employee's 'Location'. The administrator wants to minimize manual data entry and enforce consistency. Which configuration approach should be used to achieve this?

A.Configure a default value for the Company field in the Job Information portlet configuration using the 'Default Value' setting.
B.Use a propagation rule on the Location foundation object to push the legal entity to all associated Job Information records.
C.Create a business rule on the Job Information object that triggers on save and sets the Company field based on the Location's legal entity.
D.Create a workflow rule that triggers on Job Information creation and sends an email to the administrator to manually update the Company field.
AnswerC

A business rule on Job Information can trigger on save and use the Location foundation object's relationship to derive the legal entity. This ensures the Company field is populated automatically based on the selected Location, enforcing consistency and reducing manual entry. The rule can be configured with a 'Set' action to assign the Company value from the Location's associated legal entity field.

Why this answer

The correct approach is to use a business rule on the Job Information object that triggers on save and sets the Company field based on the Location's legal entity. This dynamically derives the value from the related Location object, ensuring consistency and reducing manual entry. Other options either apply static values or require manual intervention, which do not meet the requirement.

Exam trap

The trap here is assuming that a default value configured in the portlet can reference another field dynamically, when it only supports static values.

Full explanation →
57
MCQmedium

An administrator is configuring the Employee Central Foundation Object 'Location' for a company with offices in multiple countries. The company requires that when a new location is created, it must be associated with a specific legal entity and a time zone. The administrator also wants to ensure that locations can be filtered by country in reports. Which configuration steps are necessary to meet these requirements?

A.Create a Location object with a lookup to Business Unit and a field for Time Zone, and enable the Country field for filtering.
B.Create a Location object with a lookup to Legal Entity and a field for Time Zone, and enable the Country field for filtering.
C.Create a Location object with a lookup to Legal Entity and a field for Currency, and enable the Country field for filtering.
D.Create a Location object with a lookup to Legal Entity and a field for Time Zone, but do not enable the Country field for filtering.
AnswerB

This is correct because the Location object must have associations to Legal Entity and Time Zone to meet the business requirements. Legal Entity is typically a lookup field, and Time Zone can be a standard or custom field. The Country field is often part of the Location object and can be used for filtering in reports. Enabling these fields ensures proper data capture and reporting capabilities.

Why this answer

The Location object must be associated with a Legal Entity and include a Time Zone field to meet the business requirements. Additionally, the Country field must be enabled for filtering to allow reporting by country. Configuring these elements ensures that locations are properly linked to legal entities, time zones are captured, and reports can be filtered by country.

Exam trap

The trap here is overlooking the need to enable the Country field for filtering; many administrators assume that adding the field is sufficient, but it must also be configured as a filterable field in the object definition.

Full explanation →
58
MCQeasy

A SuccessFactors administrator is configuring the Employee Central Foundation Object 'Department' and needs to prevent employees from selecting obsolete department codes that are no longer in use, while preserving the historical assignments on existing employee records. What is the recommended approach in Employee Central?

A.Delete the obsolete Department records from the Manage Data interface.
B.Set the status of the obsolete Department records to Inactive in the Manage Data interface.
C.Configure a business rule that hides the Department field when an obsolete code is selected.
D.Create a new Department picklist and assign it to the Job Information Department field.
AnswerB

Inactivating the Department Foundation Object record prevents it from appearing in the picklist for new assignments while keeping it available for existing employee Job Information records that already reference it. This is the standard EC pattern for retiring Foundation Object values without breaking historical data.

Why this answer

Setting the Department Foundation Object record to Inactive is the correct way to retire a value while preserving existing employee assignments. Inactive records remain valid for historical references but are excluded from the selection list for new entries, which directly satisfies both parts of the requirement.

Exam trap

The trap here is assuming that obsolete Foundation Object values must be deleted, when Employee Central's design preserves referenced records and expects status changes instead.

Full explanation →
59
MCQmedium

A company wants to ensure that when an employee's 'Job Information' is updated, a notification is sent to the employee's manager. The administrator creates a business rule on the Job Information object. Which trigger event should the administrator use to ensure the notification is sent after the changes are saved?

A.OnInit
B.OnChange
C.OnSave
D.OnPostSave
AnswerD

OnPostSave triggers after the record has been successfully saved to the database. This ensures that the notification is sent only after the changes are persisted. This event is specifically designed for actions that should occur after a successful save, such as sending notifications or triggering integrations. Therefore, it meets the requirement precisely.

Why this answer

The OnPostSave event is designed to execute after a record has been successfully saved. This guarantees that the notification is sent only when the changes are committed, aligning with the requirement. Other events either fire too early or are not related to the save action.

Exam trap

The trap here is assuming OnSave is sufficient for post-save actions; however, OnSave occurs before the save is committed, while OnPostSave ensures the save was successful.

Full explanation →
60
MCQmedium

A global company uses SAP SuccessFactors Employee Central. The HR team needs to ensure that when an employee's 'Job Information' record is updated, the system checks if the employee's 'Country' field is 'United States' and if so, automatically sets the 'Employee Class' to 'Regular'. If the country is not United States, the Employee Class should remain unchanged. Which configuration should the administrator use?

A.Create a business rule on Job Information that triggers on save, with a condition that Country equals United States, and sets Employee Class to Regular.
B.Configure a workflow rule that triggers when Job Information is updated and sends an email to the HR administrator to manually set Employee Class if the country is United States.
C.Set a default value on the Employee Class field in Job Information to 'Regular' and configure a country-specific picklist to hide the field for non-US countries.
D.Use a propagation rule from the Country foundation object to Job Information to set Employee Class to Regular when Country is United States.
AnswerA

A business rule on Job Information with an on-save trigger and a condition for Country equals United States can set the Employee Class to Regular. This meets the requirement to conditionally update Employee Class based on the country, and it only applies when the condition is true, leaving other records unchanged.

Why this answer

The correct solution is a business rule on Job Information that triggers on save, checks if Country equals United States, and sets Employee Class to Regular. This automatically applies the change only for US employees and leaves other records unchanged. Business rules are the standard tool for conditional field updates in Employee Central.

Exam trap

The trap here is assuming that default values or propagation rules can conditionally update fields on save, when only a business rule with an on-save trigger and condition can evaluate Country and set Employee Class.

Full explanation →
61
MCQmedium

An Employee Central administrator is configuring an event reason for the 'Hire' event. The company wants to ensure that when a new employee is hired, the event reason automatically sets the employee's 'Employee Status' to 'Active' and triggers a workflow. Which configuration step must the administrator perform to associate the event reason with the 'Hire' event and enable the desired behavior?

A.Configure a business rule on the Job Information object that triggers on hire and updates the Employee Status field.
B.Create a new Event Reason in the Event Reason configuration and assign it to the 'Hire' event type, then set the 'Employee Status' default and enable workflow.
C.Modify the Employee Status picklist to include 'Active' and set it as the default for all new hires.
D.Create a new workflow configuration that sets the Employee Status to 'Active' upon hire and assign it to the Hire event.
AnswerB

Event Reasons are configured under 'Event Reason' in Admin Center, where you specify the event type (e.g., Hire), the default employee status, and whether a workflow is triggered. Assigning the event reason to the 'Hire' event ensures that when the event occurs, the status is set and the workflow is initiated as required.

Why this answer

Event reasons are the standard way to define the default employee status and workflow behavior for a given event, such as Hire. By creating an event reason and assigning it to the Hire event, the administrator ensures that when a hire occurs, the employee status is automatically set to Active and the associated workflow is triggered. This is the correct configuration step in Employee Central.

Exam trap

The trap here is assuming that business rules or workflows alone can set the employee status on hire, when actually the event reason configuration is responsible for that default.

Full explanation →
62
MCQeasy

An administrator needs to create a new custom MDF object to track employee languages. The object should have a field for 'Language' and a field for 'Proficiency Level'. The administrator wants to ensure that the 'Proficiency Level' field only allows selection from a predefined list of values: Beginner, Intermediate, Advanced. What should the administrator do to achieve this?

A.Create a new MDF object with a field of type 'Number' for Proficiency Level and use a business rule to map numbers to the proficiency levels.
B.Create a new MDF object with a field of type 'Picklist' for Proficiency Level and associate it with a picklist that contains the values Beginner, Intermediate, Advanced.
C.Create a new MDF object with a field of type 'String' for Proficiency Level and manually enter the allowed values in the field's validation section.
D.Create a new MDF object with a field of type 'Generic Object' for Proficiency Level and create a separate MDF object for proficiency levels with the three values.
AnswerB

Using a Picklist field type allows the administrator to define a predefined list of values. Associating it with a picklist that contains the specified values ensures that users can only select from those options. This is the standard and most efficient way to restrict input to a set of values in MDF objects.

Why this answer

To restrict the Proficiency Level field to a predefined list of values, the administrator should use a Picklist field type and associate it with a picklist containing Beginner, Intermediate, and Advanced. This ensures data consistency and simplifies user input by providing a dropdown menu.

Exam trap

The trap here is thinking that a String field can be easily restricted to a list of values without additional configuration, when in fact a Picklist is the correct field type.

Full explanation →
63
MCQhard

A consultant is configuring the Employee Central 'Job Information' portlet for a company that uses multiple legal entities. The company wants to ensure that when an employee's 'Legal Entity' is changed, the 'Location' field is automatically updated to the default location of that legal entity. The consultant decides to use a business rule. Which trigger type on the Job Information object should be used to achieve this dynamic defaulting?

A.OnChange
B.OnSave
C.OnInit
D.OnPostSave
AnswerA

OnChange triggers when the Legal Entity field value changes. It can immediately look up the default location for that legal entity and set the Location field. This provides dynamic defaulting and updates the UI in real time, enhancing user experience.

Why this answer

To automatically update the Location field when Legal Entity changes, the business rule must trigger on that change. OnChange is designed for this purpose, allowing immediate defaulting based on the new value. This provides a seamless user experience by updating the form in real time.

Exam trap

The trap here is assuming OnSave is sufficient because it can set the field, but it does not provide immediate feedback when the Legal Entity changes.

Full explanation →
64
MCQmedium

A SuccessFactors administrator is configuring the MDF object 'Job Code' in Employee Central. The business wants to ensure that when a user creates a new Job Code record, the 'Job Family' field is required and must be selected from a valid list. The administrator decides to use a business rule to enforce this requirement. Which business rule event type should be used to trigger the rule when a new Job Code is being created?

A.onChange
B.onSave
C.onDelete
D.onInit
AnswerB

onSave is the correct event type because it fires when a user saves a new or modified MDF object record. For enforcing required field validation and list selection on creation, onSave triggers before the record is committed, allowing the rule to validate the Job Family field and prevent saving if invalid. This is the standard event for validation logic on MDF objects.

Why this answer

The onSave event is designed to validate MDF object records before they are saved. It allows the rule to check that Job Family is populated and valid, and to block the save if not. onInit, onChange, and onDelete serve different purposes and cannot enforce required field validation at creation time. Therefore, onSave is the correct choice.

Exam trap

The trap here is confusing onSave with onChange or onInit, and assuming any rule event can enforce required fields on creation.

Full explanation →
65
MCQeasy

A company wants to track employee participation in internal training courses. Each employee can attend many courses, and each course can have many employees. The administrator needs to create an MDF object to store this relationship. Which object type should be created?

A.A generic MDF object with a field of type 'User' and a field of type 'String' for the course name.
B.A foundation object for courses and a separate foundation object for employees, with no association between them.
C.A generic MDF object with two association fields: one referencing the Employee object and one referencing the Course object.
D.A composite MDF object with a parent-child structure where the parent is the course and the child is the employee.
AnswerC

A generic MDF object with two association fields creates a junction object that models a many-to-many relationship. Each record links one employee to one course, and multiple records allow many employees per course and many courses per employee. This is the standard pattern for many-to-many associations in Employee Central.

Why this answer

A many-to-many relationship is modeled with a generic MDF object that contains two association fields, one to each related object. Each record represents a single pairing, and the collection of records supports multiple employees per course and multiple courses per employee, which is exactly what the scenario requires.

Exam trap

The trap here is assuming that composite objects or simple string fields can represent many-to-many relationships, when only a generic object with two associations correctly models this pattern.

Full explanation →
66
MCQeasy

An HR administrator needs to add a new picklist value to the 'Employment Type' picklist used in the Job Information block. Where should the administrator make this change?

A.In the 'Manage Data' tool by selecting the 'Employment Type' MDF object.
B.In the Picklist Center under the 'Employment Type' picklist.
C.In the 'Employee Central' settings under 'Picklist Management'.
D.In the Job Information block configuration under 'Picklist Mappings'.
AnswerB

The Picklist Center is the central location for managing all picklist values in Employee Central. Administrators can add, edit, or deactivate values for any picklist, including 'Employment Type'. Changes here are automatically reflected wherever the picklist is used, such as in Job Information.

Why this answer

Picklist values in Employee Central are centrally managed in the Picklist Center. This ensures consistency across all objects and blocks that use the picklist. Adding a value there makes it immediately available in Job Information and elsewhere.

The other options either refer to non-existent features or confuse picklist management with block configuration or MDF data management.

Exam trap

The trap here is thinking that picklist values are added within the block where they are used, rather than centrally in the Picklist Center.

Full explanation →
67
MCQeasy

An administrator needs to create a new MDF object in Employee Central to store employee visa records. The object must reference the existing Employee object so that each visa record is linked to a specific employee. Which configuration step is required to establish this link?

A.Configure a business rule that copies the employee ID into the visa object on save.
B.Add a field of type 'Association' on the visa object that references the Employee object.
C.Create a picklist with all employee IDs and use it as a field on the visa object.
D.Add a field of type 'String' and manually enter the employee's user ID.
AnswerB

An Association field type in MDF is specifically designed to create a relationship between a custom object and another object, such as Employee. By defining an association to the Employee object, each visa record can be linked to the correct employee, enabling the object to appear on the employee's profile and supporting reporting. This is the standard mechanism for object-to-object relationships in MDF.

Why this answer

Linking a custom MDF object to the Employee object requires an Association field that references Employee. Associations create the underlying relationship used by the system to display related records, enforce integrity, and support reporting. Picklists, string fields, and business rules cannot create that structural link, so they do not satisfy the requirement.

Exam trap

The trap here is confusing a field that stores an identifier with a field that creates a relationship; only an Association field type builds the object-to-object link.

Full explanation →
68
MCQmedium

An administrator needs to configure a business rule that triggers when an employee's 'Job Information' is updated. The rule should check if the 'Job Title' contains the word 'Manager' and, if so, set the 'Employee Class' to 'Management'. Which base object should the rule be created on?

A.Job Information
B.Global Assignment
C.Employment Details
D.Employee Profile
AnswerA

The rule needs to evaluate the Job Title and set Employee Class, both of which are fields on the Job Information object. Creating the rule on Job Information allows direct access to these fields and triggers on its updates. This is the correct base object for the scenario.

Why this answer

Business rules in Employee Central are created on a specific base object, and the rule can only directly access fields on that object or associated objects. Since the rule must evaluate Job Title and set Employee Class, both on Job Information, the rule should be based on Job Information. This ensures the rule triggers on Job Information updates and has the required fields available.

Exam trap

The trap here is choosing a related object like Employment Details because it also holds employment data, but the rule must be on the object containing the fields being evaluated.

Full explanation →
69
Multi-Selecthard

A consultant is configuring the Employee Central 'Job Information' portlet to support a new business process. The company requires that when an employee's 'Job Classification' changes, the system automatically updates the 'Employee Class' field based on a predefined mapping. The consultant needs to implement this using the appropriate tools. Which two actions should the consultant take to achieve this requirement? (Choose two.)

Select 2 answers
A.Define a picklist for 'Employee Class' and associate it with the 'Job Classification' field to ensure values are consistent.
B.Create a business rule on the Job Information object that triggers on change of the 'Job Classification' field and sets the 'Employee Class' field based on a lookup table.
C.Use a propagation rule to copy the 'Job Classification' value to the 'Employee Class' field.
D.Create a lookup table (MDF object) that maps 'Job Classification' values to 'Employee Class' values, and reference this table in the business rule.
E.Configure a workflow that sends an email notification to the HR administrator whenever the 'Job Classification' changes, prompting them to manually update the 'Employee Class' field.
AnswersB, D

A business rule on the Job Information object can be configured to trigger when the Job Classification field changes. The rule can use a lookup table or conditional logic to set the Employee Class field. This is the standard way to automate field updates based on changes in other fields within Employee Central.

Why this answer

To automatically update Employee Class based on Job Classification changes, a business rule is needed to trigger on the change and perform the update. The rule should reference a lookup table that defines the mapping between the two fields. This combination ensures the update is automatic and based on a predefined mapping, meeting the requirement.

Exam trap

The trap here is assuming that a workflow notification or a propagation rule can automatically update a field based on a mapping, when in fact a business rule with a lookup table is required.

Full explanation →
70
MCQhard

A consultant is configuring the 'Job Information' portlet and needs to ensure that when an employee's 'Employee Class' changes from 'Regular' to 'Temporary', the system automatically updates the 'Pay Scale Group' to a default value. The Pay Scale Group field is a foundation object. Which configuration should the consultant use?

A.Set up a scheduled job that periodically scans employees with Employee Class 'Temporary' and updates their Pay Scale Group.
B.Configure a default value for Pay Scale Group in the Job Information object definition, and use a picklist dependency to change it when Employee Class changes.
C.Use a workflow rule that triggers on Employee Class change and sends a notification to the HR administrator to update Pay Scale Group manually.
D.Create a business rule on the Job Information object that triggers on change of Employee Class and sets the Pay Scale Group to a specific value using a 'Set' action.
AnswerD

A business rule triggered on the change of Employee Class can conditionally set the Pay Scale Group. This is the appropriate method to automatically update a field based on another field's change. The rule can use a 'Set' action to assign a default Pay Scale Group when the condition is met, ensuring data consistency without manual intervention.

Why this answer

The correct solution is to create a business rule on Job Information that triggers when Employee Class changes and uses a 'Set' action to assign the appropriate Pay Scale Group. This ensures the field is updated automatically and immediately, maintaining data integrity and reducing manual effort.

Exam trap

The trap here is assuming that picklist dependencies or default values can dynamically set a field value on change, when they only filter or apply at creation.

Full explanation →
71
MCQeasy

An HR administrator is configuring the Employee Central Foundation Object 'Legal Entity' for a new subsidiary. The company requires that the 'Legal Entity' field be automatically determined based on the employee's company and location, without manual selection. Which feature should the administrator configure to meet this requirement?

A.Configure the 'Legal Entity' field as a required field on the Job Information portlet.
B.Create a business rule on the Job Information object that sets Legal Entity based on the employee's Company and Location.
C.Use a propagation rule on the Job Information object to derive Legal Entity from Company and Location.
D.Set up a business rule that triggers on the Legal Entity object and populates the field based on company and location.
AnswerB

A business rule on the Job Information object can evaluate the values of Company and Location and then assign the appropriate Legal Entity. This is the standard method to automate field population based on multiple conditions. It ensures consistency and reduces manual errors in employee data.

Why this answer

The correct solution is to create a business rule on the Job Information object that derives the Legal Entity from the employee's Company and Location. This rule can be triggered on save or change, automatically setting the Legal Entity field. This approach leverages Employee Central's business rule framework to enforce data consistency and reduce manual entry.

Exam trap

The trap here is assuming that configuring the field as required or using propagation rules will automatically populate it, when actually a business rule is needed for conditional logic.

Full explanation →
72
MCQmedium

A company is implementing Employee Central and needs to ensure that when an employee's job information is updated, the system automatically recalculates the employee's benefits eligibility. The benefits eligibility is determined by a combination of the employee's job classification, pay grade, and service date. Which tool should the administrator use to configure this automatic recalculation?

A.Business rule on the Job Information object with an onSave trigger.
B.Scheduled job to run nightly and update benefits eligibility.
C.Business rule on the Benefits object with an onChange trigger.
D.Workflow on the Job Information object to route for approval.
AnswerA

A business rule on the Job Information object with an onSave trigger is the correct tool. It allows the system to evaluate the employee's job classification, pay grade, and service date whenever job information is saved, and then trigger the benefits eligibility recalculation. This ensures the recalculation happens automatically upon updates.

Why this answer

A business rule on the Job Information object with an onSave trigger is the appropriate tool to automatically recalculate benefits eligibility when job information is updated. It can evaluate multiple fields and trigger the necessary calculations or updates to benefits eligibility.

Exam trap

The trap here is assuming that a workflow or scheduled job can handle automatic recalculations, when actually a business rule on the relevant object is needed for real-time updates.

Full explanation →
73
MCQhard

A consultant is configuring a custom MDF object 'EmployeeProjectAssignment' to track multiple project assignments per employee. The object has a field 'ProjectName' and a field 'EmployeeID'. The requirement is that an employee cannot be assigned to the same project more than once. Which configuration should the consultant use to enforce this?

A.Create a composite unique key on the combination of 'EmployeeID' and 'ProjectName'.
B.Use a 'Picklist' for ProjectName and restrict values to a predefined list.
C.Set the 'ProjectName' field as a required field and enable 'Unique' on it.
D.Create a business rule that checks for existing records before saving a new assignment.
AnswerA

A composite unique key ensures that the combination of EmployeeID and ProjectName values is unique across all records of the object. This directly prevents duplicate assignments of the same employee to the same project. In MDF, you can configure a unique key by selecting multiple fields as part of a single unique constraint. This is the correct approach to enforce the business rule at the data level, ensuring data integrity without relying on user vigilance or complex validation rules.

Why this answer

To prevent an employee from being assigned to the same project more than once, a composite unique key on the combination of EmployeeID and ProjectName is the appropriate configuration. This enforces uniqueness at the data level, ensuring that no two records can have the same employee and project combination. It is a straightforward, declarative method supported by MDF that does not require custom code or complex business rules.

Exam trap

The trap here is thinking that a unique constraint on a single field like ProjectName would solve the problem, when it would actually prevent different employees from sharing the same project.

Full explanation →
74
MCQmedium

An administrator is configuring the 'Position' MDF object in Employee Central. The company wants to ensure that when a position is created, the 'Position Title' is automatically populated based on the selected 'Job Code'. The administrator needs to set up this defaulting logic. Which feature should the administrator use?

A.Create a business rule on the Position object that triggers on change of Job Code and sets the Position Title.
B.Set up a picklist dependency between Job Code and Position Title.
C.Use the 'Copy' function in the Position object to copy the title from Job Code.
D.Configure a default value for Position Title in the Position object definition.
AnswerA

A business rule on the Position object can trigger when the Job Code field changes and then set the Position Title based on a lookup or mapping. This is a common use case for business rules to automate data entry and ensure consistency. The rule can reference the Job Code's associated title from the Job Code object and populate the Position Title field.

Why this answer

Business rules on MDF objects can trigger on field changes and perform actions such as setting another field's value. By triggering on the Job Code change and using a lookup to retrieve the corresponding title, the rule can automatically populate the Position Title. This ensures consistency and reduces manual entry errors.

Exam trap

The trap here is assuming that picklist dependencies or default values can dynamically populate fields based on other field selections, when they only control available options or set static values.

Full explanation →
75
MCQeasy

An HR administrator needs to create a new employee in Employee Central. The employee will be based in Germany and will report to a manager in the same country. Which of the following is the minimum set of data required to create the employee record?

A.Employee ID, First Name, Last Name, Date of Birth, and Job Information with Company, Location, and Job Title.
B.Employee ID, First Name, Last Name, Hire Date, and Job Information with Company, Location, and Job Title.
C.Employee ID, First Name, Last Name, Hire Date, and Job Information with Company, Business Unit, and Job Title.
D.Employee ID, First Name, Last Name, Hire Date, and Job Information with Company, Location, Job Title, and Pay Grade.
AnswerB

Employee Central requires core personal data (Employee ID, First Name, Last Name, Hire Date) and Job Information (Company, Location, Job Title) to create an employee record. These fields are typically mandatory in the standard configuration. Without them, the employee cannot be properly hired or placed in the organizational structure. This set represents the minimum required for a successful hire.

Why this answer

The minimum data required to create an employee in Employee Central includes personal information (Employee ID, First Name, Last Name, Hire Date) and Job Information (Company, Location, Job Title). These fields are standard mandatory fields in the Hire and Job Information portlets. Other fields like Pay Grade, Date of Birth, or Business Unit may be optional depending on configuration.

Therefore, the set without Pay Grade is the correct minimum.

Exam trap

The trap here is assuming that additional fields like Pay Grade or Date of Birth are mandatory when they are often optional in standard configuration.

Full explanation →

Page 1 of 2

Page 2

All pages

12

Practice C_THR81 by domain

Target a specific domain to shore up weak areas.

Employee Central Core
See all domains with question counts →