3776596 - IDocs Remain in Status 18 and ARFCSSTATE Entries Stay in "RECORDED" State Due to Incorrect Table Buffering Configuration

The following symptoms may be observed in the SAP system:

• Entries remain in table ARFCSSTATE with the aRFC state "RECORDED".
• Both inbound and outbound IDocs become stuck in /PACG/ECM_COCKPIT2.
• Outbound IDocs remain in Status 18 and do not automatically progress to Status 41.
• Manual reprocessing of the affected IDocs successfully updates them from Status 18 to Status 41.
• The issue affects the automatic confirmation process while manual processing completes successfully.

Status Explanation

• Status 18 – The IDoc has been sent from the SAP ERP system to the external system through the connector. The SAP system is waiting for a processing confirmation from the external system.
• Status 41 – The processing confirmation has been received successfully, confirming that the document was processed by the receiving system.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP ERP (ECC / S4HANA)
• SAP Field Service Management (FSM)
• Proaxia Connector (PACG)

ARFCSSTATE, RECORDED, aRFC, tRFC, qRFC, RFC Processing, IDoc, IDoc Status 18, IDoc Status 41, Outbound IDoc, Inbound IDoc, Automatic IDoc Confirmation, IDoc Reprocessing, /PACG/ECM_COCKPIT2, Proaxia Integration, SAP Field Service Management, FSM Integration, SAP FSM, SAP ERP, ERP Integration, Connector, Message Broker, External Confirmation, ARFCSSTATE Buffering, Fully Buffered, Table Buffering, ST05, SQL Trace, LUW, Multi-Application Server, Queue Processing, RFC Queue, RFC Scheduler, SAP Standard Buffering, SAP Integration Suite, Integration Failure, Confirmation Flow, Middleware, SAP NetWeaver, SAP KBA 2000002 , KBA , CEC-SRV-FSM-ERP , FSM Connector for SAP ERP , BC-MID-RFC-QT , Queued RFC (qRFC) and transactional RFC (tRFC) , BC-MID-ALE , Integration Technology ALE , Problem