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

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.

• SAP SuccessFactors HCM Suite
• People Analytics
• Story Report

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

              },
      
      

   6. IAS and SAC tenants should have the correct Source Systems maintained:
      
      
      

Changes Required in IAS:

• • • People Analytics (SAC) for SF-A – should be configured with customAttribute1 as Subject Name Identifier
    • People Analytics (SAC) for SF-B – should be configured with customAttribute2 as Subject Name Identifier

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.
• personGUID_A or personGUID_B are only used as unique identifiers. These can be anything, but it needs to match between SF/IAS and SAC tenants
• Constant customAttbiute in the IAS transformation corresponds to Subject Name Identified in IAS
• The number in IAS transofrmation next to attirbutes corresponds to the place in User Management (starting from 0, being customattribute1)
  

2912865 - [Main KBA] Unable to access Story reports - People Analytics

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 , Stories in People Analytics , How To