ALE IDOCS

[Former Member]

Hi Experts,

I am new to ALE IDOC's can any one post me the material towards the basic concepts ( Begning with ) ALE IDOC's

send me the material not the LINKS if the materials is USE I assure to REWARD the Points.

Thanks,

[Former Member]

goto Google and find with "ALE development". you will find .DOC material for ur help.

[Former Member]

Data is exchanged between applications and remains consistent in all applications.

Company-wide applications such as accounting, human resource management and sales planning may be carried out in the company’s headquarters, whereas production and materials management may be carried out in decentralized plants.

Application systems are loosely coupled in an ALE integrated system. Data is exchanged asynchronously, whereby the data arrives in the receiver system, even if the receiver system cannot be connected to at the time the data is sent. ALE uses synchronous communication for rading data only

IDOC : intermediate documents which can acts as a data container to send data from one system to another remote system

Remote Function Call:

RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.

RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.

RFCs manage the communication process, parameter transfer and error handling.

http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

Refer this

http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html

http://www.saptechnical.com/InterviewQ/interviewQ.htm

http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm

[Former Member]

IDOC = Intermediate Document

IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.

When we execute an outbound ALE or EDI Process, an IDOC is created

In an inbound ALE or EDI process, an IDOC serves as input to create an application document.

In the SAP System, IDOCs are stored in database.

Every IDOC has an unique number(within a client).

IDOCs are independent of the sending and receiving systems.(SAP-to-SAP as well as Non-SAP)

IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT. In case of any conflict in data size, it adopts one with greater length

IDOCs are independent of the direction of data exchange e.g. ORDERS01 : Purchasing module : Inbound and Outbound

IDOCs can be viewed in a text editor. Data is stored in character format instead of binary format.

An IDOC is an instance of an IDOC Type

At run time the following events occur

A unique IDOC no. is allocated by SAP

One control record is attached to the IDOC

Segments translate into data records

Status records are attached

Syntax rules are checked.

Each IDOC has 3 parts

Control Record

Data Record

Status Record

We02 or We05 is used to

display an idoc

Control Record

All control record data is stored in EDIDC table. The key to this table is the IDOC Number

It contains information like IDOC number,the direction(inbound/outbound), sender, recipient information, channel it is using, which port it is using etc.

Direction ‘1’ indicates outbound, ‘2’ indicates inbound.

Data Record

Data record contains application data like employee header info, weekly details, client details etc

All data record data is stored in EDID2 to EDID4 tables and EDIDD is a structure where you can see its components.

It contains data like the idoc number, name and number of the segment in the idoc, the hierarchy and the data

The actual data is stored as a string in a field called SDATA, which is a 1000 char long field.

Status Record

Status record are attached to an IDOC at every milestone or when it encounter errors.

All status record data is stored in EDIDS table.

Statuses 1-42 for outbound, 50-75 for inbound

Basic IDOC Type (we30)

Basic IDOC Type defines the structure and format of the business document that is to be exchanged.

IDOC Type has a

specific name

list of permitted segments

hierarchy of segments

mandatory/optional segments

minimum/maximum range of each segment.

IDOC Components

Segments

Segment defines the format and structure of a data record. Segments are reusable components.

For each segment SAP creates

Segment Type (version independent)

Segment Definition (version dependent)

Segment Documentation

The last 3 characters is the version of the segment

Definitions keep changing as per the version but the segment type remains the same

[Former Member]

hi there...

follow the following pdfs for ale and idoc related queries

www.erphome.net/pdf/tech/J07.pdf

help.sap.com/printdocu/core/Print46c/en/data/pdf/SDEDI/SDEDI.pdf

the second book wil be very helpful provided u r just a beginner with idocs.

<REMOVED BY MODERATOR> or get bak for further info.

Edited by: Alvaro Tejada Galindo on Apr 7, 2008 5:26 PM

[Former Member]

Hi,

I have some material on ALE IDOC, hope it will help you,

ALE Idoc is method to migrate data between two SAP systems.whereas EDI used to transfer data between one SAP and other non-SAP systems and vice versa.

IDoc (for intermediate document) is a standard data structure for data migration between two SAP application programs.it carries Business Information.

Business Data is of three types-

1. Control Data - i.e. configuration data (client, company code etc.)

2. Master Data - i.e. Application level data (Material/vendor master etc.)

3. Transactional Data - i.e. also Application level data (Like invoice, billing etc)

For control data IDocs are created once, and after being transferred it can not be changed,

whereas for transactional and master data many IDOCs can be created.

Structure of IDOC-

Message Type- Can contains several segments.

Segment Type- Actual contents of the data contained into the SEGMENT.Segments are the section of data.Segments containns the fields, it means ields are the basic building block of any segment.segments are identified by the Sequence no. of the segment i.e. IDOCSYN.

EDIDD,EDIDC,EDID4 are the tables for IDOC data.

Imp. Terms -

Logical System - Logical system is an appropriate name to identify the sender and receiver.it should be

uniquely binded with a particular client.

CDM (Customer distribution model) - Is responsible for finding out the axact recepient for the IDOC.

Partner Profile - Recipient system should know what type of message it is going to receive from which system,for this partner profile has to be created,every information related to PORT, RFC, LS, IDOC Type should be maintained in Partner Profile.

RFC Destination - it will be the other SAP system.

Imp. Tcodes-

WE31 - Creating Segment

WE30 - Creating IDOC Type

WE81 - Creating Message Type

WE82 - Assigning Message type to IDOC

BD64 - Creating CDM

WE20 - Creating Partner Profile

BD82 - Generating Partner Profile Automatically

WE21 - Assign Port to RFC Destination

BD54/SALE - Creating logical System and assign LS to appropriate client.

SM59 - Creating RFC Destination

WE21 - Creating Port and assigning port to RFC destination.

Steps -

1. Create the Logical System.

2. Assign LS to Client.

3. Create RFC Destination.

4. Create PORT.

5. Bind the PORT with RFC dest. to create communication channel.

6. Create Partner Profile.

7. Create CDM.

8. Assign partner profile to CDM.

9. distributing the CDM.

To Create Message type-

10. Create Segment. (WE31)

11. Create IDOC.(WE30)

12. create Message type (WE81)

13. Assign Message type to Idoc Type.

14. Assign the IDOC type to partner profile.

[Former Member]

Hi Nilanjana,

Indeed useful material. Thanks for sharing it. Do you have anything similar for BAPIs.