Object Number (OBJNR) in BW Data Model

Question

Hi Gurus,
We are currently facing a hard to answer question. Here is the context:
- We use PS module in ECC6
- Somtimes WBS elements are renamed, ie the input mask is changed whereas costs were already allocated to that WBS
- The standard extractor for cost extract the WBS with its input mask
- Thus when a WBS element changes of input mask the cost might be on 2 different WBS in the BW datawarehouse. The attributes might change and thus the cost might be wrongly split on different objects...
Some other effects are for example that the User and systems statuses are not updated on the new WBS element.
The only we found to mitigate that issue, is to use the Object Number as the key reference. Thus, today, we think of using the OBJNR for each object category (Project, WBS, etc), and use it as the new key for these objects. We would transfer the attributes from 0WBS_ELEMT for example to ZOBNJRWB.
Has anyone experienced taht approach ? What would you see as benefits and disadvantages for that way of modelling the data ?
Thanks for your help
PY

Answer 1

Hi
thanks for the reply
Actually, the key is also changed when we extract transactional data.
For example, there is a cost of 10$ for WBS1, which has the OBJNR1, for period January
In february, there is a new cost of 20$, but between the two operations, WBS1 was fully renamed (the mask fully renames everything) to WBS2. The OBJNR did not change at all.
So if I look at the oveall cost per WBS or any attributes that was not updated correctly against the new WBS, I am screwed.because I am missing some data. But If I look at the data by OBJNR I am OK.
So I was wondering if someone decided to use that approach for BW.
Anyway, the conversion aspect is something very important that I haven't seen yet!
Thanks
PY