In SAP SuccessFactors People Analytics (specifically Story Reports, which replaced Advanced Reporting), data is organized into schemas. The core Employee Central data is primarily structured around the Person and Employment objects. The system is designed to allow flexible querying by navigating between these related objects.

You can start a query with the Person schema to select personal details (like name and date of birth from the Personal Information table) and then navigate to the related Employment data to select job information fields. Conversely, you can start with the Employment schema to select job details and then navigate back to the associated Person data to retrieve personal information. Both paths are valid and achieve the desired result.

C. While the User category is related to Employment, the Employee Information table is not the canonical or most comprehensive source for personal details like date of birth, which resides in the Personal Information table.

D. Similar to option C, starting with the User category is less direct. The Person and Employment schemas are the primary starting points for building reports on core Employee Central HR data.

1. SAP SuccessFactors People Analytics: Stories | Document Version: 1H 2024

Section: Query Designer > Available Schemas for Story Queries

This official guide details the available schemas for building queries. It explains that schemas like "Person and Employment (as of date)" and "Job Information (Date Range)" are the primary sources for Employee Central data. The documentation implicitly supports the navigation between these core objects. For instance, when you select the Job Information schema, the tool allows you to expand and select fields from the related Person object, and vice-versa. This confirms the bi-directional relationship described in answers A and B.

2. SAP Help Portal: Implementing and Managing Reporting and Analytics in SAP SuccessFactors

Section: Building a Story Report > Using the Query Designer

The documentation on the Query Designer demonstrates how to add tables to a query. It shows that after selecting a primary table (e.g., from the Employment schema), you can use the navigation path in the left panel to find and add related tables (e.g., from the Person schema). This process validates the steps outlined in both correct answers. The tool's design is built on these relational navigations.