SAP SuccessFactors Employee Central uses a transaction sequence number (seq-number) to manage multiple data changes for an employee on the same effective date. When more than one record is created for the same day (e.g., a promotion and a pay rate correction), the system assigns an incremental sequence number to each record. The record with the highest sequence number is considered the most recent and active record for that specific day, ensuring a clear and ordered history of events.

A. Last modified timestamp: This is a technical audit field that records when the data was last saved. It is not the primary business key used by the system to determine the logical sequence of records.

C. Created Date: This field indicates when the record was initially created and cannot be used to order multiple records that are created on the same day for the same effective date.

D. Event: An event (e.g., Promotion, Transfer) specifies the reason for a change. It does not provide a mechanism to order multiple, distinct changes that occur on the same day.

1. SAP SuccessFactors Employee Central OData API: Reference Guide (H2 2025): In the documentation for the EmpJob entity (which corresponds to Job Information), the field seqNumber is described as: "The sequence number of the record. It is used to distinguish between multiple records with the same start date." This directly confirms its purpose for sequencing. (Access via SAP Help Portal).

2. Implementing Employee Central Core Guide: In the chapter on "Fundamentals of Employee Central," the section on "Effective Dating" explains how the system handles data over time. It details that for records with the same effective start date, the sequence number is the determining factor for ordering. (Access via SAP Help Portal, specific section on effective-dated entities).