Skip to Content

LSA Design for SAP BW Open Items

Hi Experts

I would like to built BW(BI7.3) data flow based on LSA for the DS 0FC_OP_01.

Since DS data source does not support Delta,I use Full IP with filters.

DS (Full IP with filters),Write Optimized DSO1 (as Acq.Layer),Write Optimized DSO2 (as BTL) and final Cube (for reporting).I use request based Delta to furhter data flow.Is this correct approach?

I have design document (BW 3.5) but not based on LSA,kindly share documents if any.



Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on Dec 27, 2013 at 11:55 PM

    Hi TG,

    First of all, let me give some background information on LSA (Layered, Scalable Architecture). It's SAP's reference model for an Enterprise Data Warehouse Architecture. It's all about standardizing your BW implementation by defining your own "customer LSA". I.e. the reference model can be the starting point or inspiration, you have to work it out, find sponsorship and embed the architecture in your own organization. That makes it hard to predefine how it should look like in your case.

    However, from my own consulting practice, I see that many organizations adopt the reference Layers:

    • Data Acquisition Layer (DWH);
    • Harmonization & Quality Layer (DWH);
    • Corporate Memory Layer (DWH);
    • Propagation Layer (DWH);
    • Business Transformation Layer (BI);
    • Reporting Layer (BI);
    • Virtual Layer (BI).

    The (Enterprise) Data Warehouse Layer consists of the first 4 layers. The Architected DataMart Layer or BI Layer consists of the last 3 layers.

    Scalability is another story, I see much different approaches here. However, the basics are strategic partitioning using Data Domains and tactical partitioning mostly using time characteristics calendar year and fiscal year.

    Please refer to my blog series Pattern-based Partitioning using the SPO BAdI - Part 1: Introduction which cover a lot of aspects in this area.

    Please refer to the SAP Help for more information on the Data Warehouse concept and LSA.

    My practical advise for your data flow is as follows:

    • Data Acquisition Layer: no need for a w/o DSO (PSA is enough);
    • Harmonization Layer: transformation -> generic, data unification & harmonization;
    • Propagation Layer: standard DSO if possible (refer to Business Content DSO or main ECC table(s) to determine appropriate key fields);
    • Business Transformation Layer: transformation -> business rules;
    • Reporting Layer: InfoCube;
    • Virtual Layer: MultiProvider.

    If your DataSource does not support delta uploads, then you should try to make it work with full uploads. It's important to stick as much as possible to a limited set of data flow patterns. Please refer to my blog Standardizing Data Flow Patterns using Data Flow Templates for more information in this area.

    I hope this helps. If you have any other questions in the area of LSA, please let me know.

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Hi TG,

      Good to hear that you are aware of LSA but based on my own experience, it's not easy to implement it. I see quite some discrepancies between your suggested data flow and my advised data flow.

      The new data flow pattern which covers this example data flow should in my opinion contain a standard Propagation DSO. An important design choice is the key fields; normally you should reflect the source system's table or Business Content DSO. A standard DSO is advised because it's much easier to consume by DataMart applications.

      Although your DataSource can only handle full uploads, it's likely that you can switch to a "pseudo delta" mechanism, filtered on fiscal period or posting period. This way you can significantly reduce the data volume to be uploaded.

      Anyway, the challenge of any LSA implementation is finding solutions to this kind of generic problems. This should in my opinion be reflected in data flow templates to reinforce a consistent, pattern-based implementation.

      Best regards,


  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2013 at 12:57 PM

    Hi TG,

    For Delta to work you need to understand the KeyFigures and impact on it. for LSA you can search for Layered Structured Architecture on SCN.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 27, 2013 at 01:00 PM

    Hi TG,

    Am not familiar with LSA.

    But your approach was acceptable one.

    When data source doesn't supports delta we alwyas use DSO in our data flow. before the info cube. so that we can load delta records to info cube by using dtp.

    Write optimized DSO - its fast loading and no activation was step required. its good approach.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 27, 2013 at 02:18 PM

    Thanks.I am aware of LSA for other flows.But I would like to know about how we should configure LSA for open Items (Finance Data).Even KF update mode can be either Overwrite or summation,since I get unique record for my IP filter value.Question is 2 DSO and cube will work,because as per the BW 3.5 standar flow has only DS to Cube no DSO inbetween.But for LSA I need DSO.Any inputs experts?



    Add a comment
    10|10000 characters needed characters exceeded

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.