CHaRM-Handling old transport request before CHARM was activated.

[Former Member]

Hi All,

Recently i just activated CHARM in solman-SM1 for new a project implementation. This CHARM was setup in in such a way that it tie to one of the local IMG project EPROJ in developmemnt-DEV. Now i have one concern and that is those transport requests where created before i activated CHARM.

These old transport requests were crerated directly in DEV without project assigned. Therefore, we tried to assign IMG project EPROJ (the same IMG project setup in CHARM) into those old transport request manually.

Problem : When i tried to perform released step in CHARM tasklist it says that "No transport request found"

Question : How do i make CHARM to pickup those old transport requests?

Really appreciate your feedback as there are a lots of old transport request which needed.

Thank you.

[Former Member]

Hi,

Please check to which CTS Project the transport requests are assigned

and then you could change the CTS Status Switch for the specific CTS

Project.

Then you would be able to work with those transport requests.

If you don´t have CTS Projects assigned change in SE03 the Project

Assignment as not mandatory, just for a short period. Then you should

able to work with the old transport request.

In case they are already released and imported in test system I think

you can not include these orders to be manage by the solman CHARM

scenario.

Hope this helps.

Cheers

SH

[Former Member]

Hi Seet Ho Li,

Thank you for your prompt reply.

I have disable the CTS project as mandatory for CTS.

I tried manually assign the CHARM IMG project to old transport requests but some how tasklist in CHARM still doesn't pick it up when again try to release transport request.

Found one function in CHARM tasklist "/TMWFLOW/SCMA_TRORDER_ASSIGN". Which is to "register transport request in tasklist" but nothing happen when click on it.

Do you have any idea what does this function does in CHARM tasklist "/TMWFLOW/SCMA_TRORDER_ASSIGN"?

Thank you.

[prakhar_saxena]

Hi,

If you use Change Request Management, you should always use Change Request Management means to create transport requests; that is, create transport requests in a change transaction or in the task list.

Manually registered transport requests can be assigned to a task list only, not to a change transaction. If you use change transactions ,,,,the system does not take into account transport requests that you added manually.

This note is what you want

Note 1150426 - Registering transport requests in ChaRM

Hope it solve ur problem completely.

Regards

Prakhar