Symptom
- Importing standard content views to a different space fails with the error as below:
- Error during import: "Couldn’t import object <Object A> [SAP_CONTENT\<Object A>] : 'We couldn’t save your object <Object A> because it’s dependent on missing objects: SAP_CONTENT.<Object B>, SAP_CONTENT.<Object C>. Create or import the missing objects first, and then reimport your package.'"
- However, <Object B> and <Object C> exist in both the target space and the SAP_CONTENT space.
Environment
SAP Datasphere
Reproducing the Issue
- Open Semantic Onboarding -> Content Network -> Business Content.
- Install a standard package to the space SAP_CONTENT.
- Go to Transport.
- Export and import this package to a different space in the same Datasphere tenant.
- The import fails with the error indicating missing dependencies SAP_CONTENT.<Object B> and SAP_CONTENT.<Object C>.
Cause
The prerequisite views are expected to be shared from the SAP_CONTENT space. Because the dependencies are not the shared SAP_CONTENT entities, the importer reports them as missing.
Resolution
- In the SAP_CONTENT space, share the prerequisite views to the target space.
- In the target space, ensure that the dependencies point to the shared SAP_CONTENT entities. If local duplicates exist, delete or rename them to avoid conflicts.
- Deploy the shared prerequisite views in the target space.
- Reimport the standard content package and select “Deploy after import.”
- Verify that the import completes without the missing dependency error.
See Also
Keywords
datasphere, standard content, import error, dependent on missing objects, missing dependencies, SAP_CONTENT, share entities, prerequisite views, graphic view, transportorder, transportorderitem, unit of measure, SAP_BC_IL_A_UnitOfMeasure, SAP_BC_IL_A_UnitOfMeasureDimension, target space duplicates , KBA , DS-MD-REPO , Repository Backend , Problem
Product
SAP Datasphere 1.0
SAP Knowledge Base Article - Public