Question:
We are using 0PLANPLANT(Maintenance Planning plant) in our query. which is reference from 0PLANT.
In R/3 they built a custom table with Region,Division and plant . All the three fields form the key.They are grouped like hierarchy.
In query they want to see this grouping.
Please do advise on how i can design this .
My initial approaches were :
1. Add region and division as compounding to 0PLANPLANT. On the R/3 side append the 0Plant DataSource with Region and Division.
I was not able to implement this as , i can't just compound these infoobjects to 0PLANPLANT. I also need to compound them to 0Plant. If i compound them to 0Plant, these two Info objects should be in all the Cubes/ODS/Infosources in which Plant is used.
2. My second approach was to create a DataSource on that custom table and in BW i created a ZPLANT with Region and Division compounded to it.
I tried to replace 0PLANPLANT with ZPLANT in my ODS but 0PMPLANGRP has 0PLANPLANT compounded to it. In 0PMPLANGRP i tried to replace 0PLANPLANT with ZPLANT but as region and division are compounded to ZPLANT it was asking for those two infoobjects. When i added them, i am getting error as 0PMPLANGRP is used in many places and that i need to add region and division in all those places.
Please do advise on this issue.
Appreciate any help.
Thank you.
Answer:
Compounding additional objects add some complexities as you have discovered. If you are simply transfering a single table from R/3 to a BW ODS, then you really don't need to compound the objects. Simply set the key of the ODS to match that of the R/3 table. The hierarchy effect can still be achieved in the query tool.
The only reason you would need to compound these objects is if you are using the contents of this table as master data attributes (or nav attributes) on another data provider. It that is the case, then you should probably take a step back and make completely custom objects for the whole process and not be bound by business content restrictions.
Answer:
Harrins...Thank you for your immediate response...
I am using the contents of the table as master data attributes. That's the reason i am compunding as all the three of them form the key.
As you mentioned i created a completly custom object. But i also need 0PMPLANGRP which should have this custom infoobject zplant compounded to it. IF i do that it is also asking for region and division.
0PMPLANGRP is used in many infoobjects and all those should also have region and division.
Please do advise....
Answer:
You should ask the R/3 developers if the key is correct on their table. Can the same plant really exist in two different regions and/or divisions?
If it can, then you correctly defined the zplant compounded with these objects. The next question is if you have master data associated with the group that changes by division/region.
If the answer is yes, then you have no choice but to create a new group object with the proper compounding and deal with any cascading issues. If the answer is no, then you can use the existing object (or a new one with no compounding if this object is compounded with plant). You would populate that field from your transaction data or with a lookup to a xref table in your TR/UR.
Answer:
Thank you so much harrins for your immediate responses.
I did ask R/3 developers and what they said is one Plant will be associated with only one Region/Division combination.
I am thinking of creating a new Zplant compoundeed with Region/Division . This plant will be loaded from the custom datasource built on that custom table.
If i need to get the text for this Zplant or to get the other attributes of 0PLANT for this Plant..
How do i get them.....Please do advise...
Will flexible update on 0PLANT works or is there any other approach...
Thank you and appreciate your help....
Answer:
You are overthinking this issue. Basically the R/3 developer has included region and division on the key of their attribute table when it does not need to be there. You do not need to make the same mistake in BW for no advantage. Go to the developers and ask them to change the key to only include plant with region/division as attributes. You can then do the same in BW. Even if they do not make the change, I would not introduce the additional keys in BW unless you have some historical significance to the region/divion.
Answer:
Thank you So much harrins. R/3 developers are changing the key to only include Plant.
Now i will just take Region/Division as attributes to 0PLANT and that should solve my issue..
I will enhance 0PLANT_ATTR to get the values for Region/Division..
Please do correct me if i am worng.
Appreciate all your help and time....
Thank you