SAP Knowledge Base Article - Public

2855524 - Data inconsistency between SAP Analytics Cloud and S/4HANA Cloud


  • Data does not match between SAP Analytics Cloud (SAC) and S/4HANA Cloud.
  • It only happens with certain dimension members.


  • SAP Analytics Cloud

Reproducing the Issue

  1. User imports data from S/4HANA Cloud to a Planning Model in SAC.
  2. The import uses an incremental load.
  3. Compare the data under same data region.
  4. Notice in SAC that there is data missing.


Incorrect import schedule customization settings.



  1. USe the Full Load option to ensure that there is no missing data in SAC.

Things to consider:

  1. Check the incremental load if the data load meets the three restrictions on the column data for the column user picks:

    1. The values must be unique.
    2. The data must be incremental.
    3. Previously imported data must be unchanged.

  2. Recommend to bring in the transaction ID as the incremental load column as this column satisfies the restrictions stated above.
  3. It is not  recommended to use the transaction date time integer column as the incremental load column because there is no guarantee that these values are unique.

  4. If multiple transactions happen at the same timestamp during the data acquisition import schedule, there is a high chance of a timing issue. 

  5. Alternative way: if the "transaction date time integer column" is selected: 
    1. User needs to schedule a timeslot for the import job where there are no new transactions being entered into the source table.
      This reduces the chances of the timing issue occurring using incremental load.

    2. After each import job run, users will need to compare the data and ensure that it matches the data in the source system.
      In case of missing data, user could use the replace subset option to fix the data without bringing in the full data again.

  6. See the following help document for more information: Building a Query.

  7. The incremental load will only bring in rows where the column value of the selected column is greater than the column value stored in a previous import. 
  8. Data rows could have been dropped due to rows being rejected in the data wrangling step.
    If rejected rows are not added back manually, then they will be missing from the SAC model.

See Also

Your feedback is important to help us improve our knowledge base.


SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, EPM-ODS, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics , KBA , standard procedure(data source) , LOD-ANA , SAP Analytics Cloud (SAC) , LOD-ANA-BI , Business Intelligence Functionality, Analytic Models , LOD-ANA-PL , Planning , LOD-ANA-BR , SAC Boardroom , LOD-ANA-PR , SAC Predictive , Problem


SAP Analytics Cloud 1.0