S.25 - Transport Pre-Import Analysis
This workflow extracts objects from a list of selected custom transports on the Source system, and identifies other transports containing common objects on the Target system. In these scenarios the Source and Target systems can both be DEV since all transports should originate in the development system. A match is done to determine the impact before importing the Source transports into the production system.
The workflow discovers transport objects that are affected by the following development scenarios:
Untested Scenario
-
Developer 1 creates a transport, in the Source system, containing one or more objects. She releases the transport but does not import them into QA for testing right away.
-
Developer 2 creates a transport, in the Source system, with new changes to some of the same objects that Developer 1 has changed. He is unaware his version also includes the changes made by Developer 1. He releases his transport, tests his changes in QA and imports his changes into PRD unknowingly copying Developer 1’s untested changes into PRD as well.
Overlay Scenario
This scenario presumes that the Untested Scenario above occurred without taking the appropriate action.
-
Developer 1 now imports her transport into QA, tests her changes and imports them into production overlaying changes made by Developer 2 (her version was created first, and therefore does not contain Developer 2’s changes).
The results from the workflow are stored in four Table datasets which are used to generate an Excel report. The Table datasets are described below.
1. Most Recent Target Objects Changed AFTER the Source Objects
This table contains the most recent Target transport changes made after the changes to the common objects in the Source transports. If you import the Source transports into the production system, you risk overwriting those changes. The next step might be to feed these results into the ‘Compare Objects’ workflow to see side-by-side how the Source objects are different from the Target objects.
| Column | Description |
|---|---|
| OBJECT_NAME | The name of an object in the selected transport. |
| OBJECT_TYPE | The converted type of the object from the selected transport. |
| ORIG_OBJECT_NAME | The original name of the transport object. |
| ORIG_OBJECT_TYPE | The original type of the transport object. |
| STATUS | The status of the selected transport. |
| SOURCE_TRANSPORT | The name of the source transport. |
| TARGET_TRANSPORT | The name of the target transport. |
| SOURCE_CHANGED_BY | The user who last changed the source transport. |
| TARGET_CHANGED_BY | The user who last changed the target transport. |
| TARGET_LAST_CHANGED_DATE | The last change date and time for the target transport. |
2. All Target Objects Changed AFTER the Source Objects
This table provides the full transport change history for each of the objects in (1). While (1) shows the most recent Target transport to change each object, this table includes all the Target transports that have changed the objects. This table may be useful when examining the history of changes to objects. It is an information source only.
| Column | Description |
|---|---|
| OBJECT_NAME | The name of an object in the selected transport. |
| OBJECT_TYPE | The converted type of the object from the selected transport. |
| ORIG_OBJECT_NAME | The original name of the transport object. |
| ORIG_OBJECT_TYPE | The original type of the transport object. |
| STATUS | The status of the selected transport. |
| SOURCE_TRANSPORT | The name of the source transport. |
| TARGET_TRANSPORT | The name of the target transport. |
| SOURCE_CHANGED_BY | The user who last changed the source transport. |
| TARGET_CHANGED_BY | The user who last changed the target transport. |
| TARGET_LAST_CHANGED_DATE | The last change date and time for the target transport. |
3. Most Recent Target Objects Changed BEFORE the Source Objects
This table contains the most recent Target transport changes made before the changes to the common objects in the Source transport. If you import these Source transports into a Target system, you risk pulling untested changes into the Target system. The next step might be to feed these results into the ‘Compare Objects’ workflow to see side-by-side how the Source objects are different from the Target objects.
| Column | Description |
|---|---|
| OBJECT_NAME | The name of an object in the selected transport. |
| OBJECT_TYPE | The converted type of the object from the selected transport. |
| ORIG_OBJECT_NAME | The original name of the transport object. |
| ORIG_OBJECT_TYPE | The original type of the transport object. |
| STATUS | The status of the selected transport. |
| SOURCE_TRANSPORT | The name of the source transport. |
| TARGET_TRANSPORT | The name of the target transport. |
| SOURCE_CHANGED_BY | The user who last changed the source transport. |
| TARGET_CHANGED_BY | The user who last changed the target transport. |
| TARGET_LAST_CHANGED_DATE | The last change date and time for the target transport. |
4. All Target Objects Changed BEFORE the Source Objects
This table provides the full transport change history for each of the objects in (3). While (3) shows the most recent Target transport changes made prior to the changes in the Source transport, this table includes all the Target transports that have changed the objects. This table may be useful when examining the history of changes to objects. It is an information source only.
| Column | Description |
|---|---|
| OBJECT_NAME | The name of an object in the selected transport. |
| OBJECT_TYPE | The converted type of the object from the selected transport. |
| ORIG_OBJECT_NAME | The original name of the transport object. |
| ORIG_OBJECT_TYPE | The original type of the transport object. |
| STATUS | The status of the selected transport. |
| SOURCE_TRANSPORT | The name of the source transport. |
| TARGET_TRANSPORT | The name of the target transport. |
| SOURCE_CHANGED_BY | The user who last changed the source transport. |
| TARGET_CHANGED_BY | The user who last changed the target transport. |
| TARGET_LAST_CHANGED_DATE | The last change date and time for the target transport. |
Creating RFC Destinations
Before you begin, you will need to create RFC Destinations for the Source and Target SAP systems.
Preparing the Workflow
To prepare the S.25 - Transport Pre-Import Analysis workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:
To specify the Source and Target systems:
-
Select the System1 (Source) parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.
-
Select the RFC Destination for the Source system, then click ‘Save’.
Repeat the above steps to link the System2 (Target) parameter to the RFC Destination for the Production system.
To specify the Source custom transports to analyze:
-
Select the Transport list parameter and choose ‘Edit Table’ from its context menu to display the Table Editor dialog.
-
Enter one or more custom transport names from the Source system, then click ‘Save’.
To specify the start date:
-
Select the Begin Date of Selection from Target parameter and choose ‘Edit Select List’ from its context menu to display the Select List Editor dialog.
-
Modify the AS4DATE line so that the ‘Low Value’ column contains the desired start date in YYYYMMDD format, then click 'Save'.
Save the workflow using the ‘Save’ toolbar button.
Running the Workflow
To run the S.25 - Transport Pre-Import Analysis workflow, click the ‘Run’ toolbar button, choose ‘Run Now’ from the diagram’s context menu, or press F5. The currently running workflow action is marked with an animated display. When the workflow execution has completed, select the Report URL dataset and choose ‘View Details’ from the context menu to display the report.