3522876 - Associated Entities not coming up during Semantic Onboarding from S4HANA on-premise

Executing the semantic onboarding option with access "Replication Flow to Local tables" and not all associations are getting imported as local table. Only text association gets imported. For example, when importing entity I_Customer from an S/4 HANA on-premise system only the text association entity CustomerClassificationText is imported. The rest of the association is not imported, although they are seen in the I_Customer local table under associations tab.

SAP Datasphere

All these associations are part of the metadata, i.e. they come with the CSN definition, and get stored in the Datasphere Repository as part of the "Entity". Therefore one can see the associations in the metadata display.  However, the backend system does not provide all "target" entities of these associations when you execute an import. For most imported entities the so-called "import scope" is "ObjectModel": Hereby the backend typically only resolves text associations, and a few others (based on complex back-end side criteria), for most other "sidewards" associations the targets are not part of the import scope. (This is backend side logic, Datasphere does not have an influence on this). 

When deploying the runtime tables for the entities in the import scope there are two cases: 

•  The target entity is part of the import scope (e.g. text entities) - in this case the dependency will immediately become usable and you can navigate between the entities
•  The target entity is not part of the import scope. In this case the association is only stored in the Repository as a "dangling" association, but it won't be deployed because the target is missing the association and it cannot be followed at this point of time. But if you import the association target at a later point of time (or if the target entity is part of the import scope of a different entity) and the target entity gets deployed, then the Repository is checked for matching dangling associations, and the association will be deployed. Afterwards it will be usable from both sides. Check note 3463326 - SAP Datasphere: Metadata Import from SAP S/4HANA On-Premise via "CSN Exposure" Service - New Deployment Option "Replication Flow to Local Table" section "Association Import (Runtime) - Dangling Associations:"

• 3463326 - SAP Datasphere: Metadata Import from SAP S/4HANA On-Premise via "CSN Exposure" Service - New Deployment Option "Replication Flow to Local Table"
• Semantic Onboarding

Semantic onboarding, datasphere, association, csn, I_Customer, replication flow to local tables , KBA , DS-MD-ESH , Repository Explorer , Problem