How to Transport Requests Safely in SAP

Assume that you have 3 SAP systems: DEV, QA and LIVE. Assume that you have 3 requests to transport to the LIVE system; lets call them A, B and C. There are a handful of scenarios which might occur.

Scenario 1: A, B, C are in the DEV system and are not released yet. This is the simplest scenario. Release them, import to QA simultaneously and import to LIVE simultaneously.

Scenario 2: A & B are in the DEV system and not released yet. However, C is released and is in the import queue of QA. If you import C to QA and LIVE, you will face a big risk: someone might have imported D before you import C, which contains a newer version of an ABAP program. Therefore, you need to make sure that you get the latest version from the DEV system (assuming that the programs in C are not under construction for a new requirement). Steps are:

1. Create a new workbench request in DEV and include the contents of C
2. Release A & B & WB
3. Import A & B & C & WB to QA simultaneously
4. Import A & B & C & WB to LIVE simultaneously

Scenario 3: A is in the DEV system and not released yet. B is released and is in the import queue of QA. C is released, imported to QA, and waits in the import queue of LIVE. Due to the same reasons mentioned in scenario 2, we need precautions. Steps are:

1. Create a new workbench request in DEV and include contents of B
2. Create a new transport of copies request in DEV (for LIVE) and include contents of C
3. Release A & WB & TOC
4. Import A & B & WB to QA simultaneously
5. Import A & B & C & WB & TOC to LIVE simultaneously

Advertisement