Symptom
- This article provides guidance on the necessary configuration changes for scenarios where two SuccessFactors instances are connected to a single IAS tenant and SAP Aanlytic Cloud is enabled in both instances.
- This configuration is typically required when more than one test SuccessFactors system (Preview and Development) is linked to one TEST IAS system.
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 HCM Suite
- Identity Authentication
- Identity Provisioning
- Story Reports
Resolution
For a best performance and experience with the integration, it's highly recommend to have one IAS tenant to each SuccessFactors instance. To remap the SuccessFactors instance, follow the instructions outlined in KBA 3089598 - How to change an existing IAS & IPS integration with a SuccessFactors instance?
However, to map two SuccessFactors tenants to one IAS, follow the steps below. The transformations below apply only for this specific scenario.
INITIAL NOTES
- Consider an example where two SuccessFactors instances (SF-A & SF-B) are connected to one IAS tenant.
- If there are more than two SuccessFactors instances connected to one IAS tenant, you can modify their personGUID field & customAttribute with the same logic, with different suffixes.
- personGUID_A or personGUID_B are only used as unique identifiers. These can be anything, but they need to match between SF/IAS and SAC tenants
- Constant customAttribute in the IAS transformation corresponds to Subject Name Identified in IAS
- The number in IAS transformations next to attributes corresponds to the place in User Management (starting from 0, being customAttribute1)
PRE-REQUISITES
- Make sure users are either the same across SuccessFactors instances or completely different. If users have different emails between instances, syncing issues might occur.
- IAS and SAC tenants should have the correct Source Systems maintained.
CONFIGURATION STEPS
- Add the transformations available in the Transformations table below to the corresponding system depending if it's using ODATA API or SCIM API
- In IAS, go to Identity Provisioning
- Select Source Systems or Target Systems
- Select the system and click on Transformations
- Switch to Jason editor by clicking on icon {...}
- Click on edit and add the transformations bellow:
- SF-A source system: copy the corresponding transformations from Source System Configuration - SF-A
- SF-B source system: copy the corresponding transformations from Source System Configuration - SF-B
- SAC-A (SAP Analytics Cloud tenant mapped to SF-A): copy the transformations from Target System Configuration - SAC-A
- SAC-B (SAP Analytics Cloud tenant mapped to SF-B): copy the transformations from Target System Configuration - SAC-B
- IAS target system (CustomAttribute1 and CustomAttribute2): copy the corresponding transformations from Target System Configuration - IAS
- Change the Subject Name Identifier for each SAC system:
- SAP Analytics Cloud (SAC) for SF-A – should be configured with customAttribute1 as Subject Name Identifier
- SAP Analytics Cloud (SAC) for SF-B – should be configured with customAttribute2 as Subject Name Identifier
If you’re unsure of which SAP Analytics Cloud tenant is linked with which SuccessFactors tenant, you can find the SAP Analytics Cloud tenant URL in SuccessFactors provisioning under Company Settings > “SAP Analytics Cloud Application URL”. Only certified Partners and SAP Support have access to provisioning, contact your partner or create a support ticket if you need assistance in determining this.
TRANSFORMATIONS
|
Source System Configuration - SF-A | |
|
ODATA API (sf.api.version = 1) |
{ "sourcePath": "$.personKeyNav.perPersonUuid", "targetPath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_A']" }, |
|
SCIM API (sf.api.version = 2) |
{ "sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid']", "optional": true, "targetPath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_A']" }, |
|
Source System Configuration - SF-B | |
|
ODATA API (sf.api.version = 1) |
{ "sourcePath": "$.personKeyNav.perPersonUuid", "targetPath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_B']" }, |
|
SCIM API (sf.api.version = 2) |
{ "sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid']", "optional": true, "targetPath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_B']" }, |
|
Target System Configuration - SAC-A | |
|
Transformation Rule |
{ "sourcePath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_A']", "targetPath": "$.userName" }, |
|
Supported Transformation (SCIM API) |
{ "condition": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_A'] EMPTY false", "sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_A']", "targetPath": "$.userName" }, |
|
Target System Configuration - SAC-B | |
|
Transformation Rule |
{ "sourcePath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_B']", "targetPath": "$.userName" }, |
|
Supported Transformation (SCIM API) |
{ "condition": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_B'] EMPTY false", "sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_B']", "targetPath": "$.userName" }, |
|
Target System Configuration - IAS | |
|
SF Version 1 - CustomAttribute1 and CustomAttribute2 |
{ "sourcePath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_A']", "optional": true, "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][0]['value']" }, { "condition": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_A'] EMPTY false", "constant": "customAttribute1", "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][0]['name']" }, { "sourcePath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_B']", "optional": true, "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['value']" }, { "condition": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_B'] EMPTY false", "constant": "customAttribute2", "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['name']" }, |
|
SF Version 2 - CustomAttribute1 and CustomAttribute2 |
{ "sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_A']", "optional": true, "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][0]['value']" }, { "condition": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_A'] EMPTY false", "constant": "customAttribute1", "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][0]['name']” }, { "sourcePath": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_B']", "optional": true, "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['value']" }, { "condition": "$['urn:ietf:params:scim:schemas:extension:successfactors:2.0:User']['perPersonUuid_B'] EMPTY false", "constant": "customAttribute2", "targetPath": "$['urn:sap:cloud:scim:schemas:extension:custom:2.0:User']['attributes'][1]['name']" }, |
See Also
Keywords
IAS, SuccessFactors, multiple, tenant, instance, mapping, sync, issue, override, custom, attribute, personGUID, IPS, transformation, SAC, story reports, , KBA , LOD-SF-PLT-IAS , Identity Authentication Services (IAS) With BizX , LOD-SF-ANA-SAC , Stories in People Analytics , How To
Product
Attachments
| Pasted image.png |
| Tenant Mapping Guidelines- 07-17.pdf |
| Pasted image.png |
| Pasted image.png |
| Tenant Mapping Guidelines- 07-17.pdf |
SAP Knowledge Base Article - Public