3661170 - Blank records in Table reports despite correct permissions

In Table reports, records will be blank depending on the column sorting of a field despite correct permissions.

SAP SuccessFactors HCM Suite

1. Add two fields to a Table report that are configured with the same column ID.

   • Example: Country-specific custom fields like "Parking (Germany)" and "Parking (Denmark)", both using the identifier "cust_Parking"

2. Observe the report output:

   • Records may not populate for the field that appears to the right of the other in the report layout.

3. Change the column order:

   • Move "Parking (Denmark)" to appear before "Parking (Germany)".
   • You’ll notice that the previously missing records now appear for "Parking (Denmark)", while "Parking (Germany)" may now show blanks.

Employee Central Engineering has confirmed that this is expected behavior: Role-Based Permissions (RBP) will only recognize the first field with a given identifier. As a result, any subsequent field with the same identifier will inherit the permission status of the first one.

In the example above, if the "Parking (Germany)" field appears before "Parking (Denmark)" in the report, and the user does not have permission to view "Parking (Germany)" for a user in Denmark, then "Parking (Denmark)" will also appear blank (even if the user does have permission for "Parking (Denmark)") because the system applies the RBP of the first field it encounters.

Scenario 1 (Germany first):

Scenario 2 (Denmark first):

There are two ways to address this:

• Configure fields with unique identifiers
• Grant the permission for all fields with the same identifier in the roles where the access users had the permission for specific fields in the first place

Table, RBP, permission, blank, null, missing, incorrect, result. , KBA , LOD-SF-ANA-ADH , Adhoc Reports & Report Builder , Problem