Inbound IDOC_AAE configuration in PI 7.31 single stack

1. Determining values for GatewayHost and GatewayService 

  • Log in to the SLD and choose Administration -> Settings tab Parameters and All from the drop-down menu:

SLD Gateway PI/PO 7.31 single stack

2. Creation of RFC connection to a SAP system, from which Idocs will be sent:

  • After logging in to SAP NetWeaver Administrator (NWA) go to Configuration -> Infrastructure -> Destinations

SAP NWA Destinations

 

  • Connection parameters:

Hosting System: Local Java System PID
Destination Name: XI_IDOC_DEFAULT_DESTINATION
Destination Type: RFC

SAP NWA Destinations step 1

 

In next steps please provide connection parameters to the SAP system and logon data:

SAP NWA Destinations step 2

 

To make sure that the connection works properly you may use an option Ping Destination. An expected test result is Successfully connected to system <PID> as user <user>

Ping destination

3. Creating a JCo connection (Java Connector)

  • In SAP NetWeaver Administrator (NWA) go to Configuration -> Infrastructure -> Jco RFC Provider

JCo RFC Provider

 

  • Use an option Create, parameters to be provided:

Program ID: XI_IDOC_DEFAULT_PID
Gateway Host: as in step 1
Gateway Service: as in step 1

JCo step 1

 

  • In the next step enter the connection name from step 2, in our case XI_IDOC_DEFAULT_DESTINATION

JCo step 2

 

After saving, the newly created connection needs to be started (option Start), expected message is JCo servers started

4. Adding parameters for Resource Adapter inboundRA

  • In SAP NetWeaver Administrator (NWA) go to Configuration -> Infrastructure -> Application Resources and filter Resource List using *inboundRA*

Resource Adapter step 1

  • In Properties tab please fill parameters (or make sure that they are already entered):

GatewayServer – as in step 1.
ProgramID – as in step 3. – XI_IDOC_DEFAULT_PID
MaxReaderThreadCount – value between 5 and 10
DestinationName – as in step 2. – XI_IDOC_DEFAULT_DESTINATION
GatewayService – as in step 1. – sapgw01
Local – true
BindingKey – PI_AAE_IDOC

Resource Adapter step 2

  • After saving the application needs to be started: More Actions -> Start Applications and choose com.sap.aii.adapter.idoc.sapjra.inboundRA from the list:

Resource Adapter step 3

5. Creating a RFC destination in SAP system that will send Idocs to PI

  • In transaction SM59 create a new connection of type (T) TCP/IP Connection using parameters:

Activation Type: Registered Server Program
Program ID: as in step 3. – XI_IDOC_DEFAULT_PID
Gateway Host: as in step 1.
Gateway Service: as in step 1. – sapgw01

SM59 TCP/IP Connection

 

SM59 TCP/IP Connection

 

  • After connection test an expected message is:

SM59 RFC connection test

 

6. Creating sender communication channel in PI

  • In contrast with Idoc configuration for Integration Engine (ABAP) a communication channel of type Sender is required, it will be used in Integrated Configuration. 
  • Parameter RFC Server Parameters should be set to Default, in Ack Destination please enter a connection from step 2. – XI_IDOC_DEFAULT_DESTINATION

Idoc_AAE sender channel

 

After completing all steps above PI system is ready for configuration of inbound Idoc scenarios.

Materials available on help.sap.com and scn.sap.com have been used when creating this guide.

2 replies
  1. Mirta
    Mirta says:

    Link exchange is nothing else but it is simply
    placing the other person’s webpage link on your page at suitable place and other person will also do similar in favor of you.

Comments are closed.