Stories in People Analytics

PUBLICDocument Version: 2H 2020 – 2021-01-22

Stories in People Analytics

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 What's New in the Stories in People Analytics Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Limitations and Important Notes for Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Known Gaps in Schemas Available for Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 System Requirements and Technical Prerequisites for Stories in People Analytics. . . . . . . . . . . . . 19

5 Enabling Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.1 Configuring Identity Authentication Settings for Instances Using Corporate Identity Providers . . . . . . . . 225.2 Syncing Users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud. . . . . . . . . . . . . . . . . . . . . 24

6 Permissions Required for Using Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.1 What Are Role-Based Permissions?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Permission Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Permission Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Grant Permission Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47What Are Rules in RBP?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7 Configuring Custom MDF Objects for Reportability Using Story Reports. . . . . . . . . . . . . . . . . . . . 577.1 Creating Custom Schema for Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.2 Adding Root Object to Custom Schema for Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

8 Creating a Story Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608.1 Type of Pages in a Story Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

9 Adding Queries for a Story Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

10 Creating Reports Using Blended Data from Multiple Queries (Data Sources). . . . . . . . . . . . . . . . . 68

11 Story Design Functions Available for Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

12 Filters in Query Designer of Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7712.1 Applying a Simple Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7812.2 Applying a Time Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuring Date Range in Time Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8012.3 Applying an Advanced Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Creating Input Parameters for Advanced Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8312.4 Applying a Scope Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

13 Available Data (Schema) in Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

2 PUBLICStories in People Analytics

Content

14 Schema Joins Available for Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11314.1 Schema Join Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Creating Custom Joins Using Schema Join Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

15 Measures and Dimension in Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

16 Creating Calculated Columns for Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13816.1 Formula Functions in Calculated Columns for Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . 139

17 Report Center Actions Supported for Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

18 Creating Story Reports Using the Story Templates Available in Content Store. . . . . . . . . . . . . . . 15518.1 Import and Export of Story Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

19 Scheduling a Story Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

20 Sharing a Story Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

21 Actions to Support Manual Refresh in Target Tenants with Story Reports. . . . . . . . . . . . . . . . . . 16421.1 Exporting X509 Certificates and OAuth Settings for Stories in People Analytics. . . . . . . . . . . . . . . . . . .16521.2 Importing X509 Certificates and OAuth Settings for Stories in People Analytics. . . . . . . . . . . . . . . . . . 166

22 Using the Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16822.1 Benefits of the Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16922.2 Check Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16922.3 Creating Support Tickets from the Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17022.4 Using the Quick Fix Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

23 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17223.1 Centralized Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17223.2 Data Retention Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

24 Appendix: Stories in People Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Stories in People AnalyticsContent PUBLIC 3

1 What's New in the Stories in People Analytics Guide

This document describes changes to the Stories in People Analytics guide for the recent releases.

2H 2020

Changes to this Guide in 2H 2020

What's New Description More Information

January 22

Pagination Support for Table Widgets

Added a note to explain that when exporting a story to PDF and PPT from the View mode, you can opt for a paginated view of the table widgets. The pagination support allows you to export all the rows of the table widgets.

Creating a Story Report [page 60]

Explorer View Mode After you enable the explorer view mode for the widgets, you can create multiple explorer views of each widget, copy the explorer views, and paste them as new widgets on any of the existing pages or a new Canvas or Responsive page in the story.

Story Design Functions Available for Story Reports [page 72]

Removed a known gap from Recruiting

Removed the following known gaps in Recruiting, as it's not a Recruiting specific gap. It's a limitation that impacts the entire solution:

● There is no auto join support for custom FO / GO objects, meaning we can expose only the internalID to the reporting user which is not expected. In order to provide the capability to show the external Code and external name for the custom objects, framework support is required.

Known Gaps in Schemas Available for Stories in People Analytics [page 16]

Added Notes for Configuration of Identity Authentication Settings for Instances Using Corporate Identity Providers

Added the following "Notes" within the procedure for configuring the identity authentication settings for tenants that use Corporate Identity Providers,

● In Conditional Authentication, ensure that you define the same set of rules for both the SAP Analytics Cloud tenant and the SAP SuccessFactors tenant.

● Ensure that you use the same Identity Provider for both the SAP Analytics Cloud tenant and the SAP SuccessFactors tenant.

Configuring Identity Authentication Settings for Instances Using Corporate Identity Providers [page 22]

November 20

Added a topic on creating Story reports with blended data

You can create stories with visualizations using data from multiple queries or data sources.

Creating Reports Using Blended Data from Multiple Queries (Data Sources) [page 68]


What's New in the Stories in People Analytics Guide


Added a known gap for Recruiting Marketing

Recruiting Marketing data is not currently available for Stories in People Analytics. For example:

● User Refer & Apply Refer data [It is on the road map for inclusion in Recruiting schema]

