3415955 - Story Reports in SAP SuccessFactors to be Provisioned for your tenant [auto-enablement]

Symptom

This document will guide you with your Journey of Stories in Story Reporting & FAQ.

You would have received the below notification:

“[Story Reports in SAP SuccessFactors to be Provisioned for your tenant] SAP SuccessFactors HCM | DB3 (HCM_D22), FR3 (HCM_D33), SH6 (HCM_D30), XG7 (HCM_D52), XG9 (HCM_D50), XGB (HCM_D55), XGF (HCM_D80), XGH (HCM_D57), XM2 (HCM_D41), XM3 (HCM_D68“.

Dear colleagues,

You are receiving this email as a customer who has moved their authentication for the HCM Platform over to SAP Identity Authentication and Provisioning Services (IAS/IPS) but has yet to enable our Story reporting solution.

Story is the Reporting tool of choice for our customers to build transactional reports for end-users. We introduced Story Reports halfway through 2020, and we have heavily invested in our customers’ success with this functionality. SAP SuccessFactors has always had the viewpoint that Story Reports becomes the main solution for our customers for their operational reporting on the day-to-day transactional data within SAP SuccessFactors.

We have continued to add features and expand data coverage within Story Reports, and we have begun the deprecation of some of our Legacy Reporting tools. Please review our Customer Community blog announcement.

Next Steps

As your tenant listed below is ready for the Story upgrade, we will be completing the technical upgrade on your behalf to allow you to begin your journey with the Story reporting solution. Once completed, within 3-5 days, we will notify you via an email communication and provide a checklist of steps to be completed in Role-Based Permissions and the user sync within IPS. After these steps are completed, your organization will be ready to utilize Stories in your instance.

SAP SuccessFactors will begin provisioning Story Report instances for customers using the following schedule:

Non-Production tenants (Preview or Test on Production servers): 15-June to 24-June
HCM Production tenants: 25-June to 29-June

You will receive a notification 3-5 days after your tenant has had Story Reports provisioned.

Environment

SAP SuccessFactors HCM Suite
- Analytics & Reporting (Ad Hoc, YouCalc, ORD)
  - Story Reporting
    - SF Admin configurations (Security Center, Provisioning)

Cause

SAP is taking the action of running the Upgrade Center task for Story Reports in your SAP SuccessFactors tenant.

This specific upgrade DOES NOT modify anything else within the BizX suite (i.e. SAP SuccessFactors tenant) and absolutely no impact on reporting functionality as Story Reports cannot even be used after SAP completes the upgrade. Primarily, it still requires RBP (permissions) to be set and a User Sync from IPS to bring users from BizX into Story Reports (i.e. embedded SAP Analytics Cloud tenant). As the customer, you have the complete control of when users can see or even access Story Reports as an option in the SAP SuccessFactors Preview or Test environment.

This upgrade merely completes creating SAP Analytics Cloud instance and integrating with your SAP SuccessFactors tenant, and nothing more as you still have to undergo at least 2 steps before Story Reports is ready to use. For more details on post enablement steps, kindly refer to SAP SuccessFactors Story Reporting Enablement Configurations help guide.

Hopefully this clarity helps and eliminates any concern with the update sent via email.

Resolution

Please refer SAP SuccessFactors Stories Enablement Configuration V1.0 which will help you will complete end-to-end configuration required for Enabling and using Story.

To learn more about Story Reporting and the resources available to support you through your transition away from our legacy Reporting tools, please review the content listed below:

If you encounter a technical issue while enabling Stories, submit an incident within the SAP Support Portal, using the component LOD-SF-ANA-. If you have further questions, please feel free to visit our SAP SuccessFactors Customer blog to post your questions and any feedback on this topic.

FAQ:

Is SAP doing end-to-end Story Configuration?
- There are 4 Steps to activate Story Reporting as mentioned below:

- - Step 1: Enable Stories via Upgrade Center Task
  - Step 2: Conditional Authentication configuration for Corporate Identity provider
  - Step 3: IPS user sync
  - Step 4: Grant Story report permissions

- Currently only Step 1 is performed by SAP.
- Step 2-4 are to be performed by Customer
- Refer Page 6 of SAP SuccessFactors Story Reporting Enablement Configuration V1.0
What actions I should take before using Stories?
- IPS user sync
  - If you are using Corporate IDP, please make sure the IDP settings are rightly configured.
- Grant Story report permissions
Will auto-enablement of Story impact any other functionality of SF?
- Enabling Story will not impact any other functionality or existing Report types.
- You could continue to use SF and all its features as-is.
Is Story accessible by end users as soon as it is enabled?
- Unless the post enablement steps, mentioned in FAQ #1 are performed, no user would be able to use Story.
Will I receive any notification once the auto-enablement is complete?
- Once completed, we will notify you via an email communication and provide a checklist of steps to be completed in Role-Based Permissions and the user sync within IPS.

Keywords

Stories, Provisioned, Preview, Test, Environment, notification, email , KBA , LOD-SF-ANA-SAC-ADM , SF Admin configurations (Security Center, Provisioning) , LOD-SF-ANA-SAC , Stories in People Analytics , How To

Product

SAP SuccessFactors HCM Core all versions