3751870 - FOLocation & FOCorporateAddressDEFLT IDs

Symptom

Location (FOLocation) and Address object IDs (FOCorporateAddressDEFLT) are unique and do have a 1-1 relationship.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP SuccessFactors Employee Central

Reproducing the Issue

1. Query the Location ID and Address ID via Integration Center to confirm.

Cause

This is expected behavior.

Resolution

Location and Address are stored in different database tables and are designed to have independent IDs. They are not expected to consistently match.

Both entities use separate database sequences: location_s and address_s, each starting at 1. These sequences may appear aligned only in specific scenarios—such as when an address is created directly through the Location creation process.

However, the Address table is shared across multiple system components and business processes.

For example, creating a home address or other address-related records will also generate entries in the Address table. In such cases, only the address_s sequence is incremented, while the location_s sequence remains unchanged.

As a result, over time the values of these two sequences will naturally diverge, and it is expected that Location IDs and Address IDs will not match.

Keywords

INC25960147 , FOCorporateAddressDEFLT, FOLocation, integration, address ID, manage organisation pay and job structures, foundation object, odata api. , KBA , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , LOD-SF-INT , Integrations , Product Enhancement

Product

SAP SuccessFactors HCM Core 2511

3751870 - FOLocation & FOCorporateAddressDEFLT IDs - Behavior of object IDs