Is an Open ODS View in the middle of a dataflow a good idea?

[martin_chambers]

Can or even should Open ODS Views be used in the middle of a dataflow?

Example - A dataflow consists of
DataSource -> aDSO -> aDSO -> aDSO -> Composite Provider

Now, because I want to save memory space and because the transformation between the two aDSOs is fairly simple, I decide to replace the second aDSO with an Open ODS View.

The new dataflow Looks like this.
DataSource -> aDSO -> Open ODS View -> aDSO -> Composite Provider

Questions:

Is it a good idea to virtualize an aDSO by replacing it with an Open ODS View?

If so, why?

If not, why not?

Any help will be appreciated

Martin

[shanthi_bhaskar]

Hi Martin,

Open ODS View not only meant for consuming for external data access it can used used for virtualizing the data in the BW data flow.

It is always recommended to reduce the data persistence by reducing more layers with Virtual models.

If I were you then I would had tried to remove the next ADSO with virtual model.

Thanks,

Shanthi.

[Former Member]

Hello Martin,

The whole purpose of having a open ODS is to handle data from external systems and using it in the middle of data flow will defeat the purpose. If you want to virtualize it then why not use composite provider instead?

Thanks

Abhishek Shanbhogue

[martin_chambers]

Why? What are the disadvantages?

[FCI]

Composite provider and Open DSO are virtual structures. They have no place in the middle of a physical data flow (at least I can't find one).

Regards,

Frederic