SAP Knowledge Base Article - Public

2607166 - EC Standard Report 'Compa Ratio and Range Penetration' cannot be validated due to a missing table - ORD


Standard EC Reports 'Compa Ratio and Range Penetration' and/or Pay Range fail to run and customers are unable to validate it when checking via 'Instance Validation' or 'Report-Canvas Validation' tool.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental


SAP SuccessFactors HXM Suite

Reproducing the Issue

If using Report Center:

  1. Home
  2. Admin Center
  3. Click 'Reporting & Analytics' Icon
  4. Go to Report-Canvas Validation
  5. Validate 'Compa Ratio and Range Penetration'
  6. See Error Message.


  1. Access the Analytics page
  2. Access the Analytics tab
  3. Go to Report Designer
  4. Find and edit the report 'Compa Ratio and Range Penetration'
  5. Validate the report
  6. See one or more of the following error messages.



  • All EC standard reports are built based a configuration considered to be a commonly used one.
  • It is quite possible for the configuration of instance you are uploading the report to, does not match with what the report was built on.
  • The PayRange related standard reports (payrange and comparatio and range penetration reports) are built for instances with the PayRange defined based on Geozone, Paygrade and Legal entity.
  • If your instance does not have the same association, these standard reports will fail to run and the validation errors cannot be fixed.

Below is an example where the Payrange is defined based on geozone and payGrade but has not dependency on Legal Entity



The ideal solution would be for you to rebuild the report manually, based on how payrange us defined in your instance.

The following articles should help you with the same:

2136061 - How to determine which Pay Range is used in the Compa-Ratio and Range Penetration calculations - Employee Central

2559179 - Compa Ratio and Range Penetration report - Advanced Reporting

However, if you wish to reconfigure the instance, just to make the standard report work in your favour, you would have to add the missing association for PayRange.

  1.  In this scenario, you will need to update your Corporate Data Model with the following association:
    • <association id="id" multiplicity="ONE_TO_ONE" destination-entity="LegalEntity" required="false"/>. 
  2. Once this is done, you will need to add data for Legal Entity for at least one Pay Range to validate the association so that it is picked up in Advanced Reporting.
  3. Then a metadata reload  has to be performed for the recent changes, made to your EC configuration, to be reflected in Advanced Reporting. This can be done by following one of the below approaches:
    • See if View Based Metadata (VBM) is enabled on the instance. In which case, you could perform the reload yourselves. Refer EC Advanced Reporting Metadata Sync (View Based Metadata)
    • If you do not see the option of 'Purge Advanced Reporting Metadata Cache', please raise an case with Support requesting a reload.
  4. Once the above is completed, validate the report and then you will be able to run/edit the report Compa Ration and Range Penetration. 

See Also

2357821 - EC Standard Report Validation Errors Descriptions, Cause and Fix - tips and tricks

Installing and Validating Report – Canvas Templates

How to determine which Pay Range is used in the Compa-Ratio and Range Penetration calculations - Employee Central


FOUNDATION_OBJECTS_VIEW_FO_OBJECT_RELATIONSHIPS_T_PAY_RANGE_LegalEntity, Standard, Report, Reports, Transfer, Validation, validate, instance, Advanced, Reporting, Data, Model, Configuration, Compa, Ratio, Legal, Entity, Table, not, found , KBA , LOD-SF-EC-REP , Reporting Data (EC core only) , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , LOD-SF-ANA-ADV , Advanced Reporting (ODS) , Problem


SAP SuccessFactors HXM Suite all versions