Sener and Receiver IDOC Configurations

 

Sender IDOC Configuration in SAP PI:


1. Configure sender IDOC Communication Channel (One Sender Channel is enough for one ERP)

2. Check inbound RA Configuration as below.

 

3. Check Properties for inbound RA Resource Adapter for particular ERP  


Sender IDOC Configuration ECC:

1. Create/Check Program ID in RFC Destination in R/3


2. Create /Check Partner Port Details in WE21

3. ADD Basic IDOC details for Outbound and Inbound Parameters in WE20


Receiver IDOC Configuration in SAP PI:

1. Create IDOC Receiver Communication Channel as below.

2. Below Created RFC Destination in PI must be maintained in above Communication Channel.


NOTE: Inbound RA is not required for Receiver Configuration


IDOC T CODES ECC

WE02--TO FIND THE LIST OF IDOCS

WE05--TO FIND THE LIST OF IDOCS 

WE09-- To search IDOC based on Business Content (Segment, Field Value)

WE19--To Reprocess the Existing IDOC (new IDOC number will generate)

WE20-- Partner Profiles

WE21--port Profiles

SM58-- To reprocess RFC stuck messages in QUEUE

SM59-- TO Create IDOC RFC Destination TYPE T

WE60 -- TO VIEW IDOC DOCUMENTATION

BD54-- LOGICAL SYSTEM (Mostly Created by Functional Team) 

BD64- DISTRIBUTION MODEL

BD84-- To reprocess existing IDOC (new IDOC number will not generate)

SM58-- To reprocess RFC stuck messages in QUEUE

SM59-- TO Create IDOC RFC Destination TYPE T



Reference Blog In Detail: https://blogs.sap.com/2012/12/12/how-to-create-and-configure-sender-idoc-aae-scenario-pi-73/



Comments

Post a Comment

Popular posts from this blog

PROXY COMMUNICATION BETWEEN SAP ECC AND SAP PI

Image
  PROXY COMMUNICATION BETWEEN SAP ECC AND SAP PI Prerequisites : All the proxy Configuration should be done in between ECC and PI PI Configurations : ESR objects must be created. ID objects to be created. Parameters to be maintained in ECC for outbound Proxy: Go to T-CODE SXMB_ADM in ECC  Maintain below values: Sender/Receiver Interface name - Outbound Service Interface Name Description - Name as per Understanding Interface Name - Outbound Service Interface Name Interface Name Space - Interface name space in PI   CATEGORY – RUNTIME PARAMETERS – IS_URL SUB PARAMETER- SERVICE INTERFACE NAME (OUTBOUND) CURRENT VALUE – RFC DESTINATION (TYPE G CREATED FOR SENDER SOAP                          CHANNEL)                         EXAMPLE RFC: NAMING CONVENTION Dest: //RFC_NAME Reference for Complete ...
Read more

CHECK LIST (To Integrate PI with Third Party System using SOAP Adapter)

  CHECK LIST (To Integrate PI with Third Party System) :  Import WSDL shared by Third Party System in PI.                    If WSDL is not compatible or not able to import, Create structure manually.                        Use XSLT Mapping for adding customized Soap Envelop.                        Use Java Mapping to Handle Special characters as per the WSDL Structure.  Check for Connectivity PI and Third Party System                    Whitelist End Point URL Shared by the Third Party System.             ...
Read more

TO CHECK CONNECTIVITY BETWEEN PI 7.4 AND THIRD PARY SYSTEM ONCE PORT IS OPENED (DUAL STACK)

Image
  TO CHECK CONNECTIVITY BETWEEN PI 7.4 AND THIRD PARY SYSTEM ONCE PORT IS OPENED (DUAL STACK) Note: Another Method to check at OS Level with Basis Team (This method is applicable for both Dual Stack & Single Stack) Steps: 1.       Log into the PI ABAP STACK 2.       Execute T code SE38 3.       Enter standard program name RSBDCOS0 and execute in the SE38 Screen 4.       TYPE TELNET host name Port Number and press Enter 5.       If the port is opened then we can see result as connected 6.       If the port not opened then it shows return code 1  
Read more