No status record passed to ALE error

Hello,
My idocs are failing with the above mentioned error. Kindly suggest some remedy for the same.
Thanks,
Alok Bhardwaj

Hi,
Thanks for your reply, but the problem is coming even when I am trying to reprocess these idocs one after another. Can you please throw some light on this issue.
Thanks,
Alok Bhardwaj.

Similar Messages

IDocStatus Application document not posted, No status record passed to ALE

Hi,
I am sending CREMAS04 IDOC to receiver system.The receiver system should create vendor entry in master table by using IDOC data.
IDOC is getting posted successfully in R/3,but while calling inbound function module i.e process code CRE1 I am getting following status records :
51 Application document not posted
No status record was passed to ALE by application.
62 IDOC passed to application
Direct call started.
64 IDOC ready to be transfered to application
No filters , No conversion , No version change .
50 IDoc added
Please help me to resolve this problem.

Shweta,
The IDOC has been posted by XI to the R3 system. It is the funtional module that is not able to handle the IDOC and only your Functional Team can tell you why the IDOC is not being processed properly by the R3 system.
It can be because of multiple reasons including invalid data, etc . For instance we once faced an issue once when the User ID used to post the IDOC did not have the authorizations to do financial manipulations and it was our functional team that was able to pin point the reason to us.
Regards,
Bhavesh

Application failed to return status record to ALE layer after Idoc procesed

Hi,
I am loading a full load to Product category (hierarchies) through process chain.
One of the load failed with the following error. The Idoc has status 51 in BW.
Can some suggest me the process for correcting this.
Thanks
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.

Hi
If this is standard code then you will have to write code to populate the status message in exit. But in case of custom code, the above mentioned solution is best (if coding logic is correct). I have given this solution to many queries and all worked.
Thanks
Anuraag

Status record 65 error in ale service

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 doesnt 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

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

Status 51:No status record was passed to ALE by the application

Hi All,
my scenario is file->XI->IDOC.
data is reaching r/3 system, but i see below error in WE02
status 51: Application document not posted
No status record was passed to ALE by the application
registering the function module, linking FM with basic type with direction equal to 2, assigning FM to process code and inbound parameters of partner profiles are configured well.
Plz let me know if i missed any steps.
Thanks,
Goutham

use similar thread
Inbound IDOC
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...
Edited by: Dharamveer Gaur on Sep 19, 2008 2:17 PM

No status record was passed to ALE by the application

Hi Experts,
My requirement is something like this: The middleware (XI) is triggering an IDOC which is Inbound to SAP-ECC. This IDOC is used for posting of Financial documents (Invoice and Credit memos).
I am processing the IDOC by writing a FM. Inside the FM I am reading data from IDOC and using a BAPI to post the documents. Then I am updating the status of the IDOC based on successful or unsuccessful posting.
Issue: When XI triggers the IDOC, the IDOC is resulting in status "No status record was passed to ALE by the application". This is not the status that I am populating inside my FM. This means that the control is not entering the FM at all (please correct if I am wrong).
My findings: When I re-process the same IDOC which resulted in error previously using WE19, the control goes inside my FM (obviously as I give my FM name in WE19 ) and the status gets populated according to my code.
Problem that I am facing is only when I am trying to do an Intergration testing.
I have searched SDN for same issue and found out that I need to clear/refresh all the necessary variables. I am doing that (and double checked it too).
Please help me with this problem as I am running out of ways to find the solution (and time also ).
Many thanks,
Daljeet.

Hi Daljeet,
Please check SM58 logs.
Thanks,
Best regards,
Prashant

Error while updating the status record of IDOC in SAP

