Configuring an SAP system to send and receive IDocs

To send or receive IDoc from SAP ECC, you must set up HCL DevOps Test Integrations and APIs (Test Integrations and APIs) or HCL DevOps Test Virtualization (Test Virtualization) as a registered TCP/IP program.

About this task

The following procedure is only an example of how the configuration is typically handled. For complete assistance with the setup, contact your SAP system administrator.

Procedure

  1. Log into the SAP system.
  2. Define a remote function call (RFC) for Test Integrations and APIs.
    1. Set start transaction for SM59.
      1. Right-click on the menu area.
      2. Click Set Start transaction.
      3. Enter the transaction code in the pop-up and click the tick mark.
    2. Enter a name for the RFC destination. For example, RITESTER.
    3. Enter the program ID. For example, RIT. The value is used in the physical configuration of the resource.
      Defining an RFC Destination for RIT
    4. Click Connection Test to verify that HCL DevOps Test Integrations and APIs (Test Integrations and APIs) or HCL DevOps Test Virtualization (Test Virtualization) is connected. For the connection to work, however, a test with an active Subscribe step or a virtual service must be running.
  3. Define an RFC Port for the IDoc processing.
    1. Set start transaction for WE21.
    2. Enter a name for the RFC port. For example, RITPORT.
    3. Configure RITPORT to point to the RFC Destination created in Step 2 (RITESTER in the example).
      Configuring an RFC Port
  4. Define a logical system for Test Integrations and APIs.
    1. Set start transaction for BD54.
    2. Enter a name for the logical system. For example, RITSYS.
      Defining a logical system

      Ignore any warning message that appears.

  5. Create a logical system partner profile.
    1. Set start transaction for WE20.
    2. Create a partner profile and configure it to use the logical system defined in Step 4; that is, enter RITSYS in the Partner No field.
      Partner profile
    3. Configure the inbound and outbound IDoc types as appropriate.