SAP C_THR92_2411 - SAP Certified Application Associate - SAP SuccessFactors People Analytics: Reporting

Schema and Table Relationships

In SAP SuccessFactors Story Reporting, tables are only displayed in theAvailable Datasection if they have a direct relationship or join with the selected starting table (in this case,Basic User Information).

Why the 2019 Performance Review Table is Missing

Since theBasic User Informationtable is selected, only tables directly related to it will appear. The 2019 Performance Review Table is likely not joined directly to the User schema.

Why Other Options are Incorrect

B (No Report Object Configuration Entity record): The table is present in the schema, so it must have a valid ROCE record.

C (No RBP permission): This would prevent any access to the table but does not explain its absence from the Available Data section.

D (No data access permission): This would restrict data access, not the visibility of the table.

References

SAP SuccessFactors Story Reporting Guide

Default People Scope:

When building a query, the defaultPeople Scopeis set to theDirect Reportsof the logged-in user. This ensures the user only sees data relevant to their scope of responsibility.

Runtime Filters (A):

These are filters that the user is prompted to set when executing a report. The user can define filter criteria dynamically at runtime.

People Scope (D):

This filter type allows reports to be filtered based on groups or populations defined in the user’s permissions, such as specific departments or locations.

Refreshing Metadata Cache:

When new MDF objects or fields are added, the Advanced Reporting tool may not immediately reflect the changes.

Using thePurge Advanced Reporting Metadata Cache Toolensures that the latest metadata is loaded into the reporting framework.

Quick and Effective Solution:

This method is faster than requesting support or rebuilding cubes and resolves most synchronization issues instantly.

When a user cannot see a table report in the Report Center list, the issue typically stems from insufficient role-based permissions (RBP) granted to the user for accessing reports in that domain. Specifically:

Understand Role-Based Permissions (RBP):

In SAP SuccessFactors, reports and analytics visibility is governed by RBP settings. These settings ensure that users only see the reports and data they are authorized to access.

Permissions are categorized into domains such as "Employee Central," "Performance Management," etc.

Key Permissions for Reports in the Report Center:To view or run reports in Report Center, users need:

Run Report Access: This allows users to execute reports for domains they are permitted to access.

Create Report Access: This enables users to create or modify reports.

Manage Tiles and Dashboards Access: This is necessary for interacting with dashboards and tiles, not table reports specifically.

Access to Insights: This refers to viewing analytic insights and does not directly impact table report visibility.

Diagnosing the Issue:

The given scenario describes a user being unable to view a shared table report.

The most likely cause is the absence ofRun Report access to the domainassociated with the table report.

Without this permission, the system restricts the user from running or even viewing the report, even if it has been shared with them.

Steps to Resolve:

Navigate to Admin Center→Manage Permission Roles.

Select the permission role assigned to the user in question.

ClickPermissions→Reports Permissions.

Verify that theRun Report Permissionis granted for the specific domain associated with the shared report.

If not, enable this permission and save the changes.

Test Access:

After updating the permissions, the user should be able to view the table report in the Report Center.

SAP SuccessFactors Help Portal:Role-Based Permissions

SAP SuccessFactors People Analytics Reporting Guide (Latest Release):Check for details on report permissions and their implications.

SAP KBA 2461114:Troubleshooting Report Center permissions.

Learning Path:SAP Open Learning on SuccessFactors RBP and Analytics (openSAP).

Step-by-Step Analysis:References and Documentation:This explanation ensures that the resolution is precise, supported by standard SAP practices, and verifiable through official SAP documentation.

Reporting Menu (A):

Users can access shared canvas reports directly from theReporting Menuin SAP SuccessFactors.

Report Center (D):

The primary location for managing and accessing all types of reports, including shared canvas reports, is theReport Center.

Issue with Static Date Filters:

If the query uses a static date filter (e.g., a specific range like "January 1, 2023, to March 31, 2023"), the report will not reflect the most recent data as the filter restricts results to the defined date range.

Resolution:

Update the query to use dynamic date filters (e.g., "Last 30 Days" or "Current Year") to ensure the pivot table includes the latest data.

To allow a user to add a new story that includes Career Development Planning (CDP) data:

Career Development Planning → Data Access: Story (A):

This permission grants access to Career Development Planning data for use in stories.

Career Development Planning → Career Development Plan (CDP) Access Permission (D):

This permission ensures access to the Career Development Plan data necessary for including it in a story.

Understanding the Problem

The issue arises because employees without data in either the Dependents table or Address table are excluded from the results.

Explanation of Inner Join

Aninner joinreturns only rows that have matching entries in both tables. If an employee does not have corresponding records in either Dependents or Address tables, they are excluded from the result set.

Solution

To ensure all employees are included, you should use aleft join, which retains all rows from the Personal Information table even if there are no matches in the joined tables.

Why Other Options are Incorrect

A, B, and D: These describe left join scenarios, which do not cause the issue described in the question.

References

SAP SuccessFactors Query Designer Guide

Saving Chart States in a Story ReportSAP SuccessFactors Story Reports provide the ability to save states or views for specific visualizations.

Explanation of Correct Answers

B. View the chart in explorer mode, and choose + New View: Explorer mode allows creating a custom view of the chart with selected filters or dimensions.

C. Select the chart on the canvas, view the bookmark menu, and choose Bookmark Current State: Bookmarking saves the current state of the chart for easy retrieval later.

Explanation of Incorrect Answers

A. Export: Exporting does not save the state; it simply downloads the chart.

D. Explorer Mode Export: Similar to A, this does not save the state but generates an export file.

References

SAP SuccessFactors Story Reporting Guide