As Syensqo continues to modernize its operations and expand its digital ecosystem, SAP solutions are playing an increasingly central role across multiple business domains. With the organisation’s landscape becoming more cloud-based and integrated, maintaining a consistent identity framework across systems is essential.
By using the field Person ID from Success Factors to map to the Global ID field in IAS/IdDS via IPS, we will be able to maintain the unique user identifier across all downstream applications without the need to maintain complex local user mapping routines.
As a minimum, the below user attributes will be mapped from Success Factors and transformed to IAS/IdDS.
The transformation will also need to consider other attributes such as group association and other user attributes as these can be used for filtering, conditional authentication and other security policies.
Application | Field Name IAS | IAS Technical Name | Source | Success Factors | Example |
SAP CIS | Global User ID | TBC | SF | Person ID | XXXX1234 |
SAP CIS | Status | TBC | SF | status | Active |
SAP CIS | First Name | TBC | SF | First name | abcd |
SAP CIS | Last Name | TBC | SF | Last name | Xxxxolola |
SAP CIS | TBC | SF |
The Global ID represents a single unique user identifier across all systems and platforms for the user.
The transformation logic in IPS is crucial for creating and maintaining the global user ID. By mapping attributes consistently, IPS ensures that the correct global user ID is assigned and used, linking user identities and attributes across different systems, even if the user's username or email differs in each system.
Global ID Mapping Architecture Diagram
