IDOC Impact Analysis

This workflow is provided with a set of transports and or changing objects from a Transport system. It assesses the impact of the transport objects and changing objects on the IDOCs retrieved from an IDOC system. The results are used to generate an Excel report identifying the IDOC functions and function groups that are impacted by the transport objects and changing objects.

Before You Begin

Before running the IDOC Impact Analysis workflow, please note the following:

If a support pack or transport has not been applied to the Transport system. It must be disassembled before it can be analyzed by the IDOC Impact Analysis workflow. This can be done in SAP by running the SAINT transaction and selecting ‘Disassemble OCS Package’ from the Utilities menu. Alternatively, the support pack or transport may be disassembled in LiveCompare using the Package Disassembler App.

The IDOC Impact Analysis workflow requires that SAP’s Where Used indexes are up to date on the Analysis system. For further details, see the Step 1 (As-Is) - Checking the Integrity of the Where Used Indexes help topic.

The Create Object Links Cache workflow in the Prerequisites templates folder should be run for the IDOC system to create a cache of object links. See the workflow’s associated help file for details.

Creating RFC Destinations

Before you begin, you will need to create RFC Destinations for the Transport and IDOC systems.

Preparing the Workflow

To prepare the IDOC Impact Analysis workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:

To specify the system from which to retrieve transports or changing objects:

  1. Select the TRANSPORT RFC Destination parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.

  2. Select the appropriate RFC Destination, then click ‘Save’.

To specify the system from which to retrieve IDOCs, and their associated functions and function groups:

  1. Select the IDOC SYSTEM RFC Destination parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.

  2. Select the appropriate RFC Destination, then click ‘Save’.

To specify the transports to analyze:

  1. Select the Transport List parameter and choose ‘Edit Table’ from its context menu to display the Table Editor dialog.

  2. Enter one or more transport names from the Transport system, or paste in a selection of transport names from an Excel spreadsheet, then click ‘Save’.

To specify the changing objects to analyze:

  1. Select the Changing Objects parameter and choose ‘Edit Table’ from its context menu to display the Table Editor dialog.

  2. Complete the table fields as follows:

Field Description
TRKORR An identifier for the changing object. This field does not need to be set to a transport name.
PGMID The Program ID of the changing object as stored in the E071 table.
OBJECT The type of the changing object, as stored in the E071 table.
OBJNAME The name of the changing object.
  1. Click ‘Save’ to save the entries.

Save the workflow using the ‘Save’ toolbar button.

Additional Configuration Steps

The following additional configuration steps may be required:

  • The workflow uses a Uses What action to find the functions, includes, structures and tables used by each IDOC function. If required, edit the action’s Types to Report parameter to specify any additional object types to find.

  • The workflow uses a Uses What action to find the functions, includes, structures and tables used by each IDOC function group. If required, edit the action’s Types to Report parameter to specify any additional object types to find.

  • The FUNC Exclusion List and FUGR Exclusion List parameters may be ignored. By default the Uses What actions in the workflow do not expand dynamic function calls.

Running the Workflow

To run the IDOC Impact 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 access the generated report.

Excel Report

The IDOC Impact Analysis workflow generates an Excel report, which includes the following spreadsheets.

Inbound-FUNC

This spreadsheet lists details of the impacted inbound IDOC functions.

Column Description
DOCTYP IDOC type.
DIRECT IDOC direction (1 = Inbound).
RCVPOR Receiver port (SAP system, EDI subsystem).
RCVPRT Partner type of receiver.
RCVPRN Partner number of receiver.
MESCOD Logical message variant.
MESFCT Logical message function.
TEST Test flag.
SNDPOR Sender port (SAP system, EDI subsystem).
SNDPRT Partner type of sender.
SNDPRN Partner number of sender.
MESTYP Message type.
IDOCTP Basic type.
CIMTYP Extension.
RCVPFC Partner function of receiver.
SNDPFC Partner function of sender.
EVCODE Inbound process code.
METHOD Choice: EDI or ALE (no longer used).
PNAME Program name.
FUNCNAME Impacted IDOC function name.
INCLUDE_NAME Include name.
FUGR_NAME Function group name.
TRKORR Associated transport name from the Transport system.
TRKORR_TYPE Type of a transport object.
TRKORR_NAME Name of the transport object.

Outbound-FUNC

This spreadsheet lists details of the impacted outbound IDOC functions.

Column Description
DOCTYP IDOC type.
DIRECT IDOC direction (2 = Outbound).
RCVPOR Receiver port (SAP system, EDI subsystem).
RCVPRT Partner type of receiver.
RCVPRN Partner number of receiver.
MESCOD Logical message variant.
MESFCT Logical message function.
TEST Test flag.
SNDPOR Sender port (SAP system, EDI subsystem).
SNDPRT Partner type of sender.
SNDPRN Partner number of sender.
MESTYP Message type.
IDOCTP Basic type.
CIMTYP Extension.
RCVPFC Partner function of receiver.
SNDPFC Partner function of sender.
EVCODE Inbound process code.
METHOD Choice: EDI or ALE (no longer used).
PNAME Program name.
FUNCNAME Impacted IDOC function name.
INCLUDE_NAME Include name.
FUGR_NAME Function group name.
TRKORR Associated transport name from the Transport system.
TRKORR_TYPE Type of a transport object.
TRKORR_NAME Name of the transport object.

Inbound-FUGR

This spreadsheet lists details of the impacted inbound IDOC function groups.

Column Description
DOCTYP IDOC type.
DIRECT IDOC direction (1 = Inbound).
RCVPOR Receiver port (SAP system, EDI subsystem).
RCVPRT Partner type of receiver.
RCVPRN Partner number of receiver.
MESCOD Logical message variant.
MESFCT Logical message function.
TEST Test flag.
SNDPOR Sender port (SAP system, EDI subsystem).
SNDPRT Partner type of sender.
SNDPRN Partner number of sender.
MESTYP Message type.
IDOCTP Basic type.
CIMTYP Extension.
RCVPFC Partner function of receiver.
SNDPFC Partner function of sender.
EVCODE Inbound process code.
METHOD Choice: EDI or ALE (no longer used).
PNAME Program name.
FUNCNAME Impacted IDOC function name.
INCLUDE_NAME Include name.
FUGR_NAME Function group name.
TRKORR Associated transport name from the Transport system.
TRKORR_TYPE Type of a transport object.
TRKORR_NAME Name of the transport object.

Outbound-FUGR

This spreadsheet lists details of the impacted outbound IDOC function groups.

Column Description
DOCTYP IDOC type.
DIRECT IDOC direction (2 = Outbound).
RCVPOR Receiver port (SAP system, EDI subsystem).
RCVPRT Partner type of receiver.
RCVPRN Partner number of receiver.
MESCOD Logical message variant.
MESFCT Logical message function.
TEST Test flag.
SNDPOR Sender port (SAP system, EDI subsystem).
SNDPRT Partner type of sender.
SNDPRN Partner number of sender.
MESTYP Message type.
IDOCTP Basic type.
CIMTYP Extension.
RCVPFC Partner function of receiver.
SNDPFC Partner function of sender.
EVCODE Inbound process code.
METHOD Choice: EDI or ALE (no longer used).
PNAME Program name.
FUNCNAME Impacted IDOC function name.
INCLUDE_NAME Include name.
FUGR_NAME Function group name.
TRKORR Associated transport name from the Transport system.
TRKORR_TYPE Type of a transport object.
TRKORR_NAME Name of the transport object.