3794413 - Transport fails due missing dependent objects although these objects are already shared to target space

An error occurs during the import of entities (tables, views, models) stating dependency on missing objects.

However, the dependent entities are already deployed in the Target Space.

• Couldn't import object <Object_name> to space <Space_name>.
• We couldn't save your object <Object_name> because it's dependent on missing objects:
• Create or import the missing objects first, and then reimport your package.

• SAP Datasphere

1. Create an entity (Object A) which depends on another deployed entity (Object B).
2. Import Object B to Datasphere tenant and share it to the target space.
3. From Content Network, start installing the package containing only Object A into the target space, where Object B have already been shared.
4. Get the error.

The installer resolves dependencies based on objects included in the import package.

Dependent entities that are only shared across spaces but not added to the import package are not resolved.

Therefore, the missing dependencies need to be added to the package. 

Check lineage of the entity you would like to import as per: Impact and Lineage Analysis | SAP Help Portal.

A package must contain the complete lineage of all the objects including shared objects.

For further information please refer to: Packages | SAP Help Portal

1. Add the required dependent tables/views to the same import package, even if they are already shared and visible in the target space.
2. Re-run the validation and deployment of the business content installation.
3. If issues persist, verify that sharing and authorizations are correctly configured for all dependencies, then repeat steps 2–3.

• Impact and Lineage Analysis | SAP Help Portal.
• Packages | SAP Help Portal

medallion architecture, local table not found in target space, business content, content network, dependency resolution, shared objects, cross-space, inbound space, central development space, harmonization views, installation failure, datasphere import, shared table dependency, analytic models, repository explorer, dependent on missing objects , KBA , DS-MD-REPO , Repository Backend , DS-ACN , Datasphere Content Network and Transport , Problem