Importing Releases: Best Practices

Problem

When importing updates for the PPM Process Package (PPP) via SAP CTS (e.g. STMS), it is often unclear whether multiple versions can be imported in a single import queue, how to deal with migration steps between versions, and what to consider when working with separate frontend and backend systems.

Environment

SAP CTS, STMS

Solution

The appropriate strategy depends on both the system landscape and the specific content of the releases. The following distinctions apply:

1. Combined Frontend and Backend System

If your landscape includes a combined system where both the SAP Gateway (frontend) and the SAP backend (S/4HANA, PPM 6.1, etc.) reside in the same instance:

  • You may import multiple PPP versions in one import queue, only if no migration steps are required between those versions.

  • Example: Importing 20XX.1, 20XX.2, and 20XX.3 together is acceptable if none of these releases introduce required configuration or migration steps.

  • If any release includes mandatory manual or guided migration steps, the following procedure must be followed:

    1. Import up to (and including) the release that introduces the migration.
    2. Complete the migration step(s) fully.
    3. Only then import the next release(s).

Always consult the release notes to verify whether any of the releases introduce required steps.

2. Separate Frontend and Backend Systems

In cases where the frontend (SAP Gateway) and backend are implemented on separate systems:

  • Ensure that:

    • Frontend transports are deployed only on the Gateway system.
    • Backend transports are deployed only on the backend system.
    • Each system’s queue contains only the transports relevant to that layer and version.

  • Sequence the imports carefully to avoid inconsistencies or dependency errors.

3. Transporting to Quality Assurance (QAS) and Production (PRD)

After completing updates and any required migration activities in the development system (DEV):

  • Transport only the tested and migrated state to QAS and PRD.

  • Even if multiple versions were involved during testing in DEV, QAS and PRD must receive a clean, consolidated version that:

    • Reflects the final backend and customizing state
    • Includes any adjusted frontend components
    • Contains no partial updates or leftover transport fragments

Avoid splitting releases across transports or importing versions that were only partially configured or migrated.

Additional Recommendations

  • Never import releases with required migration steps together with other releases in one queue.
  • Avoid mixing frontend and backend transports across system types.
  • Migration steps may involve BRF+ configurations, customizing, or application data changes that must not be skipped.

Keywords

PPM Process Package, STMS, SAP CTS, Migration Steps, Multiple Versions, Transport Strategy, System Landscape, Combined System, Frontend, Backend, QAS, PRD