Symptom
In some edge cases on the SAP Datasphere Consumption API while requesting data from SAP Datasphere views which come from non-replicated external BW objects there may be a divergence between the number of the records returned and the number of records informed as total OData count.
This could result into SAP Analytics Cloud and SAP Datasphere integration issue while using OData APIs as communication layer, resulting in truncated imports.
Environment
SAP Datasphere
SAP Analytics Cloud
SAP BW
Resolution
The resolution for such problem is to temporarily disable the OData Countable capabilities for such views, for this do the following:
- Edit your view annotations manually adding "@Capabilities.CountRestrictions.Countable": false, in the same level as "elements" under the view name.
- Deploy your view and try the SAC import again.
With this in place, SAC will not process your import considering the value of @odata.count, which should fix the number of records.
Keywords
KBA , DS-BB-ODATA , To address issues related to Odata consumption API , Problem
SAP Knowledge Base Article - Public