A composite association establishes a parent-child relationship where the child (destination) object's lifecycle is dependent on the parent. To enforce this dependency and maintain data integrity, the system validates that the destination object is configured to inherit its effective dating from the parent. The "From Parent" effective dating setting ensures that the child object's effective-dated records are synchronized with the parent's records. The child object's effective start date is automatically derived from the corresponding parent record, making this configuration mandatory for a valid composite association.

B. "Basic" effective dating would allow the destination object to have its own independent timeline, which violates the principle of a composite relationship.

C. "Multiple Changes Per Day" also creates an independent timeline for the destination object, which is not permissible for a dependent composite child.

D. "None" signifies a non-effective-dated object. A composite child must be able to align with a potentially effective-dated parent, making this option invalid.

1. SAP Help Portal - Implementing the Metadata Framework (MDF): In the section "Creating an Association

" under the sub-topic for "Composite" associations

the documentation states: "The destination object must be an effective-dated object with the Effective Dating property set to From Parent." This is a mandatory system validation. (Source: SAP SuccessFactors HXM Suite

Implementing the Metadata Framework (MDF) Guide

Document Version: 2H 2024

Chapter: "Configuring Object Associations").

2. SAP Help Portal - MDF Object Relationship: The guide on MDF development principles explains that for one-to-many composite relationships

the child object's effective dating must be set to 'From Parent' to ensure that the child records are always tied to a specific version of the parent record. (Source: SAP SuccessFactors HXM Suite

Implementing the Metadata Framework (MDF) Guide

Document Version: 2H 2024

Chapter: "Fundamentals of the Metadata Framework"

Section: "Effective Dating").

To enable a custom Metadata Framework (MDF) object for Employee Self-Service (ESS), two fundamental configurations are required. First, the object's data must be directly linked to the employee. This is achieved by setting the externalCode field's data type to "User," making the employee's unique user ID the primary key for each record. Second, the employee needs an interface to view or edit this data. This is accomplished by creating a Configuration UI for the object, which defines the layout and fields visible to the end-user in their profile or as a self-service screen.

A. Set the externalName field to Data Type = User.

The externalName field is intended for a human-readable label for the object instance, not as the primary key linking it to a user.

B. Create a Valid When association for the object.

While associations link objects, the primary method to enable ESS for a parent object is setting externalCode to "User," not creating an association.

1. SAP SuccessFactors HXM Suite | Implementing the Metadata Framework (MDF) | Document Version: 2H 2023:

Section: Fields of a Generic Object. This section details the properties of object definition fields. It specifies that for an object to be used in Employee Profile (a primary ESS scenario)

the externalCode field must have its Data Type set to 'User'. This directly ties an instance of the object to a specific employee.

Section: Creating a User Interface for a Generic Object. This chapter explains that to display and interact with MDF object data

a user interface must be created using the "Manage Configuration UI" tool. It states

"Without a UI

you can't use the object on any page." This is essential for any self-service functionality.

The Set action is the primary function used within the THEN statement of a business rule to perform data propagation. Propagation in SAP SuccessFactors Employee Central involves automatically populating target fields with values from a source object. For example, when a position is selected in an employee's Job Information, a rule uses the Set action to copy values like department, division, and location from the Position object to the corresponding fields in the employee's Job Information record. This action directly assigns a value to a field, which is the core mechanism of propagation.

A. Execute: This action is used to trigger another business rule from within the current rule; it does not directly populate a field's value.

B. Raise: This action is used to display an error, warning, or informational message to the user, primarily for data validation purposes.

D. Create: This action is used to generate a new data record, such as a new recurring pay component, rather than populating a field in an existing record.

---

1. SAP SuccessFactors Employee Central Implementation Guide: "Implementing Business Rules in SAP SuccessFactors" (Document Version: 2H 2023). In the section "Rule Actions (THEN Statement)

" the Set action is explicitly defined for assigning a value to a field. Examples of propagation rules throughout the guide consistently use the Set action to copy data from foundation objects to employee data fields. (Refer to the chapter on "Common Use Cases for Business Rules in Employee Central

" specifically the sub-section on propagation from Position).

2. SAP Help Portal - Business Rules in SAP SuccessFactors: The official documentation describes the Set action as the method to "set the value of a field to a specific value

to the value of another field

or to a value derived from an expression." This is the exact functionality required for propagation. (See documentation for "Rule Action Types").

Alert Notifications in SAP SuccessFactors Employee Central are configured using Business Rules to automatically notify relevant stakeholders about important data changes or upcoming events. While rules can be built on many entities, Job Information and Pay Component Recurring are fundamental entities for this functionality. Changes in Job Information (such as promotions, transfers, or terminations) and Pay Component Recurring (such as salary adjustments) represent critical employee events that frequently require alerts for managers, HR business partners, or payroll administrators to take action.

A. Address Information: While an alert can be configured for an address change, it is not considered a primary event-driving entity for critical system alerts compared to core job and compensation data.

D. Personal Information: Similar to address information, alerts for changes in personal data (e.g., name change) are possible but are less central to core HR event management than job and pay-related changes.

1. SAP Help Portal: Implementing Business Rules in SAP SuccessFactors

Document Section: Rule Scenarios in Employee Central > Alerts

Content Reference: This section provides canonical examples for creating alert rules. The examples consistently use base objects like Job Information (for events like contract end date

probation period end) and Compensation Information (which includes Pay Component Recurring) to demonstrate how to trigger alerts for critical HR events. This highlights their primary role in the alert mechanism.

2. SAP Help Portal: Employee Central Master Guide

Document Section: Data Objects and Employee Central > Employee Data > People Profile Blocks > Job Information and Compensation Information

Content Reference: The documentation describes Job Information and Compensation Information as foundational blocks for an employee's record. The event-driven nature of these blocks (using Event and Event Reasons) makes them the logical and most common source for triggering workflows and alert notifications for significant employment changes.

SAP SuccessFactors Employee Central is built on an effective-dated data model. Each data change with a unique effective date is treated as a separate and distinct transaction, creating a new "time slice" in the employee's record. The first transaction for January 15 and the second for January 30 are seen by the system as two independent, valid events. Consequently, a separate workflow is triggered for each transaction. The system is designed to manage multiple future-dated changes concurrently, so both workflows will proceed through their respective approval processes independently without canceling or rejecting one another.

A. The system will reject both workflows.

This is incorrect because the system is designed to handle multiple, non-conflicting, future-dated transactions for the same employee.

B. The system will cancel the second workflow.

This is incorrect. A later-dated transaction does not invalidate a previously initiated one; it simply creates a new data record for a future date.

C. The system will cancel the first workflow.

This is incorrect. A future-dated transaction does not retroactively cancel a pending transaction with an earlier effective date.

1. SAP SuccessFactors Employee Central Documentation - Implementing Employee Central Core:

Section: "Employee Data and Effective-Dating"

Content: This guide explains that Employee Central entities are effective-dated. It details how changes to an employee's data create new time slices with specific start dates. The system stores a complete history

allowing multiple future-dated records to exist simultaneously. This foundation confirms that two changes with different effective dates (Jan 15 and Jan 30) are stored as two distinct records.

2. SAP SuccessFactors Employee Central Documentation - Implementing and Managing Workflows in SAP SuccessFactors:

Section: "How Workflows are Triggered"

Content: This documentation specifies that workflows are triggered by events

such as saving changes to an employee's Job Information or Compensation Information. Since two separate "save" events occur for two different effective dates

the system logically triggers two independent workflows

one for each event. There is no standard logic described that would cause one workflow to cancel the other in this scenario.