cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Source System Identification in the target from Multiple Source Systems

former_member203111
Participant
0 Likes
371

Hi All,

I have two problems:

1.

I am loading Masterdata from three different source systems into BW 7.3 and using a source system ID as a field to identify the data into the target. Lets say Source system PE, GE and CE. I am defining the 0syslog as a constant in the transformation rule in the Materdata Attribute so it can identify the data in the target based on the source system ID.

I see the data into target according to the source system but it is over writing the records For example: If I am loading data for the  Company Code 1000 (same company code exists in all 3 source systems) it over writes the previous

In other words when I load data from source system PE I can see the data into the target but then I load the data from GE it over writes it and when I load the data from CE it will over write GE accordingly because of the same company code. IF COMPANY CODE IS DIFFERENT THEN IT HAS NO PROBLEM I CAN SEE DATA FORM ALL SOURCE SYSTEMS.

Can you guys please suggest and advise that how do I go about and identify this data coming from different source system although data belongs to the same Company Code.

Regards

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Likes

Hi,

I would suggest you to load data into  DSO from all 3 sources initially before you load it to Master data object.

In the DSO make your Soure system field and company code as Key fields and other attributes as Data Fields.

Now if you have Same Company Code coming from all 3 sources, you will have 3 records in your DSO and then accordingly you will have 3 in Master data.

Regards,

Ganesh Thota

former_member203111
Participant
0 Likes

Ganesh,

Thanks for your reply.

I like to mentioned here that CompanyCode is not the only M/data I am pulling but there is tons of M/data as well such as Chart of A/C, Controlling Area. Customer, material, Plant etc etc.

Are you suggesting to create a staging DSO for all this M/data load afterwards. This seems like a lenghthy job considering number of masterdata needs to be loaded. How would I go about to create DSO in this case as master data is consist of Attribute & Text (No Hierarchy).

Is there any other way out such as deleting an existing Ma/data Transaction data and then use the compounding tab to check masterdata option to identify the source.

Please advise, thanks

Regards