How to perform PODS check in Web GUI

Steps

Click on Safety Checks under Utilities from the dashboard or request screen and select PODS check.

1. If you are performing the check from the dashboard, the Run PODS check dialog is displayed.

   1. Select the Request mode.

   2. Select a request and migration status from the dropdown lists.

   3. Click the Run button. The PODS check results are displayed (see illustration below).

2. If you are performing the check from the request screen, the request and migration status are pre-selected in the Run PODS check dialog and the check results are displayed immediately (see illustration below).

Notes:

• From Web GUI v8.3.0, transports of copies (TOCs) can be ignored in the check via override and you can also choose to ignore quarantined transports (selected by default).

• Ignoring TOCs from the analysis can result in false positives.

• If you choose not to ignore quarantined transports, any quarantined transports analysed in the results will appear stricken off.

The results also display counts per overall result. You can select any combination of filters to help you focus on a particular result. For example, the illustration below shows the filtered results when Queued and In selection are selected.

Steps

You can check transports via the Safety checks utility or Migration workbench from the dashboard.

1. Click on Safety Checks under Utilities from the dashboard and select PODS check. The Run PODS check dialog is displayed.

   1. Select the Transports mode.

   2. In the Transports field, click on Add from request button to add transports from a request or select the transport(s) from the pulldown list.

   3. Select a target group.

   4. Click on Run button. The PODS check results are displayed (see illustration above).

2. Select Migration workbench from the dashboard. The 'Migration workbench' screen is displayed.

   1. Select a Target group from the pulldown list.

   2. Populate the workbench with the relevant transports.

   3. Click the Safety checks button and select PODS check.

Notes:

• From Web GUI v8.3.0, transports of copies (TOCs) can be ignored in the check via override and you can also choose to ignore quarantined transports (selected by default).

• Ignoring TOCs from the analysis can result in false positives.

• If you choose not to ignore quarantined transports, any quarantined transports analysed in the results will appear stricken off.

Source

The source system of a transport of the enquired request.

Dependency

A dependency is an object that is referenced by an object contained in a transport of the enquired request; both objects come from the same source system.
The same dependency may appear multiple times if the transports originated from different source systems.

Note: From Web GUI v8.2.4, you would be able to filter the PODS check result by a single object.

Click the dependency object to drill-down to Version Vault (Rev-Trac Insights app ) so you can quickly view the object source code. This is applicable only to licensed Rev-Trac Insights users. Refer to Object repository apps for details on how to use the app.

Type

The type of object, i.e. program, function module, structure, screen, etc.

Minimum required version

The minimum required version of the dependency, which exists in the source system, to be analysed against the target system.
The information in this column is taken from SAP Version Management of the dependency.
The numbers, other than 0, beside the transport number, indicate versions released in chronological order; 0 is the current active version and 1 is the oldest/original released version. Please see the example below.

At the start of the result, this value is pre-selected and is determined by matching the timestamps of the transports with those of the dependency versions.
If required, you can select a different version from the dropdown list and the tool will immediately recalculate the result.

View requests containing the transport

Click on the line item icon beside the transport in the Minimum required version column to list the requests containing the transport.

Overall result

The following results are possible. You can use tooltips to view the explanation of each result.

• Found

  • The minimum required version is found in the target system. However there are two possible findings:

    • The minimum required version is identical to the current active version in the target system.

    • The minimum required version is found in the dependency's history and the current active version matches a more recent version in the source system.

• Missing

  • The minimum required version is missing from the target system.

• Overwritten

  • The minimum required version is found in the dependency's history in the target system, however the current active version does not match any version in the source system.

• Overtaken

  • The minimum required version is not found in the target system.

  • The current active version of the dependency in the target system matches a version in the source system, which is newer than the chosen minimum required version.

• Queued

  • The minimum required version is not found in the target system, however it is currently in the Rev-Trac migration queue en route to the target system.

• In selection

  • The minimum required version is not found in the target system, however it is included in the transports attached to the request being analysed.

• Not applicable

  • The system is not configured as a target system for the transport. This may occur when source-specific migration applies.

• Unknown

  • The result cannot be computed due to unexpected errors with one or more target systems, which usually rarely occurs.

Target systems

A separate column will appear for each applicable target system.
When the result is overwritten or overtaken, you can click here to quickly view the object source code difference between the two systems in Match Box (Rev-Trac Insight app). This is applicable only to licensed Rev-Trac Insights users. Refer to Match Box (from v8.2.1 onwards) for details on how to use the app.