Master data copy

[Former Member]

Hello,

I've a version 200, and selected to 'copy' it for a new version 300. My objective is to run almost the same consolidation, but with one different task on the 300. As I changed the task hierarchy in 300, the tasks also change in 200. Therefore, I've realized that I need to delete this version 300 and create a new one by selecting 'create'. But the thing is, I can't delete the 300 as the BCS shows me that the version 300 is still in use and cannot be deleted, I've checked the configurations, and it's only configured within version combinations, which I can't un-configure. So, I've tried to delete it in the Consolidation characteristics, infoObject: '0version'. but, as I check the data in it, there's no data from the BCS, I mean that all versions created in BCS are not in this infoObject. Can anyone help me?

Thanks in advance,

Beatriz

[Former Member]

HI Beantriz,

One of your question here is :

I've tried to delete it in the Consolidation characteristics, infoObject: '0version'. but, as I check the data in it, there's no data from the BCS, I mean that all versions created in BCS are not in this infoObject. Can anyone help me?

Answer:

BCS uses the object 0cs_version and not 0Version. So you can locate the version created in BCS in this infoobject. Hope this helps. Let us know.

[Former Member]

Hi Mani,

I'm aware that BCS uses 0cs_version, but I couldn't find it within the infoObject area, what i found in the infoObject area in BCS was this on I mentioned, 0version.

Is that possible, change the master data InfoObject name 0cs_version to 0version?

And if this is possible, then, maybe I don't see the versions created because it wasn't synchronized?

Can u help me, please?

[Former Member]

Hi Beatriz,

To answer your question:

Question : Is that possible, change the master data InfoObject name 0cs_version to 0version?

Answer : Yes possible.

Question: And if this is possible, then, maybe I don't see the versions created because it wasn't synchronized?

Answer: Could be .. if you feel it is not synchronized execute the program to sync it.

Please read the above answers in following context...

Though you can use the 0version in BCS, to make clear distinction in usage SAP has delivered the specific object named 0CS_version.

Functionally there is lot of benefits by keeping the BCS version( infoobject) different from BW versions .For example 0version has lot of maser data which is not at all relevant for BCS. I had a similar case in one client where 0version had nearly 40 version data , where as BCS version was needing 2 master data( such as actual and plan). hence the client kept the sepeate infoobject called 0CS_VERSION and maintained the 2 master data and kept BCS part straight forward.

But technically you can use 0version also in BCS. It is all your choice/selection.

Hope this clears the doubts...

Regards,

Mani.

[Former Member]

Hi Beatriz,

You may use almost ANY infoobject for role VERSION, including the std (0CS_VERSION or 0VERSION) and Z-objects.

Just go to Data Basis, Data MOdel tab and click on an icon for swithcing on tech names. You'll see which exactly infoobject is linked to VERSION role.

Do not forget about synchronization of data (if you do something separate in BW).

And bare in mind that if your version is linked already with some data/settings, you may break consistency if you delete the version in BW.

To check what is still linked to the version, goto version in UCWB, right click - where used.

[dan_sullivan]

Make sure that for Special Versions > Definitions > Hierarchy Structure you create a value 300 (or something unique for version 300). Then in the Special Versions > Assign to Combinations choose (double click) version 300 and for hierarchy structure > Task enter the value created for 300.

This enables you to have a separate task hierarchy for each version. Only changes made with parameters of version 300 are saved for that version. So take care with parameters when making task hierarchy changes.

[Former Member]

Hi Dan,

I'll try to do that.

Thanks!