As we step into the future of SAP SuccessFactors, a recent release notice has heralded a significant change: Story Reports will be the sole reporting tool in SuccessFactors in 2024. In light of this exciting development, I’m launching a series of blogs dedicated to unraveling the intricacies of Story Reports. These posts not only aim to provide inspirations and sparks but also guide you through leveraging the full functionality of Story Reports. The series, rooted in common reporting needs, is designed to empower decision-makers with actionable insights. Whether you’re a seasoned SuccessFactors enthusiast or an HR professional looking to elevate your story report technical skills, this guide is tailored to help you unlock the full potential of your data visualization in SAP SuccessFactors..
Prerequisites:
Before we embark on this journey, ensure you have the following prerequisites in place:
Access to SAP SuccessFactors with the necessary permissions for story report (editing) and field permissions from Employee Central or other models you want to report. If you are missing view or edit permissions on fields from the model, the contents are showing as ‘Null’ or ‘-’ in story and you are not able to see any results on analysis.
Familiarity with the data model relevant to your reporting needs, such as employment details and what job information has been configured in your system.
A clear understanding of the metrics and dimensions you wish to analyze. If the dimensions or needed metrics/measures are not directly from EC, then you need to create them in story query or in calculated measures.
In short, the definition of what is reported is the priority.
Creating a Table List: New hires in 2023 as an example
Let’s start by creating a straightforward table list to display raw data. This can be used when migrate table report to story.
Create new report and select Story, in the query, select relevant data source. In the example, Job Information under Employment has been used to report counts. Select fields that will be used for the employee list by clicking the marked icon.
Depending how the MDF has been configured in your system you are able to find all jointed data tabled linked to Job information by unfolding the joints icon marked in the screen shot:
By default, the time filter for the first table in the query (Job Information in the example) is set to ‘As of Today’ (Dynamic). You can set it as a fixed date or change it to a time range
If you want to change the type of time filter into period, Remove current time filter first.
After removing the time filter, you are able to see 2 options for time filter.
Each of the joined data tables have their own time filter. It is important that you go through each of the data table in order to make sure the time of the data pulled in the report are exactly as you need.
Review the selected columns and save the query.
In story, there are 2 ways to pull table list:
- create a Canvas to start reporting, chose Table. This means the table will be built along with other analysis such as chart.
2. Create a new page, select type of the page as Grid and insert a table. In this way, the whole page will be reported on a table. For visualization, this way will give a similar look as in legacy table report.
If you have more than 1 data model in your story, make sure you select the correct data model in popouts.
In Designer, select List under Table Structure.
Non-Aggregated means there is no aggregation on the data, so the list will pull all the data records line by line.
Aggregated means the data will be aggregated based on the first column used in the list. In some case, if the query returns more than 1 line per employee, this may help downsize (remove the duplicates) the list as a line for each employee.
Drag and drop the required dimensions and measures into the Columns.
Customize the table by applying filters,
sorting options (it can be defined on each column),
and formatting preferences:
Show or hide options are from 3 dots on the right of the table.
Or from Designer –>Styling. You are able to set the styling for each columns or measures used in the table.
Preview the table to ensure it accurately represents the desired dataset.
Remember to check Drill Limitable: by defaulting, the table limited to 500 rows and 60 Columns. This will prevent the list pull all the needed records. Change it if needed.
Cross-Tab Table (Similar to Pivot Analysis): New Hires in 2023 as an example
Now, let’s take your reporting to the next level with Cross-tab tables. This method allows for dynamic pivot analysis, providing a comprehensive view of your data. Here’s a step-by-step guide:
Data Preparation:
Ensure your dataset includes the necessary dimensions and measures for analysis. In Cross-tab table, you are able to report what is the measure per dimension option, i.e.
Building the Aggregated Table:
Same step as in table list until chose Table Structure, in this step, chose Cross-tab
Adaptive column width: Automatically resizes the columns when you resize the table.
Arrange totals / parents nodes below: Moves totals to the bottom of the table. This should be used only when you have set Show total in Rows which have been selected. Otherwise, total may not be displayed.
Optimized Presentation: Provides fast-loading In-Cell charts, pixel-level resizing of columns or rows, and smooth scrolling.
Add the dimension to the Rows. When hitting 3 dots on the selected dimension, you are able to find more options for the display, including Show Totals. You can add more than 1 Dimensions in Rows, it depends what is needed for the reporting.
Filter the measures used in Column. Measures created in query or fields saved as measure type in query or measures created in story can all be found here.
Customizing the Aggregated Table:
Explore additional features to enhance clarity.
Such as order of measures and name of the measure
Filter on Dimensions selected as Rows.
Filtering and Styling:
Apply filters to focus on specific subsets of data.
Use the Styling functionality to boost visualizations.
Incorporate color-coding, icons, and other visualization options for a more engaging experience.
In the end, switch it to View and review the data.
Best Practices:
Regularly save your work to avoid data loss.
It is much easier to validate calculations and measures in a table list on the same time, so you are able to see what data has been used in story calculations.
If you are facing errors, go back to query and preview the data source to observe what has been preventing data from delivering results.
There are still limitations and known gaps in story report, please refer the SAP help documents here
Important Things to Consider About Stories in People Analytics
Congratulations! With these insights, you are now one step closer to mastering the art of creating table lists and cross-tab tables in SAP SuccessFactors Story Reports. These techniques empower you to transform raw data into actionable insights, fostering informed decision-making within your organization
Feel free to share your experiences and insights in the comments below. If you have specific questions or challenges, don’t hesitate to communicate. Happy reporting!
For more detailed instruction and definitions of story report, please refer this office learning materials for further dive. Designing Story Reports