cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Replication Flow not being selected as Analytic model Dependency

NicolasRivas1991
Explorer
0 Likes
409

Hello everyone,

I was creating a new package for an analytic model and I noticed that neither the replication flows that replicate the tables being used in the pipeline nor the task chain that execute those RF are being selected as dependencies of that analytic model. 

Why is this happening?

It happens with every asset?

How can I achieve this?

Thank you.

Accepted Solutions (0)

Answers (2)

Answers (2)

CLTGravesen
Active Participant
0 Likes

Hello @NicolasRivas1991 ,

The short answer to your question is: Sorry, there is no way. 


Why is this happening?


In Datasphere, you can download the CSN / JSON file for almost any object. 
For the Analytical Models. that file contains the full dependency tree for that object, down to local / remote tables, including all associations. 

When you're creating a package, Datasphere unravels the CSN file to find all the dependencies. 

For a replication flow, the CSN file contains the connection, the source and the target.

So, to answer your question: It happens because the way SAP decided to build the CSN files dosen't include the replication flows. 
Why did they make this decision? God knows...🤷‍♂️


It happens with every asset?


Same as above - the replication flow isn't stored as a dependency. 


How can I achieve this?


With great difficulty, I'm afraid. 
When you add a replication flow to a package, all the target tables are added.

A solution, while low-tech as all hell, is to keep all your replication flows in a folder (Maybe called Dependency flows) and add them to your package. 

Sorry I can't be more helpful 🙂

reyemsaibot
Active Participant
0 Likes

Hi,

the "problem" is the dependency analyzer shows only direct dependet objects. The RF is dependent on the local table and if you check the table you see the RF. The same is for the task chain. The AM is not depending on the Task Chain it is the RF.

When you check the other way around a view which is used in several other views and you look from the AM you only see the direct "connection" and not the other views your view is the source.

 

I hope it is clear.