SAP Knowledge Base Article - Public

2954815 - Configuring IAS and IPS when two SuccessFactors instances are mapped to one IAS tenant - People Analytics

Symptom

This article explains the configuration changes required when:

  • You have two SuccessFactors instances connected to one IAS tenant
    and
  • Want to enable People Analytics in both of the instances

This scenario will generally popup for customers with more than one test SuccessFactors system (Preview & Dev) 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 HXM Suite
  • People Analytics
  • Story Report

Resolution

  • We will consider an example where two SuccessFactors instances (SF-A & SF-B) are connected to one IAS tenant.





  • Changes required in the transformation template are stated only for such a scenario.
  • However, if there are more than two SuccessFactors instances connected to one IAS tenant, you can modify their perosnGUID field & customattribute with the same logic, with different suffixes.


  • Changes Required in IPS:
    1. Source system configuration for SF-A:


                  {

                    "sourcePath": "$.personKeyNav.perPersonUuid",

                    "targetPath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_A']"

                  },

    2. Source system configuration for SF-B:

               {

                    "sourcePath": "$.personKeyNav.perPersonUuid",

                    "targetPath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_B']"

                  },

    3. Target system configuration for SAC-A (People Analytics tenant mapped to SF-A):


                 {

                      "sourcePath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_A']",

                      "targetPath": "$.userName"

                  },

    4. Target system configuration for SAC-B (People Analytics tenant mapped to SF-B):


                 {

                      "sourcePath": "$['urn:sap:cloud:scim:schemas:extension:sfsf:2.0:User']['personGUID_B']",

                      "targetPath": "$.userName"

                  },

    5. Target system configuration for IAS:

             {

                "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']"

              },

  • Changes Required in IAS:


    • People Analytics (SAC) for SF-A – should be configured with customAttribute1 as NameID in SAML assertion
    • People Analytics (SAC) for SF-B – should be configured with customAttribute2 as NameID in SAML assertion



      If you’re unsure of which People Analytics tenant is linked with which SuccessFactors tenant, you can find the People Analytics tenant URL in SuccessFactors provisioning under company settings > “SAP Analytics Cloud Application URL”

Note: For a best performance and experience with the integration, we highly recommend to have one IAS tenant to each SuccessFactors instance.

Keywords

IAS, SuccessFactors, multiple, tenant, instance, mapping, sync, issue, override, custom, attribute, personGUID, IPS, transformation , KBA , LOD-SF-PLT-IAS , Identity Authentication Services (IAS) With BizX , LOD-SF-ANA-SAC , People Analytics (Analytics Cloud for SF) , How To

Product

SAP SuccessFactors HXM Suite all versions

Attachments

Pasted image.png
Tenant Mapping Guidelines- 07-17.pdf