Symptom
- MESSAGE_TYPE_X is reported with Function Module CHECK_QIN_NAME_BGRFC. Sample ST22 dump below:
- Category ABAP programming error
Runtime Errors MESSAGE_TYPE_X
ABAP Program SAPLARFC
Application Component BC-MID-RFC
Date and Time -
Short Text
The current application has intentionally triggered a termination with a short dump.Error analysis
Short text of the error message:
Inbound queue name Q******* cannot be used for classic qRFC
Long text of the error message:
Diagnosis
When you called classic qRFC, you used an inbound queue name that cannot be used with classic inbound qRFC. This queue name has been implemented for bgRFC instead.How to correct the error
If you have access to the SAP Notes system, check there first using the following keywords:" MESSAGE_TYPE_X " " SAPLARFC " bzw. LARFCU01 " CHECK_QIN_NAME_BGRFC "
412 * qrfc nicht verwendet werden
>>>>> MESSAGE x321(sr) WITH l_queue_name.
414 ENDIF.
Read more...
Environment
- SAP Basis ALE
- SAP NetWeaver
- SAP Web Application Server for SAP S/4 HANA
- ABAP PLATFORM - Application Server ABAP
Product
Keywords
SAPLARFC; TRFC_QIN_DEST_SHIP; SR 321; SR321, MESSAGE_TYPE_X, SAPLARFC, LARFCU01, CHECK_QIN_NAME_BGRFC. , KBA , BC-MID-RFC , RFC , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.