Enablement Configuration Setting for Stories in People Analytics

[Smitha]

Have you been wondering how to ensure all the enablement configurations are set up in SAP SuccessFactors to ensure Stories in People Analytics are working? Look no further than this IDP - SAP SuccessFactors Stories in People Analytics: Enablement Configurations - and this blog introducing this topic to you.

Let us examine the initial and post-activation enablement configuration settings to ensure Story reports work seamlessly in your SAP SuccessFactors system. For IPS connector details, please read through the Section 5 of the IDP before executing Step 1. If you are still using SF ODATA IPS connector, we recommend you to migrate from ODATA to SCIM IPS connector before initiating the Stories in People Analytics Upgrade Center task.

There are 4 Steps to follow before you can start using Stories in People Analytics, as mentioned below:

Step 1: Enable Stories via Upgrade Center Task

Log in to SuccessFactors > Go to Admin Center> Navigate to Upgrade Center. Choose 'Stories in People Analytics' and upgrade. Check for a successful upgrade via the “View Recently Completed Upgrades” link in the Upgrade Center. Once the task is successfully submitted, you may have to wait for 45-60 minutes for backend configuration jobs to successfully complete. 

                                                         Upgrade Center

Post- Enablement Steps

Step 2: Conditional Authentication configuration for Corporate Identity provider

If your organization does not use Corporate Identity Provider, you can skip to Step 3: IPS user sync. If your organization has Corporate Identity Provider, please follow the below guidelines to add additional settings, validate and ensure configuration in Identity Authentication is compatible to run Story reports.

a) Log on to the Identity Authentication Service as an IAS admin and go to Applications & Resources, select the Applications tab.

b) In the Bundled Applications section, choose the SAP Analytics Cloud tenant (mostly configured as SF Analytics). It is configured either at the same level as the SAP SuccessFactors tenant, or under the SAP SuccessFactors tenant as its child application.

c) Edit the Conditional Authentication details.

d) Ensuring that the set of rules used for the SAP Analytics Cloud tenant and the SAP SuccessFactors tenant are the same. This should be already set in SAP analytics cloud tenant is tagged as a child application to SuccessFactors tenant.

e) In the Default Identity Provider field, select the Identity Provider that you are using to authenticate users on the SAP SuccessFactors tenant, and save the changes.

Go to Identity Providers, select the Corporate Identity Providers tab, and select your corporate identity provider. 

• Ensure that the Forward All SSO Requests to Corporate IdP option in the SINGLE SIGNON section has been disabled.
• Configure Identity Federation, enable the Use Identity Authentication user store option in the User Store section, and save the changes.

Before activating Stories, if you need help with setting up Corporate IdP with IAS / SuccessFactors, please review detailed steps and SF-IAS architecture in the KBA - Configuring SSO between Corporate IdP, Identity Authentication tenant and SuccessFactors.

Step 3: IPS user sync

At this step, it is important to know if your systems are configured with ODATA IPS connector or SCIM IPS connector to synchronize users between SAP SuccessFactors, IAS, and SAP Analytics Cloud tenant.  If you are Using ODATA IPS connector, you will need to ensure below permissions. • Manage Integration Tool- Allow Admin to Access OData API through Basic Authentication • Manage User Employee Export Using SCIM IPS connector? SCIM IPS connector with client certificate authentication, does not have any pre-requisites of permissions.

For a more detailed description of step 3 along with system screenshots, I invite you to read through page 12 of the IDP.

Step 4: Grant Story report permissions

We strongly recommend following the help guide documentation to set up permission related to Story Reports. Some modules (ex. RCM/PM/GM etc.) require additional permissions to ensure a user can report on schema specific data. Link to help guide - Set up Permission for Story report.

There are other topics of interest like the FAQs, important notes on if your systems are configured on SCIM IPS connector and you want to ensure permission-based sync relevant configurations and attribute, performing user synchronization that are mentioned in the IDP.