Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member

SAP BW system can be connected with multiple source systems. Among those source systems SAP ECC is central nerve for BW data source.  Most of BW systems are linked with at least one ECC system. How about linking more than one ECC system with single BW system?

First question – is it possible? Yes it is very much possible.

Second question - what is the best data modeling strategy to follow which minimize complexity in design as well as eliminate data redundancy?

Here I am summarizing a few best data modeling strategy while linking multiple ECC system with one BW system

A. Master Data

To minimize repetition of master data info objects utilize  single (standard or customized) master data info objects. Compound master data info object with source system (0SOURCE_SYSTEM). Due to compounding record from each system will be unique along with combination from source system.

If you are wondering, why Compounding is required? It is required because if same value arrives from both systems then it will through duplication error or even if duplicate handling is enabled at DTP level, it will overwrite existing value with new one. In such case we will have value from one system only.

For Example, if we are getting 0Materail having material number M001 with different attributes from Source system ECC1 and ECC2.

0Material details are as below

0Material Attributes

Source System ECC1

Source System ECC2

Material No



Material type



Merchandise Category









In such case if 0Material is not compounded with source system, we will have only one M001 that gets uploaded recently i.e. either from Source system ECC1 or ECC2. To retain M001 from both systems, compounding with source system is required.


B. Transaction Data

In case of transaction data any such specific mapping is not required. Best practice is to keep data in separate DSO/info cube from each system.

To create consolidated report utilize multiprovider with DSO/Info cube from both systems.

At query level as per need restrict source system in restricted key figures.

C. Process chain

Since Master data info objects are same, so we need to upload data from each system in sequence to avoid lock situation.

Transaction data have no impact because source system and target providers are different.

D. A few more frequently asked questions

- Delta Handling

No impacts on delta load and delta pointer since source systems are different.

- Data Load Performance

Data load performance will not have much impact if process chain to upload data from each system organized efficiently to avoid dead locks.

- Reporting

We can create reports as per need either from single system or consolidated one inclusive of each system. It will be more flexible. To optimize performance restrict info provider wherever possible.

- Data Volume

It is based on transaction data in each system.

Please note above list is not exhaustive. It can be adopted as per requirement and specification.

Hope it will help.


Former Member
0 Kudos

Sangita, Very nice article. I do have a question, however. The source system is a 2 character long field. Can we modify that field length or is it better to create a  new field.


Former Member
0 Kudos

Thanks Samir for your appreciation. If source system is having a field with 2 character length and in BW corresponding info object is having length 1, then better to increase the length of BW object. It will not impact, even if data is already loaded for that object. However it is not advisable to decrease the length. In such case better to create a separate info object.




Active Participant
0 Kudos

Informative...... :smile:



Former Member
0 Kudos

Thanks for the document.

I got one question: Can A single BW System connect to Multiple Clients of a Single Source System [ECC]



Former Member
0 Kudos

Hello Rajeev,

Yes, it is possible to connect Multiple clients of a single ECC system with a single BW system. You can contact Basis team for more details about connection settings (SM59 etc.).



Active Contributor
0 Kudos

Dear Sangitha,

Thanks for sharing this Document.

Regards, Vijay

Active Participant
0 Kudos

Simple and Nice Guidelines..! :smile: Thanks for Sharing ..!

Former Member
0 Kudos

thanks sangitha



0 Kudos

very informative Sangita, thanks for sharing


Manna Das

Former Member
0 Kudos

Hi Sangita,

Will there not be any issue of duplication if we have Source systems of different Clients(100, 110) of ECC into BW(100)?

We are in the same situation to have 2 different clients of ECC connect to BW.
From Basis perspective, it is a possibility, but from BW standpoint, what precautions/steps do we need to take to avoid any discrepancy.

Thanks and Regards,

Satish Dhanalakoti

0 Kudos

Hi Satish,

Each ECC Client will be created as its own source system in BW, and each one should have a different logical name, i.e.:



From this point forward apply the same logic Sangita presents in her Blog post to avoid any issues.

Note that each source system should have its own 2 digit code for infoobject 0SOURSYSTEM, you set the code assignment in RSA1 > Source Systems > Menu: Tools > Assignment of Source System to Source System ID.


Jose Luis Leitao

Former Member
0 Kudos

Hello every one,

We are in same situation.

Can you please  share me  any process documents



Former Member
0 Kudos
Hello Everyone,


What about the data sources and respective transfer rules or transformations?

Is there a program which can replicate these between new ECC and existing BW systems? (Similar to existing ECC and BW).

Or, should everything be redesigned?


Thanks & Regards

Labels in this area