Skip to Content
avatar image
Former Member

RBDMANIN - No status record was passed to ALE by the application

Hi Folks,

We are using program RBDMANIN to process idocs in batch. Right now, a bunch of idocs fail with the message "No status record was passed to ALE by the application". What we observed that once an idoc fails, all the following idocs fail with this message.

When we take these idoc numbers and re-process them via BD87 - they are processed successfully (or fail with a relevant message and status). This is a custom idoc/message type and the there is custom code which is used for processing this idoc.

I read posts here on SDN about the same error. All the variables/objects are being cleared. Also, what makes it strange is that when we go via BD87, idoc is processed successfully. Any thoughts where the problem could be?

Regards,

Munish

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Mar 15, 2009 at 10:11 AM

    Hi,

    what is status of the idoc ?

    Thanks

    Krithika

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 15, 2009 at 11:27 AM

    Hi Munish,

    Is this first time it was happened or previous version already executing in production successfully. I remembered the similar situation earlier,

    but at that time in Batch processing part of the status related logic was not triggered, we processed the same through BD87 successfully and found that same logic was executing successfully in foreground / individually. Please check the status related logic of the Idoc.

    Regards,

    ~Satya

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 15, 2009 at 03:02 PM

    Hi Munish,

    Recheck the code where you update the Status for the IDOC at Inbound processing side.

    We did encounter the same Issue and there was Bug in the code.

    Regards

    Shital

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Guys,

      Thanks for all your replies! The thing is it is not happening for all the idocs of this type. This idoc ends up in status 51 - No status passed to ALE from application. What we have seen so far - when a idoc fails to 51 (due to some valid reason - as per the application code), the following idocs in the batch start failing with the mentioned message.

      I saw the status messages for one of the idocs that originally failed with this message. It had around 25 status records (The idoc processing job runs quite often) in status 51. Out of these two random status (say 13 and 20) messages were valid reasons for failing the idoc (as per application code). Message was same both the time. Others were 51- No status message passed to ALE from application. So it seems that job is not even hitting the custom code when it fails with this error message.

      Regards,

      Munish

  • avatar image
    Former Member
    Mar 16, 2009 at 05:52 AM

    Hi Munish,

    51 status will not correct on it's own. 51 status will occur when there is a Data issue or Implementation logic issue.

    Please correct the Data side (provide required/ prerequired information or check the data correctness) or check the business logic in process code.

    Then reimplement thru bd87. This may help to process.

    regards

    Satya

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I think the problem is the Idocs are posting when you do it in foreground instead of running those in background...

      Check that scenario

  • avatar image
    Former Member
    Mar 18, 2009 at 05:44 AM

    Hi,

    51 status indicates that the error is related to the data being carried by the IDoc.

    Incase of Master Data, resend the data again and block the old IDoc.

    Transactional data, reprocess the idoc using RBDMANI2.

    Thanks

    Krithika

    Add comment
    10|10000 characters needed characters exceeded