Design Infoobject with version maintenance

Question

Hi,
We have a oralce as source system. A table material group with mat group id, version id and some other columns needs to be extracted to BW. For every material group, 4 version id's are maintained and for each version id a validity period and version number is mainatained in another table.
To design this in BW, The infoobject material group was created with attribute Version id. This did not work as the mat group is not unique without version id. If  versionid is defined as compounding infoobject,  every version will be available in the report for eachmat group. The requirement is that the mat group in the report should show the current version being used with the quantities consumed/procured.
Any ideas how to design this in BW.
Thanks and Regards,
Srinivas
Edited by: Srinivas on Mar 18, 2011 6:47 AM

Answer 1

load second table to a dso (version id, version n°, valid period)
Create the infoobject with version id as compound. add a infoobject ZCURVERS as an attribute to your infoobject.
when loading from the first table to your infoobject , read the dso date in a start routine, and with the help of the valid period, you can determine which version is the current one. if this is the case you put an X in ZCURVERS. So per material group, you'll have only one line where ZCURVERS = 'X'. Now in your report, you need to filter on ZCURVERS = 'X'.
this should do the trick, however some remarks:
- use semantic groups to have all lines of the same material group in the same pacakge
- you need to do full loads
M.