Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error in ALE service status 29

Former Member
0 Kudos

EXPERTS.

i have configurged all the ale settings.

1)logical systems SALE

sender - 800 client

receiver-810 client

2) SM59 R/3 connections

Receiver , here i checked the remote login , it is working , i mean i am able to login to 810 client

3)WE21 TRfc

generated port ie A000000038.

and given RFC destination as RECEIVER ---this is the logical system name of receiver

4)Done BD64

5)WE20 outbound partner profile

here in outbound parametes eneterd message type as cosmas

and in this given receiver port as A000000038.

and basic type as cosmas01.

6)Now i activated all the settings for changes pointers.

7)I changed cost centre in KS02 and saved

8)Executed BD21 ie idoc generation for change pointers

Got a pop up saying 1 master copy idoc generated , 1 communication idoc generated.

9)WE02.

Now status is 29 Error in ALE service

I clicked on control record.

In partner following information is there.

Receiver Informatiion

Port : A0000000038

partner number : RECEIVER

partn type : LS

Sender Infornation

Port : SAPSHS

Partner number : SENDER

partn type : LS

In sender info port is comming as SAPSHS i dont know from where it is comming.

So please tell me , where went wrong.

1 ACCEPTED SOLUTION

former_member194669
Active Contributor
0 Kudos

> In sender info port is comming as SAPSHS i dont know from where it is comming.

>

Nothing wrong in sender port, For outbound IDocs the sending system is always an SAP System. The EDI interface must determine the system ID and write it to the field in the form SAP<SYS-ID> (e.g. SAPSHS).

Test the IDoc thru WE19 using same IDoc number and test, if you can sucessfully send IDocs from WE19 then use BD21

6 REPLIES 6

former_member194669
Active Contributor
0 Kudos

> In sender info port is comming as SAPSHS i dont know from where it is comming.

>

Nothing wrong in sender port, For outbound IDocs the sending system is always an SAP System. The EDI interface must determine the system ID and write it to the field in the form SAP<SYS-ID> (e.g. SAPSHS).

Test the IDoc thru WE19 using same IDoc number and test, if you can sucessfully send IDocs from WE19 then use BD21

0 Kudos

Hi thanks for the reply

I executed WE19 as you said.

In the input screen given the idoc num 5234746

and in the menu option -> IDoc ->Test outbound idoc ->executed.

Now pop up came Idoc sent to R/3 sytem or external program.

Then we02.

one new idoc is generated ie 5234747.

And it is green ie status 3 data pased to port ok.

1) Why now it came to status 3? Even i checked the earlier failed idocs they also turened to status 3? Why so

2)So when ever we execute we19 , will it generate new idoc?

3)When we are doing in our company servers is it suggestable to execute we19 rather than BD87 , since WE19 geneates new idoc?Will business accepts it?

0 Kudos

Then check your partner profile--> select your message type and double click --> and check whether "Transfer Immediately" needs to be checked

Whenever you execute thru WE19 it will create a new IDoc, if you don't want then use BD87

Usually business will not accept this. WE19 is only a testing tool for trouble shooting

0 Kudos

I checked partner profile , it is checked as trigger immediately only.

Is there any other thing I need to check why it is happing like this

0 Kudos

What will be the error message coming under Status 29 ?

Former Member
0 Kudos

here is troubleshooting for status 29..i m converting graph in text

if partner profile exist

"YES

If (have u enhanced SAP program or using custom one)

"yes

check your logic where u modify control records

else. "

Check OSS notes

endif.

else

create partner profile

endif.