Error message "Request/task can be changed only by holder"

[Former Member]

After switching from source system, all objects have received the new original system.

Now requests have been created with multiple tasks (task for every teammember).

The tasks are not shown in the list during customizing and when explicitly the request is entered, we get the following message:

"Request/task can be changed only by holder" (TR771).

Also found a note 1412178 - Various problems when using the transport register, but that did not help.

Who has a tip?

[tomas_black]

Hello W. van Veen,

indeed note #1412178 corrects ABAP problems related to the usage the transport register. You need to follow the manual steps and the apply the note via SNOTE. Did you do this? And the problem still persits?

Are you using transaction KE3I? If the error you're getting comes when you use this transaction, please do the following:

1. Go to tcode KE3I

2. Choose "Operating concern"

3. Press "Excute" or F8

4. A pop-up window asks for the requests - leave the entries blank

and click the Continue button

5. A new window opens asking for Workbench as well as Customizing

requests seperately.

6. Here Select "Own Requests", Select Task and Continue.

Please ensure the user has enough rights to create/change a task or request.

Lastly, if you're using CTS+, pelase make sure you have implemented note #1003674.

I hope this helps

Best regards,

Tomas Black

[Former Member]

Thanks for the quick reply!

No, I am afraid that we are NOT using KE3I.

Is there any other transaction where you can set the order?

[tomas_black]

Hello Mr. van Veen,

what about note #1412178? Have you implemented it? (manual + automatic changes)?

Other than this, I would request you to open an OSS message so we can have your system checked for this problem.

Best regards,

Tomas Black

[Former Member]

Yes, we have implemented the note.

It did not help, so we opened an OSS message.

[ilija_knezevic]

Mr. van Veen,

Please, have you come to some solution to the problem? In my company we are facing now similar issue, and the only relevant results from SAP support portal are your case, and the note you mentioned. Could you share your solution?

Best regards,

Ilija Knezevic