ALE IDOCS

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 IDOCs.

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 IDOCs.

Non-SAP system cannot understand the IDOCs .

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.

IDOCS

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, 03is 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.

Steps to create an IDOC

Steps to create an IDOC:Step1: First create the required segment in WE31 with some
fields.
Step2: Create an IDOC in WE30 by inserting all the above
segments.

Step1: Steps to create a segment.

Go to WE31.

Give the segment type as Z1KNA1.

Click on the button create.

Give short description.

Give the list of the fields as below.

Click on save and back.

Click on edit from menu barset release.

The segment definition is completed and it is released also

Released status indicates that the segment definition is
completed and it can be used to transfer the data.
Similarly create one more segment by the name Z1KNBK
with the list of the below fields.
Field name

Data element

Kunnr

kunnr

Banks

banks

Bankl

bankl

Save it and release it.

Step2: Create IDOC from T-CODE WE30.

Go to WE30 and give IDOC name as ZDEBMAS05

Click on the button create.

Give description and press enter.

Click on the button create segment

A pop-up is raised.

Give the segment name as Z1KNA1.

Give the minimum and maximum no. as 1, because customer

master will have single record.
Select the check box if we want to make the segment as
mandatory segment.

Press enter

Now, Put the cursor on Z1KNA1, click on the button create.

A pop-up is raised.
Select the first radio button and press enter.

Give the segment type Z1KNBK.

Give the minimum no. as 1, maximum no. as 99999 because each
customer will have more than 1 bank account.
Press enter.

Finally, the hierarchy should look as below.

CONFIGURATION SETTINGS FOR ALE

CONFIGURATION SETTINGS FOR ALV :

1.Define Logical system:

In this step we define a logical name for the sending & receiving SAP
server systems.

The Tcode is SALE.

2.Assign client to the Logical system:

Here we maintain a client for the sending & receiving system to

transfer the particular client data.

The Transaction code is SALE.

3.Maintain RFC Destination:

In this step we maintain a connection between sender system and receiver

system which is called as RFC Destination.
The Tcode is SM59.

4.Define Port :

Port specifies the medium of transferring the data from one system to another system

WE21 is the Tcode for defining a Port.

5.Maintain Outbound Partner Profile:

Here we need to maintain the details of the receiver's system.

The details are

1.whom to send (Receiver's name)

2.what to send (IDOC name)

3.when to send(Immediately or collect)

4.How to send(Name of the port)

6.Maintain Distribution Model:

It contains the list of receivers who receives the data.

MASTER IDOC:
It is an internal table which consists of data to be sent from SX
system to RX system.
Suppose we are sending 100 materials from SX to RX , then MASTER
IDOC will be generated for each material . i.e. for 100 materials we
get 100 MASTER IDOCs.

COMMUNICATION IDOC:

These are the IDOCs which are derived from MASTER IDOC.

A COMMUNICATION IDOC is an IDOC which is generated for each

receiver.

OUTBOUND PROGRAM:
A program which is used to start the process of data transfer
from SX to RX.
With the help of selection screen , MASTER IDOC will be
generated and then COMMINICATION IDOCs will be generated
and will be sent to Receiver system.

PROCESS CODE (OPEN SQL):

Process code is a function module .

It is available at receiver side.

Processing code is responsible for receiving the data from

IDOC and updating the data into data base tables.

MESSAGE TYPE

MESSAGE TYPE:
It specify the type of the application from which IDOCs are being
used .The application may be material master or customer master and
vendor master etc.

WE81 is Tcode for defining a message type.

Always IDOC type and Message type should be linked with each other.

WE82 is Tcode used to create a link between message type and

IDOC

STEPS FOR IDOC AND MESSAGE TYPES

Define segment

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

WE31

Define IDOC Type

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

WE30

Define message type

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

WE81

Link Message type and

MASTER IDOC:

IDOC type ------------ WE82

It is an internal table which consists of data to be sent from SX

system to RX system.
Suppose we are sending 100 materials from SX to RX , then MASTER
IDOC will be generated for each material . i.e. for 100 materials we
get 100 MASTER IDOCs.

FILTERING

FILTERING:
Whenever we send the data from source system to receivers system,
by default all the IDocs and segments are received.
Suppose if we want to receive only few IDocs or segments based
on a particular value which is called as a filter value then it is called
as filtering.

Filtering is of two types:

IDoc filter

Segment filter.

IDoc filtering

IDoc filter:

Filtering the unwanted IDOCS is called IDOC filtering.

We need to specify a filter value in the distribution model(BD64), now

IDocs will be generated only for that filter type which is called as IDoc
filtering.

STEPS:

Goto BD64

Select model view as ZM_VIEW

Expand that model view and sender system and receiver system.

Expand the MATMAS message type.

Double click on NO Filter set.

Select data filtering

Click on the button create filter group.

Now, Expand the data filtering.

Expand the filter groups.

Double click on the material type.

A pop up will be raised.

Click on + symbol.

Give the filter value as FERT, so that the IDOCS will

Be generated only for this material type.

Press Enter and save the distribution model.

TESTING:

Create 5 materials in MM01.

Create 2 materials of type coupons and 3 materials of type finished

products.

Run the outbound program BD10.

Give the material no range . EX: 1437 to 1441.

Execute the programs.

Goto receivers 810 client and check the status.

Only materials of type FERT will be received because of filter value

FERT maintained at the distribution model.

Segment Filtering

Segment Filtering:

Filtering the unwanted segments in an IDoc is called segment filtering.

We need to specify the list of segments as segment filters, so that IDoc will
be generated from all the segments except the segment filters.

STEPS:

Specify the list of the segments which are to be filtered out.

Ex: Let us filter the segment EIMARMM of message type MATMAS.

Goto BD56.

Specify the message type as MATMAS.

Press enter.

Specify sender logical system, receiver logical system, segment name by

clicking on new entries

The ERROR will be displayed as below. Plz fix it by maintaining entry

in table EDPP1.

NOTE: We cannot filter the mandatory segments.

TESTING:

Run the outbound prg at the sendor system(800)

Check the status at receiver system(810)

All the segments will be received except the segment filter

E1MARMM.

Custom IDOCs

Custom IDocs:
Custom IDocs are generally copied from the standard IDoc by adding OR
removing extra segments.
We have two concepts available under custom IDocs.

Extended IDoc Type:

Ex:

Steps :

1)Create segments with fields in WE31 tcode.

