Solution : https://service.sap.com/sap/support/notes/869628 (SAP Service marketplace login required)
Summary :
During a qRFC processing, data operations at TRFCQOUT and transaction status issues in SMQ1 are encountered primarily due to timing and sequence of function calls. Key functions such as ARFC_END_TRANSACTION and ARFC_END_VB influence the transaction statuses, which can result in problematic queuing behaviors such as WAITUPDBA. The execution problems mainly relate to the handling of commitments and updates within SAPMSSY4, prompting cancellation or incorrect processing orders. Correction requires updates to these function modules and their associated mechanisms in specific R/3 and WAS versions to ensure proper transaction sequencing and system stability.
Key words :
qrfc calls retain status waitupdba, database table trfcqout, processes qrfc calls, web application server 6, function module trfc_set_background_sequence, arfcsstatefunction modules arfc_end_transaction, arfc_end_vbreport sapmssy4 reason, function modules arfc_end_transaction, attached correction instructions, function module arfc_end_vb
Related Notes :
| 925855 | "Stopped CPIC" when you use tRFC or qRFC and local update |
| 913330 | tRFC LUWs are not created |
| 902638 | No load possible from the CRM system to the R/3 system |
| 901878 | Information IDoc: Sent, but did not arrive |
| 459517 | FAQ: Business Warehouse (BW) in Purchasing |