Skip to Content
Former Member
Sep 07, 2006 at 06:55 PM

ChaRM Scenario: how to manage rejected change request


We use the ChaRM scenario of Solution Manager 3.2 to manage the transport request for the R/3


We have two different project with two different landscape:

- the first one is used for customizing purpose ED1/010 - EQ1/010 - EP1/010

- the second one is for workbench purpose ED1/011 - EQ1/010 - EP1/010

Based on current Charm functioning, when a user rejects a change in EQ1, Charm creates a new blank Transport for the developer to make further changes which can then be taken to EQ1 again once the developer has made his changes. If the User is happy with these changes in EQ1, he will approve the Charm Change Request and only the "latest" Transport will be taken through to EP1, and the "rejected" Transport just stays on EQ1.

This could cause problems because the "latest" Transport could have dependencies in the 1st "rejected" Transport. The only way to overcome this is to manually insert all the components from the 1st Transport into this new one, which is risky.

Is it possible to take both Transports to EP1 (as we currently would do), or alternativly rather than create a new blank transport, create a transprot that includes all the objects of the 1st "rejected" Transport using the standard ChaRM feautures ?