Hi All,
I am facing this problem. I have done outbound processing and IDOC was sent successfully from SAP to EDI system and it was processed in EDI and now EDI system wants to send the status back to SAP with a status message and the status number that we are using is '24' and we have mapped all the fields in the status table EDIDS and made sure that EDI system sends all those and I think Counter field can not be determined by EDI system so EDI system used the counter '1' since it can not determine how many counters are already there in SAP and unless we pass the value to this counter field we were getting the error. After passing all the values the status of the IDOC is updated with the status '00' instead of '24' and we do not know why it is happened and I would like to know how SAP converts the status record that is received from the EDI system.
Please let me know how the status record will be translated into SAP from EDI system and I ahve followed basically EDIDS structure and the IDOC status is updating in SAP but with wrong status number and the alignemnt also missing in SAP fields like if I give some text in the EDI it is splitting and storing in 2 fields.
Please help me in this and I think I have explained the problem in a detail manner.
Thanks,
Ramesh.

Hi Naresh,
Thanks for the reply and my question is since EDI system is able to send the status back to SAP from EDI system and only problem is it is updatinf the status wrong and I have checked the EDIDS table also and the entry is creating with another counter and please confirm me that it is because of EDI does not support the status record update so that I can confirm to the client that there is nothing wrong in the way SAP functions and EDI system can not update the status code in the SAP.
Thanks,
Ramesh.

Inbund IDOC error: Status records with status 51 after status 53

Hi all,
I'm looking to resolve an issue related to posting an inbound IDOC. when I process inbound IDOC created from report prg I'm getting a status message: "Status records with status 51 after 53" .
Functionality: I'm creating an IDOC from flat file and processing it to post Customer master data into SAP. During this process creation of IDOC is successful but when I'm changing the existing data record (customer master data) IDOC is throwing this error.
Changing data: For changing existing data I'm passing KUNNR field and overwriting the remaining data. Even though the idoc status is 51 the changed data is getting posted in to SAP. Here my concern is to see IDOC status as 53.
Regards,
Ganesh.
Edited by: Ganesh Sunkara on Aug 1, 2009 3:45 AM

Hi all,
I solved this issue by myself. There is an error in the user exit code.
regards,
Ganesh.

HTTP Status Code 500 Internal server error while passing complex object

Hi
When I am passing values through complex input parameter, I am getting "*HTTP Status Code 500 Internal server error: The server encountered an unexpected condition which prevented it from fulfilling the request*". Why I am getting this error? Any idea
Regards
Raj

Raj,
Can you elaborate on what exactly are you trying to do? Are you saying that same use case works when you pass simple parameters?
JC

HR ALE : Error in Idoc Status table

Hi,
We are transporting HR Master data from one client to another (message type HRMD_A) and extension ZRMD_A06. For this purpose we are using the PFAL transaction. So far, we are able to send employee data to the receiving client, all Pnnnn tables also get updated correctly ( we have applied some translation rules in our user exit).
The problem we are facing is that the idoc in our receiving client is in status 51, even though all data commit to the database tables.I checked the status records, for every segment it says "Infotype nnnn cannot be updated on database table Pnnnn " I checked the entries in T777D as suggested in the message, and everything looks fine.
Has anybody encountered this problem before? Do we need to maintain any settings/configuration for the same? All suggestion welcome!
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma Iqbal
At present I also have to work on ALE for HR Master Data from Production to other systems like Development and Test. I shall appreciate if you give me guideline on how to use the Tcode PFAL.
Thanks
Plavini

Error message B1 357-Status records with status 51 after status 53

Hi All,
somebody knows why is can be caused this message:
''Error message B1 357-Status records with status 51 after status 53''
Thanks and best regards
L

Dear Luis,
Please Check
Status records with status 51 after status 53
Best Regards,
Amit

Re STATUS Record-HR

Hi,
I have created FM for Hiring Action(HR) using BDC session,
Inbound Process
When i am trying to pass the FM to IDOC it is giving me Status Record 51 which specifies 'No status record was passed to ALE by the application',
What exactly i have to do in my FM for this error,
Can u reply with Code.
Thanks
Abhay

Hi,
using transaction PA40 in batch-input always causes problems, so maybe u can try to do it using PA30.
Regards,

ALE Error 29 - Entry in Outbound Table not found

Hi,
I am getting the following error in the IDOC processing.
IDoc: <IDOC Number> Status: Error in ALE service
Entry in outbound table not found
I have checked the partner profile. It is OK
I noticed that the IDoc record doesn't have the defined port. The value in the port section is empty.
The IDoc message type - CRMXIF_ORDER_SAVE_M
Basic Type: CRMXIF_ORDER_SAVE_M01
Any inputs will be appreciated.

