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: 

Status record 65 error in ale service

Former Member
0 Kudos

HI Experts,

I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.

This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .

The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-

For an example

Content of created Idoc in sender

Company code field | SAH001

The company code info is now SAH001. I wonder why ?

So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesn’t exist.

Content of idoc in receiver

Company code field | SAH001

I want to display 0093.

Please tel me what is error and how to rectify?

Thanks & regards

Mathi

1 ACCEPTED SOLUTION

former_member404244
Active Contributor
0 Kudos

hI,

Testing inbound idoc :

Once you configured everything then goto WE19 Transaction :

Give message type or idoc type and execute .

now here you need to fill the Mandatory data in each segment,once you done then

idoc->edit control record -> here you need to fill sender and receiver details.

now you should get green color ,if you get red color then config issue.

now click on start inbound -> now you will get idoc number.

if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.

now cursor will go debug mode

http://www.photographybykevin.net/sap/idoc_overview.pdf

Testing Outbound idoc :

Once you done all configuration ..

Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.

create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.

debugging Outbound IDOC :

keep the break point in form routine above as i said

Create invoice or invoice list

when you maintain output type in invoice or invoice list -

Now click on Further data ->select peridoc scheduling-> back and save it.

Run RSNAST00 Program

Output application : V3

Object key : Invoice or invoice list number

Output type : RD00 or LR00

Medium = 6(EDI) ,A (ALE)

when you execute the program and it will goto debugging.

See the below status codes :

See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes

Successful Transmission:

03 - Successful outbound transmission

12 - Dispatch OK

IDoc being processed:

01 - IDoc created

30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)

ALE Error Messages:

02 - Error passing data to port

04 - Error within control information on EDI subsystem

05 - Error during translation

25 - Processing despite syntax errors (outbound)

29 - Error in ALE service

32 - Resubmit edited intermediate document (DO NOT USE)

Syntax Error Messages:

26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes

IDoc Processed Successfully:

50 - IDoc added

53 - Successful posting

IDoc ready for processing:

64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

Errors in IDoc Processing:

51 - Error - application document not posted

56 - IDoc with errors added (You should never see this error code)

60 - Error during syntax check of IDoc (inbound)

61 - Processing despite syntax error (inbound)

63 - Error passing IDoc to application

65 - Error in ALE service - indicates partner profiles are incorrect

69 - IDoc was edited

Regards,

Nagaraj

3 REPLIES 3

former_member404244
Active Contributor
0 Kudos

hI,

Testing inbound idoc :

Once you configured everything then goto WE19 Transaction :

Give message type or idoc type and execute .

now here you need to fill the Mandatory data in each segment,once you done then

idoc->edit control record -> here you need to fill sender and receiver details.

now you should get green color ,if you get red color then config issue.

now click on start inbound -> now you will get idoc number.

if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.

now cursor will go debug mode

http://www.photographybykevin.net/sap/idoc_overview.pdf

Testing Outbound idoc :

Once you done all configuration ..

Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.

create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.

debugging Outbound IDOC :

keep the break point in form routine above as i said

Create invoice or invoice list

when you maintain output type in invoice or invoice list -

Now click on Further data ->select peridoc scheduling-> back and save it.

Run RSNAST00 Program

Output application : V3

Object key : Invoice or invoice list number

Output type : RD00 or LR00

Medium = 6(EDI) ,A (ALE)

when you execute the program and it will goto debugging.

See the below status codes :

See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes

Successful Transmission:

03 - Successful outbound transmission

12 - Dispatch OK

IDoc being processed:

01 - IDoc created

30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)

ALE Error Messages:

02 - Error passing data to port

04 - Error within control information on EDI subsystem

05 - Error during translation

25 - Processing despite syntax errors (outbound)

29 - Error in ALE service

32 - Resubmit edited intermediate document (DO NOT USE)

Syntax Error Messages:

26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes

IDoc Processed Successfully:

50 - IDoc added

53 - Successful posting

IDoc ready for processing:

64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

Errors in IDoc Processing:

51 - Error - application document not posted

56 - IDoc with errors added (You should never see this error code)

60 - Error during syntax check of IDoc (inbound)

61 - Processing despite syntax error (inbound)

63 - Error passing IDoc to application

65 - Error in ALE service - indicates partner profiles are incorrect

69 - IDoc was edited

Regards,

Nagaraj

Former Member
0 Kudos

Hi,

Error in ale service indicates prob in partner profile in we20.

Regards,

Bohra.

0 Kudos

Hi

Thanks for ur reply.....

I checked partner profile,it is configured correctly...

could you please tel me any other suggestion?....