CMS moves to production

[Former Member]

Hi,

We are using the CMS for our landscape ( XI 3.0) from some time, DEV to QA

transports are moved with out any problem but i am facing the below

problem when i move few transports from quality to production.

In the Assembly tab i am selecting the particular component to be moved

instead of All components in the SELECT COMPONENT field but when i

assemble the particular object and move to production all the objects

for that component are been moved to production ( around 100 objects

are moved).

Please help me on this ASAP.

Note: If i want to move one particular object of SAP_HR software component to PRD from QA ( already there are 10 objects under this component in QA) is this possible thru CMS or not ?

Thanks

Sonali

[VijayKonam · Accepted solution]

CMS works at Software component level. You will not have control over the objects at individual namespace level once they are in Q system. Thats the way it works. Refer to my doc for any other inputs -

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa-middleware/soa...

VJ

[Former Member]

Hi Sonali

CMS works for Software component level only. Individual object movement will not work. You can use the file based transport for this purpose.

Thanks

Gaurav

[Former Member]

Hi All,

Thanks for your all replies...

I agree that CMS works on software component level but in the pratical situations in any project

My question is, suppose there are 4 developers who are working on SAP_HR SC and four of them are working on four diffterent objects and 4 were moved to QA box and only out of the four objects one got approval to move to PRD, how do i move that particular object to PRD ? so do i need to wait till all the 4 objects get approval ???

I am surprised how come all the other XI projects are using CMS so effectively ?

How does developers know when to use CMS and when to use file system ??

Thanking you in advance.

[Former Member]

Hi All,

Thanks for your all replies...

I agree that CMS works on software component level but in the pratical situations in any project

My question is, suppose there are 4 developers who are working on SAP_HR SC and four of them are working on four diffterent objects and 4 were moved to QA box and only out of the four objects one got approval to move to PRD, how do i move that particular object to PRD ? so do i need to wait till all the 4 objects get approval ???

I am surprised how come all the other XI projects are using CMS so effectively ?

How does developers know when to use CMS and when to use file system ??

Thanking you in advance.

[SudhirT]

Hi Sonali,

As said in earlier reply, This is the namespace only which will be visible in PRD or QA system. Suppose in your case the one which got approved for PRD. If you transport this particular namespace then alongwith this Namespace All other which are still not approved will be visible in PRD system.

But the thing is that these will be blank namespaces and will not contain any object like Data Type, Message Type etc.

Thanks!

[Former Member]

Hi,

Thanks a lot tp every one for ur help and support...

I have raised the OSS message and SAP has replied saying as below

sorry, but I'm afraid there is a misunderstanding here: As said before

assembly in CMS will collect the complete SC content from CONS state.

It is indeed confusing that you can mark single changes in asembly tab

-that's why this has even been changed in CMS UI with NW04S, SP13: Sincethen only a list of SCs is displayed (and selectable).

To state it most explictly: There is no way to influnce the assembly

result by any kind of selection of entries in assembly tab -it will

always assemble all changes present in CONS state.

Basic idea behind CMS track concept is that everything being released

from DEV will have to be distributed, CONS is mostly to check

completeness.

Meaning also that if you only want to ship parts you have to test them

before releasing (in DEV runtime system or other local RTS) or if you

find issues in CONS blocking further distribution you have to fix them

first (preferably in DEV, then retransporting -or if not possible then

directly in CONS, additionally afterwards also in DEV...).

Fixing here of course could mean 'improving until working' or 'removing

not working parts' (content itself is of course not lost, as DTR will

keep it in version history).

Hope this can help to clarify.

Regards,

[SudhirT]

Hi,

Please check again in the production All namespaces within that component are exported without any object in them. For eg. Check any Data type message type for the other namespaces . It wont be available there.This is the normal behaviour.

Thanks!