This Blog describes about IDOC Configuration in PI.
ECC to PI:
1) Create RFC Destination in ECC ...SM59. Provide XI IP,Login, Password details.
2) Create a port in WE21
3) Create Partner Profile in WE20...type LS...Partner profile name should be same as the ECC logical system name. In Outbound parameters, assign the Idoc message
types and the receiver port.
4) Testing : WE19
a) Sender port : SAPXXX (XXX is ECC host name)
b) Partner no: ECC partner profile (CE1CLNT100)
c) Partner type : LS
d) Receiver Port :SAPXXX (XXX is XI host name)
e) Partner no: receiver logical system (CX1CLNT100)
f) Partner type : LS
Message type : Idoc message type
Click on standard outbound processing tab.
A popup will show in green with partner profile details.
First - We need to maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>
eg. SAPID1 [Optional Step. Not mandatory].
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
GO TO SLD:
- Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
- Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before
Communication channel settings:
No Sender Commnication Channel required for IDOC.
But we need to do some configurations in ECC side. ( Three steps Mandatory )
1. RFC destination: SM59
2. Port: we21
3. Partner profile: we20
1. Create RFC Destination to XI system using:-SM59 with PI system host , user id, pwd etc..
2. Create a port for PI system from tcode we21 and give the RFC destination created in step1.
3. Create Partner profiles: Go to transaction / tcode we20 . Under the Logical system of XI we need to define the idoc inbound and outboud types.
- If the Idoc is ECC - PI it is to be configured on outbound parameters
- If the Idoc is PI - ECC it is to be configured on the inbound parameters.
Sender Idoc Testing:
There is a testing tool for sender idoc its we19 transaction:- We can give the parameters here to run it.
Receiver Communication Channel configured as mentioned below: ( Four Steps Mandatory )
1. Receiver Communcation channel
2. RFC destination-SM59
3. Port- IDX1
4. IDoc Meta data import- IDX2
We can see the RFC destination created using SM59 . This RFC destination creates the connection from PI to ECC.
Port has to be created in IDX1:- Include the RFC-destination created on step1.
All the idoc Metadata should be defined in IDX2
IDOC Verifying and IDOC Status:
WE02 and We09: We can verify the IDoc status.
We09 has searching criteria..like trex in XI.
There are 2 types of IDOC status. One of outbox and another for inbox.
Outbox means going out of SAP system and inbox means coming into SAP system.
For Outbox: 4 status
For Inbox:
For Error:
Please go through and provide valuable feedback. Thanks













