Symptom
When creating a Story report that includes a Custom MDF Object field from a standard Legacy Foundation object table (such as Location), the field shows random digits instead of the expected data.
Joins are unavailable in Story reporting when Legacy Foundation objects reference Custom MDF objects as associations.
Environment
SAP SuccessFactors HCM Suite
Cause
The field in the standard table is displaying the external name for the referred custom MDF object.
This behavior can be validated by the Data Inspector tool:
- Go to Data Inspector
- For Entity, select Table_GENERIC_OBJECT_T
- For filter, select: External Code | Equals | <MDF field code>
- Under External Name, the same value will be shown as the one in the report
Resolution
This is the current limitation of Story Report.
When referenced as Field:
A custom field in legacy Foundation Object referring to a Generic Object does not create any join to the Generic Object. Instead, the field shows the external name of the Generic Object as the retrieved data in the report.
As a workaround:
- Directly fetch the data from the custom MDF Object instead of relying on the referenced field in the standard table.
- Create the same query using the Canvas reporting tool, where the field is expected to display the data correctly.
When referenced as Association:
When a Generic Object is referenced as association from Legacy Foundation objects, no join is available in Story reports
As a workaround:
Create report with advance reporting tool, where join is available from Legacy Foundation objects to Generic object
Keywords
Custom MDF, FO, GO, Incorrect Value, Random value, Generic Object, Foundation Object, Standard table, random numbers, wrong number, wrong data, Legacy, Manage Organization, Pay and Job Structures, Configure object definition, Association, Field, Reference , KBA , LOD-SF-ANA-SAC , Stories in People Analytics , LOD-SF-EC-REP , Reporting Data (EC core only) , Problem
SAP Knowledge Base Article - Public