Show TOC

Procedure documentationBasic Configuration for Connecting SAP PI and SAP ABAP Systems Locate this document in the navigation structure

 

After you have fully installed the SAP NetWeaver usage type PI and carried out basic configuration steps (see Wizard-Based Basic Configuration for SAP NetWeaver Usage Type PI), you can run this PI – ABAP connectivity wizard. The configuration wizard saves you time and manual steps.

For more information, see SAP Note 1178800.

Prerequisites

Basic connectivity configuration for connecting an SAP PI system with an SAP ABAP system requires the following:

  • You have correctly configured the SAP NetWeaver usage type PI.

  • You have set up and configured the SLD.

  • You have registered your SAP ABAP system as a technical system in the SLD.

Procedure

Automatic Configuration

To carry out the wizard-based configuration task required for your SAP system, use the configuration wizard in the SAP NetWeaver Administrator

  1. Start the configuration wizard.

    For more information, see Configuration Wizard.

  2. Under Show, choose All Configuration Tasks.

  3. Select NW: PI – AS ABAP (Basic Configuration for Idoc, Proxy): Maintain and choose Start.

  4. If required, enter the necessary data and choose Next.

    A list of the steps to be executed by the configuration wizard is displayed under Details. The steps are executed one after the other. The system makes the necessary settings and reports any configuration errors.

Mandatory Manual Configuration

Caution Caution

Since some mandatory configuration steps are not yet supported by the configuration wizard, you will have to maintain the configuration steps manually. To perform these steps manually, follow the links below:

End of the caution.
Checks

Ensure that

For more information, see

You have imported the content of software component SAP_BASIS into the Integration Repository (interfaces, mappings, and so on).

Importing Process Integration Content

The connection between the Integration Server and the SLD has been established by calling transaction SLDCHECK. The system displays a log that lists the current configuration data, the function test results, errors, and notes for checking.