8/3/2019 Cross Appl

1/46

ALEIDOCS

8/3/2019 Cross Appl

2/46

ALE :

ALE is a technology which is used to communicate between theservers available at different geographical locations.

To send the data and receive the data from one server to anotherserver, we need a dedicated network which is called asALE(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.

8/3/2019 Cross Appl

3/46

8/3/2019 Cross Appl

4/46

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,Itis called as outbound data transfer i.e, data moving out ofSAP is

called as outbound data transfer.

Inbound data transfer: Whenever we receive the data from asystem is called Inbound data transfer i.e, data coming intoSAPserver is called Inbound data transfer.

8/3/2019 Cross Appl

5/46

Communication between SAP to SAP:

ALE is a technology which is used to communicate between SAP toSAP 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 tocommunicate between SAP server to Non-SAP server.

Since IDOC is an SAP tool . The Non-SAP system cannot understandthe format of IDOCs.

8/3/2019 Cross Appl

6/46

So ,we use the Middleware technologies like TIBCO (or) XI tocommunicate between SAP to Non-SAP.

The data transfer is always through a type of a document called asIDOC.(Post Cover)

8/3/2019 Cross Appl

7/46

Since IDOC is an SAP tool , only SAP system can understandIDOCs.

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 aformat which can be understood by the receiver system.

8/3/2019 Cross Appl

8/46

IDOCS

8/3/2019 Cross Appl

9/46

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 customer 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)

8/3/2019 Cross Appl

10/46

8/3/2019 Cross Appl

11/46

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.

8/3/2019 Cross Appl

12/46

Runtime components of IDOC

8/3/2019 Cross Appl

13/46

Runtime components of IDOC:-

Whenever an IDOC is transmitted at runtime, there are 3components which are added automatically to the IDOC.

Control record.

Data record.

Status record.

8/3/2019 Cross Appl

14/46

8/3/2019 Cross Appl

15/46

Steps to create an IDOC

8/3/2019 Cross Appl

16/46

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

Step1: Steps to create a segment.

Go to WE31.

Give the segment type as Z1KNA1.

Click on the button create.

Give short description.

8/3/2019 Cross Appl

17/46

Give the list of the fields as below.

Click on save and back.

Click on edit from menu barset release.

8/3/2019 Cross Appl

18/46

The segment definition is completed and it is released also

Released status indicates that the segment definition is completedand 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.

8/3/2019 Cross Appl

19/46

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

8/3/2019 Cross Appl

20/46

A pop-up is raised.

Give the segment name as Z1KNA1.Give the minimum and maximum no. as 1, because customermaster will have single record.

Select the check box if we want to make the segment asmandatory segment.

Press enter

8/3/2019 Cross Appl

21/46

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 eachcustomer will have more than 1 bank account.

Press enter.

8/3/2019 Cross Appl

22/46

Finally, the hierarchy should look as below.

8/3/2019 Cross Appl

23/46

CONFIGURATION SETTINGS FOR ALE

8/3/2019 Cross Appl

24/46

CONFIGURATION SETTINGS FOR ALV :

8/3/2019 Cross Appl

25/46

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 receiversystem which is called as RFC Destination.

The Tcode is SM59.

8/3/2019 Cross Appl

26/46

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.

8/3/2019 Cross Appl

27/46

8/3/2019 Cross Appl

28/46

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 MASTERIDOC will be generated for each material . i.e. for 100 materials weget 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 eachreceiver.

8/3/2019 Cross Appl

29/46

OUTBOUND PROGRAM:

A program which is used to start the process of data transferfrom SX to RX.

With the help of selection screen , MASTER IDOC will begenerated 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 fromIDOC and updating the data into data base tables.

8/3/2019 Cross Appl

30/46

MESSAGE TYPE

8/3/2019 Cross Appl

31/46

MESSAGE TYPE:

It specify the type of the application from which IDOCs are being

used .The application may be material master or customer master andvendor 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 andIDOC

8/3/2019 Cross Appl

32/46

8/3/2019 Cross Appl

33/46

8/3/2019 Cross Appl

34/46

STEPS FOR IDOC AND MESSAGE TYPES

Define segment -------------------- WE31

Define IDOC Type -------------------- WE30

Define message type -------------------- WE81

Link Message type and IDOC type ------------ WE82

MASTER IDOC:

It is an internal table which consists of data to be sent from SXsystem to RX system.

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

8/3/2019 Cross Appl

35/46

8/3/2019 Cross Appl

36/46

Custom IDOCs

8/3/2019 Cross Appl

37/46

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.

8/3/2019 Cross Appl

38/46

Extended IDoc Type:

Ex: IDoc Type = standard IDoc Type + Extra custom segments.

Steps :

1)Create segments with fields in WE31 tcode.

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

STEP1:

Create a custom segment in WE31 with below segments KUNNR,NAME1,LAND1.

SAVE it back click on editset release.

8/3/2019 Cross Appl

39/46

STEP2:

Goto WE30.

Give IDoc name as ZDEBMAS05.

Select Extended Idoc radiobutton.

Click on create.

Give linked basic type as DEMAS05.

Press enter.

8/3/2019 Cross Appl

40/46

By default all the standard segments are copied.

8/3/2019 Cross Appl

41/46

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.

8/3/2019 Cross Appl

42/46

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.

.

8/3/2019 Cross Appl

43/46

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.

8/3/2019 Cross Appl

44/46

8/3/2019 Cross Appl

45/46

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

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

Fields and click on the select button.

8/3/2019 Cross Appl

46/46

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

field.

Press enter and save.