● Visitor Refer (visitor traffic unrelated to known candidates or employees) [This is not planned for inclusion in Recruiting schema. It's accessible only through Recruiting Advanced Analytics]


October 16

Updated the Limitations and Important Notes topic

As Instance Refresh using the Admin Center Instance Refreshtool is now supported for Stories in People Analytics, removed the following limitation:

● Currently, Instance Refresh is supported for Story in People Analytics in a limited way. Instance Refresh can affect the Story related configuration on your instance. To fix configuration issues that are introduced after you perform Instance Refresh, please contact SAP Cloud Support.

NoteIf you’re using Story reports, ensure you export your stories before performing Instance Refresh, and import them after Instance Refresh is complete.

Also, as Microsoft PowerPoint output is now supported for Story reports, so replacing the limitation, "Currently, you can't generate MS Word, MS PowerPoint output for Story." with "Exporting to Microsoft Word format is not supported for Story"

Limitations and Important Notes for Stories in People Analytics [page 15]

Added a known gap for Employee Profile

● Currently, Notes in Employee Profile is not reportable using Stories in People Analytics.


Added a known gap for Compensation

● Currently, you can only navigate from Compensation Planning schema to User schema. There's no schema join to enable you to navigate from the User schema to the Compensation Planning schema.


Updated List of Available Schema

Added the "Role Information" table of the "Role Based Permission" schema in the list of schema available Story reports.

Available Data (Schema) in Story Reports [page 86]

Stories in People AnalyticsWhat's New in the Stories in People Analytics Guide PUBLIC 5


Added a known gap for Goal Management

For individual goal plan templates in Goal Management schemas, the Category column in Table reports cannot be shown or selected if the control-category-element attribute is not configured.

As a workaround, you can select All Templates and then filter the corresponding template ID, or you can add the control-category-element attribute to the corresponding template XML file. For details about this attribute, see Defining Category and Default-Category.


Added a Note for Lock and Shield Icons against data fields

While designing a query, when you're selecting columns, you can come across fields with a Lock icon or a Shield icon. Added the following note to explain the meaning and impact of the lock and shield icons on your report.

NoteFor a particular field in the table, when you see:

● A Lock icon (), it means you don't have the role-based permissions required to access the data in that field. You will still be able to select the field in the query, however you won’t see any data in that field. When other users run the report they see data based on their role-based permissions. You can check and update the data access permissions granted to you for the particular fields in that module to resolve the constraint.

● A Shield icon, it means that the field includes sensitive information. If you add sensitive columns to the report, the read access logs are generated each time someone uses (previews, schedules or generates) the report. You must also include the context field (such as User Sys ID) to the report to enable the read access logging.

October 09


You can now add Story reports as Favorites on the Reports tile on Home page, access stories using Action Search, use Content Store to import story templates, and copy-paste filter values on the Story design page.

So, removed the following limitations:

● You can't add your favorite Story links to the Home page as tiles or shortcuts.

● Standard content, which means Story templates for commonly used scenarios, isn't yet available.

● You can't copy-paste filter values.




https://help.sap.com/viewer/4a24e48b5c384b18a81f6b661305021e/latest/en-US/21354275f3fa4c23bb340f129469d487.html



Added a topic on IAS Configurations for Corporate IDP users

This topic is applicable if you're using a corporate identity provider to access SAP SuccessFactors. You must configure additional settings in the Identity Authentication service to use Stories in People Analytics.

Configuring Identity Authentication Settings for Instances Using Corporate Identity Providers [page 22]

Updated the topic on Scope filtering

Updated the topic on Scope filtering to indicate that when you use the Position option in Scope filter, you can now decide whether you want to include or exclude the data of the user occupying the position.

NoteThe Position option in Scope Filtering appears only for the Position table of the Succession Nominations (MDF Position) schema.

Applying a Scope Filter [page 84]

Added a section on actions needed to support Manual refresh

Created topics on the actions needed on your part, before you initiate the manual refresh process for target tenants with Story reports.

Actions to Support Manual Refresh in Target Tenants with Story Reports [page 164]

Added missing permissions Added the permissions, Manage User Data Access: User and

Recruiting Permissions Data Access: Story to the table of Schema Permissions for Story Reports. Also, added the following note about Employee Central and Employee Profile modules.

NoteThere are no Storyspecific role-based permissions for Employee Central and Employee Profile schemas. To access data in the Employee Central and the Employee Profile fields in Story reports, you must have the permission to access the respective fields in Employee Central and Employee Profile.

Permissions Required for Using Story Reports [page 26]

Added Known Gaps for Payroll

Added the following gaps for the Payroll schema:

● Voids and reversals information doesn't appear in the payroll results.

● Payroll split information, such as WPBP and country specific tax splits, doesn't appear in the payroll results.


Added the product schema for Compliance

The product schemas available for Report - Story table now has Compliance information.


Removed the known gap for Succession

Removed the following gap for Succession:

Not reading incumbent correctly yet if Employee Central Position Management is active




Added tables for Succession schemas

● Added the following tables under the schema Succession Nominations (MDF Position).○ Nomination History Information○ Position

● Added the following tables under the schema Succession Nominations (Talent Pool):○ Nomination Information○ Talent Pool


Added known gaps for Performance Management

● The Form Template table is not supported for reporting.● Attachments on forms are not supported for reporting.


1H 2020

Changes to this Guide in 1H 2020


August 14

Updated the name of the reporting solution to Stories in People Analytics

In accordance with the recent change in the name of this solution, we've updated the guide to replace "People Analytics, embedded edition" with "Stories in People Analytics".

Stories in People Analytics [page 13]

Jul 17

Updated the procedure for creating calculated columns

Updated the steps for creating calculated measures to incorporate the minor UI changes on the Column Overview dialog within the Query Builder.

Creating Calculated Columns for Stories in People Analytics [page 138]

Updated formula functions in calculated columns

Added the description and examples for the following formula functions in calculated columns, Locate(), Left(), Right(), and ToInterger(). Also, updated the example for the AddDayToDate() function.

Formula Functions in Calculated Columns for Stories in People Analytics [page 139]

Jul 03





Updated the limitation about Instance Refresh to:

● Currently, Instance Refresh is supported for Story in People Analytics in a limited way. Instance Refresh can affect the Story related configuration on your instance. To fix configuration issues that are introduced after you perform Instance Refresh, please contact SAP Cloud Support.

NoteIf you’re using Story reports, ensure you export your stories before performing Instance Refresh, and import them after Instance Refresh is complete.

Added the following limitation:

● Objects that include custom fields configured as generic objects or foundation objects (type of reference object under DataType) aren't currently supported.


Updated Known Gaps Removed the following known gaps in Recruiting:

● The user is always prompted to enter the as of date manually for object fields based on which the FO / GO values are resolved whereas recruiting specific FO / GO fields are always resolved to the latest active version.

● The reporting users can see incorrect date and time. The time and date are always stored in server timezone and currently, it is not resolved based on reporting user's timezone.


Updated a Note on Creating Custom Joins

Added the following note on custom joins:

NoteThe Custom Join tab is disabled. If there are any joins within the Story schemas that are missing, please raise an Influence Request with the business reason for these specific joins. Your requests are evaluated to determine if these joins must be made available as standard joins for Story in People Analytics.

Creating Custom Joins Using Schema Join Manager [page 135]

Updated the procedure to sync users from SAP SuccessFactors

Added steps to enable the SAP Analytics Cloud tenant on the Target Systems tab, before you start syncing users from SAP SuccessFactors to SAP Analytics Cloud.

Syncing Users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud [page 24]

May 22

Updated the impact on report story for Succession.

Added the following information in the Impact on Report Story column for the Succession Planning Permission, Succession Approval Permission, and Succession Management and Matrix Report Permissions permissions:

If Exclude nominees from seeing themselves within a succession plan is enabled in Admin Center, employees who have been nominated as successors can't see themselves within a succession plan.




May 15


Removed the following limitations, as they're now supported for People Analytics, embedded edition:

● "Include starting from person" in scope filter is currently not supported.

● Global Assignment and concurrent employment is currently not supported.


Added a topic on Input Parameters

Add flexibility to your data filtering using parameters in advanced filters. Parameters enable you to update your filter easily, and allows you to provide filter inputs during story execution.

Creating Input Parameters for Advanced Filtering [page 83]

Updated the Advanced Filter topic

Added more information on the operator types and the types of filters you can apply in advanced filtering.

Applying an Advanced Filter [page 81]

Added a Note to Import and Export of Report - Story topic`

Added the following note,

RememberThe export functionality in Report - Story hasn't been designed for backup purposes. The exported ACN file doesn't contain the actual report definition. It only contains references to the report definition, which is stored on the content network.

Import and Export of Story Reports [page 156]

Added a note in Scheduling a Report - Story topic


NoteCurrently, each report can have only one schedule per user.

Scheduling a Story Report [page 158]

April 09

Permissions topics combined

For ease of use and better clarity, we've combined the "Setting Up Permissions for Report - Story" and "Schema Permissions Required for Using Report - Story" topics to a single topic on permissions, "Permissions Required for Using Report - Story".

Added information about the story admin permission, Report - Story Admin.


Added a Recruiting scenario to the list of limitations.

Added the limitation, "Currently, the Recruiting schema in embedded edition doesn't support the Status Audit Trail table for Application Status."


April 03




Updated list of languages that don't support People Analytics, embedded edition

Updated the list of languages that don't support People Analytics, embedded edition:

● Catalan, Danish, English UK, French Canadian, German Swiss, Spanish Mexico, Swedish, Dutch, and Welsh are now supported. So, removed the reference of these languages from the list of limitations.

● Arabic and Hebrew aren't supported. So, added these languages to the list of limitations.


Updated the list of limitations to remove scheduling and import

Report - Story now supports scheduling and import/export. So removed the following two points from the list of limitations:

● Offline story execution isn’t supported, which means you cannot schedule a Report - Story.

● You cannot currently import stories into Report Center.


Added a topic on Import and Export of Report - Story

You can now import and export Report - Story type of reports using Report Center.

Import and Export of Story Reports [page 156]

Added a topic on scheduling stories

You can now schedule the Report - Story reports for offline execution using Report - Center.

Scheduling a Story Report [page 158]

Updated the list of modulespecific known gaps

In Compensation Planning, bonus plans are now available for reporting, and the metrics for bonus plan payout are also reportable. So removing the following two from the list of Know Gaps:

● In the Compensation Planning schema, “Bonus Plan” is not available for reporting

● In the Compensation Planning schema, the metrics for bonus plan payout are not reportable


Updated the topic for creating custom joins


NoteBy default, the Custom Join tab has been disabled. Enable this feature only if the schema joins you need are not available under the Default Join tab. To enable this feature, raise an Influence request with business reason to create custom joins.

Creating Custom Joins Using Schema Join Manager [page 135]

Q4 2019

Changes to this Guide in Q4 2019


January 31

Available Data (Schema) in Report - Story

Added details about the primary tables of the Employee Profile schema: Photo, Profile Completion, Custom_Trend, Custom_Background, and Badge Information. The table name and data of the Custom_Trend and Custom_Background tables are displayed according to the configuration in the Data Model.




Schema Joins Available for Report Story

Added details about the schema joins between the Employee Profile and User schemas

Schema Joins Available for Story Reports [page 113]

December 27

Appendix: People Analytics, embedded edition

Updated the note as follows, to direct users to the topic they refer to in the guide, before referring to the SAP Analytics Could content.

NoteOnly a set of the SAP Analytics Cloud features are currently supported in the People Analytics, embedded edition solution. To avoid confusion, please read the Story Canvas Functions Available for Report - Story topic before you refer to the SAP Analytics Cloud help document, so you read only the feature topics that are relevant to People Analytics, embedded edition.

Appendix: Stories in People Analytics [page 174]

November 08

People Analytics, embedded edition

Initial Publication

NotePeople Analytics, embedded edition is now generally available in restricted phases.

Stories in People Analytics [page 13]



2 Stories in People Analytics

Stories in People Analytics offers reporting, insights, dashboards, and so on, and enables you to perform cross-suite reporting based on live transactional data across the SAP SuccessFactors HXM suite.

Story Reports

The Story type of report in Report Center is part of the People Analytics solution, and it's based on the integration of SAP SuccessFactors HXM Suite with SAP Analytics Cloud. After you create a story, you can add and edit pages, sections, and elements. You can share your story with others to enable them to use the report you've created. It is a presentation-style report that uses charts, visualizations, text, images, and pictograms to describe data. A story mainly involves building a query, and using the query to create the report.

Highlights of Stories in People Analytics

● Perform suite-wide analysis by including data from multiple modules in one story. For example, Recruiting and Onboarding; Employee Central, Recruiting, and other modules; and so on.

● Leverage improved schema structures that allow the right data elements to be found quickly and easily, including important fields being automatically suggested.

● Search across all schemas.● Create single domain and cross domain reports using product schemas that are not supported by other

reporting tools in SAP SuccessFactors:○ Onboarding (2.0)

Stories in People AnalyticsStories in People Analytics PUBLIC 13

○ Job Profile Builder○ Spot Awards○ Custom MDF Objects

● Use the additional available calculated functions (for example, CONTAINS, LENGTH, UPPERCASE).● Perform date calculations and calculations on Boolean fields.● Create and display ratios, like gender ratios, in the report.● Create reports irrespective of your data access permissions. This means, you can add fields to the query even if

you don't have the relevant data access permission. However, when you run the report, you won't see any data for such fields.

● See relevant fields automatically for the data elements linked using joins, without needing to manually navigate the data model.

● Report on fields from different schemas, which are linked using auto joins and semi-hard joins.● Create shortcuts for accessing your favorite Story reports from the Home page, by adding them to the Reports

tile.

Related Information

Limitations and Important Notes for Stories in People Analytics [page 15]Enabling Stories in People Analytics [page 21]System Requirements and Technical Prerequisites for Stories in People Analytics [page 19]Template Stories in People Analytics


Stories in People Analytics

https://help.sap.com/viewer/f1cbadf36a8d450fb2cb4324f9d56607/

3 Limitations and Important Notes for Stories in People Analytics

Check the list of known technical gaps and special scenarios before using Stories in People Analytics.

NoteThis is a preliminary list of limitations and known gaps for Stories in People Analytics, and it's subject to change with upcoming enhancements.

Current Limitations for Stories in People Analytics

● The schemas for Recruiting Marketing, Recruiting Posting, Learning, and Onboarding 1.0 aren't supported. However, the schema for Onboarding (2.0), which replaces Onboarding 1.0, is supported.

● Currently, the Recruiting schema for Stories in People Analytics doesn't support the Status Audit Trail table for Application Status.

● The option to configure timestamps in the time zone of the user running a Story isn't available.● The JDM (Job Description Manager) schema isn't available.● Objects that include custom fields configured as generic objects or foundation objects (type of reference

object under DataType) aren't currently supported.● Quick card and deep link isn't supported in story content.● Transient data (for example, fields calculated in real time in the UI such as Salary or Compa-Ratio) isn't

supported.● Exporting to Microsoft Word format is not supported for Story reports.● The languages Arabic, Hebrew, and Vietnamese are currently not supported.● Translation for inline content isn't supported.● Action Search shortcuts don't apply for Story.● You can't run a Story in proxy mode.

Related Information


Stories in People AnalyticsLimitations and Important Notes for Stories in People Analytics PUBLIC 15

3.1 Known Gaps in Schemas Available for Stories in People Analytics

Read the known gaps for product schemas that are currently available for reporting using the Story type of reports in Report Center.

Known Gaps

Product Known Gaps

Calibration ● Auto joins are not supported so the usernames are not shown while joining schemas● Hard join with Compensation is not supported● Alert messages for Business Beyond Bias functionality is not supported

360 Degree Multi-Rater ● HTML tags might be found in comments in case rich text editor has been used.● Permissions configured in form templates including section permissions, field permis

sions, and button permissions are not supported in the report.● Form-template-based configuration, for example, the message key configured in the

section name, is not supported in the report.● For single form templates, custom elements in the goal section, competency section,

and custom section are shown in the table header in the report. Localization is not supported for these custom elements in the table header.

Goal Management For individual goal plan templates in Goal Management schemas, the Category column in Table reports cannot be shown or selected if the control-category-element attribute is not configured.

As a workaround, you can select All Templates and then filter the corresponding template ID, or you can add the control-category-element attribute to the corresponding template XML file. For details about this attribute, see Defining Category and Default-Category.


Limitations and Important Notes for Stories in People Analytics


Product Known Gaps

Performance Management ● On account of the dependency on Employee Central for providing the Competency schema, the Competency Description, Competency Category Name, Competency Source, Core Competency, Competency Expected Rating (Percentage), Behavior Name, and Behavior Description fields are not reportable.

● In your report if the Performance Management schema hard joins with the Rating Scale schema, you might find that there are four columns with the same name "Scale ID" (the four columns are under the Competency/Objective/Potential/Performance logical tables). However, these columns correspond to four different "SCALE_DETAILS“ tables respectively. To avoid your confusion, you can customize the column names by clicking the "Create Computed Column" icon on the " Query Designer" page.

● Performance Management schema does not report the localized fields that are defined in message keys in template XML, for example, section names and adjusted ratings. That means the fields can't be reported in different logged-in users' languages, but can still be reported in the language in which forms are saved.

● If the calculated ratings is not mapped to the rating scale, the locale specific rating description is not reported and the displayed calculated rating will be the original rating value.

● Note that if you update rating scales used by launched forms, the reporting data of these forms might be inconsistent as the scale information in your report still uses the old scale values.

● Note that if you define different rating scale values in different locales (for example, 1/2/3 in en_US and 1/3/5 in zh_CN for the same scale ID) , the relevant data in reporting might not be accurate. Please make sure that rating scale values of the same scale ID are consistent in different locales.

● If a rating label is not defined in the user's locale, the company's locale or default scale locale, the mapping between the logical column values and target localized values might not be correct. For different locales, you should configure corresponding rating labels.

● If you generate reports for the rating scale schema as an independent schema, localization is not supported for this schema.

● The Form Template table is not supported for reporting.● Attachments on forms are not supported for reporting.

Compensation ● Rules information is missing for Rewards and Recognition.● In Compensation Planning schema, rating does not currently join to retrieve label from

rating source. Note that rating field selection will appear multiple times in the UI.● In Compensation Planning schema, Generic Objects from Employee Central are not pull

ing in localized labels, only code. Will only show on templates of type "Variable Pay" or "Total Compensation".

● In Compensation Planning schema, the route map step name and descriptions cannot be reported

● In Compensation Planning schema, column level permissions respect Field Based Permissions only. Permissions set by legacy Variable Pay Permissions are not respected in Stories in People Analytics. This does not impact the behavior on the worksheet.

● Currently, you can only navigate from Compensation Planning schema to User schema. There's no schema join to enable you to navigate from the User schema to the Compensation Planning schema.

Stories in People AnalyticsLimitations and Important Notes for Stories in People Analytics PUBLIC 17

Product Known Gaps

Onboarding 2.0 ● Since there is no subjectUser field available this entity is not fully secured from target population point of view

Recruiting ● Currently, the column labels remain the same for the auto join columns selected for multiple objects. This makes it difficult for the reporting user to understand the columns belong to which table.

● Report Story shows value for custom boolean fields as 0,1. This value has to be post processed to values, which user can understand (like Yes / No)

● Reporting support has not been provided for Pre-screening questions yet, as the functionality requires re-architecture.

● Detailed requisition reporting support is not yet available.● The Recruiting schema doesn't support the Status Audit Trail table for Application Sta

tus.

Recruiting Marketing Recruiting Marketing data is not currently available for Stories in People Analytics. For example:

● User Refer & Apply Refer data [It is on the road map for inclusion in Recruiting schema]● Visitor Refer (visitor traffic unrelated to known candidates or employees) [This is not

planned for inclusion in Recruiting schema. It's accessible only through Recruiting Advanced Analytics]

Career Development Planning ● Career Worksheet is currently not available for reporting, in Stories in People Analytics.

Payroll ● Voids and reversals information doesn't appear in the payroll results.● Payroll split information, such as WPBP and country specific tax splits, doesn't appear

in the payroll results.

Employee Profile ● Currently, Notes in Employee Profile is not reportable using Stories in People Analytics.


Limitations and Important Notes for Stories in People Analytics

4 System Requirements and Technical Prerequisites for Stories in People Analytics

Besides the system requirements for using SAP SuccessFactors HCM Suite, your system needs to meet the following requirements specific to SAP Analytics Cloud for using Stories in People Analytics.

Client Software Requirements

Client Software Version Additional Information

Desktop Browser Google Chrome, latest version (see Additional Information)

Google releases continuous updates to their Chrome browser. We make every effort to fully test and support the latest versions as they are released. For additional system requirements, see your web browser documentation.

Internet Explorer 11 Support for viewing stories.

Microsoft Edge, latest version (see Additional Information)

Microsoft releases continuous updates to their Edge browser. We make every effort to fully test and support the latest versions as they are released.

Operating system Microsoft Windows Vista

Microsoft Windows 7, 8, 10

Apple Mac OS X Lion (10.7) or higher

Stories in People Analytics aren't dependent on any specific operating system. All capabilities are accessible through a web browser.

For additional system requirements, see the HCM Suite End User System Requirements documentation.

Additional software Adobe Acrobat Reader 9 or higher

Stories in People AnalyticsSystem Requirements and Technical Prerequisites for Stories in People Analytics PUBLIC 19

Client Configuration Requirements

Client Configuration Setting Additional Information

Network bandwidth Minimum 500-800 kbit/s per user. In general, Stories in People Analytics require no more bandwidth than is required to browse the internet. All application modules are designed for speed and responsiveness with minimal use of large graphic files.

Screen resolution XGA 1024x768 (high color) or higher

Widescreen: 1366x766 or higher

Minimum recommended browser cache size

250 MB The Stories in People Analytics solution is a Web 2.0 application. We recommend allowing browser caching because the application uses it heavily for static content such as image files. If you clear your cache, the browser will not perform as well until the deleted files are downloaded again to the browser and cached for use next time.

To set browser cache size, see your browser documentation.

HTTP 1.1 Enable

JavaScript Enable

Cookies Enable web browser session cookies (non-persistent) for authentication purposes

Pop-up windows Allow pop-up windows from SAP Analytics Cloud domains

Power Option Recommendation High Performance mode for improved JavaScript performance

For Microsoft based Operating Systems

Related Information

HCM Suite End User System Requirements


System Requirements and Technical Prerequisites for Stories in People Analytics

https://help.sap.com/viewer/7e01bd2cca40425e9d025f80e100fbcb/

5 Enabling Stories in People Analytics

To enable Story, a type of report in Report Center, upgrade to the Stories in People Analytics solution.

Prerequisites

● Ensure Identity Authentication Service (IAS) and Identity Provider Service (IPS) are configured for your SAP SuccessFactors tenant.

NoteYou can either use the Optional upgrade, Create SuccessFactors Identity Authentication Service Integration available in Admin Center Upgrade Center , or work with your Implementation partners for the configuration.

● Sync users from SAP SuccessFactors HXM Suite to SAP Identity Authentication Service.● Enable Report Center in your tenant.

Procedure

1. Go to Admin Center Upgrade Center .2. In the Filter By list, select Analytics.3. Under Recommended Upgrades, click Stories in People Analytics.4. Click Upgrade Now, and on the confirmation pop-up click Yes.

Results

A message appears, after your upgrade has been successful.

Next Steps

● If you use a corporate identity provider to access SAP SuccessFactors, configure the Identity Authentication Service settings required for using Stories in People Analytics.

● Complete the user sync process using your Identity Provider Service portal.

Stories in People AnalyticsEnabling Stories in People Analytics PUBLIC 21

NoteYou can use Stories in People Analytics only after you sync users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud.

● Set up the role-based permissions for various users that you want should have access to the Story reports.

Related Information

Configuring Identity Authentication Settings for Instances Using Corporate Identity Providers [page 22]Syncing Users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud [page 24]Permissions Required for Using Story Reports [page 26]Setting Up SuccessFactors with SAP Cloud Platform Identity Authentication ServiceImplementing Report CenterVideo on SAP SuccessFactors Implementation with IASA Detailed Blog about Migration to SAP Cloud Identity Authentication

5.1 Configuring Identity Authentication Settings for Instances Using Corporate Identity Providers

If you use a corporate identity provider to access SAP SuccessFactors, you must configure additional settings in the Identity Authentication service to use Stories in People Analytics.

Prerequisites

● Enable the Stories in People Analytics solution from Upgrade Center.● Sync users from SAP SuccessFactors to the Identity Authentication service.

Context

Identity Authentication is a prerequisite for enabling Stories in People Analytics. Instead of connecting the SAP SuccessFactors tenant to the corporate identity provider, configure your corporate identity provider settings in the Identity Authentication service.


Enabling Stories in People Analytics

https://help.sap.com/viewer/568fdf1f14f14fd089a3cd15194d19cc

https://help.sap.com/viewer/6ca0eee0540248b2b3ba91eaa1f18423

https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=0_8nphq0ac

http://help.sap.com/disclaimer?site=https%3A%2F%2Fcommunity.successfactors.com%2Ft5%2FPlatform-Resources-Blog%2FMigration-to-SAP-Cloud-Identity-Authentication-With-IAS-IPS-from%2Fba-p%2F245740

Procedure

1. Log on to the Identity Authentication Service using the link from your registration email.2. Go to Applications & Resources, select the Applications tab, and select your SAP Analytics Cloud tenant.3. Edit the Conditional Authentication details.

NoteIn Conditional Authentication, ensure that you define the same set of rules for both the SAP Analytics Cloud tenant and the SAP SuccessFactors tenant.

4. In the Default Identity Provider field, select the Identity Provider that you're using to authenticate users on the SAP SuccessFactors tenant, and save the changes.

NoteEnsure that you use the same Identity Provider for both the SAP Analytics Cloud tenant and the SAP SuccessFactors tenant.

5. Go to Identity Providers, select the Corporate Identity Providers tab, and select your corporate identity provider.6. Ensure that the Forward All SSO Requests to Corporate IdP option in the SINGLE SIGN-ON section has been

disabled.7. Configure Identity Federation, enable the Use Identity Authentication user store option in the User Store section,

and save the changes.

Results

You've successfully updated the Identity Authentication Service settings required for using Stories in People Analytics, when you're using corporate identity providers.

Next Steps

After configuring the Identity Authentication Service settings, ensure that you run the sync job to sync users from SAP SuccessFactors to SAP Analytics Cloud.

NoteYou can use Stories in People Analytics only after you sync users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud.

Related Information

Syncing Users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud [page 24]


Configuring the Corporate Identity Provider in IAS (Video)

5.2 Syncing Users from SAP SuccessFactors HXM Suite to SAP Analytics Cloud

Respecting your privacy, we request you to sync users from your SAP SuccessFactors HXM Suite tenant to SAP Analytics Cloud to get started with the Stories in People Analytics solution.

Prerequisites

● Ensure that the following role-based permissions are enabled:

○ Manage Integration Tools Allow Admin to Access OData API through Basic Authentication

○ Manage User Employee Export

Procedure

1. Go to your Identity Provider Service portal.

The Identity Provisioning Service Administration page appears.

NoteThe details for the Identity Provider Service portal follow after the IAS configuration. If you don't 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, click the (Edit)icon, click Enable, and on the confirmation pop-up message that appears, click 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 of job, click Run Now.

You can track the progress of the read job from Job Logs.


Enabling Stories in People Analytics

https://help.sap.com/viewer/568fdf1f14f14fd089a3cd15194d19cc/2005/en-US/aa2c9efe68c6446a84094a84907e7f9f.html

Results

With the completion of the read job, the user sync from SAP SuccessFactors HXM Suite to SAP Analytics Cloud is complete.

Next Steps

Set up the role-based permissions for various users that you want to provide access to use the Story reports.

Related Information

Setting Up SuccessFactors with SAP Cloud Platform Identity Authentication ServiceUsing Role-Based Permissions


https://help.sap.com/viewer/568fdf1f14f14fd089a3cd15194d19cc/

https://help.sap.com/viewer/b569eee64d3f4159b2b5272ba7d6b127/latest/en-US/d77b76e71cf54201a4049906b9d8145a.html

6 Permissions Required for Using Story Reports

After enabling Stories in People Analytics, you can view existing story reports in Report Center, if any. However, the rights to create a new story or to access the data in a story are managed using role-based permissions.

Story Permissions

● Create Story: Allows you to create, edit, delete, share, import, export, duplicate, 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.

● Schedule Reports: Allows you to schedule "Story" type of reports.

Schema Permissions Required for Story Reports

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 Story doesn’t provide you access to the data you're trying to report. The Create Story permission isn’t bound by target population, so it simply 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 schemaspecific role-based permissions.

NoteThere are no Storyspecific role-based permissions for Employee Central and Employee Profile schemas. To access data in the Employee Central and the Employee Profile fields in Story reports, you must have the permission to access the respective fields in Employee Central and Employee Profile.

Schema Permissions for Story Reports

Solution Permission Name Permission Location Impact on Report Story

User Data Access: Login Data Admin Center Permissions Defines the login data of the target population for which the user has access, in the application and in the report.

User Data Access: User Manage User Allows you to access basic User specific fields like Username, First Name, Division, and so on.


Permissions Required for Using Story Reports


Calibration Create Story Reports Permission Manages if a user can create a calibration report. This permission doesn’t have any restriction on data, as there’s no target population that must be considered. So, whoever has this permission can preview/run the report and no data is shown. This permission allows you to create a report with the required fields coming from the schema.

Calibration Data Access: Story Calibration Controls what data users can see when they run a report built using the Calibration schema. Allows users to run a report and only see the employee data limited to their target population.

Mentoring Mentoring Programs Access Permission

Career Development Planning Allows you to access mentoring programs.

Mentoring Manage Mentoring Programs Manage Career Development Allows you to manage mentoring programs.

Learning Activity Data Access: Story Career Development Planning Allows you to view detailed transcript template and data based on the target population.

Development Goal Data Access: Story Career Development Planning Controls what data users can see when they run a report built using the Career Development Planning schema.

360 Degree Multi-Rater 360 Data Access: Story Performance Controls what data users can see when they run a report built using the 360 Degree Multi-rater schema.

Performance Management Data Access: Story Performance Controls what data users can see when they run a report built using the Performance schema. Allows users to run a report and only see the employee data limited to their target population.

Compensation Eligibility and Compensation Planning

Data Access: Story (Compensation and Variable Pay)

Compensation and Variable Pay

Specifies the templates users can access for reporting, which is further refined by target population.

Stories in People AnalyticsPermissions Required for Using Story Reports PUBLIC 27


Onboarding 2.0 Onboarding 2.0 or Offboarding 2.0 Object Permissions

Onboarding 2.0 or Offboarding 2.0 Object Permissions

Contains permission for all ONB 2.0 business objects like ONB2Process,ONB2ProcessTrigger, Tasks etc.

Succession Succession Planning Permission

Succession Planners ● If Allow succession planners to view successors on org chart nodes/position tile view is enabled in Admin Center, you can view all status succession nominations and also mapped talent pools.

● If Allow succession planners to view successors on org chart nodes/position tile view isn’t enabled in Admin Center, you can view pending, removed, rejected, and succeed succession nominations.

● If Allow succession planners with recruiting candidate search permissions to nominate external candidates is enabled, you can view external candidate data as well.

● Nomination History is always available for those visible nominees.

● If Exclude nominees from seeing themselves within a succession plan is enabled in Admin Center, employees who have been nominated as successors can't see themselves within a succession plan.




Succession Succession Approval Permission

Succession Planners ● If Allow succession planners to view successors on org chart nodes/position tile view is enabled in Admin Center, you can view all status succession nominations and also mapped talent pools.

● If Allow succession planners to view successors on org chart nodes/position tile view isn’t enabled in Admin Center, you can view pending, removed, rejected, and succeed succession nominations.

● If Allow succession planners with recruiting candidate search permissions to nominate external candidates is enabled, you can view external candidate data as well.





Succession Succession Management and Matrix Report Permissions

Succession Planners ● You can view only approved succession nominations and also mapped talent pools.



Succession View Talent Pool nominations Succession Planners ● If Apply target population to Talent Pool Nominations Permissions. is enabled in Admin Center, you can view successors for permitted talent pools, following user target population configured in RBP.

● If Apply target population to Talent Pool Nominations Permissions. is disabled in Admin Center, you can view successors for permitted talent pools. Not restricted to user target population even configured.


Succession Miscellaneous Permissions Miscellaneous Permissions If you’re using MDF position-based nomination method, Succession also follows the target population of Miscellaneous Permissions.

Recruiting Data Access: Story Recruiting Permissions Allows you to access all Recruiting data in Story reports.

Related Information

Using Role-Based Permissions



https://help.sap.com/viewer/b569eee64d3f4159b2b5272ba7d6b127/

6.1 What Are Role-Based Permissions?

Role-Based Permissions (RBP) is a security model that allows you to restrict and grant access to your SAP SuccessFactors HXM Suite. RBP controls access to the applications that employees can see and edit. This is a suite-wide authorization model that applies to the majority of the SAP SuccessFactors products.

Open this video in a new window

The RBP security authorization model uses groups and roles to organize employees (groups) and permissions (roles) to control access to your system; By organizing employees into groups and permissions into roles you can assign a group of employees the same set of permissions by assigning them a role.

NoteRBP is approved for organizations with up to 1,500,000 employees. We’ll continue to raise this bar in the future. When in doubt, contact SAP Cloud Support.

Role-based permissions contain three main elements: permission groups, permission roles, and target populations.

● Permission groups are a set of employees who share certain attributes such as City or Job Code and require access to a similar set of tasks within your system.

● Permission roles are defined as a set of permissions. You can assign the permission roles you define to a permission group, and if the role requires that you define a target population, meaning a group to perform tasks for, you assign the target population when you define the role.

● Target populations are groups that are assigned to permission roles when the permission granted is performed on behalf of other employees.

TipWe recommend that you create groups before creating roles so that during role creation, you can select the group for which to grant the role. In addition, you need defined groups for roles that require a target population.

Permission Groups [page 32]Permission groups are used to define groups of employees who share specific attributes. You can use various attributes to select the group members, for example a user's department, country/region, or job code.

Permission Roles [page 40]RBP uses permission roles to group a set of permissions. After grouping the permissions into a role, you can assign the role to a group of users, granting them access to certain tasks and features in your system.

Grant Permission Roles [page 47]You can assign a permission role to everyone or to a subset of employees, determined by permission groups, target populations, or by relationships. When defining a role in RBP, you can assign the role to a group that you've created or you can assign roles based on hierarchical relationships. Some roles will require that you also assign target populations, they're only necessary for certain permissions in a role and your system will notify you when a target population is required.

What Are Rules in RBP? [page 55]Rules in RBP are used to define access to permissions in your system.


https://www.kaltura.com/p/1921661/sp/192166100/embedIframeJs/uiconf_id/37285991/partner_id/1921661?iframeembed=true&playerId=kaltura_player&entry_id=1_79yw92ny

Related Information

Creating Dynamic Permission Groups [page 38]Creating Permission Roles [page 41]Assigning Roles to Groups [page 49]

6.1.1 Permission Groups

Permission groups are used to define groups of employees who share specific attributes. You can use various attributes to select the group members, for example a user's department, country/region, or job code.

ExampleThere might be a permission group called "Human Resources in US", which lists all US-based employees who work in the HR department. To define this group, you would specify that users must match the selection criteria "Country/Region = United States" and "Department = HR".

NoteThe attributes or selection criteria that are available for defining groups are configurable.

In RBP, you can assign permission roles to permission groups. In addition, you use groups to define the target population a granted user has access to.

ExampleThe group "Human Resources in US" might have access to the group "US Employees".

Groups configured with criteria other than specific user names are called dynamic (as opposed to static), which means that the assignment of employees into and out of a group is automated. For example, a group of granted users can be “All employees in the Sales department”. As employees are transferred into and out of the sales department, their permissions will automatically adjust. This automation will save you time and money. This is especially beneficial for large organizations that need higher levels of administrative efficiency.

Creating Static Permission Groups [page 33]Static permission groups are created and modified by adding individual user names to a group using an excel spreadsheet. They store a static list of users instead of a list based on dynamically generated criteria. Changing user information does not modify group members, you must redefine group members by importing an updated spreadsheet.

Creating Dynamic Permission Groups [page 38]Dynamic permission groups are generated automatically when the attributes of employees match the group selection criteria. Administrators can create and manage dynamic permission groups for both employees and external users.

Configuring Permission Groups [page 40]You can edit, copy, and delete static or dynamic permission groups. For dynamic groups, you can also view the group's change history.



6.1.1.1 Creating Static Permission GroupsStatic permission groups are created and modified by adding individual user names to a group using an excel spreadsheet. They store a static list of users instead of a list based on dynamically generated criteria. Changing user information does not modify group members, you must redefine group members by importing an updated spreadsheet.

Procedure

1. In the Admin Center, search for Manage Permission Groups.2. Click Import Static Groups to create or modify a group.3. Select between Full Replace or Delta Replace.

A full replace, creates or entirely replaces a group, while a delta replace adds members to an already existing group.

4. Download a blank CSV template after you've chosen an import type. The Full Replace template has two column headers, GROUPNAME and USERID. The Delta Replace has an additional Action column.

5. For each user that you add to a group, add the group name to the GROUPNAME column and user's ID to the USERID column.

NoteFor new users, you can create user IDs in the upload file.

NoteCharacter encoding of your file should be Unicode (UTF-8). The maximum file size is 20MB. If your import file exceeds 20MB, you can either split the file into several smaller files or request Professional Services to modify the system configuration file.


6. Select the file with your data by clicking Choose File.7. Click Validate File to validate file format, file size, etc.8. If the validation is successful, click Upload to import the static permission groups.

If your file has errors, they display at the top of the Import Static Group window.

NoteFor one group type, a maximum of two jobs can run at the same time.

Results

After the upload completes, the system sends you a notification with success or error messages. Successfully created groups display in the group list after refreshing your system.

6.1.1.1.1 Adding Individual Members to Static Groups

You can add members to a static group in your system or by importing an excel file to your system.

Procedure

1. In the Admin Center, search for Manage Permission Groups.2. Click the name of the static group you're updating.

The Permission Group screen displays.



3. To add a user to a static group, click Add User.4. Search for the users you'd like to add to the group.

Entering keywords in the search field displays user names.5. Select each user you want to add to the group.

Each user you select automatically displays in the right pane.6. Click Done.

The users you selected are added to the group immediately.

6.1.1.1.2 Adding Multiple Members to Static Groups

Instead of opening static groups one by one to add members, you can add multiple members to several static groups all at once with a CSV file.

Procedure

1. Go to Admin Center Set User Permissions Manage Permission Groups .2. Click Import Static Groups.

The Import Static Group popup displays.3. Choose Delta Replace.4. Click Download a blank CSV template.

A CSV template for delta replacement is downloaded.5. Fill in the CSV file.

Column Head Description

GROUPNAME Fill in the names of the static groups that you want to add members to.

USERID You can choose to provide either USERID or ASSIGNMENTID of employees.

ASSIGNMENTID You can choose to provide either USERID or ASSIGNMENTID of employees.

ACTION ADD

6. Save the file.7. Go back to the Import Static Group popup and upload the CSV file that you’ve prepared.8. Click Validate File.

A message displays at the top of the Import Static Group popup to inform you whether there’s any format issue in the CSV file.

9. If there are no issues found in the validation phase, choose the CSV file again and click Upload.10. Click Cancel to dismiss the Import Static Group popup.


Results

You have successfully added members to the static groups with a CSV file. You receive an email about the details.

Next Steps

Refresh the Manage Permission Groups page to double check the active membership of the static groups that you’ve updated.

6.1.1.1.3 Removing Members from Static Groups

Although you add members to a static group using a spreadsheet, you can remove static group members using the system.

Procedure

1. In the Admin Center, search for Manage Permission Groups.2. Click the name of the static group you're updating.

The Permission Group screen displays.3. Select the users that you want to remove from the group.4. Click Delete.

The list of users updates immediately.5. Click Close.

Results

Removed members will no longer have access to the tasks or data of the group.



6.1.1.1.4 Removing Multiple Members from Static Groups

Instead of opening static groups one by one to remove members, you can remove multiple members from several static groups all at once with a CSV file.

Procedure

1. Go to Admin Center Set User Permissions Manage Permission Groups .2. Click Import Static Groups.

The Import Static Group popup displays.3. Choose Delta Replace.4. Click Download a blank CSV template.

A CSV template for delta replacement is downloaded.5. Fill in the CSV file.

Column Head Description

GROUPNAME Fill in the names of the static groups that you want to remove members from.

USERID You can choose to provide either USERID or ASSIGNMENTID of employees.

ASSIGNMENTID You can choose to provide either USERID or ASSIGNMENTID of employees.

ACTION REMOVE

6. Save the file.7. Go back to the Import Static Group popup and upload the CSV file that you’ve prepared.8. Click Validate File.

A message displays at the top of the Import Static Group popup to inform you whether there’s any format issue in the CSV file.

9. If there are no issues found in the validation phase, choose the CSV file again and click Upload.10. Click Cancel to dismiss the Import Static Group popup.

Results

You have successfully removed members from the static groups with a CSV file. You receive an email about the details.


Next Steps

Refresh the Manage Permission Groups page to double check the active membership of the static groups that you’ve updated.

6.1.1.2 Creating Dynamic Permission Groups

Dynamic permission groups are generated automatically when the attributes of employees match the group selection criteria. Administrators can create and manage dynamic permission groups for both employees and external users.

Procedure

1. In the Admin Center, search for Manage Permission Groups.2. Click Create New to create a new permission group.

The Permission Group page opens.3. Enter a name for your permission group in the Group Name field.4. Choose a User Type for your group.

The available user types vary depending on how your system is configured. Possible values may include:○ Employee (default)○ External Learning User

NoteThe External Learning User option is only available if you have Learning enabled in your system.

When defining a dynamic group for an external learning user, you can identify an External Source Channel to complete the criteria for inclusion. This allows external learning users to be defined based on the source of origin. The external source channel is only available to SAP SuccessFactors Learning customers. The External Learning User must be enabled in Provisioning for external learner and external source channel to be available.

TipWhen defining External Learning User groups in your system, it is recommended that you do not create more than 50 groups.

5. Choose the group selection criteria from the People Pool, in the Choose Group Members section.

Depending on the complexity of your permission group selection criteria, you can choose multiple people pools.

6. In the Search Results screen, enter a search term or click the search, to display all available values.

For some categories, a smaller pop-up window appears where you can enter additional values or information, such as Time Zone settings. If you select the Team View category, you can use hierarchical relationships to specify the group. This allows you to apply rules such as: everybody in Carla Grant's team, all levels deep.



NoteWhen you search employees with the User category, the search results in the dropdown display only employee names. When you search employees with the Team View category, the search results in the dropdown display employee names, employee titles, and locations.

7. Make your selection and click Done.8. If you want to add another condition for defining the people pool, click Add another category and choose a

category and item. If you use two or more categories, this functions as an AND operation, that is, only users are selected who meet all selection criteria.

ExampleIf you want to create a group of sales employees working in the US, you would need to choose the category Department and select Sales. You add a second category Country/Region and select United States.

9. Complex group definitions may require you to use multiple people pools. If you use two or more people pools, these people pools functions as an OR operation, that is, all users are selected who fulfill the selection criteria of at least one pool.

Click Add another People Pool and then add categories and items.

ExampleYou have two different offices: An office in Chicago and an office in Boston. Each office has a Sales team and a Finance team. You only want to include Sales employees from the Chicago office and Finance employees from the Boston office. You'll need to create two separate pools then.

NoteThe number of people pools in a group is limited to three.

10. If there are employees you'd like to exclude from the Permission Group definition, select them in the Exclude these people from the group section.

11. If you want to prevent the group being updated automatically when new employees match the selection criteria, click Lock group.

12. (Optional) Choose Update in the Active Group Membership box to see how many users match the criteria. Click the number to see the detail list.

The active group membership number isn't updated automatically when you modify the dynamic group definition.

13. Choose Done to complete the process.


6.1.1.3 Configuring Permission Groups

You can edit, copy, and delete static or dynamic permission groups. For dynamic groups, you can also view the group's change history.

Context

NoteYou can only delete a permission group if it has no associated role.

Procedure

1. Go to the Admin Center Tools and search for Manage Permission Groups.

2. In the Manage Permission Groups screen, click the Take Action dropdown menu next to the permission group you want to modify.

3. Choose the desired action.

6.1.2 Permission Roles

RBP uses permission roles to group a set of permissions. After grouping the permissions into a role, you can assign the role to a group of users, granting them access to certain tasks and features in your system.

Permission roles consist of a set of permissions that give employees access rights to an employee or a group of employees. As such an employee or a group that has been granted with a permission role has access to certain aspects of the SuccessFactors application or to aspects of employee data. With this access, they can perform functions within the application for other groups of employees.



Role-based permissions allow you to grant a role to a specific employee, a manager, a group, or to all employees in the company. The roles can provide very granular permissions, as this example illustrates:

ExampleThere may be roles such as "HR Compensation and Benefits Manager", "HR Manager for Sales", and "HR Learning and Development Manager". While all three are HR managers, their roles have been distinctly carved out — one handling compensation and benefits, another handling the sales team, and the third handling Learning and Development.

When your permissions roles consist of one or more permissions that require a target population, you'll need to specify a target to complete creation of the role. Roles that require a target population will contain a permission that gives a group access to perform actions or view information for other employees.

ExampleA Manager may have a role where one permission allows the manager to modify the salary for all of their direct reports. In this example, the manager's direct reports represent the target population needed for the permission role.

NoteCustomers can have as many permission roles as the company requires.

Creating Permission Roles [page 41]Permission roles can be created for employees and for external users, such as External Learning Users.

Assigning Permissions to a Role [page 43]After creating groups and roles, you'll need to assign permission roles to your employee groups.

Configuring Permission Roles [page 44]You can edit, copy, or delete a permission role, view a summary of a permission role, and view its change history.

Creating a New Role for External Users [page 45]Role-based permissions support the role of External User and allows the External Learner User limited access to complete specific tasks or training.

6.1.2.1 Creating Permission Roles

Permission roles can be created for employees and for external users, such as External Learning Users.

Context

Permission roles contain a group of permissions that can be granted to an employee or a group of employees known as the Granted Users Circle. In general, it's best practice to define your user groups before defining your permission roles.


Procedure

1. Go to the Admin Center.2. In the Tools Search field, select Manage Permission Roles.3. To add a Permission Role, click the Create New button. The Permission Role Detail page opens.4. In the Role Name field, type a name describing of what the role allows you to do.5. In the Description field, provide a statement describing what the role allows an employee to do. Add a note

about when the role was created and by whom.6. In the Permission Settings section, click the Permission button to specify the permission you want to assign to

the role. The Permission Settings window opens.7. On the left side of the page, you'll see the different permission categories. Click a permission category to reveal

the different permissions.

The list of permissions associated with this category is displayed.

8. Select the checkboxes next to the permissions you'd like to grant to the role.9. Click the Done button when you finish marking your selections.10. In the Grant this role to section, click the Add button to select the employees to be granted this permission.11. Grant the permissions and specify the target population according to what you have defined in the workbook.

For a detailed description, see the topic on granting permission roles in the Related Links section.12. For some permissions, it might be necessary to exclude the granted users from applying the permissions on

themselves. For this, select Exclude Granted User from having the permission access to him/herself.

ExampleIf the role grants permission to edit the salary, you want to prevent the members of this permission group to be able to edit their own salary as well.

13. Click the Done button to assign this role to the defined users. You are taken back to the Permission Role Detail page.



14. Click the Save Changes button to complete creating the role.

Next Steps

Once this role is successfully created, the new role will be listed on the Permission Role List page.

Related Information

Grant Permission Roles [page 47]

6.1.2.2 Assigning Permissions to a Role

After creating groups and roles, you'll need to assign permission roles to your employee groups.

Procedure

1. In the Permission Settings section, click the Permission button to specify the permission you want to assign to the role. The Permission Settings window opens.

2. On the left side of the page, you'll see the different permission categories. Click a permission category to reveal the different permissions.

The list of permissions associated with this category is displayed.


3. Select the checkboxes next to the permissions you'd like to grant to the role.4. Click the Done button when you finish marking your selections.5. Click Save Changes.

Next Steps

Assign a target population, if your role indicates that a target is needed.

6.1.2.3 Configuring Permission Roles

You can edit, copy, or delete a permission role, view a summary of a permission role, and view its change history.

Context

When you copy a role, only the permissions get copied over. You will need to manually grant employees access to this new role.

Procedure

1. Go to the Admin Center Tools and search for Manage Permission Groups.

2. In the Permission Role List screen, click the Take Action dropdown menu next to the permission role you want to modify.

3. Choose the desired action.



6.1.2.4 Creating a New Role for External Users

Role-based permissions support the role of External User and allows the External Learner User limited access to complete specific tasks or training.

The external user role can be granted to the user type External Onboarding user. Permissions for the external user role can be set to grant access to the Onboarding home page.

6.1.2.4.1 Restoring the External User Password

If you have external users, consider creating a management system for them so that you can maintain their access.

Prerequisites

Either Onboarding 2.0 (including Internal Hire Process) or Learning or both must be enabled in Provisioning to reset the external user password.

RememberAs a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner. If you're no longer working with an implementation partner, contact SAP Cloud Support.

Context

When you have external users in your extended enterprise, your plan for maintaining them must include: resetting user passwords, granting access, and so on. In most cases, you manage external users as you do any other users.

One exception is target populations. External users can be a unique target population. For example, if you want to manage external users in Onboarding, you must add All(External Onboarding User) to the target population of users managed by the administrator.

Procedure

1. To reset an external user password, go to Admin Center Reset User Password .

The Resetting User Passwords page appears. From this page you can reset individual user password, or reset the passwords for a group of users.

2. Select External Users from Onboarding and/or Learning (If enabled) from the Find dropdown.

Enter the First Name, Last Name, or the Username to search for the user whose password you’re trying to reset. You can filter your search further using Starts With or Exact Match.


3. When the user details appear on the screen, select the user and enter the new password in the New Password: field and confirm the same in the Confirm Password: field.

4. Click Reset User Password.

Results

You have successfully reset the external user password.

6.1.2.4.2 Assigning Role Based Permissions to External Learners

Create a role mapping for external learners and grant them the permissions to log in to SAP SuccessFactors and access Learning.

Prerequisites

Role Based Permissions (RBP) must be enabled.

Enable External Learning User is selected in Provisioning.

Procedure

1. Log in and go to Admin Center.2. In Tools, click See All.3. In Search Tools, type Manage Permission Roles and then click Manage Permission Roles.

4. Click Create New Role For External User.5. In User Type, select External Learner, and then click Done.6. Type a name and description for the role and then click Permissions.

The Permission Settings page opens.

7. In User Permissions General User Settings , select User Login.

8. In User Permissions Learning , select Learning Access Permission.

You can select additional permissions. For example, you can grant the external learners access to SAP Jam or Mobile.

9. Click Done.

You return to the Permission Role Detail page.10. Click Add.



The Grant this role to... page opens.11. In Grant role to, select Everyone (External Learner).12. Click Done.

You return to the Permission Role Detail page.13. Click Save Changes.

Next Steps

You grant admins permissions to manage external learners.

6.1.3 Grant Permission Roles

You can assign a permission role to everyone or to a subset of employees, determined by permission groups, target populations, or by relationships. When defining a role in RBP, you can assign the role to a group that you've created or you can assign roles based on hierarchical relationships. Some roles will require that you also assign target populations, they're only necessary for certain permissions in a role and your system will notify you when a target population is required.

● Permission groups: You assign a permission role to a defined group of users. However, relationships can also play a role here as you can define that the granted user's managers have the same permissions. You can also define how many levels up in the hierarchy you want this permission to be granted.

NoteIf you want to grant a role to a named user, you first have to create a group and add the user to this group. Then you can grant the role to the just created group.

● Target Population: Depending on the permissions included in the role, you might also have to define the target population. Not all permissions require you to define a target population. For example, if the permission includes just the access to an application (such as the Learning Access Permission), there is no need to add a target group. For certain permissions, in the Permission settings screen, a target population must be defined. This is identified by the "t" icon next to the permission name with the following text displayed: t= Target needs to be defined.


Note

You can define a target population for external users through Manage Permission Roles Add For External Target Population . A target population for an external Learning user can be defined two ways:○ Select Everyone (External Learner)○ Select Target population of: and click Select, to select groups

● Relationships: Access groups can be defined using relationships (for example, manager-employee relationship) that are derived from the job relationship object. These relationships can be hierarchical or non-hierarchical. You can find more information in the following chapter Using Relationships to Grant Permissions [page 51].

NoteIf you allow the respective managers to have the same permissions, this may have a negative impact on the performance. The hierarchy then has to be checked whenever such a manager tries to access an element which was permissioned this way.



6.1.3.1 Assigning Roles to Groups

After creating your roles, you must assign the role to a group of employees. This ensures that employees are given access the permissions they need to perform their tasks.

Procedure

1. Go to the Admin Center.2. In the Tools Search, search for Manage Permission Roles.

3. Select one of the permission roles you created.4. In the Grant this role to section of the Permission Detail screen, click Add.5. When the Grant this role to screen displays, select Permission Group.

6. Click Select to select the access groups you wish to assign to this permission role.

You can allow managers to have the same permissions and define how many levels up in the hierarchy you want this permission to be granted. However, allowing respective managers to have the same permissions may have a negative impact on the performance. The hierarchy then has to be checked whenever such a manager tries to access an element which was permissioned this way.

7. Exclude Granted Users:

For some permissions, it might be necessary to exclude the granted users from applying the permissions on themselves. For this, select Exclude Granted User from having the permission access to themselves.


8. Click Done to assign this role to the defined users. You are taken back to the Permission Role Detail page.9. Click Save Changes to complete creating the role.


Next Steps

If required, assign a target population to your role.

6.1.3.2 Assigning Target Populations to a Role

Target populations are assigned to roles that require tasks to be performed on behalf of another employee.

Context

Target populations allow you to give employees such as managers and administrators access to data or tasks that need to be maintained for other employees. Depending on the permissions included in the role, you may need to define the target population. Not all permissions require you to define a target population. For example, if the permission includes just the access to an application (such as the Learning Access Permission), there is no need to add a target group. For certain permissions, in the Permission settings screen, a target population must be defined. This is identified by the "t" icon next to the permission name with the following text displayed: t= Target needs to be defined.

Procedure

1. Go to the Admin Center.2. In the Tools Search, search for Manage Permission Roles.

3. Select one of the permission roles you created.4. In the Grant this role to section of the Permission Detail screen, click Add.5. Select Everyone or choose Target population of to select a group .



6. Click Select to select the target groups that you want to assign to this permission role.7. Exclude Granted Users:

For some permissions, it might be necessary to exclude the granted users from applying the permissions on themselves. For this, select Exclude Granted User from having the permission access to themselves.


8. Click Done to assign this role to the defined users. You are taken back to the Permission Role Detail page.9. Click Save Changes to complete creating the role.

6.1.3.3 Relationships Between Managers and Employees

There are relationships that can be specified through employee fields, and managed through tools, like the employee data.

General Relationship Types: Hierarchical relationships are characterized by a reporting line between the granted user and the target user. These are relationships between employees and their managers, and employees and their second managers or alternate managers. Non-hierarchical relationships on the other hand are single-level relationships. These include the relationship of an employee to the HR manager, the matrix manager and custom


manager. While each employee can have only one Manager, one Second Manager and one HR Manager, they can have multiple Matrix Managers and Custom Managers.

Employee Central Only: If employees have global assignments (that is, a job in another country/region), they have both a home manager and a host manager. In addition, they have a home HR manager and a host HR manager. All managers need to have access to both the home jobs of the employees as well as to the host jobs of the employees. This is covered by the following additional relationship types for global assignments:

The Five General Relationship TypesEmployee Central Only: Relationship Types for Global Assignments

Manager Home Managers

Second/Alternate Manager Home HR Managers

HR Manager Host Managers

Matrix Manager Host HR Managers

Custom Manager

6.1.3.3.1 Delegate Relationship Assignments

As a delegator you can assign delegates to perform actions on your behalf that affects other employees in your organization.

As a manager, you can use the Delegate A and Delegate B relationship roles to assign permissions to up to two individuals for each role, allowing them to act as your delegates. The delegate users you assign, can access your direct and indirect reports and can perform tasks that have been permitted to you, while acting as your delegates. You can assign up to two delegates per delegate role and each delegate can be given separate tasks or permissions to cover different functional or regional areas.

NoteYou must configure Delegate relationship type in the Employee Central Picklist. After you've configured your delegates, you'll see the option to give permissions to this relationship type in your system. For more information about how to configure picklists, see the topic Picklist Configuration for Employee Status and Job Relationship Type.

Why would I want to use delegates?

You might use a delegate when you want to assign delegates permissions in different functional areas.

You can also assign permissions to delegates that separate functionality according to locations.

If delegate relationship has been defined in Employee Central picklists, you can grant a permission role to delegates. When a manager delegates his or her tasks to two delegates, delegate A and delegate B, the manager's direct reports are the target population of delegate A and delegate B. If the manager, delegate A, and delegate B are in the same permission roles, delegate A and delegate B will have the same permissions. The manager's direct



https://help.sap.com/viewer/b14dd15ca58f43e0856184a740a4b212/latest/en-US/e2aa8c2584e24125a4b327420cecebd9.html

https://help.sap.com/viewer/b14dd15ca58f43e0856184a740a4b212/latest/en-US/e2aa8c2584e24125a4b327420cecebd9.html

reports are the target populations of the delegate A and delegate B for the permissions that require a target. However, this delegate relationship can’t be used in non-user-based permissions. For example, even if delegate A and delegate B has the same Miscellaneous Permissions Position permission as the manager, delegate A and delegate B can’t view the current state of the position or view its history because the Position permission isn’t user-based.

User-Based RBP Permissions Non-User-Based RBP Permissions

Description Permission to the data of a user.The target population of the permission can be grouped as a user list.It can be RBP permissions or some of the MDF permissions.

MDF objects that are categorized in the Permission requiring MDF object target section.

Example The Personal Information permission controls access to the personal information data of a user.

The Miscellaneous Permissions

Payment Information Detailpermission.


6.1.3.3.2 Hierarchy Depth and User Permissions

Understand how to use hiearchy depth when assigning permissions to your users.

When granting permissions using hierarchical relationships, you can specify how many levels down to go in the hierarchy for the target population. For example, you can indicate that Managers can see performance ratings on their direct reports (1 level deep), or allow it to go deeper into their team, that is 2 levels down or all levels.

When granting permissions to non-hierarchical relationships (HR, Matrix and Custom Managers), you can follow this non-hierarchical relationship for only one level. Beyond the first level, you can cross over to the standard manager hierarchy if desired to go deeper.



For example, using the Matrix Manager relationship, you can use hierarchical depth to accomplish the following:

● 1 Level Deep: Matrix Managers can view ratings information for their Matrix Reports.● 2 Levels Deep: Matrix Managers can view ratings information for their Matrix Reports and the Direct Reports of

their Matrix Reports.● All Levels Deep: Matrix Managers can view ratings information for their Matrix Reports (1 level deep) and the

Direct Reports, all levels deep of the manager hierarchy of their Matrix Reports.

The following graphic illustrates the different hierarchical depths you can specify when you use the Matrix Manager relationship:

6.1.4 What Are Rules in RBP?Rules in RBP are used to define access to permissions in your system.

Rules are defined by determining which permission roles you’ll assign to your groups or users. From the Permission Role Detail screen in your system, each rule is represented by a row that contains your list of granted users or groups and the associated target group. Depending on the complexity of the roles and access or target group assignments, your roles could have various combinations of access and target group rules.


From your permission role detail screen, where you manage your permission roles, each row represents a rule and each rule can have multiple access and target group associations, as detailed in the display.



7 Configuring Custom MDF Objects for Reportability Using Story Reports

Using Stories in People Analytics, you can report on custom Metadata Framework (MDF) objects that aren’t reportable using other reporting tools in SAP SuccessFactors HXM Suite.

Prerequisites

● The custom MDF objects must be reportable. In this case, it means that the custom MDF object must appear in the results, when you search for the object name in Report Object Configuration Entity on the Admin CenterManage Data page.

Note

To verify whether the object is reportable, go to Admin Center Manage Data , select Report Object Configuration Entity in the first search bar, and look for the MDF object name in the adjoining search bar.○ If a record exists, the MDF object is reportable.○ If a record doesn’t exist, create a record of Report Object Configuration Entity type for the MDF object

to make it reportable. Refer to the "Implementing the Metadata Framework (MDF)" guide for more details.

Context

By default, all the standard MDF objects are available for reporting in Story reports. The custom MDF objects are also reportable by default, but they appear in the Available Data section of the Query Designer page, only after you associate them with one or more schemas. So, identify the schemas you want to link with the MDF object. You can also create a custom schema, if needed.

Procedure

1. Go to the Admin Center Manage Data page.2. In Report Object Configuration Entity type, search for the custom MDF object.

A Report Object Configuration Entity type instance of the custom MDF object appears.

3. On the right side of the screen, click Take Action Make Correction .4. In the Sub-Domain Schema List section, select the schema you want to link with the custom MDF object

instance.

Stories in People AnalyticsConfiguring Custom MDF Objects for Reportability Using Story Reports PUBLIC 57

NoteYou can add multiple schemas to the list, and link them to the custom MDF object.

5. Click Save.

Results

The MDF object is linked with one or more schemas, and it becomes available for reporting in the Available Data section of the Query Designer page.

NoteEvery schema must have at least one root object to appear in the Available Data section of the Query Designer page.

Related Information

"Creating an MDF Object Instance" topic in the "Implementing the Metadata Framework (MDF)" guide

7.1 Creating Custom Schema for Story Reports

A reportable custom MDF object must be associated with a schema to become available for reporting using Story reports. So, you can create a custom schema to link with such MDF objects.

Context

A reportable custom MDF object appears in the Available Data section of the Query Designer page, only if it’s linked to a schema. You can either select an existing schema to link with the MDF object, or you can create a custom schema.

Procedure

1. Go to the Admin Center Manage Data page.2. In Create New, select Report Schema Configuration Entity.3. Enter the name of the Sub Domain Schema in Schema ID.


Configuring Custom MDF Objects for Reportability Using Story Reports

https://help.sap.com/viewer/e4a4ce68589841709a8202928c23803a/latest/en-US/f93a087e480544c59dcf352cc95fa210.html

4. In Schema Label, enter a label for the schema that appears in the Available Data section of the Query Designer page.

5. Click Save.

Results

The custom schema has been created, and it appears in the Sub-Domain Schema List section while editing a custom MDF object.

NoteEvery schema must have at least one root object.

7.2 Adding Root Object to Custom Schema for Reporting

By default, custom MDF objects are non-root objects. However, you can easily make a custom MDF object as the root object for the schema.

Context

A custom schema must have at least one root MDF object. The other objects, linked with the custom schema, must also be navigable from the root object.

Procedure

1. In Report Object Configuration Entity type, search for the custom MDF object.

A Report Object Configuration Entity type instance of the custom MDF object appears.

2. On the right side of the screen, click Take Action Make Correction .3. Update is Root to Yes.4. Click Save.

Stories in People AnalyticsConfiguring Custom MDF Objects for Reportability Using Story Reports PUBLIC 59

8 Creating a Story Report

Visualize or display the data that you retrieve through queries, in the form of charts, tables, pictograms, and so on.

Prerequisites

● Enable the Create Story permission, and select the schemas you want to use while creating report stories.● Enable schemaspecific permissions to access data from the schema tables. Refer to the Schema

Permissions Required for Using Story topic for more information.● Enable the permissions to access modulespecific data and to view the employeespecific data.

Context

Story is a presentation-style report that uses charts, visualizations, text, images, and pictograms to describe data. The Story type of report is available after you enable the Stories in People Analytics solution.

Stories involve queries that retrieve data that you want to report and widgets that represent the data. To build or update queries, you work on the query designer page. To manage the representation of the data the queries retrieve, you work on the story designer page.

Note

If you're unable to access or use the Story reports, go to the Admin Center Check Tool and use the Availability of user record for People Analytics check to troubleshoot the issue.

Procedure

1. Go to the Reporting module. The Report Center page appears.2. Click New, and select Story.

The Query Designer page appears.3. Build one or more queries (also known as private models in SAP Cloud Analytics), on which you can base your

story. Refer to the Adding Queries for Story Reports topic for more information.4. On Page 1 in the story designer, to add a widget that represents the story, click Chart or Table icons under the

Insert menu.

60 PUBLICStories in People AnalyticsCreating a Story Report

NoteFor SAP SuccessFactors HXM Suite users, we recommend that you use either Chart or Table. For more information on the other types of widgets, available under the option, refer to the SAP Analytics Cloud Help documentation.

The Builder section of the Design pane appears for the selected widget.5. Select one of your queries as the Data Source for the widget.

NoteIf you add a Chart widget, the Chart Structure appears in the design builder, and if you add a Table widget, the Table Structure appears in the design builder pane.

6. Under Chart Structure or Table Structure, build the structure of the selected widget as follows:a. Select the type of chart or table you want to create.b. Define the chart orientation, or define the column widths and arrangement of rows for table.

NoteYou can opt for pagination support to export all the rows of the table widgets, by selecting the Automatically resize table vertically option in the Designer Builder pane. The paginated view for table widgets is available only when you view or export the story to PDF or PPT formats, from the View mode.

c. Select Measures and Dimensions that appear on your chart, or select Rows and Columns that appear on the table.

NoteBy default, Count is a system-generated Measure that is added to a query. For tables, a default column is Measures, and it's set to Count.

d. For charts, add colors for each measure and dimension.7. To add filters to your story, click the Add Filters option under Filters in the Builder section of the Design pane,

and select the field on which you want to filter your report.

NoteYou can also add advanced filters, if needed. Refer to the topic on applying an Advanced filter for more information.

8. Optional: Click the Styling (paint brush) icon to style the table, chart, or selected widget on the story page.

9. In the File menu, click , and select Save.10. Enter a Title for the story, provide a suitable Description, and click OK.

Results

You’ve created a Story report successfully.

Stories in People AnalyticsCreating a Story Report PUBLIC 61

● To view your report click View on the top-right of the Story screen, or use the Run action for this report on the Report Center page.

● To edit the report, click Edit on the top-right of the Story screen.

You can also run or edit this story using Action Search, which finds the report by its name.

Read the Story Canvas Functions Available for Story topic to learn more about the actions that you can perform on the story.

Related Information

Filters in Query Designer of Story Reports [page 77]Adding Queries for a Story Report [page 64]Applying an Advanced Filter [page 81]Story Design Functions Available for Story Reports [page 72]SAP Analytics Cloud Help - StoriesUsing the Check Tool [page 168]

8.1 Type of Pages in a Story Report

You can select from three types of pages, while designing your Story report. The page types are Canvas, Responsive, and Grid.

The page type offers different characteristics. While designing your Story report, you can choose the page type that best suits your business needs.

Canvas

The Canvas page is the default page of your Story report. It's a flexible space where you can explore and present your data. You can use Canvas pages to bring your story to life. Add charts, tables, or some other objects that make your data visually appealing.

For example, if you don't like the placement of objects on your Canvas page, you can rotate, resize, or move the objects around to help you tell your story better. You can even copy the objects and paste them elsewhere on the same page, or paste them to a different Canvas page.

Similarly, you can also change the appearance of objects on your Canvas page. You can apply styling changes to individual objects, or group them together and then apply the styling changes.

62 PUBLICStories in People AnalyticsCreating a Story Report

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/29e0feaf17584e118ef30e6102008224.html

Responsive

The Responsive page lets you create lanes to section the page content into groups.

By default, a Responsive page starts with two lanes and you can add tiles (widgets) to either lane. Tiles within a lane stay together when the Responsive page is resized. For information on responsive lanes, read the topic on "Responsive Lanes".

You can preview a Responsive page to see how it looks on different screen sizes and device types. To preview a responsive page, from the story toolbar, select (Device Preview). From the preview screen, you can change the device or size to see how your page looks on a particular device or screen size. In some cases, tiles resize and flow to fit smaller resolution screens when space becomes limited.

NoteThe preview screen shows an approximation of how the tiles appear, but it isn't an exact match to how the tiles actually appear on a specific mobile device.

Grid

The Grid page is a space where you can create and work with formulas, either directly on the page or with a table that has been generated from existing data.

Related Information

Canvas PagesResponsive PagesResponsive LanesGrid PagesUsing Grid Pages to Create Custom Calculations Based on Data from Multiple Queries (Data Sources)

Stories in People AnalyticsCreating a Story Report PUBLIC 63

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/27682dd642674c7cbba92d04364a78d0.html

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/2565609b2d02464e8023b90e22155750.html

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/5c1f6d2cbd114a2a937ec090f1291538.html

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/5d10193a6c8d4ec987f4bbf82e3058f8.html

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/97afe7d9385647f68871e0c6eb8b299c.html

9 Adding Queries for a Story Report

Build queries that can be added to your stories to retrieve the right data for your business task.

Context

A query model is a representation of large amounts of business data, using common business terminology. The Query Builder enables you to select the fields which you want to include in your Story report. The queries you build using the Query Builder are equivalent to private models in SAP Analytics Cloud that are stored with the stories, and can't be accessed outside the story. You can create multiple queries (also, called as models and data source) for a Story report.

Note

If you're unable to access or use the Story reports, go to the Admin Center Check Tool and use the Availability of user record for People Analytics check to troubleshoot the issue.

Procedure

1. In Report Center, create or edit a Story.

The Query Designer tool in SAP Analytics Cloud appears. The data sets that you can use for building the query appear in the Available Data section, and a message to start building the query appears on the empty canvas.

2. Browse the module data sets in the Available Data section, and expand the data set for your report.

The primary tables of that data set appear, which you can further expand to view the field level details.

TipYou can find tables and columns within the available data sets using the <Search> Functionality. The schemas that have tables or columns matching the name you enter in <Search> Appear in the search results.

3. To select a table for your query, double-click it or drag-and-drop it on the query canvas.

The table appears on the canvas.

NoteAfter you have a table on the canvas, only the tables joined or related to that table appear in the Available Data section. If you don't find a table in the list of the related tables, you can create a join between the primary table on the canvas and the table you need. Refer to the topic on Schema Join Manager for more information.


Adding Queries for a Story Report

4. On the query canvas, click the table on which you want to build your query.

An action menu corresponding to the selected table appears.5. Use the following options on the action menu to add columns and filters to build your query.

Option Description

Show related tables Shows the tables, joined to the selected table. You can join different tables using the Admin Center Report Schema Join Manager tool. You can select columns from related tables to build your query.

Select columns Enables you to select columns for the query.

Add filters Enables you to add filters on your column selection. Applying filter is a good option to limit the data in a view without altering the design of the underlying object. It helps you see only the data that you want displayed. There are three types of filters you can apply to the table, Simple Filter, Time Filter, and Advanced Filter.

Remove table Removes the selected table from the canvas of the query designer.

6. To select columns for the query, click the table on the canvas, and either click the icon for columns to select columns from the same table, or click the related tables icon to see the related tables and select columns from the related tables.

NoteFor a particular field in the table, when you see:○ A Lock icon (), it means you don't have the role-based permissions required to access the data in that

field. You will still be able to select the field in the query, however you won’t see any data in that field. When other users run the report they see data based on their role-based permissions. You can check and update the data access permissions granted to you for the particular fields in that module to resolve the constraint.

○ A Shield icon, it means that the field includes sensitive information. If you add sensitive columns to the report, the read access logs are generated each time someone uses (previews, schedules or generates) the report. You must also include the context field (such as User Sys ID) to the report to enable the read access logging.

7. Optional: Click the Create Calculated Column icon in the Data section of the toolbar to add calculated columns to your query. Refer to the Calculated Columns section for more information.

TipIf you select two or more columns with the same name, then click the Create Calculated Column icon, and on the Column Overview dialog that appears, edit the column description and rename the columns to avoid confusion.

8. Optional: Add filters on the selected columns or the tables, if required. Refer to the Use of Filters in a Query section for more information.

Stories in People AnalyticsAdding Queries for a Story Report PUBLIC 65

NoteCurrently, your query can include only up to 30 columns, which are selected from maximum 30 tables. Your query can retrieve data up to 1,000,000 cells.

9. Click Preview Query to take a quick glance at your query for the columns you've selected and the data they retrieve.

NoteYou can click Hide Preview to hide the preview of the query, and you can click Cancel to discard the query.

10. If you've selected "As of Date" type columns in your report, set the Date value.11. If you're happy with the query, click Finish.

The Model Information dialog appears.12. Enter a Query Name along with an appropriate Description.

RememberYou cannot edit the name and description of your query after you save it.

13. Click OK to save the query.

The query (private model) is saved.

Results

You have successfully created a query, and you are redirected to the story canvas. You can build multiple queries for a story. To edit an existing query or build another query, click the (More) menu, select Add or Edit Datasources. Click the name of an existing query to edit it, or click Add New Datasource to create a new one. The Query Builder appears. After you add or edit the query, you are again redirected to the story canvas.

Next Steps

Continue with the creation of your Story report. Assign your queries to charts or tables and apply the various capabilities that the story canvas offers to achieve a desired graphical representation of the data the queries retrieve.

Related Information

Filters in Query Designer of Story Reports [page 77]Creating Calculated Columns for Stories in People Analytics [page 138]Creating a Story Report [page 60]Available Data (Schema) in Story Reports [page 86]


Adding Queries for a Story Report

Schema Joins Available for Story Reports [page 113]Story Design Functions Available for Story Reports [page 72]Permissions Required for Using Story Reports [page 26]Using the Check Tool [page 168]

Stories in People AnalyticsAdding Queries for a Story Report PUBLIC 67

10 Creating Reports Using Blended Data from Multiple Queries (Data Sources)

You can create stories with visualizations using data from multiple queries or data sources.

Prerequisites



Context

Blending data sources lets you join a primary data source with secondary data sources that contain common linked dimensions. For example, you can blend data from a Job Information data source with User Information data. Blending can be done within individual charts.

NoteCurrently, Table widgets don’t support data blending.

Procedure

1. Create a new Story report or edit an existing one.2. Add two or more queries (data sources) that can logically be linked with one another.3. On the Story Designer page, add a Chart widget, and select the widget.

The Builder section of the Design pane appears for the selected widget.4. Select one of the queries as the primary Data Source for the chart.5. Choose the Add Linked Models link.

The Link Dimensions dialog appears that allows you to link two data sources. By default, the primary data source is selected as the left data model and its dimensions are listed below.

6. On the right hand-side, select the other data source that you want to link to your primary data source.

The dimensions of the second data source also appear.7. From both data sources, select the dimensions that can be linked logically.


Creating Reports Using Blended Data from Multiple Queries (Data Sources)

For example, if your primary data source is Job Information and secondary data source is User Information, you can link the two data sources using the "User ID" dimension.

8. Choose Set.

The linked or the blended data source is created and it appears below the primary data source on the Builder panel.

NoteBy default, the Link Type of the blended data source is All primary data (which is also known as the left-outer join). You can edit the Link Type to All data (also known as outer join) or to Intersecting data only (also known as inner join).

Stories in People AnalyticsCreating Reports Using Blended Data from Multiple Queries (Data Sources) PUBLIC 69

9. From the blended data source, select Measures and Dimensions that you want to show on your chart.

10. Save the changes to your Story report.

Results

You’ve successfully created (or updated) a Story report using a blended data source.


Creating Reports Using Blended Data from Multiple Queries (Data Sources)

Related Information

Creating a Story Report [page 60]Adding Queries for a Story Report [page 64]

Stories in People AnalyticsCreating Reports Using Blended Data from Multiple Queries (Data Sources) PUBLIC 71

11 Story Design Functions Available for Story Reports

Use a set of the SAP Analytics Cloud functions that People Analytics supports to build new or edit existing Story pages. The supported functions are available as menu options during the story design phase.

File Menu

Option Description

(Edit Story) > Story Details Allows you to rename the story.

> Preferences Allows you to set your story preferences to specify default formatting options in a story, such as the page size and background color, the text style and background color of tiles, or the color palettes of charts.

> Query Settings Allows you to enable query batching.

> Save Allows you to save the story report.

> Save As Allows you to save another copy of the Story report.

> Save As Template Allows you to save the Story report as a template that can be used to create a new story.

> Export Allows you to export the Story report to a PDF file or into Google slides.

> Copy Creates a copy of a story component (like, chart or table) on your clipboard.

> Copy To Creates a copy of a story component (like, chart or table) and paste it to a new Canvas or a new Responsive.

> Duplicate Creates a duplicate copy of the selected story component on the same page.

> Paste Allows you to paste a copy of the story component from your clipboard to your selected location in the story.

> Paste Special Allows you to choose to Copy Source Distribution or Keep Target Distribution, and set the selected option as the default for future Paste Special operations.

Insert Menu

Option

(Chart) Inserts a chart component on the current page of your story.

(Table) Inserts a table component on the current page of your story.


Story Design Functions Available for Story Reports

Option

Input Control Allows you to create a page filter on a dimension or a measure that is represented on a chart or table to change it at view time.

(Add) Allows you to add Image, Shape, Text, Clock, RSS Reader, Web Page, and Symbol to build your story.

Tools Menu

Option Description

(Story Filter/Prompt) Allows you to create a story filter based on the dimension or measure from the selected query (data source).

(Formula Bar) Allows you to calculate values in empty table rows and columns, or cells outside a table. The formula is displayed by default. Choose the icon in the formula bar to toggle between displaying the formula and the text value.

(Chart Scaling) If multiple charts in a story contain the same measure, the measure values can be scaled differently in different charts, which can make comparisons difficult. This option allows you to scale the charts so that measures have the same scale across multiple charts.

Conditional Formatting Allows you to highlight information using several options, including thresholds in queries (data sources) and stories, and assigned colors in stories.

Cell References and Formulas Allows you to show or hide references and show formulas.

You can use references to other cells, including cells that contain model data. To add a reference while typing a formula, type the coordinate of the cell (for example, E6), or select the cell. You can also click and drag to select cell ranges, and click an existing reference in the formula and select a new cell to update the reference. Each cell reference is identified by color in the cell and the formula.

You can add a formula to an empty cell in a grid, or to an empty row or column in a table. To add a formula, select an empty column or row header, or an empty cell outside a table, and start typing the formula text, beginning with an equals sign (=). (If the formula is a long one, you can prefer to type it in the formula bar instead.)

Format Menu

Option Description

Layouts Allows you to set and format the story layout.

Stories in People AnalyticsStory Design Functions Available for Story Reports PUBLIC 73

Display Menu

Option Description

Comment Mode Allows you to view the comments posted on the story components.

Examine Allows you to examine the data behind a chart or value driver tree, or view a chart based on selected table data.

While designing your story, you can open the Examine panel to explore certain types of tiles:

● Select a chart. The data that makes up the chart is shown in the Examine panel. If you filter the chart by selecting data points or dragging a rectangle around data points, only the selected data is shown in the Examine panel.

● Select a value driver tree tile, or a node within the tile. The data for the value driver tree, or the selected node, is shown in a table view in the Examine panel. You can create or change values for data source nodes and base values for year-over-year nodes by typing in the corresponding table cells.

● Select a table, or select cells within the table. A visualization based on the selected data in the table is shown in the Examine panel. You can also change the visualization type, or select the icon to apply operations such as sorting and ranking.

Enable (Synchronize Visualization Automatically) to update the chart as you select cells (you can disable this option by selecting the icon again).

If the Synchronize Visualization Automatically option is disabled, select (Synchronize Visualization) to update the chart manually.

If you want to save charts and tables from the Examine panel, first copy them to story pages.

Explorer View Mode Allows you to modify charts and tables in the Explorer view. You can create multiple explorer views of each widget, copy the explorer views, and paste them as new widgets on any of the existing pages or a new Canvas or Responsive page in the story.

If explorer is enabled for at least one of the widgets in the story, this option toggles the display of the story to the explorer view. If explorer hasn't been enabled for any widget, this option allows you to enable the explorer for all widgets in the story.

You can manage the explorer for all widgets, using the Enable Explorer for all Charts and

Tables option available on the File Story Details screen.

More Menu

Option Description

Refresh Refreshes the data in various components on the Story page.



Option Description

Edit Prompts Allows you to set variables for the prompts defined in the story. The prompts are applied to the queries in the Story reports.

NoteOn the pop-up to set variables,

● If you select the Automatically open prompt when story opens check box, you’re prompted to set the variable value for the prompt during scheduling.

● If you don't select the Automatically open prompt when story opens check box, the predefined value for this prompt filter gets applied to the report.

Link Dimensions Allows you to create links between dimensions in multiple queries (data sources).

Add or Edit Datasources Allows you to add a new query (data source) or edit an existing one.

Designer Menu

The Designer menu applies to a component you’ve selected on the current page of your story.

Option Description

Builder Allows you to:

● Select a data source to build the selected component.● Define structure of the selected component.● Add measures, dimensions, and filters to build the compo

nent view.

Styling Allows you to set the various styling options like color, font, formatting, etc. for the entire page or for your selected component on the page.

Controls Menu

Allows you to manage the filters for charts, tables, or any filterable widgets.

View/Edit

Allows you to view the story output or edit the story.

Stories in People AnalyticsStory Design Functions Available for Story Reports PUBLIC 75

Related Information

SAP Analytics Cloud Help - Stories



https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/29e0feaf17584e118ef30e6102008224.html

12 Filters in Query Designer of Story Reports

While creating queries for your Story reports, you can apply filters to refine the data records retrieved using the query.

Applying filter is a good option to limit the data in a view without altering the design of the underlying object. It helps you see only the data that you want displayed.

You can apply multiple filters, while building queries and while designing the Story report. For the query building phase, you have Table filters that are applied to individual tables within a query, and Query Filters that are applied to the entire query.

● Table Filters: Simple Filter, Time Filter, and Advanced Filter● Query Filters: Scope Filter and Advanced Filter

TipFor the story design phase, you have Story Filter and Page Filter.

● The Story Filter allows you to apply filters for all charts in a Story that are based on the same query (data source).

● The Page Filter is the same as a Story Filter, but applies to just one page in a story. (An Input Control is one type of page filter.)

Using Filters in the Query Designer Phase

Applying a Simple Filter [page 78]Use Simple Filter on a table to limit the records from one or more of its selected columns.

Applying a Time Filter [page 79]If you want to retrieve data over a date range or as of a particular date, you can use the time filter on a table while building a query.

Applying an Advanced Filter [page 81]Advanced filtering allows you to filter multiple data fields by defining a set of logical conditions.

Applying a Scope Filter [page 84]The scope filter allows you to decide the scope of the report in terms of the people you want to include in the report.

Related Information

Story and Page Filters in Story Reports

Stories in People AnalyticsFilters in Query Designer of Story Reports PUBLIC 77

https://help.sap.com/viewer/00f68c2e08b941f081002fd3691d86a7/release/en-US/71e6b3a0f8fb465caa156e6417b68b79.html

12.1 Applying a Simple Filter

Use Simple Filter on a table to limit the records from one or more of its selected columns.

Context

You can define a simple filter to display data for specific column values in a table. You can apply a simple filter on one column at a time, but you can apply multiple simple filters to a table.

Procedure

1. On the Query Designer canvas, find the table for applying the simple filter and click it.

2. Click the (filter) icon and select Simple Filter.3. From the list of columns that you see, select a column for your simple filter.

The Select Members dialog appears, and the Available Members section shows all the values of the selected column appears.

4. From the Available Members section, select the values you want to include in your filter definition.5. Check the Selected Members list to ensure that your choices are correct.6. Click OK.

You've successfully created a simple filter for the selected table.

Next Steps

Using the Simple Filter option for a table, you can

● Edit an existing filter definition by clicking it.● Define another simple filter for that table by clicking Add Filter.


Filters in Query Designer of Story Reports

12.2 Applying a Time Filter

If you want to retrieve data over a date range or as of a particular date, you can use the time filter on a table while building a query.

Context

You can use Time filters on schema tables, only while building queries. Time filters are applicable for Employee Central tables, and the tables connected to Employee Center schemas.

Procedure

1. Click the table on which you want to apply the Time filter, and on the action menu that appears click .2. Select Time Filter.

A pop-up to manage time filter appears, and <Today> is selected, by default. Please note that <Today> is available under the As of Date option of time filters.

3. If you want a time filter other than <Today>, click Remove Filter.

The <Today> filter option is removed, and the time filter pop-up shows two options - As of Date and Date Range.

4. Choose an option.

If you choose... then...

As of Date Select either a <Fixed Date> or a <Dynamic Date>, and set a date value for the filter.

Date Range Configure the date range values for the filter. For more information, see the "Configuring Date Range in Time Filter" topic.

5. Click OK.

A confirmation message indicating that the filter has been successfully set appears.

Results

Click and select Time Filter. The time filter settings that you applied appear on the pop-up for managing time filters along with Edit Filter and Remove Filter options. You can:

● Edit the configuration of the applied filter using the Edit Filter option.● Remove the applied filter using the Remove Filter option.


12.2.1 Configuring Date Range in Time Filter

You can retrieve data from a selected schema table for a defined duration by configuring and applying the Date Range option of time filter.

Context

This configuration applies when you use a Time Filter with the Date Range option. To get to the date range configuration dialog, select a schema table on the query canvas, click , (remove existing filters, if any), and select

Time Filter Date Range . The Set Date Range dialog appears.

Procedure

1. Go to the Range Definition section, select <Range Type> as Dynamic.

NoteIf you select <Range Type> as Fixed, set the Range Period by selecting the start and end dates. Next, go to the step for configuring the Records Returned section.

2. Select the Granularity of the date range to "Day", "Week", "Month", "Quarter", or "Year".3. Set the Range Period to current, previous or future instance of the selected granularity.

For example, if you select Day as the granularity of the date range, in Range Period you can select "Today", "Yesterday" or "Tomorrow"; whereas if you select granularity as Year, in Range Period you can select "This Year", "Last Week" or "Next Week".

4. In the Range Extension section, widen the date range by adding instances of selected granularity to the Start and Finish values of the date range.

NoteBy default, the values are set to "0". You can set only non negative integer values for Start and Finish fields.

For example, if you select Day as the granularity and Today as the range period, then your selected date range is set to the current day. However, if you set Start and Finish values to 1, your date range extends to three days, which starts from the previous day and ends on the next day.

5. Select one of the following options in Range Parameters to further refine the date range.

○ From the first day until the last day of the defined range: This option sets the date range to the entire duration defined using the Granularity, Range Period, and Range Extension fields.

○ Period to Date - From beginning of defined range until today: This option respects the start date defined using the Granularity, Range Period, and Range Extension fields, but it sets the end date of the date range to the current day.

○ Period to Go - From today until the end of defined range: This option sets the start date of the date range to the current day, but it respects the end date defined using the Granularity, Range Period, and Range Extension fields.



6. Optional: Check Range Overview, the topmost section of section of the Set Date Range dialog to review the date range you've defined.

7. Go to the Records Returned section, and select one of the following options to define the impact of the date range while filtering the records.

○ Include any records that partially or completely overlap your defined date range: Returns records from within the date range, and records with a date range that overlaps the defined date range.

○ Include only records that begin during your defined date range: Returns only those records where the start date of the record lies within the defined date range.

8. Click OK.

Results

You have successfully configured the date range of a time filter and applied it to the selected table.

12.3 Applying an Advanced Filter

Advanced filtering allows you to filter multiple data fields by defining a set of logical conditions.

Context

Advanced filtering mainly uses AND or OR conditions to filter the data fields. These conditions can be set to Include or Exclude the data that satisfies the filter conditions.

Add new conditions using the "+" button, and choose either fields or operators to create nested filters.

Currently, advanced filtering can be used on both queries and stories. You can apply an advanced filter for an entire story page or on individual widgets. The option for advanced filters is enabled only after you add at least one table to the query canvas or one chart to the story page.

NoteThe way you access the Advanced Filter option defines its application.

● While creating a query, to apply the advanced filter on the entire query, click from the Data menu (available on the top section) of the query builder.

● While creating a query, to apply the advanced filter on a table on the query canvas, click the table and select corresponding to the table.

● On the Story page, to apply the advanced filter as a story filter that applies to the entire page, click on the Tools menu.

● On the Story page, to apply the advanced filter to a chart or a table, select the chart or table and click the corresponding option.


Procedure

1. Click , and select Advanced Filter.

The Set Conditions for Advanced Filter dialog appears.2. Enter a Name for the filter.3. Under Conditions, select either OR to execute the filter when any of the following conditions are met or AND to

execute the filter when all of the following conditions are met.4. Click the "+" button, and select either a Data Table to create a condition or an Operator to create nested filters.5. After you select a Data Table to create a condition, select a Column from the table.6. Select an operator to filter data from the selected column.

○ For all columns, you can apply Equal to, Except, Is null, or Is not null as the operator.○ For String type columns, you can additionally apply Like.○ For Numeric, Integer, Decimal, Date and Datetime types of columns, you can additionally apply Greater

than, Greater than or equal to, Less than, Less than or equal to, or Between.7. Select filter type to complete the condition.

Filter Type Allows you to...

Free Text Enter a filter value you want to apply.

Member Selector Choose field values from the selected column as your filter.

Column Choose another column as your filter.

Input Parameter Select a parameter as your filter, if you've created input parameters. For more information, see the "Creating Input Parameters for Advanced Filtering" topic.

TipClick to delete a condition.

8. Repeat steps four through six to add more operators and conditions, if needed.

9. Optional: On the AND or OR operator, use option to:

○ Allow or prevent viewers from disabling the condition.○ Collapse child conditions.○ Delete () the operator.

10. After you have configured the conditions, click OK to apply the advanced filter.

Results

The advanced filter has been applied successfully.

NoteClick , select Advanced Filter, and then select the filter you've created to review or edit the applied filter.



Related Information

Creating Input Parameters for Advanced Filtering [page 83]

12.3.1 Creating Input Parameters for Advanced Filtering

Make your data filtering more flexible using parameters in advanced filters.

Context

Parameters enable you to update your filter easily. Using Edit Prompts in Story, you can prompt users to provide filter inputs during story execution.

Procedure

1. In Report Center, create a new Story report, or edit an existing Story report and go to Edit Datasource.

The Query Designer page appears.2. Select {} (Input Parameter)

The Input Parameter dialog box appears.

3. Select to add an input parameter.4. Enter a suitable Input Parameter Name.

NoteYou can add "_", but you can't add space in Input Parameter Name.

5. Select Type of input parameter.

NoteA parameter must be of the same data type as the field on which you intend to apply it.

While you can set the data type to either String, Numeric, Decimal, Integer, Date or Datetime, most of the fields in SAP SuccessFactors products are of type String, Decimal, and Datetime.

6. Enter Default Value for the input parameter.7. Click OK.


Results

You've successfully created an input parameter that you can use in advanced filters.

Related Information

Applying an Advanced Filter [page 81]

12.4 Applying a Scope Filter

The scope filter allows you to decide the scope of the report in terms of the people you want to include in the report.

Context

The scope filter is a query filter, which applies to the primary schema table in the query.

NoteThe scope filtering functionality is available only if the schema table selected on the query canvas supports it, else the Scope Filtering option appears gray.

Procedure

1. After you've a table on the Query Designer canvas, on the Data menu above the canvas, click , and click to choose a query filter.

2. Click the Scope Filtering option, and select the table for which you're applying the scope filter.

The Scope Filters dialog appears.3. In the Start With list, define the starting point for the scope of the report. You can either select the default value

of All Data Included, or select a user role from where you begin filtering the report data, like "Manager", "Human Resource","Matrix Manager", "Custom Manager", and "Second Manager".

NoteIf you select All Data Included and click OK, the scope filter is applied to the query and the report includes all the data for all employees. However, if you select any of the user roles, the report includes data only for employees within the defined scope of the selected user role.



4. If you select a user role in Start With, in Up to, select the hierarchy levels under the selected user role to be included in the report.

Option Description

All Levels Selects all direct and indirect reports of the Start With user role.

Direct Reports Selects only the direct reports of the Start With user role.

Levels Allows you to define the hierarchy levels under the Start With user role that you want to include in the report.

5. For data tables that support scope filtering by both Person and Position, select any one of them in the Who should be the subject of this report? section.

NoteThe Position option in Scope Filtering appears only for the Position table of the Succession Nominations (MDF Position) schema.

6. Select any user or a position ID as the subject for the scope filter.

For example,○ If you select Logged In User (which belongs to the Person scope), the scope of the filter begins with the

employee who runs the report, and if you select an employee, the scope of the filter begins with the selected employee.

○ Whereas, for the Position table of the Succession Nominations (MDF Position) schema, if you select Position and Position of Logged in User, the scope of the filter begins with the organizational position of the employee who runs the report.

7. In the Who should this report include from this domain? section, use the options to further refine the selection of employees you want to include in the report.

Option Description

Include inactive users in the data Select this option to include inactive employees within the scope of the subject of this report.

Include the subject data in the report Select this option to include the data of the subject of this report.

8. Click OK.

Results

The scope filter has been successfully applied to the query, and it appears in a row above the Query Designer page. Click the query to edit it, or click the icon on the top-right of the query to delete it.


13 Available Data (Schema) in Story Reports

Take a quick look at the product schemas on which you can report using Story reports.

NoteThe list of SAP SuccessFactors product schemas available for Story reports is evolving, and this might cause intermittent discrepancies in the list of schemas included in the documentation versus the list of schemas available in the application. Please refer to this list only to understand the details of the documented schemas.

Product Schema Table Purpose of the Table

Effective Dated Filter?

Scope Filter?

Default Filter?

360 Degree Multi-rater

Form Show Details of the Forms launched for 360 Reviews

NA NA NA


Form Overall Ratings Show Details of the Overall Ratings on the form

NA NA NA


Form Routing Information

Show Routing Details of the form NA NA NA


Participant Show Details about the Participants of a form

NA NA NA


Participant Basic Information

Show more Details about the Participant

NA NA NA


Form Section Show Details about the sections on the form

NA NA NA


Participant Overall Rating Show Overall Ratings for participants NA NA NA


Competency Show Competency Details for the form NA NA NA


Objective Show Objective Details for the form NA NA NA


Custom Element of Custom Section

Show Custom Elements in the form NA NA NA


Custom Element of Competency

Show Custom Elements in the Competency Sections

NA NA NA


Custom Element of Objective

Show Custom Sections in the Objective Sections

NA NA NA


Behavior Show Behaviour Details for the form NA NA NA


Form Completion Information

Show Completion Details about the form.

NA NA NA


Available Data (Schema) in Story Reports



Scope Filter?

Default Filter?

Advances Accumulation For Advances

Advances Advance

Advances AdvancesInstallments

Advances Eligibility For Advances

Advances Non Recurring Payment

Apprentice Management

Apprentice School


Apprentice School Event


Apprentice


Apprentice Event Type


Apprentice Group


Apprentice Internal Training


Apprentice On-The-Job Training


Apprentice School

Benefits Balance Carry Forward

Benefits Benefit

Benefits Benefit Balance Carry Forward Details

Benefits Benefit Claim Accumulation

Benefits Benefit Company Car

Benefits Benefit Company Car Allowed Models

Benefits Benefit Company Car Enrollment

Benefits Benefit Company Car Lease Service Provider

Benefits Benefit Company Car Recommended Vendors

Benefits Benefit Contact

Benefits Benefit Deduction Detail

Stories in People AnalyticsAvailable Data (Schema) in Story Reports PUBLIC 87



Scope Filter?

Default Filter?

Benefits Benefit Dependent Detail

Benefits Benefit Documentation

Benefits Benefit Effective Date Configuration

Benefits Benefit Employee Car Claim

Benefits Benefit Employee Claim

Benefits Benefit Employee Claim Details

Benefits Benefit Employee Opt-out Requests

Benefits Benefit Employment Opt-out Details

Benefits Benefit Enrollment

Benefits Benefit Exceptions Details

Benefits Benefit Fuel Reimbursement

Benefits Benefit Insurance Dependent Details

Benefits Benefit Life Event Configuration

Benefits Benefit Payment Options

Benefits Benefit Pension Employee Contribution Detail

Benefits Benefit Pension Employer Contribution Detail

Benefits Benefit Pension Fund

Benefits Benefit Pension Statutory Lookup

Benefits Benefit Program

Benefits Benefit Program Enrollment

Benefits Benefit Savings Plan Tier Configuration

Benefits Benefit Schedule Period

Benefits Benefit Schedules





Scope Filter?

Default Filter?

Benefits BenefitPensionEnrollmentContributionDetail

Benefits Benefits Exception

Benefits Benefits Exception

Benefits Company Housing

Benefits Company Housing Enrollment

Benefits Default Insurance Plan

Benefits Delected Benefit

Benefits Dependent Nominees

Benefits Eligible Employees Data For Benefit

Benefits Eligible Enrollee Options

Benefits Employer Contribution Details

Benefits Fuel Reimbursement Claim Details

Benefits Fund Contribution Details

Benefits Insurance Coverage

Benefits Insurance Coverage Details

Benefits Insurance Coverage Options

Benefits Insurance Dependent Type

Benefits Insurance Plan

Benefits Insurance Plan Enrollment Details

Benefits Insurance Provider

Benefits Insurance Rate Chart

Benefits Legal Entity For Benefit

Benefits Non-dependent Nominees

Benefits Rate Chart For Plas Covering Dependents only




Scope Filter?

Default Filter?

Benefits Rate Chart For Plas Covering Employee and Dependents

Benefits Savings Plan Catch Up Detail

Benefits Savings Plan Contingent Beneficiary

Benefits Savings Plan Employer Contribution

Benefits Savings Plan Enrollemnt Details

Benefits Savings Plan Primary Beneficiary

Benefits Selected Wallet

Calibration Calibration Session Show Details of the Calibration Session NA NA NA

Calibration Calibration Subject Show Details of the Subject in the Session

NA NA NA

Calibration Calibration Template Show Details of the Calibration Template

NA NA NA

Calibration Session Reviewer Show Details of Reviewers in a Calibration Session

NA NA NA

Calibration Rating Change Details of any change in Rating NA NA NA

Calibration Rating Overall View Details of Rating change at activation and finalization of a Session

NA NA NA

Calibration Subject Ranking Ranking of a subject in a Session NA NA NA

Compensation Eligibility Rule Provides Rule Name, Rule ID and the impact of which fields a user is eligible or ineligible based on the results of the rule

No None None

Compensation Eligibility User Info Provides basic user information for the usesr to whom the rule is being applied

No People Scope filter supported

None

Compensation Template Name Provides template name and localized template name associated with the eligilbity rules

No None None

Compensation (Recurring and Non Recurring)

Compensation


Compensation Information





Scope Filter?

Default Filter?


Spot Bonus

Compensation Planning

Template Provides basic template-level information, including name, route step and start and end information.

No None None


Worksheet Provides information about form-level data that can differ from each planner's form. Includes start nd end dates, owner, when last modified and form-level budget information

No None None


Employee Entry Provides employee-level information and for variable pay programs, the summary level information. Includes all planning information and columns, standard and custom fields, eligiblity information, notes, and last modified information, etc.

No People Scope filter supported

None


Budget Info Provides budget inforamtion associated wit the form, including the name, value and total.

No None None


GuideLine Info Provides information for guidelines associated with the employee entry level associated to the specific employee

No None None


Rating Info Provides rating information for each of the multiple types of rating on a form at the employee entry level, including values and ratings across all tabs and types

No None None


Comments Provides comment information for force-comment fields that can have multiple values per employee. Not to be confused with entry-level comments found on the Employee Entry table

No None None


Bonus Assignment Variable Pay and Total Comp Template Only - Provides assignment level information, such as information from Employee History file, as well as assignment level targets, basis, attainments, etc. Child of Employee Entry table and parent of Team, Individual and Business Sections

No None None


Form Subject Basic information about the user for whom the form was created, i.e. the Planner versus the individuals on the form whose compensation appears.

No None None




Scope Filter?

Default Filter?


Business Section Variable Pay and Total Comp Template Only - Provides Business Section information, such as section totals, sums of business goals, section weights and custom fields. Child of Bonus Plan and parent of Business Goal information. Will only appear if template has business section configured.

No None None


Business Section 1 Variable Pay and Total Comp Template Only - Provides Business Section information, such as section totals, sums of business goals, section weights and custom fields. Child of Bonus Plan and parent of Business Goal information. Will only appear if template has business section configured using multiple business sections. This is section (1)

No None None



No None None


Business Section 3 Variable Pay and Total Comp Template Only - Provides Business Section information, such as section totals, sums of business goals, section weights and custom fields. Child of Bonus Plan and parent of Business Goal information. Will only appear if tempalte has business section configured using multiple business sections. This is section (3)

No None None



No None None





Scope Filter?

Default Filter?



No None None


Business Goal Variable Pay and Total Comp Template Only - Provides Business Goal information, such performance values and payout curves, actuals, forcast information, etc.. Child of Business Section. Will only appear if template has business section configured.

No None None


Business Goal - Sect 1 Variable Pay and Total Comp Template Only - Provides Business Goal information, such performance values and payout curves, actuals, forcast information, etc.. Child of Business Section. Will only appear if template has business section configured using multiple business sections. This is for goals in section (1)

No None None



No None None



No None None




Scope Filter?

Default Filter?



No None None



No None None


Team Section Variable Pay and Total Comp Template Only - Provides Team Section information, such as section totals, sums of team goals, section weights and custom fields. Child of Bonus Plan and parent of Team Goal information. Will only appear if template has Team section configured.

No None None


Individual Section Variable Pay and Total Comp Template Only - Provides Individual Section information, such as section totals, sums of team goals, section weights and custom fields. Child of Bonus Plan and parent of Individual Goal information. Will only appear if template has Individual section configured.

No None None


Team Goal (ABR) Variable Pay and Total Comp Template Only - Provides Team Goal information, such performance values and payout curves, actuals, forcast information, etc.. Child of Team Section. Will only appear if template has Team section configured. Assignment Based Rating programs only.

No None None





Scope Filter?

Default Filter?


Individual Goal (ABR) Variable Pay and Total Comp Template Only - Provides Individual Goal information, such performance values and payout curves, actuals, forcast information, etc.. Child of Individual Section. Will only appear if template has Individual section configured. Assignment Based Rating programs only.

No None None


Team Goal Variable Pay and Total Comp Template Only - Provides Team Goal information, such performance values and payout curves, actuals, forcast information, etc.. Child of Team Section. Will only appear if template has Team section configured.

No None None

Compliance Compliance Process Contains details of process type, status, initiator, and responsible user details.

No No NA

Compliance Compliance Process Task Contains compliance process task details.

No No NA

Compliance Compliance Process Responsible Object

Contains the details of the user who is responsible for the compliance process.

No No NA

Compliance Compliance Form Data Holds information related to compliance document flow, DocuSign envelope Id, compliance form details, compliance form signature.

No No NA

Compliance Compliance Form Contains form metadata information. No No NA

Compliance Compliance Form Signature

Contains information regarding the signatory, and the current status of the signature process.

No No NA

Compliance Compliance Document Flow

Contains information like document flow code, document status, reason for decline, declined by, and list of declined documents.

No No NA

Compliance Form Group Metadata Contains form group code, and country/ region information for a form.

No No NA

Compliance E-Verify Data Contains E-Verify form data. No No NA

Compliance E-Verify Case Status Details

Contains sase status details for E-Verify.

No No NA

Compliance I9 Audit Ttrail Contains information for I-9 user audit trail.

No No NA

Compliance I9 Document Contains document details like document number, document issuer, expiration date, document type, and so on.

No No NA




Scope Filter?

Default Filter?

Data Replication Employee Data Replication Confirmation Error Message

Data Replication Employee Data Replication Notification

Data Replication Employee Data Replication Status

Data Replication Last Confirmation

Data Replication Last Confirmation with Success

Data Replication Replication Target System

Data Replication SAP System Configuration

Deductions One Time Deduction

Deductions Recurring Deduction

Deductions Recurring DeductionItem

Goal Management OBJECTIVE maintain user's objective N N Y

Goal Management OBJ_METRICLOOKUP maintain user's metric lookup information

N N N

Goal Management OBJ_COMMENT maintain user's objective comments N N N

Goal Management OBJ_AUDITTRAIL maintain objetive's audit trail information

N N N

Goal Management OBJPLAN_TEMPLATE maintain objective template information

N N Y

Goal Management OBJ_MILESTONE_milestone

maintain sub objective - milestone N N N

Goal Management OBJ_MILESTONE_target maintain sub objective - target N N N

Goal Management OBJ_MILESTONE_task maintain sub objective - task N N N

Goal Management OBJ_STATUS_ITEM maintain objective's status information N N N

Career Development Planning

LEARNING maintain legacy learning information of objective

N N N

Employment <Country> Employment Details

Employment <Country> Job Information

Employment Alternative Cost Distribution





Scope Filter?

Default Filter?

Employment Alternative Cost Distribution Item

Employment Direct Reports

Employment Dismissal Protection Type

Employment Employee Dismissal Protection

Employment EmployeeDismissalProtectionDetail

Employment Global Assignment Details

Employment Home Assignment

Employment Job Information

Employment Job Relationship

Employment Payment Information

Employment Payment Information Detail

Employment Payment Information Detail <Country>

Employment Payment Method

Employment Payment Method Assignment

Employment Pension Payments

Employment Secondary Assignment Item

Employment Secondary Assignments

Employment Supervisor

Employment User

Employment User ID

Employment VendorInfo

Employment Work Order

Employment Work Order Owner

Employment Worker

Employee Profile Badge Information Show details about the badges that employees create and receive, including the dates a badge is created and last modified, badge creater, and badge recipient

No No No




Scope Filter?

Default Filter?

Employee Profile Custom_Background Show the background information of employees

NoteThe table and columns are displayed according to the configuration in the Data Model.

No No No

Employee Profile Custom_Trend Show the rating information of employees, for example, the overall ratings for performance and objectives

NoteThe table and columns are displayed according to the configuration in the Data Model.

No No No

Employee Profile Photo Show information about whether a user has a profile photo

No No No

Employee Profile Profile Completion Show information about the percentage of profile completion

No No No

Foundation Objects

Bank

Foundation Objects

Business Unit

Foundation Objects

Company Contact Details

Foundation Objects

Competency

Foundation Objects

Corporate Address

Foundation Objects

Cost Center

Foundation Objects

Country

Foundation Objects

Currency

Foundation Objects

Department

Foundation Objects

Division





Scope Filter?

Default Filter?

Foundation Objects

Dynamic Role

Foundation Objects

Event Reason

Foundation Objects

Frequency

Foundation Objects

Geo Zone

Foundation Objects

Job Classification

Foundation Objects

Job Classification <Country>

Foundation Objects

Job Classification Country

Foundation Objects

Job Function

Foundation Objects

Legal Entity

Foundation Objects

Legal Entity <Country>

Foundation Objects

Location

Foundation Objects

Parent CostCenter

Foundation Objects

Parent Department

Foundation Objects

Parent Division

Foundation Objects

Parent Job Classification

Foundation Objects

Parent Job Function

Foundation Objects

Parent Reporting Entity

Foundation Objects

Pay Component

Foundation Objects

Pay Component Group

Foundation Objects

Pay Grade




Scope Filter?

Default Filter?

Foundation Objects

Pay Group

Foundation Objects

Pay Range

Foundation Objects

Pay Scale Area

Foundation Objects

Pay Scale Group

Foundation Objects

Pay Scale Level

Foundation Objects

Pay Scale Type

Foundation Objects

Reporting Entity for North America

Foundation Objects

Unit of Measure according to UN/CEFACT Recommendation 20/21

IT Declaration Declaration Type

IT Declaration Income Tax Declarations

IT Declaration Investment Types For Tax Declaration

Login Data Login detail Provides access date No Yes, only populates Login audit data in SF_Sysaudit table

Yes, only populates Login audit data in SF_Sysaudit table

Login Data User account Provides Login name No No No

Mentoring MENTORING_PROGRAM maintain mentoring program data N N Y

Mentoring MENTORING_PARTICIPANT

maintain mentoring participant data N N N

Mentoring MENTORING_OWNER maintain mentoring owner data N N N

Mentoring MENTORING_ACTIVITY maintain mentoring activity data N N N

Mentoring MENTORING_MATCHED_PARTICIPANT

maintain matched participant data N N N

Mentoring MENTORING_MENTOR_REQUEST

maintain mentor request data N N N

Mentoring MENTORING_MENTOR_SIGNUP_FORM

maintain mentor signup form data N N N





Scope Filter?

Default Filter?

Mentoring MENTORING_MENTEE_SIGNUP_FORM

maintain mentee signup form data N N N

Mentoring MENTORING_EMAIL_TEMPLATE

maintain email template data N N N

Mentoring MENTORING_SIGNUP_TEMPLATE

maintain signup template data N N N

Onboarding 2.0 ONB2ProcessTrigger Contains cross module details from RCM like RCM Application ID , Candidate ID , ATS application etc. acts like place holder from the onboarding initiation to successful onboarding process creation

No No NA

Onboarding 2.0 ONB2BuddyActivity Holds Buddy Task details for onboardee

No No NA

Onboarding 2.0 ONB2ChecklistActivity Holds Checklist task details for onboardee

No No NA

Onboarding 2.0 ONB2EquipmentActivity Holds Equipment Task details for onboardee

No No NA

Onboarding 2.0 ONB2GoalActivity Holds Goal Task details for onboardee No No NA

Onboarding 2.0 ONB2LinkActivity Holds Recommended Links Task details for onboardee

No No NA

Onboarding 2.0 ONB2MeetingActivity Holds Meeting Task details for onboardee

No No NA

Onboarding 2.0 ONB2WhatToBringActivity

Holds What to bring Task details for onboardee

No No NA

Onboarding 2.0 ONB2WhereToGoActivity Holds Where to go Task details for onboardee

No No NA

Onboarding 2.0 ONB2UsefulContactActivity

Holds Useful Contacts Task details for onboardee

No No NA

Onboarding 2.0 ONB2MessageActivity Contains Onboarding Message Activity details

No No NA

Onboarding 2.0 ONB2WhereToGoActivityResponsible

Contains Responsible user details for where to go task

No No NA

Onboarding 2.0 ONB2BuddyActivityResponsible

Contains Responsible user details for Bussy assignment task

No No NA

Onboarding 2.0 ONB2EquipmentActivityResponsible

Contains Responsible user details for Equipment assignment task

No No NA

Onboarding 2.0 ONB2GoalActivityResponsible

Contains Responsible user details for Goal task

No No NA

Onboarding 2.0 ONB2LinkActivityResponsible

Contains Responsible user details for Recommended links task

No No NA




Scope Filter?

Default Filter?

Onboarding 2.0 ONB2MeetingActivityResponsible

Contains Responsible user details for Meeting task

No No NA

Onboarding 2.0 ONB2MessageActivityResponsible

Contains Responsible user details for Message task

No No NA

Onboarding 2.0 ONB2UsefulContactActivityResponsible

Contains Responsible user details for useful contacts task

No No NA

Onboarding 2.0 ONB2WhatToBringActivityResponsible

Contains Responsible user details for What to bring task

No No NA

Onboarding 2.0 ONB2ProcessTask Contains Onboarding process task details

No No NA

Payroll Employee Payroll Run Results

Payroll Employee Payroll Run Results Items

Performance Management

Form Template Provides the information of a Performance Management template. Note that there are no columns under this table.

NA NA NA


Form Provides information about the Performance Management form, including Document ID, Form Creation Date and Route Map ID.

NA NA NA


Ask For Feedback The requester uses the "Ask For Feedback" feature to solicit feedbacks from participants via e-mail. This table provides information about the feedback participant, feedback requester, feedback received time and request time.

NA NA NA


Competency Provides details about Competencies, which includes the comments, ratings and rating scales of competencies and behaviors.

NA NA NA


Form Section Provides information about sections in Performance Management form, including section name, comments in the section, section rating and values of the custom elements.

NA NA NA


Objective Provides details about Objectives, including Objective Official Rating, Objective Other Rating and Objective Comment.

NA NA NA





Scope Filter?

Default Filter?


Performance Provides details about Performance, including Overall Performance Rating, Calculated Overall Performance Rating, Unadjusted Calculated Overall Performance Rating and Performance Scale ID.

NA NA NA


Potential Provides details about Potential, including Overall Potential Rating, Overall Potential Rating Description and Potential Scale ID.

NA NA NA


Signature Provides information about the Signature Section in the form. This table has two columns: Signed Date and Signer Name.

NA NA NA


Subject Provides information about form subject, including the subject's user ID as well as the subject's department, division, location, manager when form was completed.

NA NA NA

Person <Country> Global Information

Person <Country> Home Address

Person Biographical Information

Person Dependents

Person Dependents <Country> Global Information

Person Dependents <Country> Home Address

Person Dependents Biographical Information

Person Dependents Global Information

Person Dependents Home Address

Person Dependents National ID Information

Person Dependents Personal Information

Person Email Information

Person Global Information

Person Home Address




Scope Filter?

Default Filter?

Person National ID Information

Person Personal Information

Person Phone Information

Person Primary Emergency Contact

Person Work Permit Info

Position Matrix Relationship For Position

Position Position

Position Position Right To Return

Recruiting Job Requisition Contains the Job Requisition template defined standard and custom fields

No No No

Recruiting Application Contains the Job Application template defined standard and custom fields

No No No

Recruiting Application templates Contains details of the Application template linked to the Job Requisition

Recruiting Approver Contains the details of the Job Requisition Approvers

No No No

Recruiting Candidate progress Contains details of the most advanced status in the pipeline to which the applicant is moved

No No No

Recruiting Co-Recruiter Contains the details of the Co-Recruiters

No No No

Recruiting Co-recruiter recruiting team (…)

Contains the details of the Co-Recruiters team

No No No

Recruiting Current Route entry Contains the details of the current route step of the Job Requisition

No No No

Recruiting Family Role Contains the Job Family details. No No No

Recruiting Hiring manager Contains details of the hiring manager No No No

Recruiting Hiring manager recruiting team (…)

Contains details of the hiring manager team

No No No

Recruiting Job Family expert contains details of job family expert's ID

No No No

Recruiting Hiring manager’s manager (…)

Contains details of the hiring manager's manager

No No No

Recruiting approval status Contains the details of the Job Requisiiton approval status

No No No

Recruiting originator Contains details of the Originator of the Job Requisition

No No No





Scope Filter?

Default Filter?

Recruiting Referrals - Job Req Contains referral details of the application

No No No

Recruiting Approver Recruiting team

Contains details of the Team Recruiting approvers

No No No

Recruiting Job code Contains the Job Code details No No No

Recruiting Locale specific fields - Job Requisition

Contains the details of the fields that can different localizable content.

No No No

Recruiting Operator - Job Requisition

Contains details of the operators on the Job Requisition

No No No

Recruiting Route Entry Contains details on the current route step of the Job Requisition

No No No

Recruiting Templates - Job requisition

Contains details on the Job Requisition template

No No No

Recruiting JOB_REQ_Location_obj ( Label to be picked from system labels )

Contains details of the location FO fields configured in job requisition

No No No

Recruiting Other recruiter Contains details of the other recruiters of the Job Requisition

No No No

Recruiting Other recruiter recruiting team (…)

Contains details of the team of other recruiters of the Job Requisition

No No No

Recruiting Posting Contains details of the job postings No No No

Recruiting RCM_JOB_REQ_MULTI_Selects_mfield5 (…) --> <mfield label configured in int/ext applicant search settings> - Multi value fields

Contains details of the multi select fields configured in the job requisition

No No No

Recruiting RCM_JR_GROUP_OPERATOR (…) -> Group operator - Job Requisition

Contains the list of operators who belong to a job requisition

No No No

Recruiting Workflow status Contains details of Job Requisition's step description, step type and step status

No No No

Recruiting Application Contains the reportable custom and standard fields defined in application template

No No No

Recruiting Assessment order - Application

Contains the Application's assessment order details.

No No No

Recruiting Offer Letter Contains the Offer detail template defined fields(including fields which derive data from the Job Requisition and Application)

No No No




Scope Filter?

Default Filter?

Recruiting Is internal candidate Contains information if the Candidate is an internal or not

No No No

Recruiting Interview result Contains the interview results details No No No

Recruiting Overdue interviews Contains detials of overdue interviews No No No

Recruiting Application source Contains detials of the application source

No No No

Recruiting Status group details Audit trail details of the application status group

No No No

Recruiting Status set item details Audit trail details of the application status item

No No No

Recruiting First advantage Contains details of the FADV background check details

No No No

Recruiting Application comments Contains the application comments No No No

Recruiting Referrals Contains the referral details of the application

No No No

Recruiting Certificates --> These are background element fields. Label is user defined

Augmented tables which appear only if Background elements are configured in the Candidate Profile Template

No No No

Recruiting Education --> These are background element fields. Label is user defined


No No No

Recruiting Employment --> These are background element fields. Label is user defined


No No No

Recruiting Pls indicate (what is this? ) --> These are background element fields. Label is user defined


No No No

Recruiting Last offer detail Contains details of the last offer generated for a candidate

No No No

Recruiting LOCALIZED_APP_STATUS_LABEL (…) -> Application status label

Contains the application status - internal label

No No No

Recruiting Offer detail Contains the details of the offer No No No

Recruiting Candidate Hard Join to Candidate No No No

Recruiting Application history Contains the details of the application history

No No No





Scope Filter?

Default Filter?

Recruiting Referrals Contains the referral information of candidates

No No No

Recruiting Candidate Hard Join to Candidate No No No

Recruiting Referral agency recruiter Contains the candidate & agency information to which the candidate is referred

No No No

Recruiting Referral agency recruiter contains details of the agency and the recruiter involved in referring candidate to agency

No No No

Recruiting agency recruiter details Contains the information about the agency recruiter's account status and email address

No No No

Recruiting referral agency Contains information about the agency account

No No No

Recruiting Offer Detail / Last offer detail

Contains standalone and job req, application extension fields configured in the offer detail templates

No No No

Recruiting Approval date Contains details of when the offer is approved

No No No

Recruiting last approver Details of the last approver of the OFfer No No No

Recruiting approvers DEtails of all the approvers of the Offer No No No

Recruiting Offer detail Template Contains the list of offer detail templates in the system

No No No

Recruiting offer version Contains the version of each offer detail record

No No No

Recruiting Candidate contains the fields configured in candidate profile template ( standard & custom reportable fields )

No No No

Recruiting Comments Contains the details of the comments entered for a candidate

No No No

Recruiting Certificates These are augmented tables which appear only when background elements are configured in the candidate profile template

No No No

Recruiting Education These are augmented tables which appear only when background elements are configured in the candidate profile template

No No No

Recruiting Employment These are augmented tables which appear only when background elements are configured in the candidate profile template

No No No




Scope Filter?

Default Filter?

Recruiting candidate:Pls indicate These are augmented tables which appear only when background elements are configured in the candidate profile template

No No No

Recruiting Internal Employment Info These are augmented tables which appear only when background elements are configured in the candidate profile template

No No No

Recruiting External candidate details (…)

contains the details of converted candidates

No No No

Recruiting Tagged Candidates Contains the list of candidate tags available in the system

No No No

Recruiting Candidate tags for locales

contains the details of the candidates assigned to the tags

No No No

Recruiting Role Name Contains the details of the job requisition's role name

No No No

Rewards and Recognition

Spot Award to EC Integration Status

Provides the status of spot awards published to EC, relevant pay component, time of publication, error messages if applicable, etc.

No No No (Note :: by default mdfSystemRecordStatus field has been set as default filter with value "N")


Spot Award Provides detail of individual (employee leve) awards such as amount, nominator, guideline and aproval status.

No "Yes ( Award Recipient ) Note :: Have to find the reason behind on making this field as Scope Filter"

No (Note :: by default mdfSystemRecordStatus field has been set as default filter with value "N")


Spot Award Budget Provides data at the budget holder level of currency , amount, amount remaining, etc.

Yes No No (Note :: by default mdfSystemRecordStatus field has been set as default filter with value "N")





Scope Filter?

Default Filter?


Spot Award Program Provides program-level information such as program status, program name, type of program, currency conversion table, and so on

No No No (Note :: by default mdfSystemRecordStatus field has been set as default filter with value "N")

Succession Nominations (Legacy Position)

Position Information Shows details of the legacy position object, which is the nomination target

NA NA NA


Nomination Information Shows details of the Succession nomination, including nominee, readiness, ranking, comments, status, and so on

NA NA NA


Nomination History Information

Shows details of the nomination history, including nomination information and last changed on (date) and by (user)

NA NA NA

Succession Nominations (MDF Position)


NA NA NA




NA NA NA


Position Shows details of the MDF position object, which is the nomination target

Yes Yes, position scope filter supported

Succession Nominations (Role-Person)

Incumbent Shows the user that is the nomination target in the role-person nomination method (Incumbent ID and Job code)

NA NA NA



NA NA NA




NA NA NA

Succession Nominations (Talent Pool)

Talent Pool Shows details of Talent Pool, including the pool name, owner, number of nominees, and so on

Yes NA NA




Scope Filter?

Default Filter?



NA NA NA




NA NA NA

Time Management

Allowance

Time Management

Allowance Type

Time Management

Employee Time

Time Management

Employee Time Sheet

Time Management

Employee Time Sheet Entry

Time Management

Employee Time Valuation Result

Time Management

replaces

Time Management

replaces By

Time Management

Time Account

Time Management

Time Account Detail

Time Management

Time Account Payout

Time Management

Time Account Type

Time Management

Time Collector

Time Management

Time Type

Time Management

Time Type Group

User Basic User Information No Yes, manager filter supported

No

User User account No No No





Scope Filter?

Default Filter?

User User’s other information No No No

User User Custom fields No No No

User Extended User information

No No No

User Extended Other information

No No No

User Manager No No No

User HR manager No No No

User Matrix Manager No No No

User Custom Manager No No No

User Second Manager No No No

User User Group

Workflow Workflow Request Comments

Workflow Workflow Request Delegate

Workflow Workflow Request Step

Workflow Current Workflow Request Step

Workflow Employee Workflow Request

Workflow Generic Object Workflow Request

Workflow Parent Workflow Request

Workflow Workflow Request

Workflow Workflow Request Attributes

Workflow Workflow Request Participator

Workflow Workflow Steps Workflow Request Step

Continuous Performance Management

Achievement Provides Information about Achievements, including date, ID, Name

NA NA NA


Achievement Development Goal Details

Provides information details related to personal development goals related to an achievement goal. This table provides information about Goal ID, date, modifications.

NA NA NA




Scope Filter?

Default Filter?


Achievement Goal Detail Provides information about achievement Goals, including Goal ID, linked date, modifications.

NA NA NA


Activity Provides details about activities, included creation details, modification details, owner ID, and Activity ID.

NA NA NA


Activity Development Goal Description

Provides activity details related to personal development goals. This table provides information about activity ID, linking date, modifications.

NA NA NA


Activity Goal Detail Provides information about activity Goals, including Goal ID, linked date, linking modifications.

NA NA NA


Activity Status Provides details on activity status ID and name

NA NA NA


Activity Update Provides details on activity update dates, ID, modifications, provider.

NA NA NA


Feedback Flag Provides details about Feedback flag ID and name

NA NA NA

Role Based Permission

Role Information Provides you information about the roles available in your tenant.

NA NA NA



14 Schema Joins Available for Story Reports

Take a quick look at the schema joins available for use in Story reports.

NoteThe schema joins in the SAP SuccessFactors data sets available for Story reports are evolving, and this might cause intermittent discrepancies in the list of schema joins included documentation versus the list of schema joins available in the application. Please refer to this list only to understand the details of the schema joins that have been documented.

Left Schema Left Table.Field Right Schema Right Table.Field

360 Reviews Form.Form Subject User ID Employment Employment Info.User ID

360 Reviews Form.Form Originator User ID Employment Employment Info.User ID

360 Reviews Form Routing Information.Current Owner User ID

Employment Employment Info.User ID

360 Reviews Form Routing Information.Signer ID Employment Employment Info.User ID

360 Reviews Participant.Participant User ID Employment Employment Info.User ID

360 Reviews Objective.Objective ID Objective Primary Objective Fields.Objective ID

360 Reviews Form Overall Rating.Overall Rating Scale ID

Scale Information Scale Details.Scale ID

360 Reviews Competency.Competency Rating Scale ID

Scale Information Scale Details.Scale ID

360 Reviews Behavior.Behavior Rating Scale ID Scale Information Scale Details.Scale ID

360 Reviews Objective.Objective Rating Scale ID Scale Information Scale Details.Scale ID

Advances Accumulation For Advances.User ID Employment User ID.User ID

Advances Advance.Approver Employment Approver.User Id

Advances Non Recurring Payment.User Id Employment User ID.User ID

Advances Accumulation For Advances.Currency Foundation Objects Currency.internalId

Advances Advance.Currency Foundation Objects Currency.internalId

Advances Eligibility For Advances.Currency Foundation Objects Currency.internalId

Advances Eligibility For Advances.Department Foundation Objects Department.internalId

Advances Eligibility For Advances.Legal Entity Foundation Objects Legal Entity.internalId

Advances Non Recurring Payment.Currency Foundation Objects Currency.internalId

Advances Accumulation For Advances.User ID Employment User ID.User ID

Advances Advance.Approver Employment Approver.User Id

Advances Non Recurring Payment.User Id Employment User ID.User ID

Stories in People AnalyticsSchema Joins Available for Story Reports PUBLIC 113


Advances Accumulation For Advances.Currency Foundation Objects Currency.internalId

Advances Advance.Currency Foundation Objects Currency.internalId

Advances Eligibility For Advances.Currency Foundation Objects Currency.internalId

Advances Eligibility For Advances.Department Foundation Objects Department.internalId

Advances Eligibility For Advances.Legal Entity Foundation Objects Legal Entity.internalId

Advances Non Recurring Payment.Currency Foundation Objects Currency.internalId


Apprentice.Mentor Employment Mentor.User ID


Apprentice.User Employment User.User ID


Apprentice On-The-Job Training.Department

Foundation Objects Department.internalId


Apprentice.Mentor Employment Mentor.User ID


Apprentice.User Employment User.User ID


Apprentice On-The-Job Training.Department

Foundation Objects Department.internalId

Benefits Benefit Claim Accumulation.Worker ID Employment Worker ID.User ID

Benefits Benefit Contact.Employee ID User Employee ID.User ID

Benefits Benefit Employee Claim.Worker ID Employment Worker ID.User ID

Benefits Benefit Employee Opt-out Requests.Worker ID

Employment Worker ID.User ID

Benefits Benefit Exception.Worker Id Employment Worker Id.User ID

Benefits Benefit Employee Claim.Currency Foundation Objects Currency.internalId

Benefits Insurance Coverage.Pay Component Foundation Objects Pay Component.INTERNAL_CODE

Benefits Insurance Coverage.Pay Component Group

Foundation Objects Pay Component Group.INTERNAL_CODE

Benefits Insurance Rate Chart.Currency Foundation Objects Currency.internalId

Benefits Benefit Pension Fund.Employee Contribution Pay Component

Foundation Objects Employee Contribution Pay Component.INTERNAL_CODE

Benefits Benefit Pension Fund.Employer Contribution Pay Component

Foundation Objects Employer Contribution Pay Component.INTERNAL_CODE

Benefits Benefit.Country Foundation Objects Country.internalId

Benefits Benefit.Currency Foundation Objects Currency.internalId

Benefits Benefit.Frequency Foundation Objects Frequency.INTERNAL_CODE

Benefits Benefit Company Car.Installment Frequency

Foundation Objects Installment Frequency.INTERNAL_CODE


Schema Joins Available for Story Reports


Benefits Benefit Payment Options.Pay Component

Foundation Objects Pay Component.INTERNAL_CODE

Benefits BenefitDeductionDetails.Base Salary Pay Component

Foundation Objects Base Salary Pay Component.INTERNAL_CODE

Benefits BenefitDeductionDetails.Deduction Pay Component

Foundation Objects Deduction Pay Component.INTERNAL_CODE

Benefits BenefitDeductionDetails.Pay Frequency Foundation Objects Pay Frequency.INTERNAL_CODE

Benefits Benefit Claim Accumulation.Worker ID Employment Worker ID.User ID

Benefits Benefit Contact.Employee ID User Employee ID.User ID

Benefits Benefit Employee Claim.Worker ID Employment Worker ID.User ID

Benefits Benefit Employee Opt-out Requests.Worker ID

Employment Worker ID.User ID

Benefits Benefit Exception.Worker Id Employment Worker Id.User ID

Benefits Benefit Employee Claim.Currency Foundation Objects Currency.internalId

Benefits Insurance Coverage.Pay Component Foundation Objects Pay Component.INTERNAL_CODE

Benefits Insurance Coverage.Pay Component Group


Benefits Insurance Rate Chart.Currency Foundation Objects Currency.internalId

Benefits Benefit Pension Fund.Employee Contribution Pay Component

Foundation Objects Employee Contribution Pay Component.INTERNAL_CODE

Benefits Benefit Pension Fund.Employer Contribution Pay Component

Foundation Objects Employer Contribution Pay Component.INTERNAL_CODE

Benefits Benefit.Country Foundation Objects Country.internalId

Benefits Benefit.Currency Foundation Objects Currency.internalId

Benefits Benefit.Frequency Foundation Objects Frequency.INTERNAL_CODE

Benefits Benefit Company Car.Installment Frequency

Foundation Objects Installment Frequency.INTERNAL_CODE

Benefits Benefit Payment Options.Pay Component


Benefits BenefitDeductionDetails.Base Salary Pay Component

Foundation Objects Base Salary Pay Component.INTERNAL_CODE

Benefits BenefitDeductionDetails.Deduction Pay Component

Foundation Objects Deduction Pay Component.INTERNAL_CODE

Benefits BenefitDeductionDetails.Pay Frequency Foundation Objects Pay Frequency.INTERNAL_CODE

Calibration Calibration Session.Creator User ID Employment Employment Info.User ID

Calibration Session Reviewer.Reviewer User ID Employment Employment Info.User ID

Calibration Calibration Template. Executive Reviewer User ID


Calibration Rating Change.Changed by User ID Employment Employment Info.User ID



Calibration Rating Overall View.Last Modified By User ID


Calibration Calibration Subject.Subject User ID Employment Employment Info.User ID

Calibration Calibration Sbuejct.Authorizer User ID Employment Employment Info.User ID

Calibration Calibration Sbuejct.PM Form Data ID Performance Management

Form.Document ID

Calibration Calibration Sbuejct.Comp Form Data ID Compensation Compensation.Compensation ID


Compensation Information.User Sys Id Employment Job Information.User ID


Compensation.User Sys Id Employment Job Information.User ID


Spot Bonus.User Sys Id Employment Job Information.User ID


Compensation Information.Currency Foundation Objects Currency.Currency Code


Compensation Information.Event Reason Icode

Foundation Objects Event Reason.INTERNAL_CODE


Compensation Information.Pay Component Code



Compensation Information.Pay Group Foundation Objects Pay Group.internalId


Compensation.Currency Foundation Objects Currency.Currency Code


Compensation.Frequency Foundation Objects Frequency.INTERNAL_CODE_CHAR


Compensation.Pay Component Foundation Objects Pay Component.INTERNAL_CODE


Spot Bonus.Alternative Cost Center Foundation Objects Cost Center.internalId


Spot Bonus.Currency Code Foundation Objects Currency.Currency Code





Spot Bonus.Type Foundation Objects Pay Component.INTERNAL_CODE


Spot Bonus.Wf Request Id Workflow Workflow Request.Workflow Request ID


Compensation Information.User Sys Id Employment Job Information.User ID


Compensation.User Sys Id Employment Job Information.User ID


Spot Bonus.User Sys Id Employment Job Information.User ID


Compensation Information.Currency Foundation Objects Currency.Currency Code


Compensation Information.Event Reason Icode



Compensation Information.Pay Component Code



Compensation Information.Pay Group Foundation Objects Pay Group.internalId


Compensation.Currency Foundation Objects Currency.Currency Code


Compensation.Frequency Foundation Objects Frequency.INTERNAL_CODE_CHAR


Compensation.Pay Component Foundation Objects Pay Component.INTERNAL_CODE


Spot Bonus.Alternative Cost Center Foundation Objects Cost Center.internalId


Spot Bonus.Currency Code Foundation Objects Currency.Currency Code


Spot Bonus.Type Foundation Objects Pay Component.INTERNAL_CODE




Spot Bonus.Wf Request Id Workflow Workflow Request.Workflow Request ID

Compensation Eligibility

USRGRP_MAP#USERS_SYS_ID Employment Employment Info.User ID


Worksheet.Form Subject Employment Employment Info.User ID


Employee Entry.USERS_SYS_ID Employment Employment Info.User ID


Rating Info.Individual Form ID Performance Management

Form.Form ID


Rating Info.Team Form ID Performance Management

Form.Form ID


Rating Info.Salary Form ID Performance Management

Form.Form ID


Rating Info.Bonus Form ID Performance Management

Form.Form ID


Rating Info.Stock Form ID Performance Management

Form.Form ID


Achievement.ParentExternal ID CPM Activity.Activity ID


Goal Detail.Goal ID Goals Objective. Objective ID


Achievement.Goal ID Goals Objective. Objective ID


Development Goal Detail.Goal ID Goals Objective. Objective ID


Achievement Development Goal Detail. Goal ID

Goals Objective. Objective ID


Achievements.Achievements Created By Employment Employment Info. User ID


Achievement.Achievement Last Modified By

Employment Employment Info. User ID


Achievement. Achievement Owner Employment Employment Info. User ID





Achievement Development Goal Detail. Achievement Development Goal Link Modified By



Achievement Development Goal Detail. AChievement Development Goal Link Linked By



Achievement Goal Detail.Achievement Goal Link Modified By



Achievement Goal Detail. Achievement Goal Linked By



Activity.Activity Created By Employment Employment Info. User ID


Activity.Activity Last Modified By Employment Employment Info. User ID


Activity.Activity Owner ID Employment Employment Info. User ID


Activity Development Goal Detail. Activity Development Goal Detail Link Modified By



Activity development Goal Detail. Acitivity Goal Detail Linked By



Activity Goal ID. Activity Goal Detail Link Modified By



Activity Goal ID.Activity Goal Detail Linked By



Coaching.Coaching Advice Subject User ID



Coaching.Coaching Created By Employment Employment Info. User ID


Coaching.Coaching Last Modified By Employment Employment Info. User ID


Feedback.Feedback Provider ID Employment Employment Info. User ID




Feedback.Subject User ID Employment Employment Info. User ID


Feedback Request.Feedback Requestee ID



Feedback Request.Feedback Requester ID



Feedback Request.Feedback Subject User ID



Meetings.Meetings Captured by User ID Employment Employment Info. User ID


Meetings.Meeting Employee ID Employment Employment Info. User ID


Other Topic.Other Topic Created By Employment Employment Info. User ID


Other Topic.Other Topic Last Modified By Employment Employment Info. User ID


Other Topic.Other Topic Subject User ID Employment Employment Info. User ID

Data Replication Employee Data Replication Notification.User

Employment Job Information.User ID

Data Replication Empoyee Data Replication Status.User Employment Job Information.User ID

Data Replication Last Confirmation With Success.User Employment Job Information.User ID

Data Replication Last Confirmation.User Employment Job Information.User ID

Data Replication Employee Data Replication Notification.Country

Foundation Objects Country.internalId

Data Replication Empoyee Data Replication Status.Country


Data Replication Last Confirmation With Success.Country Foundation Objects Country.internalId

Data Replication Last Confirmation.Country Foundation Objects Country.internalId

Data Replication Employee Data Replication Notification.User


Data Replication Empoyee Data Replication Status.User Employment Job Information.User ID

Data Replication Last Confirmation With Success.User Employment Job Information.User ID

Data Replication Last Confirmation.User Employment Job Information.User ID




Data Replication Employee Data Replication Notification.Country


Data Replication Empoyee Data Replication Status.Country


Data Replication Last Confirmation With Success.Country Foundation Objects Country.internalId

Data Replication Last Confirmation.Country Foundation Objects Country.internalId

Deduction One Time Deduction.Advance Advances Non Recurring Payment.internalId

Deduction Recurring Deduction.Advance Advances Non Recurring Payment.internalId

Deduction One Time Deduction.auditUserSysId Employment auditUserSysId.User ID

Deduction Recurring Deduction.User Employment User.UserID

Deduction One Time Deduction.Currency Foundation Objects Currency.internalId

Deduction One Time Deduction.Unit Of Measure Foundation Objects Unit Of Measure.internalId

Deduction Recurring Deduction.Currency Foundation Objects Currency.internalId

Deduction Recurring Deduction.Unit Of Measure Foundation Objects Unit Of Measure.internalId

Deduction One Time Deduction.Advance Advances Non Recurring Payment.internalId

Deduction Recurring Deduction.Advance Advances Non Recurring Payment.internalId

Deduction One Time Deduction.auditUserSysId Employment auditUserSysId.User ID

Deduction Recurring Deduction.User Employment User.UserID

Deduction One Time Deduction.Currency Foundation Objects Currency.internalId

Deduction One Time Deduction.Unit Of Measure Foundation Objects Unit Of Measure.internalId

Deduction Recurring Deduction.Currency Foundation Objects Currency.internalId

Deduction Recurring Deduction.Unit Of Measure Foundation Objects Unit Of Measure.internalId

development_goal_sac

development_goal_sac#OBJECTIVE#USERS_SYS_ID

Employment Employment#employmentInfo#USERS_SYS_ID


development_goal_sac#OBJECTIVE#OBJECTIVE_MODIFIER



development_goal_sac#OBJECTIVE#OBJ_AUDIT_SENDER



development_goal_sac#OBJ_COMMENT#COMMENTATOR



development_goal_sac#OBJ_MILESTONE_milestone#OBJ_MILE_MODIFIER


Employment Job Information.User ID Advances Accumulation For Advances.User ID

Employment Job Information.User ID Advances Non Recurring Payment.User ID

Employment Job Information.User ID Benefit Benefit Claim Accumulation.Worker ID

Employment Job Information.User ID Benefit Benefit Employee Claim.Worker ID



Employment Job Information.User ID Benefit Benefit Enrollment.Worker ID

Employment Job Information.User ID Benefit Eligible Employees Data For Benefit.Worker ID

Employment Job Information.User ID Compensation (Recurring and Non Recurring)

Compensation Information.User Sys Id


Compensation.User Sys Id


Spot Bonus.User Sys Id

Employment Job Information.User ID Deduction One Time Deduction.User

Employment Job Information.User ID Deduction Recurring Deduction.User

Employment Job Information.User ID Employee Profile Employee.User Sys ID

Employment Job Information.Business Unit Foundation Objects Business Unit.internalId


Employment Job Information.Company Foundation Objects Legal Entity.internalId

Employment Job Information.Cost Center Foundation Objects Cost Center.internalId

Employment Job Information.Department Foundation Objects Business Unit.internalId

Employment Job Information.Division Foundation Objects Cost Center.internalId

Employment Job Information.Event Reason Foundation Objects Event Reason.INTERNAL_CODE

Employment Job Information.Job Classification Foundation Objects Job Classification.INTERNAL_ID_CHAR

Employment Job Information.Location Foundation Objects Location.INTERNAL_ID_CHAR

Employment Job Information.Pay Grade Foundation Objects Pay Grade.INTERNAL_CODE_CHAR

Employment Job Information.Pay Group Foundation Objects Pay Group.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Area Foundation Objects Pay Scale Area.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Group Foundation Objects Pay Scale Group.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Level Foundation Objects Pay Scale Level.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Type Foundation Objects Pay Scale Type.INTERNAL_ID_CHAR

Employment Alternative Cost Distribution Item.Cost Center

Foundation Objects Cost Center.internalId

Employment Work Order.Billing Rate Foundation Objects Billing Rate.INTERNAL_CODE

Employment Work Order.Currency Foundation Objects Currency.Currency Code

Employment Payment Information.Job country Foundation Objects Job country.internalId

Employment Job Information.User ID IT Declaration Income Tax Declarations.User ID

Employment Job Information.User ID Onboarding 2.0 ONB2Process.User ID




Employment Job Information.Person ID Person Personal Information.Person ID

Employment Job Information.Position Position Position.Internal ID

Employment Job Information.User ID Proxy Proxy Information.User ID

Employment Job Information.User ID Time Management Employee Time.User

Employment Job Information.User ID Time Management Employee Time Sheet.user Id

Employment Job Information.User ID Time Management Time Account.User

Employment Job Information.User ID Time Management Time Collector.User

Employment Job Information.User ID Advances Accumulation For Advances.User ID

Employment Job Information.User ID Advances Non Recurring Payment.User ID

Employment Job Information.User ID Benefit Benefit Claim Accumulation.Worker ID

Employment Job Information.User ID Benefit Benefit Employee Claim.Worker ID

Employment Job Information.User ID Benefit Benefit Enrollment.Worker ID

Employment Job Information.User ID Benefit Eligible Employees Data For Benefit.Worker ID


Compensation Information.User Sys Id


Compensation.User Sys Id


Spot Bonus.User Sys Id

Employment Job Information.User ID Deduction One Time Deduction.User

Employment Job Information.User ID Deduction Recurring Deduction.User

Employment Job Information.User ID Employee Profile Employee.User Sys ID



Employment Job Information.Company Foundation Objects Legal Entity.internalId

Employment Job Information.Cost Center Foundation Objects Cost Center.internalId

Employment Job Information.Department Foundation Objects Business Unit.internalId

Employment Job Information.Division Foundation Objects Cost Center.internalId

Employment Job Information.Event Reason Foundation Objects Event Reason.INTERNAL_CODE

Employment Job Information.Job Classification Foundation Objects Job Classification.INTERNAL_ID_CHAR

Employment Job Information.Location Foundation Objects Location.INTERNAL_ID_CHAR

Employment Job Information.Pay Grade Foundation Objects Pay Grade.INTERNAL_CODE_CHAR

Employment Job Information.Pay Group Foundation Objects Pay Group.INTERNAL_ID_CHAR



Employment Job Information.Pay Scale Area Foundation Objects Pay Scale Area.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Group Foundation Objects Pay Scale Group.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Level Foundation Objects Pay Scale Level.INTERNAL_ID_CHAR

Employment Job Information.Pay Scale Type Foundation Objects Pay Scale Type.INTERNAL_ID_CHAR

Employment Alternative Cost Distribution Item.Cost Center

Foundation Objects Cost Center.internalId

Employment Work Order.Billing Rate Foundation Objects Billing Rate.INTERNAL_CODE

Employment Work Order.Currency Foundation Objects Currency.Currency Code

Employment Payment Information.Job country Foundation Objects Job country.internalId

Employment Job Information.User ID IT Declaration Income Tax Declarations.User ID

Employment Job Information.User ID Onboarding 2.0 ONB2Process.User ID

Employment Job Information.Person ID Person Personal Information.Person ID

Employment Job Information.Position Position Position.Internal ID

Employment Job Information.User ID Proxy Proxy Information.User ID

Employment Job Information.User ID Time Management Employee Time.User

Employment Job Information.User ID Time Management Employee Time Sheet.user Id

Employment Job Information.User ID Time Management Time Account.User

Employment Job Information.User ID Time Management Time Collector.User

Employee Profile Badge Information.User Sys ID User Basic User Information.User Sys ID

Employee Profile Custom_Background.User Sys ID User Basic User Information.User Sys ID

Employee Profile Custom_Trend.User Sys ID User Basic User Information.User Sys ID

Employee Profile Photo.User Sys ID User Basic User Information.User Sys ID

Employee Profile Profile Completion.User Sys ID User Basic User Information.User Sys ID

Foundation Objects Business Unit.Head of Unit Employment Head of Unit.User ID

Foundation Objects Cost Center.Cost Center Manager Employment Cost Center Manager.User ID

Foundation Objects Department.Head of Department Employment Head of Department.User ID

Foundation Objects Division.Head of Division Employment Head of Division.User ID

Foundation Objects Dynamic Role Assignment.GO_INTERNAL_ID

Position Position.internal ID

Foundation Objects Business Unit.Head of Unit Employment Head of Unit.User ID

Foundation Objects Cost Center.Cost Center Manager Employment Cost Center Manager.User ID

Foundation Objects Department.Head of Department Employment Head of Department.User ID

Foundation Objects Division.Head of Division Employment Head of Division.User ID

Foundation Objects Dynamic Role Assignment.GO_INTERNAL_ID

Position Position.internal ID

IT Declaration Income Tax Declarations.User ID Employment User ID.User ID




IT Declaration Income Tax Declarations.UserSysIdCopy Employment UserSysIdCopy.User ID

IT Declaration Investment Types For Tax Declaration.Country


IT Declaration Income Tax Declarations.User ID Employment User ID.User ID

IT Declaration Income Tax Declarations.UserSysIdCopy Employment UserSysIdCopy.User ID

IT Declaration Investment Types For Tax Declaration.Country


Legacy Position Position.IncumbentID Employment Employment Info.User ID

Legacy Position Nomination.Nominee ID Employment Employment Info.User ID

Legacy Position Nomination.CandidateID Recruiting People Analytics - Embedded Edition

External Candidates.Position Internal ID

Login data Login detail.Usys_Sys_ID User Basic User Information.Users_Sys_ID

MDF Position Position.InternalIID Employment Employment Info.PositionID

MDF Position Position.Incumbent Employment Employment Info.User ID

MDF Position Nomination.Nominee ID Employment Employment Info.User ID

MDF Position Nomination.CandidateID Recruiting People Analytics - Embedded Edition


MENTORING_MATCHED_PARTICIPANT

mentoring_sac#MENTORING_MATCHED_PARTICIPANT#MATCHED_MENTOR_USER_ID


MENTORING_MATCHED_PARTICIPANT

mentoring_sac#MENTORING_MATCHED_PARTICIPANT#MATCHED_MENTEE_USER_ID


MENTORING_MENTOR_REQUEST

mentoring_sac#MENTORING_MENTOR_REQUEST#REQUEST_MENTOR_ID


MENTORING_MENTOR_REQUEST

mentoring_sac#MENTORING_MENTOR_REQUEST#REQUEST_MENTEE_ID


MENTORING_OWNER

mentoring_sac#MENTORING_OWNER#OWNER_USER_ID


MENTORING_PARTICIPANT

mentoring_sac#MENTORING_PARTICIPANT#PARTICIPANT_USER_ID


ONBOARDING2 ONB2Process.user Employment Employment Info.User ID

ONBOARDING2 ONB2Process.manager Employment Employment Info.User ID

ONBOARDING2 ONB2WhereToGoActivityResponsible Employment Employment Info.User ID

ONBOARDING2 ONB2BuddyActivityResponsible Employment Employment Info.User ID

ONBOARDING2 ONB2EquipmentActivityResponsible.responsibleUser




ONBOARDING2 ONB2GoalActivityResponsible.responsibleUser


ONBOARDING2 ONB2LinkActivityResponsible.responsibleUser


ONBOARDING2 ONB2MeetingActivityResponsible.responsibleUser


ONBOARDING2 ONB2MessageActivityResponsible.responsibleUser


ONBOARDING2 ONB2UsefulContactActivityResponsible.responsibleUser


ONBOARDING2 ONB2WhatToBringActivityResponsible.responsibleUser


ONBOARDING2 ONB2ProcessTask.completedBy Employment Employment Info.User ID

ONBOARDING2 ONB2ProcessTrigger.rcmApplicationId recruiting People Analytics - Embedded Edition

RCM_APPLICATION.CAN_JOB_MAP_ID


Form. Form Originator Employment Employment Info. User ID


Form. Current Owner User ID Employment Employment Info. User ID


Form Section. Comment Owner User ID Employment Employment Info. User ID


Ask For Feedback. Feedback Participant User ID



Ask For Feedback. Feedback Requester User ID



Subject. Subject User ID Employment Employment Info. User ID


Performance. Performance Scale ID Rating Scale People Analytics - Embedded Edition

SCALE_DETAILS. Scale ID


Potential. Potencial Scale ID Rating Scale People Analytics - Embedded Edition



Competency. Competency Scale ID Rating Scale People Analytics - Embedded Edition



Objective. Objective Scale ID Rating Scale People Analytics - Embedded Edition



Objective. Objective ID Objective Management

Objective. Objective ID





Ask For Feedback. Feedback Participant User ID



Ask For Feedback. Feedback Requester User ID



Objective. Objective Comment Owner User ID



Subject. Subject User ID Employment Employment Info. User ID


Form. Form Originator Employment Employment Info. User ID


Form. Current Owner User ID Employment Employment Info. User ID


Signature. Signer Name Employment Employment Info. User ID


Form Section. Comment Owner User ID Employment Employment Info. User ID

Person Personal Information.Person ID Employment Job Information.Person ID

Person Personal Information.Nationality Foundation Objects Country.Country Code (3 char)

Person Personal Information.Person ID Employment Job Information.Person ID

Person Personal Information.Nationality Foundation Objects Country.Country Code (3 char)

Position Position Right To Return.User Employment User.User ID

Position Position.Incumbent Employment Incumbent.User Id

Position Position.Internal ID Employment Internal ID.Position

Position Position.Business Unit Foundation Objects Business Unit.internalId

Position Position.Company Foundation Objects Company.internalId

Position Position.Cost Center Foundation Objects Cost Center.internalId

Position Position.Department Foundation Objects Department.internalId

Position Position.Division Foundation Objects Division.internalId

Position Position.Job Code Foundation Objects Job Code.internalId

Position Position Right To Return.Time Type Time Management Time Type.Internal ID

Position Position Right To Return.User Employment User.User ID

Position Position.Incumbent Employment Incumbent.User Id

Position Position.Internal ID Employment Internal ID.Position

Position Position.Business Unit Foundation Objects Business Unit.internalId

Position Position.Company Foundation Objects Company.internalId

Position Position.Cost Center Foundation Objects Cost Center.internalId

Position Position.Department Foundation Objects Department.internalId



Position Position.Division Foundation Objects Division.internalId

Position Position.Job Code Foundation Objects Job Code.internalId

Position Position Right To Return.Time Type Time Management Time Type.Internal ID

Recruiting Application Comments.Commentator Employee Profile Employee.User Sys ID

Recruiting Application Comments.Commentator Employment Job Information.User ID

Recruiting Approver.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Approver Recruiting Team.Group Owner Users SysId

Employee Profile Employee.User Sys ID

Recruiting Approver Recruiting Team.Team Member User Sys ID


Recruiting Approver Recruiting Team.Group Owner Users SysId


Recruiting Approver Recruiting Team.Team Member User Sys ID


Recruiting Approver.Approver User Sys ID Employment Job Information.User ID.User ID

Recruiting Candidate.User Sys ID Employment Job Information.User ID

Recruiting Candidate.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Comments.Commentator Employee Profile Employee.User Sys ID

Recruiting Comments.Commentator Employment Job Information.User ID

Recruiting Coordinator Recruiting Team.Group Owner Users SysId


Recruiting Coordinator Recruiting Team.Team Member User Sys ID


Recruiting Coordinator Recruiting Team.Group Owner Users SysId


Recruiting Coordinator Recruiting Team.Team Member User Sys ID


Recruiting Current Route Entry.Step User Employment Job Information.User ID

Recruiting Current Route Entry.Step User Employee Profile Employee.User Sys ID.User Sys ID

Recruiting First Advantage.Submitted User UserID Employee Profile Employee.User Sys ID

Recruiting First Advantage.Submitted User UserID Employment Job Information.User ID

Recruiting Hiring Manager.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Hiring Manager Recruiting Team.Group Owner Users SysId

Employment Job Information.User ID.User ID

Recruiting Hiring Manager Recruiting Team.Team Member User Sys ID


Recruiting Hiring Manager Recruiting Team.Group Owner Users SysId





Recruiting Hiring Manager Recruiting Team.Team Member User Sys ID


Recruiting Hiring Manager.User Sys ID Employment Job Information.User ID

Recruiting Hiring Manager's Manager.User Sys ID Employment Job Information.User ID

Recruiting Hiring Manager's Manager.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Human Resources Administrator.User Sys ID


Recruiting Human Resources Administrator.User Sys ID

Employee Profile Employee.User Sys ID.User Sys ID

Recruiting Job Family Expert.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Job Family Expert.User Sys ID Employment Job Information.User ID.User ID

Recruiting Offer Letter.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Offer Letter.User Sys ID Employment Job Information.User ID

Recruiting Operator - Job Requisition.User Sys ID Employment Job Information.User ID

Recruiting Operator - Job Requisition.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Originator.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Originator.User Sys ID Employment Job Information.User ID

Recruiting Posting.Posted By Employee Profile Employee.User Sys ID

Recruiting Posting.Posted By Employment Job Information.User ID

Recruiting Recruiter (R).User Sys ID Employee Profile Employee.User Sys ID

Recruiting Recruiter ®.User Sys ID Employment Job Information.User ID.User ID

Recruiting Recruiter Recruiting Team.Group Owner Users SysId


Recruiting Recruiter Recruiting Team.Team Member User Sys ID


Recruiting Recruiter Recruiting Team.Group Owner Users SysId


Recruiting Recruiter Recruiting Team.Team Member User Sys ID


Recruiting Recruitment Collaborator.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Recruitment Collaborator.User Sys ID Employment Job Information.User ID

Recruiting Recruitment Coordinator.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Recruitment Coordinator.User Sys ID Employment Job Information.User ID.User ID

Recruiting Referrals.Referred By Employment Job Information.User ID

Recruiting Referrals.Referred By Employee Profile Employee.User Sys ID

Recruiting Referrals - Job Requisition.Reffered by Employee Profile Employee.User Sys ID

Recruiting Referrals - Job Requisition.Reffered by Employment Job Information.User ID.User ID



Recruiting Requisition Administrator.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Requisition Administrator.User Sys ID Employment Job Information.User ID

Recruiting Route Entry.Step User Employment Job Information.User ID

Recruiting Route Entry.Step User Employee Profile Employee.User Sys ID

Recruiting Second Recruiter Recruiting Team.Group Owner Users SysId


Recruiting Second Recruiter Recruiting Team.Team Member User Sys ID


Recruiting Second Recruiter Recruiting Team.Group Owner Users SysId


Recruiting Second Recruiter Recruiting Team.Team Member User Sys ID


Recruiting Sourcer Recruiting Team.Group Owner Users SysId


Recruiting Sourcer Recruiting Team.Team Member User Sys ID


Recruiting Sourcer Recruiting Team.Group Owner Users SysId


Recruiting Sourcer Recruiting Team.Team Member User Sys ID


Recruiting Tagged Candidate.User Sys ID Employee Profile Employee.User Sys ID

Recruiting Tagged Candidate.User Sys ID Employment Job Information.User ID

Recruiting VP Of Staffing Recruiting Team.Group Owner Users SysId


Recruiting VP Of Staffing Recruiting Team.Team Member User Sys ID


Recruiting VP Of Staffing Recruiting Team.Group Owner Users SysId


Recruiting VP Of Staffing Recruiting Team.Team Member User Sys ID


Recruiting Workflow Status.Created By Employee Profile Employee.User Sys ID

Recruiting Workflow Status.Created By Employment Job Information.User ID

Role Person Incumbent.IncumbentID Employment Employment Info.User ID

Role Person Nomination.Nominee ID Employment Employment Info.User ID

Role Person Nomination.CandidateID Recruiting People Analytics - Embedded Edition


Spot Awards SpotAward.workflowRequestId workflow emp_workflow_request.WF_REQUEST_ID

Spot Awards SpotAwardProgram__advancedSettings.payComponent

Foundation Objects payComponent.INTERNAL_CODE




Spot Awards SpotAward.userId Employment employmentInfo.USERS_SYS_ID

Spot Awards SpotAward.budgetHolderId Employment employmentInfo.USERS_SYS_ID

Spot Awards SpotAward.nominatorId Employment employmentInfo.USERS_SYS_ID

Spot Awards SpotAwardBudget.userId Employment employmentInfo.USERS_SYS_ID

Time Management Employee Time Sheet.created By Employee Profile Employee.User Sys ID

Time Management Employee Time Sheet.user Id Employment Job Information.User ID

Time Management Employee Time.User Employment Job Information.User ID

Time Management Time Account Payout.User Employment Job Information.User ID

Time Management Time Account.User Employment Job Information.User ID

Time Management Time Collector.User Employment Job Information.User ID

Time Management Allowance Type.country Foundation Objects Country.internalId

Time Management Employee Time.Time Type Foundation Objects Time Type.Internal ID

Time Management Time Account Payout.Currency Foundation Objects Time Account.Internal ID

Time Management Time Account Type.Country Foundation Objects Country.internalId

Time Management Time Account Type.Pay Component Foundation Objects Pay Component.INTERNAL_CODE

Time Management Time Account Type.Pay Component for Accrual on Termination

Foundation Objects Separate Pay Component for Accrual on Termination.INTERNAL_CODE

Time Management Time Account Type.Pay Component Group


Time Management Time Account Type.Pay Component on Termination

Foundation Objects Pay Component on Termination.INTERNAL_CODE

Time Management Time Account Type.Separate Pay Component for Accrual

Foundation Objects Separate Pay Component for Accrual.INTERNAL_CODE

Time Management Time Type.Country Foundation Objects Country.internalId

Time Management Time Type.Leave of Absence Event Reason (Plan)

Foundation Objects Leave of Absence Event Reason.INTERNAL_CODE

Time Management Time Type.Leave of Absence Event Reason (Return To Work)


Time Management Employee Time Sheet.created By Employee Profile Employee.User Sys ID

Time Management Employee Time Sheet.user Id Employment Job Information.User ID

Time Management Employee Time.User Employment Job Information.User ID

Time Management Time Account Payout.User Employment Job Information.User ID

Time Management Time Account.User Employment Job Information.User ID

Time Management Time Collector.User Employment Job Information.User ID

Time Management Allowance Type.country Foundation Objects Country.internalId

Time Management Employee Time.Time Type Foundation Objects Time Type.Internal ID

Time Management Time Account Payout.Currency Foundation Objects Time Account.Internal ID



Time Management Time Account Type.Country Foundation Objects Country.internalId

Time Management Time Account Type.Pay Component Foundation Objects Pay Component.INTERNAL_CODE

Time Management Time Account Type.Pay Component for Accrual on Termination

Foundation Objects Separate Pay Component for Accrual on Termination.INTERNAL_CODE

Time Management Time Account Type.Pay Component Group


Time Management Time Account Type.Pay Component on Termination

Foundation Objects Pay Component on Termination.INTERNAL_CODE

Time Management Time Account Type.Separate Pay Component for Accrual

Foundation Objects Separate Pay Component for Accrual.INTERNAL_CODE

Time Management Time Type.Country Foundation Objects Country.internalId

Time Management Time Type.Leave of Absence Event Reason (Plan)


Time Management Time Type.Leave of Absence Event Reason (Return To Work)


User Basic User Information.User Sys ID Employment employmentInfo.User_Sys_ID

User Basic User Information.User Sys ID Employee Profile Badge Information.User Sys ID

User Basic User Information.User Sys ID Employee Profile Custom_Background.User Sys ID

User Basic User Information.User Sys ID Employee Profile Custom_Trend.User Sys ID

User Basic User Information.User Sys ID Employee Profile Photo.User Sys ID

User Basic User Information.User Sys ID Employee Profile Profile Completion.User Sys ID

Workflow Current Workflow Request Step.Created By

Employment Created By.User ID

Workflow Current Workflow Request Step.Last Modified By

Employment Last Modified By.User ID

Workflow Current Workflow Request Step.Owner Employment Owner.User ID

Workflow Current Workflow Request Step.Processed By

Employment Processed By.User ID

Workflow Employee Workflow Request.Subject ID Employment Job Information.User ID

Workflow Workflow Request Comments.Created By Employment Created By.User ID

Workflow Workflow Request Comments.Last Modified By


Workflow Workflow Request Delegate.Created By Employment Created By.User ID

Workflow Workflow Request Delegate.Delegatee ID Employment Delegatee.User ID

Workflow Workflow Request Delegate.Delegator ID Employment Delegator.User ID

Workflow Workflow Request Delegate.Last Modified By


Workflow Workflow Request.Created By Employment Created By.User ID

Workflow Workflow Request.Last Modified By Employment Last Modified By.User ID




Workflow Workflow Steps Workflow Request Step.Created By


Workflow Workflow Steps Workflow Request Step.Last Modified By


Workflow Workflow Steps Workflow Request Step.Owner

Employment Owner.User ID

Workflow Workflow Steps Workflow Request Step.Processed By


Workflow Current Workflow Request Step.Dynamic Role approver

Foundation Objects Dynamic Role.INTERNAL_CODE_CHAR

Workflow Employee Workflow Request.Event Reason Internal Code


Workflow Workflow Steps Workflow Request Step.Dynamic Role approver


Workflow Current Workflow Request Step.Workflow Steps Role ID

Position Position.INTERNAL_ID_CHAR

Workflow Workflow Steps Workflow Request Step.Workflow Steps Role ID


Workflow Current Workflow Request Step.Dynamic Group Approver

RBP User to Group Report

Group Information.Group ID

Workflow Workflow Steps Workflow Request Step.Dynamic Group Approver



Workflow Current Workflow Request Step.Created By


Workflow Current Workflow Request Step.Last Modified By


Workflow Current Workflow Request Step.Owner Employment Owner.User ID

Workflow Current Workflow Request Step.Processed By


Workflow Employee Workflow Request.Subject ID Employment Job Information.User ID

Workflow Workflow Request Comments.Created By Employment Created By.User ID

Workflow Workflow Request Comments.Last Modified By


Workflow Workflow Request Delegate.Created By Employment Created By.User ID

Workflow Workflow Request Delegate.Delegatee ID Employment Delegatee.User ID

Workflow Workflow Request Delegate.Delegator ID Employment Delegator.User ID

Workflow Workflow Request Delegate.Last Modified By


Workflow Workflow Request.Created By Employment Created By.User ID

Workflow Workflow Request.Last Modified By Employment Last Modified By.User ID



Workflow Workflow Steps Workflow Request Step.Created By


Workflow Workflow Steps Workflow Request Step.Last Modified By


Workflow Workflow Steps Workflow Request Step.Owner

Employment Owner.User ID

Workflow Workflow Steps Workflow Request Step.Processed By


Workflow Current Workflow Request Step.Dynamic Role approver


Workflow Employee Workflow Request.Event Reason Internal Code


Workflow Workflow Steps Workflow Request Step.Dynamic Role approver


Workflow Current Workflow Request Step.Workflow Steps Role ID


Workflow Workflow Steps Workflow Request Step.Workflow Steps Role ID


Workflow Current Workflow Request Step.Dynamic Group Approver



Workflow Workflow Steps Workflow Request Step.Dynamic Group Approver



14.1 Schema Join Manager

You can join two different schema for reporting purpose using the Schema Join Manager tool in Admin Center.

The schema joints in Reporting enable you to navigate from one module schema to another, while selecting columns for your report. The Schema Join Manager tool thus enables you to create reports using data across different modules or domains. For example, if you want to create a report on the successors in your team along with their recent achievements, you could create a join between the Succession schema and the Continuous Performance Management schema.

Prerequisites for accessing Report Schema Joint Manager

● Enable the Report Schema Join Manager permission.



Types of Schema Joins

The Schema Join Manager tool provides you default joins, and allows you to create custom joins. The default joins are system defined, and cannot be modified. However, you can modify the custom joins. Both, the default joins and the custom joins are available to all users who build "Report - Story". On the Schema Join Manager tool, the predefined joins are available under the Default Join tab, and the joins you create are available under the Custom Join tab.

Related Information

Creating Custom Joins Using Schema Join Manager [page 135]Using Role-Based Permissions

14.1.1 Creating Custom Joins Using Schema Join Manager

If the system defined default joins don't meet your business needs, you can create custom joins using the Admin Center Schema Join Manager tool.

Context

With custom joins, you create a connection between two module schemas, which enables you to report on columns from the unrelated schemas using a single query. After you create a custom join, it appears under the Custom Join tab of the Schema Join Manager tool.

NoteThe Custom Join tab is disabled. If there are any joins within the Story schemas that are missing, please raise an Influence Request with the business reason for these specific joins. Your requests are evaluated to determine if these joins must be made available as standard joins for Story in People Analytics.

Procedure

1. Go to Admin Center Schema Join Manager , and click the Custom Join tab.2. Click New Join. The New Join dialog appears.3. Select a Schema, and a Table from that schema for the Left Domain of the join.4. Select a Schema, and a Table from that schema for the Right Domain of the join.


https://help.sap.com/viewer/b569eee64d3f4159b2b5272ba7d6b127/latest/en-US/d77b76e71cf54201a4049906b9d8145a.html

NoteFrom the tables you select in the left and right domains, you can create a join only on columns with similar data type.

5. In the Join and Cardinality section, select Join Type.

Join Type Description

Left Outer Join This join selects the complete set of entities from the left domain table, and the matching, available entities from the right domain table.

Inner Join This join selects the set of entities that match in both the domain tables.

6. In the Join and Cardinality section, select Cardinality to define how the rows in the left domain table must match rows in the right domain table. Your choices are:

○ One to One○ One to Many○ Many to One○ Many to Many

7. In the Column Mapping section, select Left Join Column, Operator, and Left Join Column to define the fields mapping between the tables.

8. Click Save.

Results

You’ve created a new custom join that appears under the Custom Join tab. You can edit or delete a custom join by selecting the corresponding icon, when you place the cursor over the custom join.



15 Measures and Dimension in Story Reports

Measures are numerical value data fields that work with mathematical functions. Dimensions are fields with qualitative data that don’t total a sum.

Measures quantify the data sets on which you’re trying to create a report. Dimensions provide a structure to categorize the facts and figures. If you’re creating a report for employee attrition rates, then “attrition rate” is the measure and employees are the dimension. Measures and dimensions work together to help answer complex business questions.

Common examples of Measures are: Percentage fields in Job Information table, such as Salary Increment Percentage, some Meeting ID in the Meetings table of Continuous Performance Management,

Common examples of Dimensions are: Most fields in SAP SuccessFactors HCM Suite product schemas. For example, name fields, External ID, Country/Region, Department, Job Title, status fields, etc.

Stories in People AnalyticsMeasures and Dimension in Story Reports PUBLIC 137

16 Creating Calculated Columns for Stories in People Analytics

Create new output columns and calculate its values at runtime based on the result of an expression. You can use other column values, functions, input parameters, or constants in the expression.

Context

You can create Calculated Columns within queries in Stories in People Analytics. For example, consider that you're creating a query on employees' Job Information and you want to report the duration of their employment. You can create a calculated column "Job Tenure" using the expression "DAYS_BETWEEN ([Job Information#Hire Date], CURRENTDATE())/365".

Procedure

1. Go to the Query Builder page.

2. Under Data, choose the (Create Calculated Column) icon.

The Column Overview dialog appears.

3. On the Calculated Column tab, choose Add Calculated Column.

The Calculated Columns dialog appears.4. Enter a column ID, and enter name of the calculated column in Description.5. In the Edit Formula section, create an expression using the available Functions, Conditions and Operators, and

choose Format to verify whether the expression is correct.

TipIn the formula, you can add fields only from the tables that you've selected, which are available on the canvas of the Query Designer.

NoteFor more information about using the available Functions, Conditions and Operators, see the Formula Functions in Calculated Columns for Stories in People Analytics topic.

6. Choose OK.

The newly added column appears under the Calculated Columns tab of the Column Overview dialog.7. To save the calculated column, choose OK on the Column Overview dialog.


Creating Calculated Columns for Stories in People Analytics

NoteThe Show in Grid option is enabled, by default, which means the calculated column gets added to the list of columns in your report.

Results

The calculated column has been created. The calculated column is either a dimension or a measure, depending on the expression you create. On the Calculated Columns tab of the Column Overview dialog, select a calculated column, and...

● To edit it, choose the (edit function) icon.● To delete it, choose the (delete) icon.

16.1 Formula Functions in Calculated Columns for Stories in People Analytics

You can use Calculated Columns in your report to derive data by applying functional, conditional, and arithmetical operations on data stored in other columns.

Functions

Function Name Description Code Syntax with Example

ABS() Returns the absolute value of a number. Code Syntax

Abs(num)

● num: A number

Example

Abs(-11)

returns 11

Stories in People AnalyticsCreating Calculated Columns for Stories in People Analytics PUBLIC 139


ADDDAYTODATE() Returns the date produced by adding a specified number of days (periods) to a specified date (date).

Code Syntax

AddDayToDate(date,periods)

● date: A Date or Datetime object● periods: A number of days

Example

AddDayToDate(#2015-01-20#, 2)

returns 2015-01-22

ADDMONTHTODATE() Returns a date that is produced by adding a specified number of months to a specified date.

Code Syntax

AddMonthToDate(#date#,periods)

● #date#: Original date● periods: Number of periods to add

Example

AddMonthToDate(#2012-01-01#,1)

returns 2012-02-01

CONCAT() Concatenates two strings into a single string. Code Syntax

Concat(str1, str2)

● str1: First string● str2: Second string

The operator + can also concatenate strings.

Example

Concatenate("Mr", "Brown")

returns "MrBrown"




CONTAIN() Returns occurrences of a string within another string. The search is not case-sensitive.

Code Syntax

Contain(whereStr, whatStr)

● whereStr: String in which a search is conducted

● whatStr: Substring that is the object of the search

Example

Contain("Cats are grey", "aRe")

returns true

DAY() Returns the day of the month as a number from 1 to 31.

Code Syntax

Day(#date#)

● #date#: A date

Example

Day(#2012-03-23#)

returns 23

DAYS_BETWEEN() Returns the number of days between two dates. Code Syntax

Days_Between(#date1#, #date2#)

● #date1#, #date2#: Date values

Example

Days_Between(#2019-03-06#, #2019-05-06#)

returns 61



DOUBLE() Converts argument to a high precision floating point number. Code Syntax

Double(arg)

● int: An integer

Example

Double(14)

returns 14.0

FLOAT() Converts argument to a floating point number. Code Syntax

Float(arg)

● int: An integer

Example

Double(14)

returns 14.0

IF() Chooses between two alternatives, based on whether a Boolean condition is true or false. The first alternative corresponds to true and second value corresponds to false. The second alternative is optional and evaluates to null when missing.

Code Syntax

If(<cond>, <alt1>, <alt2>)

● cond: Boolean condition to test

● alt1: Alternative 1

● alt2: Alternative 2

Example

If(#2018-03-10# >= CURRENTDATE(), "It's On", "It's Gone")

returns It's Gone

ISNULL() Returns a Boolean value that indicates whether the supplied field contains a null value. If a field contains a null value, the function returns true. Otherwise it returns false.

Code Syntax

IsNull(obj)

● obj: User object (column)




LEFT() Returns the left part of a specified string, with the specified number of characters.

Code Syntax

Left(str, num)

● str: Input string● num: Number of characters you select from the

input string, left to right.

Example

Left("Mathematics", 4)

returns Math

LENGTH() Returns the length of a string. Code Syntax

Length(str)

● str: Input string

Example

Length("How long")

returns 8



LIKE() Determines whether a character string matches a specified pattern. The search is not case-sensitive.

Code Syntax

<matchExpr> like <pattern>

● matchExpr: The string expression to search● pattern: The pattern string constant to

search for

The pattern can include regular characters and the following special characters:

● "_" matches a single character● "%" matches zero to many characters

Before you can use a special character as a regular character, you must escape it, using a backslash ("\").

Note"[", "^", "-", and "]" are reserved for future use.

Example

"Hiking is fun" like "H% is _un"

returns true

LOCATE() Returns the position of the first occurrence of a sub-string in a string. Code Syntax

Locate(substring, string, start index)

● substring: A part of the string that you want to locate

● string: A string that contains the sub-string● start index: A positive number lesser than

the length of the string.

Example

Locate("on","concoction",2)




LOG() Returns the natural logarithm of a specified number. Code Syntax

Log(num)

● num: A number

Example

Log(100)

returns 4.605

LOG10() Returns the base 10 logarithm of a specified number.

Code Syntax

Log10(num)

● num: A number

Example

Log10(100)

returns 2

LOWERCASE() Returns a copy of a string, with all characters converted to lowercase. Code Syntax

LowerCase(str)


Example

LowerCase("GOOD JOB")

returns "good job"



MONTH() Returns the month of the year as a number from 1 to 12. Code Syntax

Month(#date#)

● #date#: A date

Example

Month(#2012-03-23#)

returns 3

NOT() Use to negate a Boolean input. Code Syntax

not<bool>

● bool: A Boolean

Example

not false

returns true

POWER() Raises a number to a power. Code Syntax

Power(num, exponent)

● num: A number● exponent: The exponent

The operator ^ (caret) can be used instead of this function.

Example

Power(2,3)

returns 8




QUARTER() Returns a number that represents the quarter of a specified date. Code Syntax

Quarter(#date#)

● #date#: A date

Example

Quarter(#2012-03-23#)

returns 1

REPLACE() Returns a string, with all occurrences of a specified string replaced with another specified string.

Code Syntax

Replace(str, target, replacement)

● str: Input string● target: String to be replaced● replacement: String value to insert

Example

Replace("hyperthermia", "ert", "ot")

returns "hypothermia"

RIGHT() Returns the right part of a specified string, with the specified number of characters.

Code Syntax

Right(str, num)

● str: Input string● num: Number of characters you select from the

input string, counting from right to left.

Example

Left("Closure", 4)

returns sure



ROUND() Returns a numeric value, rounded to a specified number of decimal places.

Code Syntax

Round(num, digits)

● num: A number● digits: The number of decimal places to

round off to.

Example

Round(14.81, 1)

returns 14.8

SUBSTRING() Returns a substring of a string. Code Syntax

SubString(str, start)

● str: String from which a substring is computed● start: Start position in the input substring

ExampleFor example:

SubString("Wong", 3)

returns "ng"




TODATE() Converts an input string to a date in a specified format, when the dates in a column of an original data source are in string format.

Code Syntax

ToDate(string, format)

● string: Input string to convert● format: Date format

The date format is a combination of the following reserved tokens, separated by delimiters:

● d or dd: Day of month (1-31)● M or MM: Month of year (1-12)● y or yy: Abbreviated year without century

(00-99)● yyyy: Year with century (1956, 2012, 2014, and

so on)

All other characters are considered delimiters.

Example

ToDate(Obj, 'yyyy/dd/MM')

converts a string in the format yyyy/dd/MM to a date

TOINTEGER() Returns an integer representation of a character string in the form of an integer constant.

Code Syntax

ToInteger(numberStr)

● numberStr: A numberical value, which is entered as a string

ExampleFor example:

ToInteger("123")

returns 123

TONUMBER() Converts any type of parameter to a numeric value. Numbers are truncated to zero decimal places.

Code Syntax

ToNumber(param)

● param: Parameter to convert



TOTEXT() Converts a specified number or a parameter to a string. The number is truncated to the specified number of decimal places.

Code Syntax

ToText(num, digits) or ToText(param)

● num: A number● digits: Number of decimal places to use. This

parameter is optional, and its default value is 0.● param: Parameter to convert

Example

ToText(12.1451, 2)

returns 12.14

UPPERCASE() Returns a copy of a string, with all characters converted to uppercase. Code Syntax

UpperCase(str)


Example

UpperCase("Little Boy")

returns "LITTLE BOY"

WEEK() Returns a number that represents the week of a specified date. Code Syntax

Week(#date#)

● #date#: A date

Example

Week(#2012-03-23#)

returns 12




YEAR() Returns the year of a specified date. Code Syntax

Year(#date#)

● #date#: A date

Example

Year(#2012-03-23#)

returns 2012

Conditions and Operators

Condition Name Description Code Syntax with Example

AND Returns the logical conjunction of its Boolean inputs. This function returns false: true and false.

Code Syntax

<left> and <right>

● left: Left operand● right: Right operand

OR Returns the logical disjunction of its Boolean inputs. This function returns true: true or false.

Code Syntax

<left> or <right>

● left: Left operand● right: Right operand

> (Greater than), < (Lesser than), >= (Greater than or equals), <= (Lesser than or equals), = (Equals), and != (Not equals)

Returns the comparison results between two operands with compatible types. Example

● 1 = 1, returns true● 1 = 2, returns false● 1 > 1, returns false● 2 > 1, returns true


Condition Name Description Code Syntax with Example

+ (Add), - (Substract), * (Multiply), and / (Divide)

These are basic numeric calculations. Code Syntaxnum1 + num2 ; num1 - num2 ; etc.

● num1, num2: Numbers



17 Report Center Actions Supported for Story Reports

Using the Action menu on the Report Center page, you can run, edit, rename, duplicate, and delete a Story report, which was either created by you, or shared with full control.

You can also add a label to the story for easier categorization. If a story has been shared with you with Read access, then only the Run, Duplicate, and New Schedule options on the Action menu are available to you. You can use the Run, Edit, Rename, Delete, Share, Export, Duplicate, New Schedule, and Label As options on the Action menu, if you've authored a Story report, or you're a Story admin, or you've been granted the rights to edit a shared story.

List of Supported Actions

You can... ...a Story report,

Run If one or more of the following conditions are met:

● You're the author of the Story report.● The Story report has been shared with you.● You've been granted the Story Admin permission.

Edit If one or more of the following conditions are met:

● You're the author of the Story report.● The Story report has been shared with you with edit access rights.● You've been granted the Story Admin permission.

Share If one or more of the following conditions are met:


Rename If one or more of the following conditions are met:


Delete If one or more of the following conditions are met:


Export If one or more of the following conditions are met:


Stories in People AnalyticsReport Center Actions Supported for Story Reports PUBLIC 153

You can... ...a Story report,

Duplicate If one or more of the following conditions are met:


New Schedule If one or more of the following conditions are met:


Label As If one or more of the following conditions are met:


Related Information

Grant Permission Roles [page 47]Running a Report in Report CenterSharing Reports in Report CenterScheduling Reports in Report CenterAdding Labels to a ReportExporting a Report Definition


Report Center Actions Supported for Story Reports

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/2011/en-US/737bd7f7c89c43dcb99781954613c852.html

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/2011/en-US/feb64690125f47a8a6d44fbd0bfa4800.html

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/2011/en-US/a1e6de81a25e40f183c35e0f5aaa034c.html

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/2011/en-US/e360e0e91c914b8e89b842a609f0713c.html

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/2011/en-US/e830c048c62d4731b8cc0cf582cb306c.html

18 Creating Story Reports Using the Story Templates Available in Content Store

Import ready-to-use Story reports from the Content Store available in Report Center, and create your reports based on the imported Story template.

Prerequisites

● Enable the Manage Dashboards/Reports Story Admin permission to access the Content Store from the Import reports dialog in Report Center.



Context

The Content Store is currently managed by SAP SuccessFactors. The Story templates available in Content Store help you to get started with Story reports. They offer a basic report structure that you can modify to best suit your business needs. Currently, the Content Store UI supports only the English language; it lacks localization support.

NoteThe Content Store provides a set of commonly used Story report templates, only for the products that are active in your tenant.

Procedure

1. On the Report Center page, choose Import.

The Import report definition dialog appears.2. Choose the Content Store tab.

The Story report templates, only for the products that are active in your tenant, appear.3. Either search for a Story template by its name or description or browse the list of available templates, and

select the template you want to import.

Stories in People AnalyticsCreating Story Reports Using the Story Templates Available in Content Store PUBLIC 155

TipChoose See more details in the Description column of a Story template to read the summary of the template.

4. Choose Import.

A pop-up message for confirmation appears.5. To proceed with the Story import, read the message and choose OK, I understand, and wait for the import

process to complete.

Results

You've successfully imported the Story template into your instance.

TipIf you aren't able to view the imported Story reports in Report Center, please wait for a couple of minutes and reload the Report Center page.

Related Information

Template Stories in People AnalyticsTemplates for Stories in People Analytics

18.1 Import and Export of Story Reports

You can reuse the stories created on a different tenant or environment, instead of having to manually create them again, using Import and Export options in Report Center.

● Using the Export option on the Action menu, or the (Export) icon on the Report Center menu bar, you can export one or more Story types of reports, and store them as an ACN file on your local drive.

RememberThe export functionality in Story hasn't been designed for backup purposes. The exported ACN file doesn't contain the actual report definition. It only contains references to the report definition, which is stored on the content network.

● Using the Import button on the Report Center menu bar, you can import Story type of reports into your instance, using an ACN file.


Creating Story Reports Using the Story Templates Available in Content Store

https://help.sap.com/viewer/1a17ad0982664c629f8af7d47a631672/2011/en-US/f7876e08ffd347078e5e1b149693bdd9.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fblogs.sap.com%2F2020%2F09%2F10%2Ftemplates-for-stories-in-people-analytics%2F

TipIf you aren't able to view the imported Story reports in Report Center, please wait for a couple of minutes and reload the Report Center page.

The ACN file format is used for storing Story type of reports, and it's native to the application.

You can import stories if you have the Create Story permission. Whereas you can export stories, if any of the following conditions are met.

● You're the author of the story.● A story has been shared with you, and you have the rights to edit the story.● You've been assigned the Story Admin permission.

Related Information

Exporting a Report DefinitionImporting a Report DefinitionSyncing Existing Reports into the Report Center Search

Stories in People AnalyticsCreating Story Reports Using the Story Templates Available in Content Store PUBLIC 157

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/latest/en-US/e830c048c62d4731b8cc0cf582cb306c.html

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/latest/en-US/78b73a6c2c884c9eaa78a427e7edb95c.html

https://help.sap.com/viewer/6ca0eee0540248b2b3ba91eaa1f18423/latest/en-US/a152510809c64d24a7d6ab9b8b9f18e8.html

19 Scheduling a Story Report

You can schedule Story reports for offline execution, using the New Schedule option on the Action menu in Report Center.

Prerequisites

● Enable the Schedule Reports permission.

Context

The ability to schedule Story report allows you to generate reports at a later date and time, and at recurring intervals.

Procedure

1. Go to Reporting.

The Report Center page appears.

2. In Report Center, click the (Action) menu of a story report, and select New Schedule.

The Job Definition tab of a new schedule under Report Scheduler appears.3. Enter a Job Name that helps you identify the report you’re scheduling.4. In Report Format, select a file format for storing the output of your scheduled report.

NoteCurrently, scheduled stories support only the CSV file format.

5. In Choose the data you want to retrieve, select the check box with the story name to select the entire story, or select the pages and/or widgets from the Story that you want to include in the scheduled report.

NoteCurrently, only table widgets are supported. This means, the output of a scheduled story contains data only for its selected table widgets.

6. Optional: In Send Notifications to, enter email addresses of users that you want to notify about the status of the scheduled job; and under Send Notification On, select the events that trigger the email notifications.

7. Click Step 2.


Scheduling a Story Report

The Filters tab appears, and displays the prompt filters defined using Edit Prompts available on the Story Canvas page, if any.

NoteOn the Story Canvas page, in the pop-up to set variables for the prompt,○ If you select the Automatically open prompt when story opens check box, you are prompted to set the

variable value for the prompt during scheduling.○ If you don't select the Automatically open prompt when story opens check box, the predefined value for

this prompt filter gets applied to the report.

8. Click Step 3.

The Destination tab appears.9. In Method, select Offline to download the generated report from the application.10. Click Step 4.

The Job Occurrence tab appears.11. In Occurs, select either Once or Recurring to determine the frequency of running this job.

Select... If you want to...

Once Run this job only once.

Recurring Run this job at regular intervals that you can configure as follows:○ In Recurring Pattern, select the frequency for running

this job.○ In First Occurrence, set the date and time at which the

job occurs.○ In Ending On, set the date for the last occurrence of the

scheduled job.

12. Click Save and Continue, and click Submit to schedule the job.

A confirmation message appears.

Results

You've successfully scheduled a Story type of report.

NoteCurrently, each report can have only one schedule per user.

Next Steps

Click the View Schedules link to

● View the scheduled job under the My Schedules and the All Schedules tabs.

Stories in People AnalyticsScheduling a Story Report PUBLIC 159

NoteYou can access the All Schedules tab if you have the View All Schedules admin permission.

● View the status and details of each occurrence of your scheduled job under My Jobs.

Related Information

Scheduling Reports in Report Center


Scheduling a Story Report

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/2005/en-US/a1e6de81a25e40f183c35e0f5aaa034c.html

20 Sharing a Story Report

Enable users to run or update a Story by sharing the report with them, with specific access rights.

Prerequisites

● Enable Create Story and Share Reports to Groups & Roles permissions.

Context

As an author, you can share stories that you've created, and as a Story admin, you can share any story in the instance. When you share stories with Story admin users, by default, they have the permission to perform any action on the story irrespective of the access you grant. However, when you share stories with the non-admin users, you can grant read, edit, or full access to the shared report.

Procedure

1. In Report Center, click the (Action) menu of a Story you want to share.

2. Select Share, and follow one of the three options available to share the report.3. Option 1: To share the report with users, click User.

a. Enter the user name to whom you want to share the report.b. Use the additional fields: Department, Division, Location, and User Role to further filter the user selection.

Stories in People AnalyticsSharing a Story Report PUBLIC 161

NoteDon't use space or combination of first name, last name, partial name, full name as it doesn't return any result. For example, Adele Smoke doesn't return any result.

4. Option 2: To share the report with groups, click Group.a. Enter the group name to whom you want to share the report.b. Use the additional fields: Group Creator Username, Department, Division, Location, Last Modified Date

Range, User Role, and Group Type to further filter the user selection.

5. Option 3: To share the report with the roles, click Role.a. Enter the role name to whom you want to share the report.b. Use the additional fields: Role Creator Name, Role Creation Date Range, Role Last Modified By:Last Modified

Date Range, and Role Type to further filter the user selection.

6. Click Go.

Based on your search, users, groups, or roles are listed under Matched Result.7. Select the users, groups, or roles, with whom you share the report.8. Select the type of access rights you want to provide to the shared report, such as Read, Edit or Full Access, and

then click .

NoteIf a Story is shared with Admin users, by default they have the permissions to perform any action on the story irrespective of the access level you select while sharing the story. The access levels apply only to non-admin users


Sharing a Story Report

The Saved Successfully message appears, which indicates your Story has been shared successfully.

Results

You can see the icon next to the shared report name on the Report Center page.

Related Information

Sharing Reports in Report Center

Stories in People AnalyticsSharing a Story Report PUBLIC 163

https://help.sap.com/viewer/deb510367ec844b4bc84b8c52442f5e5/latest/en-US/feb64690125f47a8a6d44fbd0bfa4800.html

21 Actions to Support Manual Refresh in Target Tenants with Story Reports

For uninterrupted access to Story reports after manual refresh, export the relevant X509 certificates and OAuth settings before you initiate the manual refresh process, and import the files into your tenant after the refresh is complete.

Note

This topic is not applicable if you're using the Admin Center Instance Refresh tool to perform instance refresh on your tenant. This topic is applicable only when you want to perform manual refresh on your tenant.

Use the Admin Center Import and Export Data tool to export and import the X509 certificates and the OAuth settings related to Stories in People Analytics.

CautionIf you don't export the X509 certificates and the OAuth settings before manual refresh, you can't access the Story reports after the manual refresh process is complete.

Exporting X509 Certificates and OAuth Settings for Stories in People Analytics [page 165]Before initiating manual refresh on your instance, export and store the relevant X509 certificates and OAuth settings that you can later import into your tenant after the refresh is complete.

Importing X509 Certificates and OAuth Settings for Stories in People Analytics [page 166]After completion of manual refresh on your instance, import the relevant X509 Certificates and OAuth Settings to ensure uninterrupted access to Stories in People Analytics.


Actions to Support Manual Refresh in Target Tenants with Story Reports

21.1 Exporting X509 Certificates and OAuth Settings for Stories in People Analytics

Before initiating manual refresh on your instance, export and store the relevant X509 certificates and OAuth settings that you can later import into your tenant after the refresh is complete.

Prerequisites

● Ensure you’ve been granted the Metadata Framework Import Permission on Metadata Frameworkpermission.

● Ensure you've access to the Admin Center Import and Export Data tool.

Procedure

1. Go to Admin Center Import and Export Data .2. In Select the action to perform, select Export Data.3. To export the X509 certificates, in Select Generic Object, select IntegrationProcessX509Keypairs.4. In Select all data records, select No, and in Select objects, select the SAC_Keys(xxxxx-xxx-xxxxxxx) object.5. Choose Export.

A confirmation message that your export request has been submitted successfully, appears. You've successfully submitted the request to export the X509 certificates.

6. To export the OAuth settings, in Select Generic Object, select IntegrationProcessOAuthSettings.7. In Select all data records, select No, and in Select objects, choose sac (xxxxx-xxx-xxx-xxx-xxxxxxx).8. Choose Export.

A confirmation message that your export request has been submitted successfully, appears.9. With Select all data records set to No, in Select objects, choose sac_getAllStories (xxxxx-xxx-xxx-xxx-xxxxxxx),

and choose Export.

A confirmation message that your export request has been submitted successfully, appears. You've successfully submitted the request to export the files for the OAuth settings.

10. To save a copy of the exported files, go to Admin Center Monitor Jobs , and for each of the export requests you submitted in previous steps, choose the Download Status link.

The Zip files for X509 certificates and the two OAuth settings are saved to your local drive.

Results

You've successfully exported the relevant X509 certificates and OAuth settings as Zip files to your local drive.

Stories in People AnalyticsActions to Support Manual Refresh in Target Tenants with Story Reports PUBLIC 165

Task overview: Actions to Support Manual Refresh in Target Tenants with Story Reports [page 164]

Related Information

Importing X509 Certificates and OAuth Settings for Stories in People Analytics [page 166]Using Role-Based Permissions

21.2 Importing X509 Certificates and OAuth Settings for Stories in People Analytics

After completion of manual refresh on your instance, import the relevant X509 Certificates and OAuth Settings to ensure uninterrupted access to Stories in People Analytics.

Prerequisites

● Ensure you've been granted the Metadata Framework Import Permission on Metadata Frameworkpermission.

● Ensure you've access to the Admin Center Import and Export Data tool.● Ensure that the manual refresh process is complete.

Procedure

1. Go to Admin Center Import and Export Data .2. In Select the action to perform, select Import Data.3. Choose the ZIP File tab.4. In File, choose the Zip file for the previously exported X509 Certificates.5. Choose Import to import the X509 Certificates, related to Stories in People Analytics, into your tenant.

An import confirmation message appears.6. In File, choose the Zip file for both the previously exported OAuth settings, one-by-one, and choose Import.

An import confirmation message appears. You've successfully imported both the OAuth settings files related to Stories in People Analytics, into your tenant.


Actions to Support Manual Refresh in Target Tenants with Story Reports


Results

You've successfully imported the previously saved X509 Certificates and OAuth Settings to your SAP SuccessFactors tenant, after the Manual Refresh process is complete.

Task overview: Actions to Support Manual Refresh in Target Tenants with Story Reports [page 164]

Related Information

Exporting X509 Certificates and OAuth Settings for Stories in People Analytics [page 165]Using Role-Based Permissions

Stories in People AnalyticsActions to Support Manual Refresh in Target Tenants with Story Reports PUBLIC 167


22 Using the Check Tool

Use the check tool to find potential problems and errors in your configuration before you call support about an issue.

Prerequisites

Enable Metadata Framework. Most customers already use Metadata Framework.

Assign Access Check Tool and Allow Configuration Export to your role in Role-Based Permissions (RBP). If you want to use the Quick Fix feature for the checks that have it, assign the Allow Check Tool Quick Fix permission too,

● Access Check Tool authorizes users to access the tool.● Allow Configuration Export authorizes users to attach configuration information to a ticket.● Some checks have a quick fix, which can be used to immediately correct any issues found by that check.

Assign the Allow Check Tool Quick Fix permission to authorize users to run these quick fixes.

Tip

Refer to Guided Answers for the Check Tool for a guided navigation through the available check tool checks and more information on each check.

Procedure

1. Go to Admin Center.2. In the tools search field, type Check Tool.3. In Application, select the application you want to check.

TipAll Applications runs checks in all your applications.

For example, to run checks for Time Off, select Time Off.

You see the checks for the application you selected. The description for each check describes the situation you hope to find in running the check. For example, in running the check Accrual lookup by seniority is consistent, you hope to find that the lookup is indeed consistent.

4. Click the check the box at top left in the table to run all checks.5. If you want to run only some checks, select them individually.

TipTo understand what a check does, right click the Check ID. The system then displays some information on the check.


Using the Check Tool

http://help.sap.com/disclaimer?site=https%3A%2F%2Fga.support.sap.com%2Fdtp%2Fviewer%2F%23%2Ftree%2F2616%2Factions%2F36400

6. Click Run Checks to check your applications for the checks you selected.

Next Steps

Evaluate the results and resolve the issues. If you encounter an error you cannot resolve, contact Support by creating a ticket.

Benefits of the Check Tool [page 169]The SAP SuccessFactors check tool helps you identify and resolve issues when your system doesn’t work as you expect.

Check Results [page 169]After you run checks in the check tool, it returns the results of the check so that you can resolve issues that it found.

Creating Support Tickets from the Check Tool [page 170]When the check tool reports a serious issue, you might need to contact Support. You can create a Support ticket from within the check tool.

Using the Quick Fix Feature [page 171]The Check Tool includes a Quick Fix feature that you can use to immediately correct issues found during a check run.

22.1 Benefits of the Check Tool

The SAP SuccessFactors check tool helps you identify and resolve issues when your system doesn’t work as you expect.

If your SAP SuccessFactors applications are behaving in unexpected ways, it is likely that it has a configuration or data conflict: you have some data that is inconsistent or a configuration error. The check tool quickly identifies these types of problems so that you can avoid support tickets. You might still need to create a support ticket if the problem is severe, but even in severe cases, the check tool can save you time because it can export the results of the check and your configuration for support. The support engineer, therefore, can identify the issue more quickly.

When you run the check tool, you see:

● A list of issues in your configuration or data and the severity of each issue.● A solution or recommendation to address the issue.

22.2 Check Results

After you run checks in the check tool, it returns the results of the check so that you can resolve issues that it found.

To see the results of the checks, look in the Results column. If you run the checks multiple times to see how you are resolving issues, look in the Previous Result column to compare the current results to previous results.

Stories in People AnalyticsUsing the Check Tool PUBLIC 169

Possible Results of Check Tool

Result Action

No issues found If the tool cannot find issues, you see a green check mark the Result.

Issues found If the tool finds issues, it reports the number of issues and a yellow warning icon or a red alarm icon.

● The yellow icon indicates a low severity issue. The system proposes a solution.● The red icon indicates a high severity issue. You must take action, which could include creat

ing a Support ticket.

Related Information

Creating Support Tickets from the Check Tool [page 170]

22.3 Creating Support Tickets from the Check Tool

When the check tool reports a serious issue, you might need to contact Support. You can create a Support ticket from within the check tool.

Prerequisites

Run the check tool. You can find the check tool by going to Admin Center Check Tool . You create the ticket from the results page of the tool.

Procedure

1. On the results page, look in the Result column for the errors you want to report on.

You usually contact Support for high severity issues not low severity issues.2. Click the error in the result to open the Detailed Result.

NoteIf you cannot click the error, expand the list of checks from the Description column, and then click the error from the Result column.

3. In Detailed Result Need Assistance? , copy the component ID.

For example, LOD-SF-EC is the component ID for Employee Central.


Using the Check Tool

4. Create a customer incident in the relevant category.5. When you create the ticket, paste the component ID into the ticket.

22.4 Using the Quick Fix Feature

The Check Tool includes a Quick Fix feature that you can use to immediately correct issues found during a check run.

Procedure

1. Run checks as described in Using the Check Tool for one or more components. The tool generates check results, some of which might be warnings or errors.

2. Select the result of one of the checks where issues were identified. If the check includes a quick fix, you see the four-step process at the top of the resulting window. You are in step 1, called Found Issues.

3. Choose Step 2 to proceed to Select Correction.4. The resulting window shows one or more corrections for the issue. Select the one you want and choose Step 3

to proceed to Final Approval.5. In the Final Approval step, you can opt to change your mind and not carry out the fix. If you want to proceed,

choose Step 4.6. The system confirms that the fix is now running. Choose Close to complete the procedure. The system verifies

that the fix has run correctly after a short time by running the check again.

Stories in People AnalyticsUsing the Check Tool PUBLIC 171

23 Data Protection and Privacy

Learn how you can keep the personal data of your employees secure and private with SAP SuccessFactors.

Centralized Data Protection and Privacy [page 172]Data protection and privacy features work best when implemented suite-wide, and not product-by-product. For this reason, they are documented centrally.

Data Retention Management [page 173]Identify which data purge function in the Data Retention Management tool meets your data protection and privacy requirements.

23.1 Centralized Data Protection and Privacy

Data protection and privacy features work best when implemented suite-wide, and not product-by-product. For this reason, they are documented centrally.

The Setting Up and Using Data Protection and Privacy guide provides instructions for setting up and using data protection and privacy features throughout the SAP SuccessFactors HXM Suite. Please refer to the central guide for details.

NoteSAP SuccessFactors values data protection as essential and is fully committed to help customers complying with applicable regulations – including the requirements imposed by the General Data Protection Regulation (GDPR).

By delivering features and functionalities that are designed to strengthen data protection and security customers get valuable support in their compliance efforts. However it remains customer’s responsibility to evaluate legal requirements and implement, configure and use the features provided by SAP SuccessFactors in compliance with all applicable regulations.

Parent topic: Data Protection and Privacy [page 172]

Related Information

Data Retention Management [page 173]Setting Up and Using Data Protection and Privacy


Data Protection and Privacy

https://help.sap.com/viewer/2becac773fcf4f84a993f0556160d3de/latest/en-US

23.2 Data Retention Management

Identify which data purge function in the Data Retention Management tool meets your data protection and privacy requirements.

The Data Retention Management tool supports two different data purge functions: the newer data retention time management (DRTM) function and legacy non-DRTM function.

RememberWe encourage all customers to stop using the legacy purge function and start using data retention time management (DRTM) instead. To get started using this and other data protection and privacy features, refer to the Data Protection and Privacy guide.

If you already use the legacy data purge function as part of your current business process and you are sure that it meets your company's data protection and privacy requirements, you can continue to use it, as long as you aware of its limitations.

NoteIf you are using the legacy data purge function, you can only purge a calibration session when there is at least one facilitator assigned to the session.

RestrictionBe aware that the legacy data purge function may not meet your data protection and privacy requirements. It doesn't cover the entire HXM Suite and it doesn't permit you to configure retention times for different countries or legal entities.

In the longer term, we recommend that you also consider adopting the newer solution. In the meantime, to use legacy data purge, please refer to the guide here.

Parent topic: Data Protection and Privacy [page 172]

Related Information

Centralized Data Protection and Privacy [page 172]

Stories in People AnalyticsData Protection and Privacy PUBLIC 173

https://help.sap.com/viewer/2becac773fcf4f84a993f0556160d3de/LATEST/

https://help.sap.com/viewer/dbdeaf664f894726b21680e3ebaf26d8/LATEST/en-US

24 Appendix: Stories in People Analytics

Stories in People Analytics powered by SAP Analytics Cloud offers a lot of capabilities that you can leverage to enhance your reports.

The stories you create in Report Center are built in the SAP Analytics Cloud environment, so for more information about creating and managing stories, please see the Stories section of the SAP Analytics Cloud help.

NoteOnly a set of the SAP Analytics Cloud features are currently supported in the Stories in People Analytics solution. To avoid confusion, please read the Story Canvas Functions Available for Report - Story topic before you refer to the SAP Analytics Cloud help document, so you read only the feature topics that are relevant to Stories in People Analytics.


Appendix: Stories in People Analytics

https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/29e0feaf17584e118ef30e6102008224.html

https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/index.html

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Stories in People AnalyticsImportant Disclaimers and Legal Information PUBLIC 175

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Documents

Stories in People Analytics