SAP Knowledge Base Article - Public

3836871 - IPS Sync Job Shows User Updates from SuccessFactors to IAS with No Actual Data Changes

Symptom

  • When running an IPS (Identity Provisioning Service) sync job to synchronize users from SuccessFactors to IAS , the sync job log shows that certain users were updated.
  • However, no data changes were made to those users' data in SuccessFactors.
  • After verifying in IAS, the user data in IAS also shows no actual changes.

Environment

SAP SuccessFactors HCM Core

Reproducing the Issue

  1. Configure an IPS sync job with SuccessFactors as the source and IAS as the target.
  2. Ensure the source system properties use OData API (User entity).
  3. Run the sync job without making any changes to user data in SuccessFactors.
  4. Observe the sync job log — some users appear as updated.
  5. Verify in IAS — the user data has not changed.

Cause

The affected users have Multiple Employment records in SuccessFactors.

When the IPS source system is configured to use the OData API, it reads data based on the User entity. The OData API retrieves all employment records for a user, including all multiple employment entries. As a result, the system detects data differences across these multiple employment records and marks the user as "updated" — even though no actual user attribute has changed.

This is a known characteristic of the OData API's data reading behavior with Multiple Employment.

Resolution

There is no impact for user authentication and user sync between SF with IAS.

If you don't want to update those user's data in IAS, please switch the IPS source system configuration from OData API to SCIM API.

The SCIM API reads data based on the Person entity (or User Account table) rather than the User entity. It does not aggregate data across multiple employment records. Therefore, no false updates will be triggered when users have Multiple Employment and no data has actually changed.

Steps:

  1. Navigate to your IPS source system configuration for SuccessFactors.
  2. Update the API type property to use SCIM API instead of OData API.
  3. Re-run the sync job and verify that no spurious updates appear for users with Multiple Employment.

Note: Validate that all required user attributes are correctly mapped when switching to SCIM API, as the entity structure differs from OData API.

Keywords

OData API,ips user sync,updated entity in IAS , KBA , LOD-SF-PLT-IAS , Identity Authentication Services (IAS) With BizX , LOD-SF-PLT-MNG , Manage user Issues , LOD-SF-INT , Integrations , Problem

Product

SAP SuccessFactors HCM Core all versions