Wow - thanks Tom!
-----------------------------
3)
In terms of troubleshooting, did you copy SAP standard transaction type? SMMJ into ZMMJ
yes.
If yes, then if you test the SAP standard transaction type SMMJ, do you have the same problem?
- we only encounter the situation on our production system, which only uses ZMMJ
If no, then you should compare SMMJ and ZMMJ customizing because the chances are that something went wrong during the copy process which causes a difference between SMMJ and ZMMJ
- I will doublecheck those settings
If you have the problem in both SMMJ and ZMMJ, the chances are higher that there is a bug and a SAP note correction is needed. If you would create a customer message, SAP will definitely want to check the standard transaction type (common practice) so you could already do that yourself.
- since we only encounter the issue in our production environment with ZMMJ I cannot check weather it also occurs with SMMJ
I would check out "Make settings for transaction types" in SPRO and then Assign Actions and compare SMMJ and ZMMJ. The action COPY_ALL is responsible for the TOC's in combination with status E0004. Check the "Define Execution Time of Actions" because there should be an entry for COPY_ALL to be executed after the checks.
- I will doublecheck those settings
1978427 - ChaRM: Transport of copies is missing in transport of copies popup
--> cannot be implemented
2067107 - ChaRM: invalid originator ID for transport request assigned in task list directly
--> can be implemented - currently checking with colleagues
-----------------------------
Checking
/TMWFLOW/TRORDHC
/TMWFLOW/TRORDCP
already helped me getting a better look at the situation and I am still following your steps, I just wanted to let you know: Thank you for all the tips so far!!! - so I will get back to you as soon as I have checked all your recommendations.
What I noticed is, that the issue always occurs when the Change Document somehow reaches a timeout. This happens when a large (e.g. Customizing) Transport Request with a high amount of dependencies is included in the Change Document.
It happens when we try to set Status "To Be Tested" as well as when we create the Transport of Copies via Transport Management Assignment Block (without status change).
In the background the ToC is created in every case - in SM66 you can see that there are a lot of reads on table SCTS_TRACK. Eventually the action aborts and no link between the created Transport of Copies and the Document (and Transport) it originated from is written.
My Change Document ID: xxx41
Original Transport ID: DEVKxxx604
missing ToC: DEVKxxx279
In table /TMWFLOW/TRORDHC (Transport Requests) I can only find the following entry with Originator_Key xxx41 and original Transport DEVKxxx604:
TRORDER_NUMBER: DEVKxxx604
ORIGINATOR_KEY xxx41
TRORDER_COPY DEVKxxx279
if I browse for orignator_key xxx41 only I get the original Transport (see above) with DEVKxxx279 as TRORDER_COPY and additionally 4 further results
DEVKxx746
DEVKxx877
DEVKxx228
DEVKxx232
which are marked with TRFUNCTION "T" (=Transport of Copies) - I cannot find this kind of entry for DEVKxx279 ...
Table /TMWFLOW/TRORDCP Change & Transport System: Copies of Requests
however only brings up 4 Transport of Copies for TRORDER_NUMBER DEVKxxx604 (also here DEVKxxx279 is not part of this list) flagging DEVKxxx232 with "IS_LATEST"