ChaRM Batch Job

[Former Member]

Hi,

For the ChaRM Implementation we have created a batch job which moves the transports into the QA system every 5 minutes. In the case of Normal Corrections ChaRM creates two types of transports, namely Generated Copies of transports and then the Actual transports. In the case of Generated Copies , a copy of the transport is moved to the QA system in some manner even though the Main Transport is not released but the Child Transport is released. The Actual transport is moved only when the the Main transport is also released. Both these two types of transports are visible in the buffer. The batch job moves both the transport of copies and the actual transport when it runs after they appear in the QA buffer.

However what we want is for the Generated Copies to be moved whenever the batch job runs and the Actual transport to be moved by the batch job only when the Change Manager approves it.

Is there any way this could be accomplished.

Regards,

Vinod

[sridhar_rao4]

hi Vinod,

can you share details of the batch job which moves the TR? We are looking for a solution to move TR into Prod based on a timing logic, which is aligned to Transport window.

Please share program name which is used and if any other customizing was done to achieve this.

[Paul_Babier]

Hello Vinad,

Have you looked over this [Blog|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20451] [original link is broken] [original link is broken] [original link is broken];?

Regards,

Paul

[khalil_serrhini]

Hello Vk,

can u tell me if my explanations are clear for you. If your problem is solved would you please close topic

Regards

Khalil

[Former Member]

Hi,

Let us assume that we have a batch job which runs every 5 minutes to transport whatever transports are there in the QA system buffer to the QA system.

Now when the developer selects test transport from the actions button a generated copy is put into the QA buffer. When the batch job runs this is imported to the QA system. This is fine.

Subsequently when the developer selects Complete Development from the actions menu another generated copy is put to the QA buffer. when the batch job runs this is imported to the QA system. This is also fine.

When the change request comes to the to be tested state, the actual transport is released. This then goes to the buffer and is transported to the QA system when the batch job runs next.

This is where we have the problem. We want the actual transport to be released to the QA buffer only when the change manager approves it.

Regards

Vinod

[Former Member]

The way we accomplish what you asking is by allowing the developers to u201CTest Transportu201D, but they can not u201CComplete Developmentu201D. Only the change manager can u201CComplete Developmentu201D. We started this process because we wanted to make sure a code review had taken place before releasing the actual transport to QA. This allows us to keep a lot of junk transports from entering our production buffers.

Thanks

Jeff

[Former Member]

Hi Jeff,

We are implementing ChaRM and would you be able to share more on how did configured so only the change manager can u201CComplete Developmentu201D.

Thanks

Huan

[khalil_serrhini]

Hello vk

Concerning your point 1 : 'In the case of Generated Copies , a copy of the transport is moved to the QA system in some manner even though the Main Transport is not released'. This is a functionnality that Solman offers that gives the opportunity to do tests in QUAL system w/o releasing the actual TR. The main advantage of this is that you can do tests and then if you re unsatisfied re-do changes before releasing actual TR. To make it simple it gives 'more flexibility'

Concerning your Point 2: Your batch job does nt make any difference between TR types (T: copy or actual TR).

So in order to sepaarate them during transport to QUAL you simply have to make sure that only the copy TR is in buffer when batch job runs. And the only way a TR can be added to buffer is when it is released (different for Copy TR: automatically done) -> that means that you do not have to release your actual TR unitl you test the copy in QUAL system and tests of change are OK. The TR hsould be released only when the Change Manager wants to approve Change

hope it helps

keep me updated if my explanations are not clear

Khalil