SAP Datasphere - Semantic Onboarding - Dimensions / Text View - Usability

[nloeblich]

Dear Community,
I appreciate the new capability to import semantically-rich objects from your SAP systems. I have a few questions about issues that I noticed while dealing with this.

(1) Technical Name
The picture below shows the result after a successful upload with the option: "Replication Flows to Local Table". In result the automatic naming convention is Remote.{Connection}.{CDS View}. This is a bit irritating because a locale table is created. In case I'm onboarding an view with the option: "Remote Table" the same naming convention is used. 

Well this leads me to fact that the mechanism of Semantic Onboarding does not separate between source type like Remote.{Connection}.{CDS View} or Local.{Connection}.{CDS View}. Additionally, I don't seem to be able to import a view for federation and replication.

What is your recommendation to achieve both integration scenarios via Semantic Onboarding? (Of course, there is the known capability of "Import Remote Table").

(2) Semantic Usage
The picture below shows the result after a successful upload with the option: "Replication Flows to Local Table". The field Semantic Usage shall me indicate how can i use this artefact for. In that case it is of type dimension. 

The picture below shows the result after a successful upload with the option: "Replication Flows to Local Table". As result of semantic onboarding all semantic types were taken over. But the last column is very import for a decent dimension artefact. The different semantic types or associations are made usable for further usage. But this column is empty and loads of warnings appear to this issue.

If I worked with this automatic result, I always had to create an additional dimension view on top. Well, that is certainly relevant for further modeling requirements. But what is your recommendation to use this "Ready to Go" - Feature (Semantic Onboarding)?

Thanks
Nico

[Martin_Kuma]

Hey Nico :). Only BW objects from BW/4 can be "onboarded" directly. From CDS Views, you just use this as a template - like BW content, which you either copied or modified to your needs, but never used out-of-the-box. You can use the replication flow to create the target table proposal and before you deploy, you alter the table. Cheers, Martin