Do you have any question about this error?
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 &)
During processing of inbound status records from the IDoc with the
number &v2& of type SYSTAT01, a status record occurred for inbound IDoc
&v1&.
Inbound status records for inbound IDocs do not make sense and are
therefore not supported. Processing is ended with an error.
Check and correct the IDoc numbers in SYSTAT01-IDoc &v2&.
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.
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:
- 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.
- Configuration Issues: There may be configuration issues in the IDoc processing settings or the partner profile that prevent the IDoc from being processed correctly.
- Data Issues: The data contained in the IDoc may be incorrect or incomplete, leading to a failure in processing.
- Application Logic: The application logic that is supposed to handle the IDoc may not be implemented or may have errors.
Solutions:
- 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.
- 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.
- Review Partner Profile: Check the partner profile settings in transaction WE20 to ensure that the inbound processing settings are correct.
- Correct Data Issues: If the IDoc contains incorrect data, you may need to correct the data in the source system and resend the IDoc.
- 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:
By following these steps, you should be able to identify the cause of the E1322 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
E1321
Inbound status for inbound IDocs not supported (IDoc no. & in file &)
What causes this issue? File &v2& in the operating system contains a status record for an inbound IDoc.System Response <DS:GLOS.3526B58CA...
E1320
-> Messages status processing
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
E1323
OPEN error CONVT_CODEPAGE_INIT for port & and file & for status inbound
What causes this issue? The runtime error CONVT_CODEPAGE_INIT occurred in connection with status inbound processing of file using port &v1& i...
E1324
OPEN error CONVT_CODEPAGE_INIT occurs in directory entered
What causes this issue? For test purposes an OPEN DATASET was performed in the directory entered when testing the file transfer. The system error CON...
Click on this link to search all SAP messages.