Solution : https://service.sap.com/sap/support/notes/555229 (SAP Service marketplace login required)
Summary :
IDocs are experiencing hang-ups in status 64, indicating resource limitations which prevent immediate processing. This issue, underlined by messages like "NO RESOURCES, IMMED. PROCESSING NOT POSSIBLE," particularly impacts scenarios where quasi-synchronous communication relies on IDoc. Troubles began after certain Support Packages were imported, which altered IDoc handling to secure single-instance data transfer, inadvertently creating processing inconsistencies. The recommended fixes involve strategic code updates and adjustments in IDoc configurations between specified Support Packages. Two resolution paths are outlined: reverting to original process settings or shifting from dialog processing to a background setup via the TEDEF table configuration.
Key words :
proposed solution includes source code corrections, source code corrections, symptom idocs hang, oltp system hangs, idoc partner profile, quasi-synchronous communication, idoc receipt maintain, original behavior prior, idoc status record, trfc port type
Related Notes :
| 805469 | |
| 763982 | IDoc: tRFC inbound, syn. processing depends on message type |
| 628397 | SAPKU30015: Support Package 15 for EBP 3.0/CRM 3.0 |
| 561880 | Requests hang because IDocs are not processed |
| 535172 | IDoc: Dup. IDocs in tRFC inbound processing w/ runtime error |
| 492589 |