Show TOC

Example documentationExample:

 

Example: System Landscape

Three entries are made for this landscape in the Customizing settings for the product transport in the source system:

  1. Test system with status 2 – Active for Testing

  2. Test system with status 3 – Released

  3. Production system with status 3 – Released

This means that you can transport product versions with the status 2 and 3 to the test system, but you can only transport a released product version to the production system.

Example: Ability to be Transported According to Status

You can only transport product versions if they do not yet exist in the target system or do not exist in this system with the current status.

Procedure for the example system landscape:

  1. The product version is returned to the status 2 so that the transport can be performed.

  2. In the next step, the product version is transported to the test system, where it is also assigned the status 2.

  3. Following the corresponding tests in the test system, it was decided that the product version can be used in its current status. It is released in the test system.

  4. The product version is also released in the source system. This means it is no longer necessary to perform another transport to the test system for the status change.

  5. A new version 2 is created in the source system because the specialist requirements for the product have changed.

  6. A version 2 is also created in the target system. This is however performed manually, meaning that a transport from the source system is not performed.

  7. Version 2 is released in the source system and is to be transported. This causes a conflict, since the status of product version 2 in the target system must first be changed to Obsolete or Released. Product version 2 can then be transported from the source system and creates a new version 3 in the target system.

  8. Version 2 is then set to Obsolete in the target system.

  9. The transport is repeated in the source system. A version 3 is created in the target system whose basic version 2 comes from the source system.

Example: Transport Sequence
Product Module and Reference Product

A utilities product Energy Sales Product is defined, which is based on the reference product Energy Basis. The reference product Energy Basis also contains Module Bank Data from the product module in addition to its own attributes.

Energy Sales Product cannot be transported until all of the elements used have first been transported. In this example, the transport sequence is as follows:

  1. Product module Module Bank Data

  2. Reference product Energy Basis

  3. Utilities product Energy Sales Product

Utilities Package

The utilities package CombiPackage consists of the components Energy Sales Product and Gas Sales Product. CombiPackage cannot be transported until all product components used including their elements have first been transported. However, since these were not assigned using an explicit version, the system only checks their general availability and does not perform a specific version check.

In this example, the transport sequence is as follows:

  1. Utilities product Energy Sales Product in the sequence above including the reference product and product module.

  2. Utilities product Gas Sales Product

  3. Utilities package CombiPackage