Skip to Content

DXC landscape side car approach

Hello All,

While reading about the DXC landscape side car approach from the document "Extractor based Data Acquisition by SAP HANA Direct Extractor connection", I unable to understand a particular sentence (i.e.)

"We go for Side Car approach when the embedded BW is already in use".

Could anyone please explain.

Below is my understanding,

The ECC system by default has an embedded BW system in it and if thats used for any requirement other than using it for DXC then we go for Side Car approach since that emb.BW system is already used for loading purposes.

Do we really use the embedded BW which is in ECC system for any requirements? If we use then for what kind of requirements we go for embedded BW other than using it for DXC?

Vinoth V

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Aug 23, 2012 at 01:36 PM


    Here are my thoughts.

    From an SAP HANA perspective, DXC is a cost effective data provisioning alternative to SLT and/or BODS (aka data services).

    The downside of DXC is that it replicates data into SAP HANA on a batch mode usually with delta enabled extractors provided by SAP. Meaning near real-time since the scheduled batch job can run every few minutes - which should still work for most of the business scenarios that do not need actual real-time. The advantage of using DXC is simpler infrastructure, cost and maintenance. Even though not worked on DXC, I personally favor DXC due to the advantages mentioined above.

    Hope this helps.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Vinoth Vasudevan

      Yes Vinoth,

      That is very correct. This is because (I think) - in DXC the PSA table connected to the extractor/datasource do not store data - it is only used for request handling. A request is created in the PSA but the data is only stored in the corresponding IMDSO in HANA.

      Whereas if the datasource is used in embedded BW, you will need the PSA table to store data for loading it to other objects in the data flow. Hence you need to use a sidecar approach. There could be other reasons as well but this is the one reason I can think of.



  • author's profile photo Former Member
    Former Member
    Posted on Aug 23, 2012 at 11:52 AM

    Hi Vinoth,

    Your understanding is right - It is very rare that the embedded BW in ECC or other netweaver source systems are used for reporting purposes. However, because it is available one cannot rule out the possibility either. For e.g. in small to mid-size organizations where the business suite is only used for a specific module and where the data volume is less - for multi-dimensional reporting purpose it makes sense to use the embedded BW instead of moving the data across to another BW system. With embedded BW, data lies in the same database (you are only moving it between tables - its free, same app server and same database) and if the data volume is less it wouldn't put too muchh load on the transactional system.

    Most companies go for a separate datawarehousing system just so that they avoid putting more load on the transactional systems with the number of reads & processes. If not, you could run OLTP & OLAP on the same system/database. So such a scenario makes sense in small-mid size system or for select modules with relatively low data volumne in large systems as well.

    For DXC, you cannot use an extractor that is already been used in the embedded BW and hence the sidecar approach for such cases.



    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.