SAP Knowledge Base Article - Public

2989939 - DRM 2.0 produces error ‘Data could not be fetched’ while filtering by payGroup


You are observing the error ‘Data could not be fetched’ while filtering by payGroup in the new Admin center > Data Replication Monitor 2.0.

Looking the browser F12 > network > you will see in the $batch call response the error similar to this:

  • "error" : {
    "code" : "ServerErrorException", "message" : {
    "lang" : "en-US", "value" : "Invalid property names: EmpJob/payGroup. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this field, and please execute a refresh metadata to ensure the cache is not corrupted."


  • SAP SuccessFactors Employee Central
    • Data Replication Monitor 2.0


Some customers have the EC field payGroup configured under Job information > EmpJob/payGroup.

Some customers have the EC field payGroup configured under Compensation > personNav/employmentNav/compInfoNav/payGroup.

The DRM 2.0 uses OData internally and the tool cannot make one call to fetch the fields in both places together (HTTP 404 error).


There is no current solution for this issue and SAP engineering team is discussing internally in the reference internal number ECT-154000.

The issue is being evaluated to be fixed with some configuration or other method not decided yet. This issue is happening since DRM 2.0 was introduced (not tied with some new releases) and it might take time to be fixed.

Please check the What's new Viewer for future releases or also this KBA to see the status.


ECT-154000, DRM 2.0 Data Replication Monitor, SAP SuccessFactors Employee central payGroup, Invalid property names: EmpJob/payGroup, Data could not be fetched. Please try refreshing the browser page. If the problem persists, contact your system administrator' , KBA , LOD-SF-INT-DRM , Data Replication Monitor , LOD-SF-INT , Integrations , Problem


SAP SuccessFactors HXM Suite all versions