SAP Community Network Wiki - ABAP Development - ALE IDOCS

Page 1 of 1

Log In

Register

About Us

How to Contribute
Welcome

SDN Community
Home Forums Wiki Blogs

BPX Community
Articles eLearning

Business Analytics
Downloads

University Alliances
Career Center

SAP EcoHub
Events InnoCentive

Code Exchange

ALE IDOCS
Added by jeevitha, last edited by jeevitha on Jul 14, 2008

BEGINNER'S GUIDE TO ALE AND IDOCS - A STEP-BY-STEP APPROACH

This article will help you understand the basics of ALE and IDocs via a simple do-it-yourself example. We will create a custom IDoc in one SAP sys another SAP system. Business data will be picked up from custom data dictionary tables. ALE - Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it master data as well as for exchanging transactional data. The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. transaction WE60. Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of

fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. A

an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the datab

the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to Now, let us understand the ALE Configuration by means of an example scenario below: The Scenario

Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE R/3 systems or we can simulate this on two clients of the same SAP R/3 system. Create three tables as shown below. Creating Custom IDoc type and Message type All the objects created should be present on both source as well as target system(s). 1. Create segments - Transaction WE31 Create a segment ZRZSEG1 Add all fields of table ZCUSTOMERS to it Save the segment Release it using the menu path Edit -> Set Release Similarly create two more segments given below Seg. ZRZSEG2 - to hold all fields of table ZSOHEADERS Seg. ZRZSEG3 - to hold all fields of table ZSOITEMS 2. Create Basic IDoc type - Transaction WE30 Create a Basic type ZRZORDER Add the created segments in the hierarchy shown Maintain attributes for each of the segments Save the object and go back Release the object using the menu path Edit -> Set Release

http://wiki.sdn.sap.com/wiki/display/ABAP/ALE+IDOCS

8-11-2011