IDOC Status

[Former Member]

Hi Experts,

I am getting the idoc error as problem in ALE service and the status number is 29. That’s why it is giving the description as entry in outbound table is not found. I have checked partner number and partner type in we20. I am able to see the same parter number and partner type which I have passed in my program.

But I don’t know still why it is giving same error. Can any body help on this?

Thanks a lot.

[paruchuri_nagesh]

hi

if the idoc is in the status 29 means error in ale sevice

for this u have to do ale consistency check

check distribution model view consistency check with BDM5

and partner profile consistency check with RSECHK07

and analyze RFC log by using TCODE SM58 OR RSARFCEX executable program

hope u find solution

reward if u find useful

regards

Nagesh.Paruchuri

[Former Member]

Hi Babji,

Status 29 mean its ALE service layer error

Please go through this and check the connections

Intermediate Document

An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data. IDoc is not a process.

• IDocs are stored in the database.

• In the SAP system, IDocs are stored in database tables.

• IDocs are independent of the sending and receiving systems.

• IDocs are independent of the direction of data exchange.

Creation of IDOCs

• Transaction code: WE 30

Defining Segment:

Creating Segment : Tcode – WE31

Creating Message Type : Tcode – we81

Assigning Message type to Idoc type: Tcode – we82

Process

The two processes for IDoc are Outbound Process and Inbound Process.

Outbound Process

When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.

Inbound Process

When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.

Outbound Process (Sending System) Steps :

1) Goto Tcode SALE:

Click on Sending & Receiving Systems  Select Logical Systems

Here Define the Logical Systems  Click on Execute Button

Go for New Entries

1) System Name : LOG1

Description: Sending System

2) System Name : LOG2

Description: Receiving System

Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.

Assigning Client to the Logical System:

Select Assign Client to Logical Systems - Execute

 100  Double click on this and give the following information

Client : Sending System

City : Chennai

Logical System : LOG1

Currency :

Client role :

 250  Double click on this and give the following information

Client : Receiving System

City :

Logical System : LOG2

Save this Data.

Step 2) For RFC Creation:

• Goto Tcode SM59  Select R/3 Connects

Click on create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

Give the information for required fields:

RFC Destination : LOG2

Connection type : 3

Target Host :

System No : 00

Client : 210

User : Login user name

Password :

Save this & Test it and Remote Login

Step 3) Goto Tcode BD64: – Click on the change button

Click on the create model view

Short Text: model view

Technical Name: LMOD

Save this & press ok

Select just created model view

Name: “LMOD”

Goto add message type

Model Name : LMOD

Sender : LOG1

Receiver : LOG2

Message type: ZAZHARMESS

Save and press Enter.

4) Goto Tcode BD82:

Give Model View : LMOD

Partner system : LOG2

Execute this by pressing F8

It will gives you sending system port No: A00000000089 (Like)

5) Goto Tcode BD64:

Select the model view

Goto  Edit  model view  Distribute

Press ok & Press Enter.

Run your Zprogram

6) Verifying Transfer of IDOCs Tcode – we05

ALE/IDOC Status Codes (outbound):

01  IDoc Added

30  IDoc ready for dispatch

29  Error in ALE service Layer

12  Dispatch ok

03  Data passed to port ok.

Inbound Process (Receiving System) Steps:

Do the same step as you did in sending system

 Creating IDoc

 Defining the Segment

 Creating Message Type

 Assigning the Message Type

 Defining the Logical System

 Assigning the Logical System

 Creating the Distribution Model

Goto Tcode – we57:

Assign function module to IDoc type

Module: Function module

Basic type:

Message type:

Direction: 2 (inbound)

Creating Inbound process code – we42

Verifying Idoc List Tcode – we05

ALE/IDOC Status Codes (Inbound):

50  IDoc Added

51  Application Document not posted

64  IDoc ready to be transferred to application

62  IDoc passed to application

53  Application Document posted

<b>Regards

Azhar</b>