Compounding or Concatenation

[Former Member]

We are bringing in data from a 3rd party GL system that has Company and Cost Center as higher-level keys to account.

We are debating which way is better: (1) compound the 2 objects to account, or create one InfoObject that is a concatenation of all three. The one InfoObject would have the 3 individual components as attributes, probably navigational.

One one hand, I have read that compounding causes performance problems. On the other, I have heard that navigational attributes can also add overhead.

Not being in production, we're not in a position to model it with real data.

Any thoughts or advice would be appreciated.

[Former Member]

Hi,

As you mentioned that Company and Cost Center are keys, in order to get unique data into BW you have to use compounding. If you want to use navigational attributes there may be a possibility of getting duplicates.

Hope this helps...

With Regards,

Ashok

[Former Member]

hi,

I think its better to use compounding i mean ur first preference.