ALE – IDOC’S
ALE :
ALE is a technology which is used to communicate between the servers available at different geographical locations.
To send the data and receive the data from one server to another server, we need a dedicated network which is called as ALE(Application Link Enabling).
Application means customer Master Appl, Material Master Appl,
Sales Order Appl.
Link means a network or connection .
Enabling means Enable the link.
Types of data transfers
Basically we have two types of data transfers
1.Outbound data transfer.
2.Inbound data transfer.
Outbound data transfer:
Whenever we send the data from a system to another system,It is called as outbound data transfer i.e, data moving out of SAP is called as outbound data transfer.
Inbound data transfer:
Whenever we receive the data from a system is called Inbound data transfer i.e, data coming into SAP server is called Inbound data transfer.
Communication between SAP to SAP
ALE is a technology which is used to communicate between SAP to SAP server.
The data transfer is always in the form of a document called as “IDOC”(Intermediate Document).
Communication between SAP to Non-SAP:
EDI (Electronic Data Interchange) is the technology which is used to communicate between SAP server to Non-SAP server.
Since IDOC is an SAP tool . The Non-SAP system cannot understand the format of IDOC’s.
So ,we use the Middleware technologies like TIBCO (or) XI to communicate between SAP to Non-SAP.
The data transfer is always through a type of a document called as IDOC.(Post Cover)
Since IDOC is an SAP tool , only SAP system can understand IDOC’s.
Non-SAP system cannot understand the IDOC’s .
So we use the middleware technologies like TIBCO or XI to communicate between SAP to Non-SAP.
The IDOC is converted into XML and it is given to TIBCO or XI.
The middleware technologies will again convert the data into a format which can be understood by the receiver system.
IDOC’S
IDOC: - It is an intermediate document which contains the data.
Technically IDOC is a group of segments.
Each segment is group of fields.
Segments are like structures.
All the standard SAP segments will start with letter E1.
All the custom segments must start with the letter Z1.
EX: -
1. DEBMAS: 01, 02, 03,04,05 is an ex for custom IDOC.
2. CREMAS: 01, 02, 03…is an example for vendor IDOC.
3. MATMAS: 01, 02, 03…… is an example for material IDOC.
Where (05 is the latest version)
Example for segment:-
DEBMAS is an IDOC
E1KNA1Ã (Cust.Master Seg) Ã kunnr, name1, land1 are fields. E1KNB1Ã (Cust.Companycode)Ã kunnr, bukrs are the fields.
E1KNBK(customer bank details)Ã kunnr, Banks are the fields.
WE31 is the transaction code for segment definition.
WE30 is the transaction code for IDOC type.
Runtime components of IDOC
Runtime components of IDOC:-
Whenever an IDOC is transmitted at runtime, there are 3 components which are added automatically to the IDOC.
Control record.
Data record.
Status record.
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon