3638328 - Period Based Delta Transmission - When Updating The Effective As Of Date - Action Code Does Not Update

• The user's profile contains address information or any other effective-dated entity. Changes to this data required specifying a new effective date to reflect when the update should take effect.

• Successfactors
• Compound Employee API

Use Case 1:

• Update the effective as of parameter of an effective dated entity, with no other business data change
• Query the data, the action code will not have changed and will remain NO_Change in the segment metadata

Use Case 2:

• Deletes an address time slice from the profile
• Add the timeslice back but the only difference is the effective as date (only change, no business data change)
• Query the data, the action code will not have changed and will remain NO_Change in the segment metadata

Change Only to "Effective as Of":

• A user profile was updated, changing only the "Effective as Of" date to August 1 to August 3. The last_modified_on timestamp reflects this change, and the payload includes a new start date:

• The action codes are applied to effective-dated segments (like personal_information) as well as to non-effective-dated entities (such as national_id_card). In case of effective-dated segments, the consumer should be aware that the action code doesn’t always resemble the action that has been performed on the UI.

• Even though the last_modified_on timestamp updates and the start date in the payload changes, no action is triggered in the segment because no other properties were modified.
• This is expected behavior in SAP SuccessFactors: segments and workflows typically trigger only when actual data fields (e.g., address, job info) are changed—not when only the effective date is updated.

https://help.sap.com/docs/successfactors-employee-central/employee-central-compound-employee-api/action-codes

compound employee, period delta, NO_Change, Effective As Of , KBA , LOD-SF-INT-CE , Compound Employee API , LOD-SF-INT , Integrations , Problem