How To Fix E1322 - Inbound status for inbound IDocs not supported (IDoc no. & in IDoc &)


SAP Error Message - Details

  • Message type: E = Error

  • Message class: E1 - Messages for IDoc Basis

  • Message number: 322

  • Message text: Inbound status for inbound IDocs not supported (IDoc no. & in IDoc &)

  • Show details Hide details
  • What causes this issue?

    During processing of inbound status records from the IDoc with the
    number &v2& of type SYSTAT01, a status record occurred for inbound IDoc
    &v1&.

    System Response

    Inbound status records for inbound IDocs do not make sense and are
    therefore not supported. Processing is ended with an error.

    How to fix this error?

    Check and correct the IDoc numbers in SYSTAT01-IDoc &v2&.

    Procedure for System Administrators

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message E1322 - Inbound status for inbound IDocs not supported (IDoc no. & in IDoc &) ?

    The SAP error message E1322, which states "Inbound status for inbound IDocs not supported (IDoc no. & in IDoc &)," typically occurs when there is an issue with the processing of an inbound IDoc. This error indicates that the IDoc is in a status that does not allow for further processing, which can be due to various reasons.

    Causes:

    1. IDoc Status: The IDoc may be in a status that is not valid for processing. For example, it could be in a status like "51" (error) or "30" (processed) which does not allow for further inbound processing.
    2. Configuration Issues: There may be configuration issues in the IDoc processing settings or the partner profile that prevent the IDoc from being processed correctly.
    3. Data Issues: The data contained in the IDoc may be incorrect or incomplete, leading to a failure in processing.
    4. Application Logic: The application logic that is supposed to handle the IDoc may not be implemented or may have errors.

    Solutions:

    1. Check IDoc Status: Use transaction code WE02 or WE05 to check the status of the IDoc. If the IDoc is in an error status, you may need to correct the underlying issue and reprocess the IDoc.
    2. Reprocess IDoc: If the IDoc is in a status that can be reprocessed (like "51"), you can use transaction code BD87 to reprocess the IDoc after correcting any issues.
    3. Review Partner Profile: Check the partner profile settings in transaction WE20 to ensure that the inbound processing settings are correct.
    4. Correct Data Issues: If the IDoc contains incorrect data, you may need to correct the data in the source system and resend the IDoc.
    5. Debugging: If the issue persists, consider debugging the inbound processing logic to identify any application-level issues that may be causing the error.

    Related Information:

    • IDoc Status Codes: Familiarize yourself with the various IDoc status codes to understand what each status means and how it affects processing.
    • Transaction Codes:
      • WE02/WE05: To view IDocs and their statuses.
      • BD87: To reprocess IDocs.
      • WE20: To check and maintain partner profiles.
    • SAP Notes: Check for any relevant SAP Notes that may address known issues related to this error message.

    By following these steps, you should be able to identify the cause of the E1322 error and take appropriate action to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker