Upload
hema
View
7
Download
0
Embed Size (px)
DESCRIPTION
SAP XI/PI IDOC Basics
Citation preview
XI30 handling of IDOCs
basicsDennis Kropp,SAP SI AG
SAP AG 2003, Title of Presentation, Speaker Name / *
IDOC adapter prerequisites/notes this documentation provides information about receiving IDOCs (sender channel) and creating IDOC receiver channels to send IDOCs to SAP R/3 systems receiver means that an IDOC is send TO a SAP R/3 system sender means IDOCs are received FROM a SAP R/3 system Prerequisites for using the IDOC adapter are maintaining the R/3 system that sends/receives the IDOCs in SLD and configure sending/receiving of IDOCs in R/3 system
Note that the logical system name for your business system that you define in SLD must be the same name like in the corresponding SAP system (see TA: scc4 to check ls name )
you cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE AF but is an built in adapter
so XI automatically receives IDOCs via XI pipeline URL
To configure a complete roundtrip you could define a receiver channel where the message is send to
Routing rules and sender has to be specified as for any other channel in the directory object model
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : Header of IDOC in SAP system header of IDOC to be send check within TA: we19 for existing IDOCS
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : Header of Inbound IDOC in XI
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : steps in XI IS system to receive IDOCS define a R/3 RFC destination within TA: sm59 to SAP sender system this connection refers to the SAP sender system that sends the IDOCs you need a user with RFC authorization in this system to log on
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : steps in XI IS system to receive IDOCS define a tRFC port within TA: idx1 on your IS system this port refers to the created RFC connection the port must have the same name like the sender port in IDOC control header is used to get the meta data for the incoming IDOC; needed to convert the IDOC format into XI message format
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : Import IDOC structure into IB repository if a mapping between IDOC structures is needed, first import IDOC structures into repository therefore etc/services, on your J2EE host, must contain entries for sapgw and sapms ports of the system you are importing from
right click Imported Objects under your SWCV in IB repository
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : Imported IDOC structure
SAP AG 2003, Title of Presentation, Speaker Name / *
Example : send IDOC to SAP system
same preparations as for sender channel (receive IDOCs) are needed
An IDOC with type ORDERS05 is send from one SAP system to another
Now you can do any mapping with this structureIDOC adapter uses RFC Destination to send IDOCDefine RFC destination (type R/3 connection) to target SAP system as described in previous slidesPort value is needed to retrieve metadata for creating outbound IDOCMust be maintained in TA:idx1 on XI-IS and refers to a RFC destination that points to the system where metadata for this message type is available