Solution : https://service.sap.com/sap/support/notes/974537 (SAP Service marketplace login required)
Summary :
The SAP Note addresses issues in IDoc communications where execution terminates due to the OBJECT_UNKNOWN exception with the error message indicating a nonexistent IDoc type. This typically occurs because external systems like SAP Business Connector or EDI subsystems do not recognize the current structure of the IDoc type being used. To resolve this, users should invoke the IDOCTYPE_READ_COMPLETE function module locally within SAP (using SE37 for testing) ensuring proper parameters and user authorizations (S_IDOCDEFT) are in place. If IDoc types or segments are missing or unreleased, users must verify their existence and release status via transactions WE30 and WE31, respectively, ensuring that all necessary data elements and segment versions are properly configured or created. Additionally, it's advised to check and adjust external systems or contact relevant SAP application components for support.
Key words :
solution call function module idoctype_read_complete locally, function module returns structure information, call function module idoctype_read_complete, java idoc-lib reason, sap idoctype_read_complete function module, idoctype_read_complete function module, idoc communication terminates, correction instructions mentioned, customer-specific interface, relevant support package
Related Notes :
| 983414 | Error SEGMENT_UNKNOWN when creating IDoc of type HRPLL40 |
| 613697 | Missing data elements after import |
| 612913 | Missing data elements in DI or DIMP systems |
| 491264 | Output of IDoc DELVRY02/DELVRY03 does not work |
| 448283 | Data elemnt CAKEY_FELD is missng for IDoc segmnt type E1CUID |