SAP Knowledge Base Article - Preview

2732204 - MESSAGE_TYPE_X and CHECK_QIN_NAME_BGRFC

Symptom

The following DUMP occurs.:

Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           SAPLARFC
Application Component  BC-MID-RFC
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
Source Code Extract
*qrfc nicht verwendet werden
>>>>> MESSAGE x321(sr) WITH l_queue_name.
ENDIF.
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" "LARFCU01" "CHECK_QIN_NAME_BGRFC"


Read more...

Environment

  • Operating System independent
  • Database independent
  • SAP NetWeaver
  • SAP NetWeaver Application Server for SAP S/4HANA
  • ABAP PLATFORM - Application Server ABAP

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

RFC, Asynchronous RFC, Transactional RFC, qRFC, bgRFC, RFC_GDPR, RFC_STD, 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.