CHARM problem with transport request release

[#1]

Dear

CHARM was configured in standard scenario

I have a problem with the identification of error that occurs during the change of status of the document change for urgent correction. After approval step "Release transport request" process finished without errors but the application log shows the following errors " Function canceled Variant 00000000000009 already exists" and transport request is not released.

When I try to change the status of the change document to "Pass correction to test" the process finished with warning "Not all transport requests yet released."

When transport request is released manually the whole process works fine until I close the project cycle.

Maybe someone met this problem ?

Thank you in advance for your help

Mirek

[Former Member]

Sometimes you will find some information via ST22 in the satellite system (dev-system).

In some cases I hat to assign RFC-ACL authority to the developer. Only with this authority the developer was able to release transport requests via urgent correction.

[Former Member]

Are you able to release transports with normal corrections by setting their status to Consolidated? Sorry for so many questions, just trying to narrow down the possibilities.

[Former Member]

I would start with a system trace on both SolMan AND your Dev system. It sounds like an authorization issue.

You've released the task, right?

[Former Member]

Dear

I am able to manually release the transport (SE01) but I have problem with release transport from change document level.

My user has sap_all profile. I had checked authorization by trace and I had not found problem with authorization before sending this message

Kind regards

Mirek

[Former Member]

Please run the trace and ensure that it's your user trying to release the transport. It may be your RFC has a system user releasing it.

Turn on your trace and then view the results for all users for that 10 seconds you performed that action. Remember, check both SolMan and Dev.

Again, you released the task before trying selecting the pass to test action, correct?

[Former Member]

Dear

Charm was is configured for presentation solutions. I use only one system (solman) in which I have three clients. 100 - (use for CHARM and dev), 200 - test 300 - production.

I made a test of the authorization but did not find fault problem. In SMSY transaction for my client 100 I have used RFC connection type I (Internal Connection).

Kind regards

Mirek

[Former Member]

In which client did you test the authorization? What user is assigned to the ChaRM RFCs?

You need to provide more detail in your posts. It's too hard to troubleshoot this without the details and you can't assume things when doing this through a forum.

AND once again, did you go to SE09 and release your task before selecting the Pass to Test action in ChaRM?

[Former Member]

Dear

I have used "current user' for RFC to 100 client.

As described standard configuration CHARM transport should be release from the transaction, eg crmd_order (document change level) As I wrote before the whole CHARM process (urgent correction) works correctly with the exception of release transport request. I can release the transport from transaction SE09/SE01 but I would like to be able to release the transport of transaction-level eg.crmd_order. I found the only errors that I described earlier when I tried to release the transport of transaction-level crmd_order.

Kind regards

Mirek

[Former Member]

You have to release the task (not transport) in SE09 before choosing the ChaRM action Release Transport or Pass to Test (which releases your transport as well). Did you do that before selecting the action?

[Former Member]

Dear

Yes I had released all task in transport request before I tried to make action "release transport request" or "pass to test from"

from crmd_order transaction

Kind regards

Mirek