SAP Knowledge Base Article - Public

2912680 - "Schema of data source has been changed" error when refreshing a model imported from the Business Content in SAP Analytics Cloud

Symptom

When implementing integration jobs delivered as part of SAP Business Content packages (for example, SAP SuccessFactors Workforce Planning) imported from the SAP Analytics Cloud Content Network, errors during data import or job execution may occur.

Common symptoms include, but are not limited to:

  • Integration jobs failing with schema mismatch errors, such as:
    • “Schema of data source has been changed! Expected number of columns: X. Received: Y.”

  • Errors occurring even though:
    • The integration jobs are in their default state as delivered by SAP
    • No manual changes were made to the delivered jobs, queries, or mappings

  • Errors affecting one or more dimensions or fact models delivered by the business content
  • Job failures appearing after:
    • Reusing delivered integration jobs without reconfiguration

Environment

SAP Analytics Cloud Enterprise 2026

Reproducing the Issue

  1. Import an SAP Business Content package from the SAP Analytics Cloud Content Network (for example, SAP SuccessFactors Workforce Planning) into an SAP Analytics Cloud tenant.
  2. Ensure that the required connections to the source system (for example, SAP SuccessFactors) are created or adjusted in the target tenant.
  3. Use the integration jobs delivered with the imported content, without modifying the delivered queries or mappings.
  4. Execute one or more of the delivered integration jobs.
  5. Result: The integration job fails during execution with a schema mismatch error, such as “Schema of data source has been changed! Expected number of columns: X. Received: Y.”

Cause

The issue occurs because integration jobs delivered as part of SAP Business Content packages are not fully out-of-the-box across tenants without reconfiguration.

When business content is imported from the SAP Analytics Cloud Content Network, the delivered integration jobs still reference the original data source schema and internal connection identifiers from the source environment in which the content was created. In the target tenant, connections are recreated and differ. As a result, the schemas may differ from the schema expected by the delivered integration job.

Resolution

For this scenario, the delivered sample integration jobs and templates cannot be used as-is.

You must:

  • Rebuild and refresh the delivered import/integration jobs in the target tenant so that they reflect the actual data structure of your source system.
  • Recreate your integration jobs by selecting the available objects in your source system, ensuring alignment between:
    • Data structure
    • Selected fields
    • Data mapping
  • Adjust or recreate mappings as required to ensure that the expected schema matches the data available in your backend.

This approach ensures that the integration jobs are fully aligned with the customer’s tenant configuration and prevents schema inconsistencies caused by differences between source and target environments.

For further assistance, questions, or issues related to SAP Business Content, please contact the SAP Business Content team at: sap_analytics_cloud_content@sap.com

See Also

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

Keywords

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, schema, data, source, failed, refresh, metadata, column, mismatch. , KBA , LOD-ANA-ACN , SAC Content Network , LOD-ANA-DES , Story Design & Visualizations , Problem

Product

SAP Analytics Cloud 1.0