Observations -
I checked the Status records for the IDOC and there are only 2 entries -
1. 01 IDoc Generated and
2. 29 Error in ALE Service - Entry in Outbound table not found

I am trying to use the T. S. operator interface I need to add pass fail and error

Hello:
I am using Labview 6.1 and Test Stand 2.0
I have made some modification to a copy of the T.S. Labview operator interface. How do I get the pass/fail or error from test stand to be pass to LabView so I can tell the operator that the unit pass or fail the test. I do not want to use the Test UUTs. I want this to be very low operator response.
Message Edited by Toro on 02-28-2006 01:52 PM

Not sure if this is available in the earlier versions of TestStand, but I think so.
You could post a UI Message, from your execution entry point in the process model, to your User Interface indicating the pass/fail/error status when a test run is complete. You will need to handle the UI Message in your Operator Interface. See TestStand II Customisation course notes for handling UI Messages.
The data passed in the UI Message can be anything you like, the UI Message handler in the User Interface will have to process the message and update the display as required.
Hope this helps
Steve
Message Edited by SercoSteve on 03-01-2006 10:02 AM
There are 10 types of people in the world that understand binary, those that do and those that don't.

Some question on IDOC (Control Record/Data Record/Status Record)

Dear all,
I am new in this area, and would like to enquire some question on this topic.
When I view a IDOC via WE02, each of the IDOC record will consist of Control Record/Data Record/Status Record).
Questions:
I notice that the data records consists of many segment (i.e. E1EDK01, etc) which are use to store application data.
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Thanks.
Tuff

Hi Tuff,
As everything in SAP, with IDOCs too there are
1) Standard IDOCs
2) Standard IDOCs(Extending - Enhancement to an IDOC, to accomodate for custom values)
3) Custom IDOCs
And every IDOC has,
Control record - EDIDC Structure - This mostly reflects the partner profile information, along with few more details which are used for IDOC extension, Sequencing etc
Data Records - EDID4 Structure - These records contain the actual business data of the document in concern. So for ORDERS05 it would contain order details, INVOIC02 - Invoice details so on...
Status Records - These records capture the status of an IDOC from the time it is received/sent from your system and a corresponding business document is created/changed. So this will have messages like "IDOC sent to the port OK" etc which are status from the communication layer(ALE) to application specific messages like "Sales Order XXX created" or "Invalid Material" etc.
You would have noticed something called as Process code in the partner profile, this is associated with a FM(or work flow task etc) which has the business logic coded in.
So in case of an Inbound IDOC, the sending system updates the IDOC - Control and Data records, and sends it to the receiving system. On the receiving system the IDOC's control record is validated against the partner profiles set, if an entry is found then using the process code it finds the associated FM which will decode the data from the IDOC data records as per the IDOC type and then use it to post data into SAP (VIA BDC, Batch Input, BAPI etc).
And all this while the Status records are being updated accordingly.
So with the above context will try to answer your questions,
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
In case of a custom IDOC, yes you will have to.
In case of a standard IDOC, you wouldn't have you just have set up the necessary configuration (Partner Profile, Process code etc)
In case of a standard IDOC extended to accommodate for some custom values(for which there are no fields in standard IDOC - Let us say you have added some new fields on VA01) - In this case you can still use the standard Process code and Standard FM associated with it, SAP provides several Function exits in these FM's which you can leverage to add your custom logic.
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
There are several documents available on the net and on SDN detailing step by step approach for all the above three cases,
just search for step by step guide for IDOCS - sap.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Again it depends, in case of using a standard IDOC you wouldn't have to. But in case you have some customizations/enhancements then you might have to.
For Ex: updating the control record accordingly for indicating that you have extended the standard IDOC. Or append custom messages to the status record as per the business logic.
Try out the examples you find on the net and post any specific questions you might have.
Regards,
Chen

No status record passed to ALE error

Similar Messages

Maybe you are looking for