0SOURSYSTEM as Attribute vs Compounding

[Former Member]

Hi BW Experts,

I have a requirement where in a new R/3 system will be connected to the existing BW system .

I read in the forums about using source system ID as compounding object to get unique records from diff source system.

But one thing i still am not clear is , cant we use 0SOURSYSTEM as an attribute instead of using as coumpounding ?

Could someone please tell me why we cant use it as an attribute? I dont think overwriting data in infoobject should be a problem since the source system would be different. Pls correct me if I am wrong.

Thanks a lot in advance

[Former Member · Accepted solution]

Hi

even if you add it as an attribute it will not uniquely identify the the charastersictic

suppose you have an R3and CRM from which U are loading data and say product is the characristic there is no gaurantee that the product ID is unique in combination from both of them so inorder to uniquely identify the master data U have to compound it with the souscesystem

Hope this helps you

Regards

Ajay

assign points if helpful

[Former Member]

Thx a lot Srini and everyone!

[Former Member]

Hi Srini,

If I am using 0VENDOR in the infocube, you mean I have to add this logic in the update routines for 0VENDOR ?

Thx in avance.

[Former Member]

Yes, Ranjani.

You can do it at transfer rules level for the new source system only. If you write in updaterules, routine will be applied for both the systems. better in transfer rules.

Hope it Helps

Srini

[Former Member]

Hi Srini,

Thanks a lot for your inputs and looking forward for your help.

I need to do this for 0VENDOR.

Could you also please tell me how this will exactly work for making records unique and how the sample code would look like ?

And what is meant by adding to Transaction data ?

Regards

Sreeranjani.

[Former Member]

You can add a transfer routine at info object level and use the function module RSDG_ID_GET_FROM_LOGSYS, add the 0SOURSYSTEM object to attribute.

please let me know for any further clarification.

Regards

Rajanikanth.

[Former Member]

Hi Sreeranjani,

0VENDOR is the standard business content object having length of 10 Chars.

If you want to make records unique you have to add somthing to Vendor no(source system).

Ex : if you are getting vendor : 1234567890(10 digits)

If you want to add : sourcesystem(S1P) it will become S1P1234567890(Becomes 13 digits), you cant make this(length is not available).

OVENDOR IS Master data, if you loading transaction data into data target you have to do the same conversion for 0VENDOR.

Sample coding:

In update/transfer rules Write a routine like:

Concatenate 'S1P' <VENDOR> to RESULT.

Hope it Helps

Srini

[Former Member]

But one thing i still am not clear is , cant we use 0SOURSYSTEM as an attribute instead of using as coumpounding ? -

---

>

There is a separate infoobject for 0SOURSYSTEM also, but to check the uniqueness of the master data picked up form several/multiple source system, there is a compounding of 0SOUSSYSTEM with other infoobjects.

kindly assignthe points if it helps.

revert back if u need some more helps in this regard.

[Former Member]

Hi,

Thanks a lot for the answers.

Looks like using compounding option is very complex in an already live system as it involves reload of lot of objects.

I believe there is another option of using ABAP routines in transfer structure to make records unique.

Any idea how this can be done ?

[Former Member]

Hi Sreeranjani.

<i> I believe there is another option of using ABAP routines in transfer structure to make records unique.</i>

You can do this, but it again depends on availability. You can make it unique by adding source system(Eg: S5P) to each record using abap coding for new records and you have to do the same for transactional data aswell. But object should have enough length to do this.

Give some more details, infoobject(name, type, length..)

Hope it Helps

Srini

[Former Member]

Hi Sreeranani,

When you add source system attribute as compounding it becomes a key field of master data tables along with the characteristic . So one value of characteristic can be assigned to a particular source system uniquely. If it is not a compounding attribute then it will not be a key field in master data tables.

Regards,

Prakash