cancel
Showing results for 
Search instead for 
Did you mean: 

Component(Data Integrator) Vs Embeded Data Flow (Data Services)

Former Member
0 Kudos

Hi,

Is Component functionality in Data Integrator and Embeded Data Flow functionality in Data Services XI 3.1 are they same ?

Is there any difference between them as I know that Embeded Data Flows are nothing but Reusable Data Flows

Regards,

Anil

Accepted Solutions (1)

Accepted Solutions (1)

werner_daehn
Active Contributor
0 Kudos

We tend to call a workflow that is self-sufficient a component, e.g. do-all-that's-required-to-load-dimension-xxxxx. But this is really just a regular workflow we named C_xxxxx.

An embedded dataflow is a dataflow that either reads or loads data and is called within a regular dataflow. Typical usecase: My dataflows for the initial load and delta loads are almost identical, just the delta has the additional TableComparison transform in it. Does that mean I have to change two dataflows whenever a new column is added? Yes, certainly. So what you can do is embedd all the source objects and transformations into one embedded dataflow (just range-select the objects, rightclick, make_embedded_dataflow). Now I have two dataflows, both read from an embedded dataflows and load a target table, the one directly, the other via a TC transform.

https://wiki.sdn.sap.com:443/wiki/display/BOBJ/ETLProjectGuidelines

Answers (0)