Administering Story Reporting


After completing this lesson, you will be able to:

  • Enable Story Reports

Story Report Enablement in SAP SuccessFactors

Story is available as a type of report in Report Center, and you can enable Story from the Upgrade Center after the prerequisites are met.

To enable Story Reports, your instance needs to meet the following requirements:

  • Identity Authentication Service (IAS) and Identity Provider Service (IPS) must be configured with your SAP SuccessFactors tenant.
  • Sync users from SAP SuccessFactors HXM Suite to SAP Identity Authentication Service Now, complete the following steps:
    1. Navigate to the Upgrade Center.
    2. In the <Filter By> list, select Analytics.
    3. In the Recommended Upgrades section, select the Stories in People Analytics upgrade link.
    4. Choose the Upgrade Now button, and on the confirmation pop-up select Yes.

Enabling and configuring an Identity Authentication Service is outside of the scope of this document. Please refer to supporting documentation on the SAP Help Portal or work with your Implementation partners for the configuration.

User Syncing

Users that will be accessing story reports must be enabled in the SAP Analytics Cloud (SAC) solution. Before you perform the sync, verify the account has the appropriate permissions in RBP. The account must have:

  • Manage Integration ToolsAllow Admin to Access OData API through Basic Authentication.
  • Manage UserEmployee Export.

IPS Syncing

To perform the IPS Sync, complete the following steps:

  1. Go to your Identity Provider Service portal.

    The details for the Identity Provider Service portal follows the IAS configuration.If you do not have the Identity Provider Service portal information, contact SAP Cloud Support.

  2. Navigate to Target Systems to enable the newly configured SAP Analytics Cloud tenant.
  3. Select the tenant, select the Edit icon, choose Enable, and on the confirmation pop-up message that appears, choose OK. The status of the tenant changes to Enabled.
  4. Navigate to Source Systems and select your source SAP SuccessFactors tenant.
  5. On the Properties tab for the user that appears, ensure the role-based permissions mentioned in the Prerequisites have been enabled.
  6. Go to the Jobs tab, and for the Read Job type, choose Run Now.

You can track the progress of the read job from Job Logs. When the read job completes, the user sync from SAP SuccessFactors HXM Suite to SAP Analytics Cloud is complete.

User Account Verification in SAP Analytics Cloud

For a user to be able to create Story Reports, their user information must be successfully synchronized to the SAP Analytics Cloud (SAC) instance and be assigned the appropriate role. When this does NOT occur, the result is a common issue where the user is unable to successfully create a new Story report. After selecting a new story report, the webpage is stuck in a blank loading screen or errors are displayed.

To validate the user exists and has the proper configuration, you can use the check tool in the SuccessFactors HXM Suite.

To perform a validation, complete the following steps:

  1. Navigate to Check Tool.
  2. Select Reporting from the drop-down menu.
  3. Expand ConfigurationSelect Availability of user record for People Analytics.
  4. Choose Run button.
  5. Enter user ID or name.
  6. Choose Run button.
  7. There will be a message in the next screen about the user's status. If there is an issue you will see "1 issue found". Click on that link.

Result: The Detailed Results screen will display the Status and the Proposed Solution.

Common Output Issues

Examples of common output when there is an issue:

If the User record exists for People Analytics check identifies the user does NOT exist, you should run an IPS sync to create the user, or troubleshoot why the IPS sync is not working.

If the User record exists for People Analytics check identifies the user DOES exists but with configuration errors, you can run theUser is correctly configured for Stories in People Analyticscheck to try to resolve the configuration issue.

Story Report and Schema Permissions

When you set permissions for story reports, you must assign permission to create story reports and grant permission to access the appropriate reporting schemas. Additionally, you need to confirm or assign permissions to the data the report creator will be working with in the report.

Once you enable Story, users can access the story reports in Report Center. However, the permission to create a new Story or to access the data in a story are managed using role- based permissions.

There are two levels of access you can set for a user on Story Reports:

  • Create Story: Allows you to create, edit, delete, share, import, export, duplicate, schedule, and add labels to Story Reports. You can work with the data from schemas selected for this permission.
  • Story Admin: Allows you to manage all reports of type Story. This permission also enables the All Reports tab in Report Center.

Story Report Access Level Setting

To set levels of access on Story Reports, complete the following steps:

  1. To enable a user to create story reports. Navigate to Manage Permission Roles. Select the role that will create story reports. Select Permissions. Enable the permission Report PermissionCreate Story. Select either Allor individual schemas the role needs to access. Save the changes.

  2. To assign a user the Story Admin role. Navigate to Manage Permission Roles. Select the role that will administer story reports. Select Permissions. Enable the permission Manage Dashboards / ReportsStory Admin. Save the changes.

Schema Permissions Required for Using Story

The Create Story permission allows you to select the schemas that you can use in a story, but you can access the data from the schemas only after you enable the schema related permissions. The permission to create stories does not provide you access to the data you're trying to report.

The Create Story permission is not bound by target population. The permission allows you to use the fields from the selected schemas while creating a report. However, to access data from a schema, you need to enable the schema specific role-based permissions.

For example, you can assign permission to the schema Performance Management in a Story. However, need to additionally permission what data users can see when they create / run a report built using the Performance schema. The Data Access: Story allows users that run a report and only see the employee data limited to the target population of the permission.

Similar permissions exist for several schemas.

For the module specific details, please review the section "Permissions Required for Using Story Reports" in the document " Stories in People Analytics" on the SAP Help Portal.

SuccessFactors Learning Permissions in People Analytics

When a user runs a report in People Analytics, the report returns only data belonging to the security domains applied to their LMS Admin roles.

The roles and permissions that you have in the SAP SuccessFactors Learning application are carried over to People Analytics.

For example, if you have an administrator role in SAP SuccessFactors Learning Administration with View permissions, then you can view the same set of tables in People Analytics that was visible in the SAP SuccessFactors Learning application.

For more detailed information on Security in SAP SuccessFactors Learning- see the Guide HR862: SAP SuccessFactors Learning - Security.

Log in to track your progress & complete quizzes