adding compounding infoobject to an infoobject with an existing one

[Former Member]

We have a characteristics infoobject ( A) with compounding infoobject (B) The data is loaded via PC file into the infoobject A and its attribute B and since it is compounding it creates the uniqueness of the data.Plan is to add another field to the PC file as another key. I know if we add another infoobject as compounding infoobject (C) and populate it via PC file it will make it unique . Problem we have many DSOs and InfoCubes attached to use the infoobject (A) and adding another compounding infoobject (C) means delete and reload. Is there any way to add this third key without having to touch all this data ?

sap 7x

Thanks..

[Former Member · Accepted solution]

Hi,

As I understood you want to add one more componding key in existing object which is used in various cubes/DSOs.

You are saying that you do not want to delte existing data so I assume that existing data structure is correct and data is as per your need. You are doing this for some new requirement.

If this is the case then only option is create a new object put all compounding as per your need, map the same with existing data source and add this object where ever you need that compounding attribute.

If the issue is with existing structure and data the compounding will impact all so it is better to add the object and realod all dependent object.

I hope it will help.

Thanks,

S

[Former Member · Accepted solution]

We thought about using remodeling tool but checking online and hearing about it that it could cause cube/DSO data corruption for large set of data not sure we want to go that route. so basically only way is for us to copy each DSO to another add the new infoobject to old one once we delele the data and copy back over and same for the cubes ?

btw this infoobject is used as part of virtual characteristics in the cube and DSO.

Thanks

[Former Member · Accepted solution]

Hi,

Yes that is the best way to do.

It is longer and time consuming but it will avoid all possibility of data corruption and inaccuracy.

It will be better for future usage of object/infoprovider/data as well.

I hope it will help.

Thanks,

S

[Former Member]

Hi,

I have a very similar requirement, so I need your suggestion to know how you implemented above.

We have 2 infoobjects (say INFO1 and INFO2 ) existed in DSO already, but they are independent as of now. It is write optimized DSO.

Now we want to do compounding of INFO1 with INFO2. I understand we need to delete data from Master data objects before doing this. I want to know Do we need to delete data from DSO also? Can we avoid data drop from DSO when we already have them added in DSO as independent infoobjects-

Thanks,

-Su

[Former Member]

Hi,

I prefer you to approach this way:

First delete the total content of the Master data and also the respective transaction where ever this object is being used in Dev.

Enhance the Master data object and also the respective transaction.

Send the new Transports to the next level. Before importing the transport take the backup of the data in the backup oDS or CUBE and then delete the content of the targets. Once this is done then import will be successful.

Finally you will have your structures were in place and then you can load the data back from back up target to the actual target. Here you need to check whether you need the data for the newly added object or not? based on that you can decide whether to use the backup data or to extract the data from the source?

Thanks

Murali M

[Former Member]

Thanks for the suggestions. But we need the cube still available to users while we do the reload . so we plan on fixing the DSOs and rollup to new cube and then map our multiprovider to new cube.

[Former Member]

Better use Remodeling:

[http://help.sap.com/saphelp_nw70/helpdata/en/58/85e5414f070640e10000000a1550b0/frameset.htm]