Skip to Content
author's profile photo Former Member
Former Member

PM Order Data Consolidation - 0PM_DSO4

Dear Experts,

I have installed the complete data flow before for the PM DSO 0PM_DS04 which has four datasources, namely 2LIS_17_I3HDR, 2LIS_17_I3OPER, 0PM_OM_OPA_1,0PM_OM_OPA_2. All the data is consolidated directly into the DSO 0PM_DS04. PM Order Number is the key in all the Update Rules.

1. I got a suggestion that I should first load the data from different datasources into individual DSOs(How about Write-optimized???) and then consolidate the data into 0PM_DS04 from these DSOs. How big a difference does such a change in the data flow make? The routines in the update rules need to adjusted and can anyone comment how tedious it could be?

Does anyone have experience implementing this BI Content DSO?



0PM_DS04.PNG (7.4 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Mar 21, 2015 at 11:54 PM

    HI Ardy,

    Business Content installation is the easy way but not always sufficient. I always consider it as a (very welcome) starting point and depending on your ambition level you can reuse it and/or enhance it to meet particular Data Warehousing standards or architecture guidelines.

    Following an LSA approach, I suggest to introduce an intermediate Propagation layer where you have a standard DSO for every DataSource (with key fields corresponding to your DataSource source tables). Optionally you could have a Corporate Memory DSO (write-optimized) for every DataSource.

    The Consolidated DSO I would position in the Business Transformation layer. You will have to analyze very well if indeed special Transformation rules (especially routines) can be found in the Transformations from DataSource to the Consolidated DSO. You will have to recreate / copy such Transformation rules to the new corresponding Transformation from Propagation DSO to Consolidated DSO.

    Best regards,

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Ardy,

      My recommendation is to create at least 4 separate standard DSOs (Propagation layer) with key fields which correspond to the source table(s). Standard DSOs are much easier to handle in data staging processes.

      Optionally, you can also create 4 write-optimized DSOs (Corporate Memory layer) for emergency cases.

      The Transformations can indeed be implemented from the Propagation DSOs to the Consolidated DSO (Business Transformation layer).

      Re. the aggregation, I think that you should experiment with the Transformation. You can oversee best how the aggregation should be done, try to achieve the required aggregation behavior by evaluating Business Content and projecting it to your new data staging model.

      Best regards,


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.