Replication Flow not being selected as Analytic model Dependency

[NicolasRivas1991]

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.

[CLTGravesen · Accepted solution]

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 🙂