2)Create an Extended IDOC by inserting the above segments.

STEP1:

IDoc Type = standard IDoc Type + Extra custom segments.

Create a custom segment in WE31 with below segments KUNNR,

NAME1,LAND1.
SAVE it back click on editset release.

STEP2:

Goto WE30.

Give IDoc name as ZDEBMAS05.

Select

Click on create.

Give linked basic type as DEMAS05.

Press enter.

Extended Idoc radiobutton.

By default all the standard segments are copied.

Put the cursor on any segment. EX: EIKNAIM.

Click on create button.

Give the custom segment name

Min No=1

Max No=1

Press enter

Click on save.

Reduced IDoc Type

Reduced IDoc Type:

It is an IDoc which consists of only the required segments and fields.

All the unwanted segments and filters are completely removed.

BD53 is the Tcode for reduced IDoc.

STEPS:

Goto BD53.

Give the message type as ZDEBMAS05_R.

Click on the Create button.

Give the message type reference as DEBMAS.

Press enter.

Give short description.

Again press enter

All the list of the segments will be displayed in different colors.

Color: RED ---------- Deselected segments / fields.

Color: WHITE-------- Selected segments/ fields.

Color: GREEN------- mandatory segments/fields.

Put the cursor on any segment Ex E1KNA11, click on button SELECT.

The color will turn from RED to WHITE which indicates that it is a required
segment.

Now double click on the segment, select the checkboxes for the required

Fields and click on the select button.

The color will turn from RED to WHITE which indicates that it is a required
field.

Press enter and save.

CHANGE POINTERS

Change Pointers:
It is a technique of sending required data i.e. materials or customers or
vendors which are changed during a certain period of time is called change
pointers.

Steps required for change pointers:

Activate change pointer centrally BD61 is the TCode.

Activate change pointer for message type BD50 is the TCode.

Activate change pointer for particular fields BD52 is the TCode.

Run the TCode BD21 or the program RBDMIDOC.

NOTE: - The changes are generally stored in 2 tables : CDHDR, CDPOS.

Remaining concepts are covered in class

INTERVIEW QUESTIONS

INTERVIEW QUESTIONS:

WHAT is ALE and EDI?

WHAT IS AN IDOC?GIVE ME SOME EX AND TCODE?

WHAT IS A SEGMENT?GIVE ME SOME EX AND TCODE?

EXPLAIN ABT RUNTIME COMPONENTS OF IDOC?

CAN WE CREATE A CUSTOM IDOC? IF YES, HOW?

WHAT IS A MESSAGE TYPE AND TCODE?

WHAT IS THE TCODE FOR LINKING MSG TYPE AND IDOC TYPE?

EXPLAIN THE SETTINGS REQUIRED AT OUTBOUND AND INBOUND FOR

ALE?

WHAT IS RFC DESTINATION AND TCODE?

WHAT IS A PORT AND TOCDE?

EXPLAIN ABT PARTNER PROILE AND TCODE?

WHAT IS DISTRUBUTION MODEL?

WHAT IS A MASTER IDOC AND COMMUNCATION IDOC?

WHAT IS A OUTBOUND PROGRAM AND PROCESS CODE?

WHARE IS THE PROCESS CODE AVAILBLE?

HOW DO U CHECK THE STATUS OFF IDOC?

EXPLAIN ABT THE ERRORS WHAT U FACED WHEN WORKING WITH AKE IDOC?

WHAT IS FILTERING AND ITS TYPES?

EXPLAIN ABT IDOC FILETRING AND TCODE?

EXPLAIN ABT SEGMENT FILETRING AND TCODE?

WHAT IS AN EXTENDED IDOC?CAN U EXPLAIN THE PROCEDURE?

WHAT IS AN REDUCED IDOC AND TCODE?

WHAT ARE CHANGE POINTERS? EXPLAIN THE STEPS?