create and Sender Idoc

This document shows the steps required to configurate the Idoc sending from ECC to PI using the new PI 7.3 feature Idoc Advanced Adapter Engine (AAE).

a)          Configurations in PI side - NWA.

Open the NWA page (http://<host>:<port>/nwa)

1) Click on:     Configuration > Infrastructure > Application Resources

Filter by key name in column Resource Name: ‘inboundRA’:

Here we have to select: Resource Name: “inboundRA” – Resource Type: “Resource Adapter” and click on Properties. Next, configure these parameters:

• GatewayService: set in accordance to PI configuration (see trx code: SMGW).
• GatewayServer: set in accordance to PI configuration (see trx code: SMGW).
• MaxReaderThreadCount: 5
• ProgramID: “XI_IDOC_DEFAULT_PID” where “PID” refers to PI system ID. Set in accordance to local configuration. This Program ID name will be used in ECC system when we create RFC dest. type “T”.
• DestinationName: XI_IDOC_DEFAULT_DESTINATION
• Local: false
• BindingKey: PI_AAE_IDOC

Remaining values will be kept as they were.

2) Again from NWA, create a destination pointing to ECC using the name XI_IDOC_DEFAULT_DESTINATION

Set the Connection Parameters and Logon Data for ECC system where Idocs will be sent. Do a connection test.

3) We also have to create another Destination equals to the last one (XI_IDOC_DEFAULT_DESTINATION) but in this case we will add the R3 System ID in the end of the name. For example: XI_IDOC_DEFAULT_DESTINATION_ECC

Note: This destination will be used to transport the Idoc metadata.

b)          Configurations in Sender System – R3 side.

1)          Create RFC Destination Type T: (Client Independent. Use Customizing client)

1. Go to trx. code SM59
2. Create a new RFC Dest. Use a name that refers to PI AAE, for example: “PIDCLNT001_AAE”.
3. Select radio button “Registered Server Program”
4. In Program ID enter the same Program ID name already configurated in resource adapter inboundRA from NWA.
5. Enter the “Gateway Host” y “Gateway Service” from PI Server.
6. In “MDP Unicode” tab, actívate the radio button Unicode.
7. Make a connection test to check connectivity.

2)          Create Port: (Client Dependent. Use the client where Idocs will be sent)

1. Go to trx. code WE21.
2. Display “Ports” and click on “Transactional RFC”
3. Click on “Create”
4. Specify a name and a description.
5. In RFC destination specify the RFC destination name created in the previous step.

3)          Create Logical System (Client Independent. Use Customizing client)

1. Enter trx. code BD54
2. Specify a name like <SID>CLNT<Client.Nr> for example “PIDCLNT001” where PID is the PI System ID and “001” it’s client number.
3. Save.

4)          Create Partner Profile (Client Dependent. Use the client where Idocs will be sent)

1. Enter trx. code: WE20
2. Select Partner Type LS
3. Click on button “Create”
4. Specify Logical System Name created in previous step as “Partner No.”
5. Create an Outbound Parameter.
   1. Select the desired “Message Type”
   2. Select the Receiver Port (Created on Step #2)
   3. Activate the option “Transfer IDoc Immediately”
   4. Configurate credentials in tab “Post Processing Permitted Agent”

c)          Scenario configuration in Integration Directory.

Create and configurate an Integrated Configuration (ICO):

i)          Create a Communication Channel sender type:  IDOC_AAE.

ii)          Create an ICO, choosing Sender System and Service Ifz. name (Idoc name)

iii)          Select the Communication Channel previously created.

iv)          Finish the configuration entering: Receiver System, Receiver Interfaces and destination Communication Channel in their respective tabs. Save & Activate.