Hi,
Yes, I see now that not all objects need to be locked in TR in order to release it on our 702 system - that should take care of including deleted objects in a new request. Weird, because I distinctly remember being unable to release the requests until I either threw out the deleted objects (bad, bad, bad!) from TR or recreated TADIRs of deleted objects and locked the whole object list when doing "re-transports" using "include objects"... Has there really been some change in TMS in this regard..?
EDIT IN: ok, help on Releasing requests explains:
Prerequisites
- If it is a Customizing request or a Workbench request, all the tasks in it must have been released.
- All lockable objects must be locked in this request.
Exceptions: You have administration authorization or it is a transport of copies. In these cases, the SAP System informs you that not all objects could be locked when you release the request. However, you are allowed to continue with the release.
I can't recall where the "all TRs accumulated in Q should go to P" came from, but the less "fiddling" with TRs and coordination effort the better - especially if the responsibilities are split: developers only have authority to release on D, and from Q import queue onward the TRs are responsibility of Basis/TR admin.
The copy TRs do write versions (don't know yet, if that can be switched off somewhere). However, I'd release the tasks after releasing copy request for the iteration and would use only newly created (unreleased) tasks to build copy request for the next iteration. That way I'd have only one redundant version with no changes per object - when the "normal" TR is released, and the rest of versions are legit and actually desirable.
The simplest TR procedure that works for you, the team and the whole organization is the best, I think... I hope that copy requests would be the best for our two D and Q systems (maintenance and next release separate, with merging maintenance TRs into next release). It would also allow to reach your goal, wouldn't it?
cheers
Jānis
Message was edited by: Jānis B