ALE / IDOC ---> (Application Link enable / Intermediate

Document).

Idoc is nothing but its like a container. its load our data objects and its transfer our sap system to
another sap system.

IDOC will not easily go from one system to another system. we have to do some enablement
some configuration in these two system.

this configuration enabliment known as Application Link enable.

once this link is eneable.

First SAP System we requied our OUTBOUND PROGRAM

WHY OUTBOUND PROGRAM?

Becoz we sending the data from one sap to another sap. thats what we need OUTBOUND
program.

In OUTBOUND program will collect the data in certaine formate and it pass to the IDOC.and it
OUTBOUND program will create IDOC and system will check whether link is enable or not.

if link is enable then our sap system will go directly to the 2nd SAP SYSTEM.

Once it comes here( SAP 2 ) we will be having one function module or like program.but
generally it create function module. inside the function module will be retained some codes .it
will take data from IDOC based on scenario of bussiness.it process the data and update the data
into requied table.(fetch the data from IDOC nd update the data to required table).
This is whole process of ALE/IDOC.

IS ALE IS ONLY FOR SAP TO SAP?

yes, ALE is only FROM SAP TO SAP.

IF YOU ONE SAP TO NON-SAP SYSTEM then you need to middleware have to use (like PI/RFC)

EDI(ELECTRONIC DATA INTERCHANGE)--NON-SAP DATA.

----------------------------------------------------------------------------------------------------------------

T-CODE:

WE02-->display the IDOC(EDI)(it specify all idoc include EDI)(non-sap to sap system)

WE05-->display the IDOC(ALE)(sap to sap system).

STATUS record:

50-IDOC ADDED

64-IDOC already to be passed to an application

62-IDOC passed to an application.

53-Application document posted.

IMPORTANT TABLE: we can see this using (se11 or se16 or se16n(most preferable))

In every IDOC is having 3 parts:

 EDIDC-- control record,

EDID4-- data record,

EDIDS-- status record.

sender system configuration:

1.first have to create segment(WE31) like structure.where we have the multiple fields.

once we create segment then we have to create BASIC TYPE(WE30)

2.BASIC TYEP(IDOC TYPE--WE30)---group of segment ---technical description.

3.MESSAGE TYPE(semantic meaning)(WE81) nd (WE80).

once we create the message type then have to create basic type in (we82).
------------------------------------------------------------------------------------------------------------------

1.create the logical system name for the system.

2.have to assign the client to this system.

3.create the RFC destination(SM59)

4.port(we21)

5.partner profile(WE20)

6.OUTBOND PROGRAM-- we create the Outbond program to generate the IDOC and
send to the receiver system.

* most frequently we use FM is MASTER_IDOC_DISTRIBUTE.

Receiver system configuration:

1.first have to create segment(WE31) like structure.where we have the multiple fields.

once we create segment then we have to create BASIC TYPE(WE30)

2.BASIC TYEP(IDOC TYPE--WE30)---group of segment ---technical description.

3.MESSAGE TYPE(semantic meaning)(WE81) nd (WE80).

once we create the message type then have to create basic type in (we82).

------------------------------------------------------------------------------------------------------------------
1.create the logical system name for the system.

2.have to assign the client to this system.

3.create the RFC destination(SM59)

4.port(we21)

5.INBOND FUNCTION MODULE/WORKFLOW-- we create the Inbond function module

to generate the IDOC data and processed the receiver system based on our business
scenario.

6.Register this inbound fun.module(BD51).

7.We have to link message type with fun.module in WE57.

8.We have to create process code(WE42).

9.Create inbound partner profile(WE20) for sender system.