SAP ALE stands for Application Link Enabling Technique. It is network technique in SAP to communicate with remote servers available at different locations.
The remote servers can be SAP to SAP servers or SAP to Non-SAP servers. IDOC (Intermediate Document) is used in ALE Networks to communicate with bot SAP to SAP Servers. EDI (Electronic Data Interchange) is used in ALE Networks to communicate SAP server to Non-SAP server. Click on read more about this notes.
APPLICATION LINK ENABLING TECHNIQUE
ALE - IDOC - EDI - NETWORKS
ALE NETWORK (SAP –TO- SAP Communication)
ALE-It is a network which is used to
create a connection between the servers available at different Geo-Graphical
locations is called as ALE NETWORK.
The data transfer in SAP to SAP server is always done
through a Document called as IDOC (Intermediate Document).
Types of Data Transfer Techniques in ALE Networks
In ALE Networks there are two types of Data Transfer Techniqus are available they are,
1.
Outbound data transfer
2.
Inbound data transfer
When ever we send the data from one SAP server to another, it is called OUTBOUND
data transfer.
When ever we receive the data in to SAP server from remote server is called
INBOUND data transfer.
IDOC (Intermediate Document) :
IDOC is intermediate document which
is a container of the data. IDOC is used in ALE networks when both the source and target servers are SAP servers. Technically IDOC is a group ofsegments, Each
segment is a group of fields, Segment
is similar to structures in SAP.
All the standard SAP segments will
start with E1.
All the custom SAP segments will
start with Z1.
EDI(Electronic Data Interchange) : (SAP –To -NON SAP communication)
ALE is a technology or network which is used to communicate from one SAP server to another SAP server. Since both are SAP server’s the data transfer is always done through IDOC’s. If one server is SAP server and other one is Non-SAP server then the communication is done through using EDI Technology.
Electronic Data Interchange. In EDI we can use some third party tools like TIBCO.
T-CODES For ALE-IDOC
WE30 – is the TCODE for IDOC
types
WE31 – is the TCODE for
Segment definition
DEBMAS05
is the IDOC type for customer data
E1KNA1 fields are KUNNR, LAND1, and
NAME1
E1KNBK
fields are KUNNR, BUKRS
E1KNB1
fields are KUNNR BANKS, BANKT
CREMAS05
is the IDOC type for Vendor data
MATMAS05
is the IDOC type for material data
Runtime components of IDOC
When ever we transmit the IDOC from
one server to another server automatically some components were added at
runtime.
The components are,
1.
Control - Stored
in table EDIDC
2.
Data - Stored
in table EDIDD
3.
Status - Stored
in table EDIDS
Message Types in IDOC's
Message Type identifies the type of the
application for which IDOC is used. That
is same IDOC is used for different applications, So to identify each application
uniquely we use message types.
Example :
MATMAS --> Message Type
Matmas01
Matmas02
--> IDOC TYPE
Matmas03
CREMAS --> Message Type
Cremas01
Cremas02 --> IDOC TYPE
Cremas03
DEBMAS --> Message Type
Debmas01
Debmas02 --> IDOC TYPE
Debmas03
First we have to create the IDOC
with segments then we should create message type, then we have to link message type
and IDOC type.
"You found the information helpful and want to say thanks? Your donation is enough to inspire us to do more. Thanks a bunch!"
Posted in: ABAP Interview Questions, ABAP-Interview-Questions, ALE IDOC, ALE IDOC Interview Questions, ale-idoc, ALE-IDOC-Interview-Questions, Data-Dictionary, IDoc Tutorials, Module-Pool-Programming, Object-Oriented-ABAP-Interview-Questions, SAP ABAP Interview Questions, SAP-Enhancements, SAP-Exits
1 comments:
I am looking for the same networks techniques. Thanks for sharing such a informative information.
EDI
Post a Comment
Note: Only a member of this blog may post a comment.