Interesting arrangement! I'm not sure how they're getting transports into the PRD queue with that arrangement, except perhaps the customer's internal security requirements mandate that there is no automatic forwarding of approved transports; instead, the transport administrator must have to manually forward the transports to the PRD queue after approval.
So, if I'm reading the diagram correctly, there are three transport routes from ZT01 to ZRQ1: the SAP standard route, the customer standard route, and then a 2nd customer route (not sure why they need two customer routes, but ok). But then we have a back-route from ZRQ1 to ZT01, and furthermore a back-route from ZRP1 to ZRQ1. What this tells me is that one of two situations is happening at this customer:
- They are developing directly in PRD and want a way to back-port those developments to QAS and DEV; or
- There are multiple development tracks (in different transport domains) pointing to the same PRD system, perhaps one as a maintenance track and the other as a project track, and they are ensuring that developments from one track find their way as inputs to the other track. Indeed, this might explain why there is no direct route from/through this QAS system to PRD; perhaps the other, unseen track is the primary development track, and what we're seeing here is a secondary track for emergency maintenance during a long project.
There you have it. Not standard, but a possible explanation for what's going on.
Cheers,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.