Master data from Multiple SAP source systems

[Former Member]

Hi Gurus,

In my present project we are having an ECC6 and r/3 from which we need to extract master data.

ex: vendor

same vendor has different entities in the systems.

I am aware of the data inconsistency as it would be overwritten.

We don't want to use MDM,compounding or transfer duplicate records options.

MDM - not in use

Compounding - expensive Option

transfer duplicate records - not reliable

Merging r/3 in to ECC6 is also under consideration but it would be late 2010.

I am sure some of you might have been through this scenario and your help is appreciated and will be rewarded.

Thank you,

Ram.

[former_member205352 · Accepted solution]

We went with Compounding option.

Can you justify Expensive ????

We compounded 0LOGSYS,infact you can use 0SOURCESYSTEM.

So that 0SOURCESYSTEM will have the server details.I mean your ECC6 or R3.

or

Some crude solution would be add some character to the beginning of your master data like from ECC 6 append E.

or

Have you heard of Consolidated infoobjects Concept.You can go with that too.

Hope this helps.

Edited by: Praveen G on Oct 1, 2008 9:04 AM

[Former Member · Accepted solution]

Compounding is automatic when you go into the compound section fo the infobject and click the box which says source system dependant (or somethign like that)

Check this months BW Expert thats where I picked this up

[former_member205352 · Accepted solution]

Simon you are right.This will just introduce 0SOURCESYSTEM.

Isnt it ??

Which is the same I was talking of.

[Former Member · Accepted solution]

Yes that is correct (I didnt realise the option was there to do it automatically!)

[Former Member · Accepted solution]

Hi praveen,

Thanks for the reply,Yes i did look at Consolidated objects option but the object (0GN_VENDOR) is too high level.

I can't use Compounding as it is expensive in BO reporting.

The master data is used in reports so users would not be happy to see 'E' appended to the vendor number..

Any other suggestions Please!

-Ram.

[Former Member · Accepted solution]

Hi Simon,

Thanks for the suggestion. However i cant use it as its expensive using compounded objects in BO query.

cheers,

Ram.

[Former Member · Accepted solution]

Would't it be much more expensive not to use it?

Imagine the continuous trouble with dealing with wrong data (master data that is necessary to fill transactional data) and the losses in credibility when you are displaying the right data with the wrong texts for end-users.

Simply cannot live with that.

Either go to Compound or create a whole new set of global objects update from ODS with the source system in the key.

I would go with compounding...

[Former Member · Accepted solution]

Hi Miguel,

I am looking for any alternative approches (if any!)

Thank you,

Ram.

[udayabhanupattabhiram_cha]

Ramu, here is my 2 cents worth. Don't know if it will work in your case.

why don't you use different InfoObjects with same attributes. So, your Cube will have multiple infobjects. In query, pick the infoobject that corresponds so that you get the right master data.

This will be less expensive than compounding.

Uday Chamarthy

[Former Member]

Hi,

you could either include source system in your masterdata (vendor) as an compounding attribute or you map the vendors depending on source system to a general one.