Database Reference
In-Depth Information
2. At the same time a database copy is performed from PRD (production system) to PSQ
(production support quality system) and a new transport path is established between
PSS, PSQ, and PRD.
3. Production support transports are created in the PSS system and are imported to the
PSQ system for testing.
4. Once production support break-fix transports are tested and approved they are ompor-
ted to PRD.
5. All production support break-fix transports imported into PRD are manually rekeyed
in the DEV system on a weekly basis.
6. New release development is performed in the DEV system and the transports are re-
leased to the QAS system. Manually rekeyed transports are released to QAS as well.
7. All transports that are imported to QAS will be queued up in a virtual holding buffer
called GLQ (Go Live Queue). After integration and regression testing is successfully
completed, all the GLQ transports are imported to the PRD system as part of the next
release cutover activities. This cycle repeats for all the subsequent releases. When all
the releases are deployed in production, the PSS and PSQ systems are retired.
SAP Best Practices in Complex System Landscapes
The following best practices are recommended in the complex System Landscapes for both
the N and N+1 path:
• No transport is allowed to be deleted from the target import queues.
• If a bad transport is moved to a system, this should be followed up with a fix transport.
This will help keep transports in the correct sequence.
• Preliminary transports moved to target systems must be left in the queue for subse-
quent mass import. This will ensure that the proper transport sequence is imported.
• Manual rekeying of all transports imported into production to the new release develop-
ment system (DEV) on a weekly basis must be enforced.
• For every PSS transport there must be an equivalent manually rekeyed DEV transport.
• Use proper naming conventions for the production support and new release develop-
ment transports.
