Order of loading Master Data - Fact or Fiction

[former_member205400]

I understand that for loading Master Data for InfoCube 0FIAA_C01 (or any other) you should load starting from the lowest level.

That means for every characteristic in the cube you have to check and see if any of the InfoObjects have Master Data attributes, and if any of those attributes have attributes, and so on. This quickly becomes a multi-level structure.

Part of the tree structure for 0FIAA_C01 would look like:

0FIAA_C01

..........0COMP_CODE

....................0CHRT_ACCTS

....................0C_CTR_AREA

..........0ASSET_AFAB

..........0ASSET

....................0ACTTYPE

....................0BUS_AREA

<snip>

So does that mean that 0bus_area should be loaded first before 0asset?

Is this fact or fiction?

If its a fact I am wondering what tools SAP has for determining the order of loading Master Data.

Discussion points and tools for facts awarded!

Mike

Edited by: Michael Hill on Feb 12, 2008 4:52 PM

[Former Member · Accepted solution]

the load sequence does matter when it comes to Asset Accounting. I believe there is OSS out there specifying the order and even you can find it in help too. I havent seen such kind of dependencies in any othe module other than AA and IPM and also where inteferential integrity comes into play.

To verify ur fact or fiction - just break the sequence and try loading data, if it goes thru its a fiction (but it will fail)

[former_member205400 · Accepted solution]

This link:

http://help.sap.com/saphelp_nw70/helpdata/en/a4/f4153c4eb5d82ce10000000a114084/frameset.htm

does talk about a sequence of loading for a couple of Master Data InfoObjects for Asset Accounting.

Other than that it must all be "FICTION", unless someone else knows better.

So .. the only loading sequence then is that all Master Data should be loaded before transaction data and there must not be a particular loading sequence for Master Data with the exception noted for Asset Management.

[Former Member · Accepted solution]

yeah other than load sequence dependent modules - you may call it fiction if you would like. Loading master data before transaction data is just a best practise at the best.

[former_member205400 · Accepted solution]

I closed this thread, but as I was re-reading it I noticed that you were inferring that I was talking about "fact" vs "fiction" in terms of loading master data before transactional data.

I'm not even questioning that! Truely master data should be loaded before transactional data.

I am questioning whether Master data should be loaded in a sequence, i.e. based on the level of the attribute in the Master Data "tree" as I described in the first posting.

Any other comments?

[former_member205400 · Accepted solution]

Must therefore be fiction.

[Former Member]

Hi

Refer this

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/afbad390-0201-0010-daa4-9ef0168d...

In this guide, load into data targets - > Infocubes

Refer data load performance -> upload performance (pg 21)

[mathew_muthalaly]

Hi,

My master data loads are largely in the area of HR.

The only order I follow while loading master data is for a particular infoobject with regard to text, attributes and hierarchy - The order being text>>attributes >>hirerachy. Frankly, I have not checked doing it otherwise.

Across different master data infoobjects I see no need to have any order atleast in HR. Generally speaking a master data object has data that has an independant existence as extracted from R/3 or other sources and not derived from any other master data object in BW.

Master data as its name implies should not have referential integrity checks with other master data.

It would be good to know if someone has real experience to the contrary.

Mathew.

[Former Member]

You can upload data although no master data exist, it is set at infopackage level. Then the load order doesn't matter.

[Former Member]

We load master data from the top down. Orgunit then job then position...so I'd say that the load order is fiction.