Embedded Files
IDOC interface
exchanges business data with an external system. There are following scenarios for IDOC interface : 1- ALE; 2- EDI; 3- To connect other business applications by IDOC. ALE provides integration across distibuted business systems and integrated by synchronous and asynchronous communication.
Logical Systems
A logical system is a business system in which applications work together in co-ordination with one database. A client in SAP can be one logical system.
Creation of IDoc
involves the following steps :
Create Segments : WE31;
Create IDoc type : WE30;
Create Message type : WE81;
Assign IDoc type to Message type : WE82.
Successor & Predecessor of an IDoc type or Extension
A successor contains all of its predecessor's segments and more.
Transactions for IDOCS
WE31 (Development of Segments) : Enter Segment type and Definitions of different versions are listed below in table control. The Segment type is not release-specific, in contrast to the internal dictionary structure. A new release can include additional fields, which creates a new version of the segment (a new segment definition). Version creation can also be used to exchange IDocs with other SAP releases. All SAP segment types begin with 'E1', all customer-specific segment types begin with 'Z1' or a customer prefix, e.g. '/SAPCUST/'.
WE30 (Develop IDoc types) : Enter Obj Name(Idoc) and select Basic type or Extention radio button. Displays the segments in an IDoc.
WE81 (EDI Logical Message Types) : Opens with list of all available message types in the table control. Can create new messg type as well.
WE82 (Output types & Assignments to IDoc types) : Opens with list of all avaiable message types with IDoc Basic type and Extensions assigned to them.
WE64 (Process codes in Idoc Outbound and Inbound).
WE20 (Partner Profiles) : Partner profiles are defined seperately for Outbound and Inbound processing. Every partner must be defined in the general partner profiles. For outbound processing under message control (MC), additional parameters are required to be configured.
Port definition : File Port, tRFC Port, Internet Port.
Partner Profiles : Inbound, Outbound, Message Control.
Inbound Process using a direct F/M 'IDOC_INBOUND_ASYNCHRONOUS'
This function module starts inbound processing in the case of port type "tRFC". The F/M checks the ID 'EDI_MES' in authorization object B_ALE_RECV against the received message type. The IDocs are saved by the F/M IDOC_INBOUND_WRITE_TO_DB (a COMMIT for all IDocs) and then transferred directly to the application by the dispatcher module IDOC_START_INBOUND.
Useful Links
IDoc Interface / ALE
http://help.sap.com/saphelp_sm32/helpdata/en/0b/2a6702507d11d18ee90000e8366fc2/frameset.htm
Important IDoc Transaction Codes
http://www.sap-img.com/basis/important-idoc-transaction-codes.htm
A step by step approach
Configuring ALE
http://www.thespot4sap.com/articles/SAP_ALE_Configuring.asp
Change Pointer-Master Data Distribution
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
XI-JMS Adaptar
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm
Page updated
Google Sites
Report abuse