cancel
Showing results for 
Search instead for 
Did you mean: 

CRMD_ORDER No link to maintenance cycle

Former Member
0 Kudos

Hello,

I am having a problem and hope that one of you can help.

We have configured are on SolMan 7.0 and have CRMD_ORDER configured to link a SLFN to Change Request (ZCRH) to a change document (ZDHF).

Scenario 1: When user id A assigns the maintenance cycle in ZCRH, it creates the ZDHF and links the task list. Then, the same user id (A) puts the ZDHF into development, the transport requests are created. It works correctly. It also works successfully using User id B for the entire process.

Scenario 2: User id A processes a new ZCRH. The ZCRH is assigned to a maintenance cycle and the ZDHF is created. When user id B opens the ZDHF and puts it in development, the ZDHF results in the error "No link to maintenance cycle".

So, when the process is performed by the same user for the entire flow, the process is successful. When it varies between user ids performing the actions, then the error occurs. It does not look like an authorization issue since I tried it using User B with SAP_ALL assigned and the error still occurs.

We've been in production for about 5 years with Solution Manager. This has been occurring in development testing and simulation testing for a few months.

Does anyone know a possible cause? Thanks in advance for any help!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Jansi,

Thank you for your response.

The tasklist status is in development without release and is active. /TMWFLOW/PROJMAP also shows the tasklist is active.

The flow works successfully with the same user performing all the actions. The error only occurs when different users are used to perform the various actions.

Do you have any more suggestions?

Paul_Babier
Advisor
Advisor
0 Kudos

Hello Robyn,

I have checked other customer messages on this issue.

If there is not a lock, then it might be best to open on OSS message with SAP.

For the messages that I see that were the lock was not the issue, it required the assistance of development support.

So in this case, my recommendation would be to open a support mesage with SAP on this specific issue.

Regards,

Paul

Former Member
0 Kudos

hI

when the process is performed by the same user for the entire flow,
 the process is successful. When it varies between user ids 
performing the actions, then the error occurs

Since you using the maintenance cycle f the same project, it may be locked as discuseed here. please look at the solution over there

[|]

Jansi