several DUMP (ST22) with error , MESSAGE_TYPE_X, SAPLARFC, RFC cannot be used for classic qRFC

[christoph_ostrop]

after upgrade to S/4Hana-2020-03, we got several DUMPs (ST22)

==============

How to correct the error

If the error occurs in one of your own ABAP programs or an SAP program that you have modified, try to correct the error yourself.

If the error occurs in a non-modfied SAP program, you might be able to find a solution in the SAP Notes system. If you have access to the SAP

Information on where terminated

The termination occurred in ABAP program or include "SAPLARFC", in "TRFC_SET_QUEUE_RECEIVER_LIST".

The main program was "RMCEXUP1".

In the source code, the termination point is in line 38 of include "LARFCU25".

include "LARFCU25". Program "SAPLARFC" was started as a background job.

Job name....... LIS-BW-VB_APPLICATION_45_100

Notes system, check there first using the following keywords:

"MESSAGE_TYPE_X"

"SAPLARFC" bzw. LARFCU25

"TRFC_SET_QUEUE_RECEIVER_LIST"

If you cannot solve the problem yourself, please send the following information to SAP:

==============

(en) Error analysis

Short text of the error message:

Destination XTRACTDWT cannot be used for classic qRFC

Long text of the error message:

Technical information about the message:

Message class....... SR

Number.............. 320

Variable 1.......... XTRACTDWT

==============

(de) Fehleranalyse

Kurztext der Fehlermeldung:

Die Destination XTRACTDWT ist für den klassischen qRFC nicht verwendbar!

Langtext der Fehlermeldung:

Technische Informationen zur Nachricht:

Nachrichtenklasse... SR

Nummer.............. 320

Variable 1.......... XTRACTDWT

==============

i guess, it is something with V3-booking => BW-Delta-Queue, ???

JobName Sp Job CreatedB Status Start date Start Tim

LIS-BW-VB_APPLICATION_03_100 xxxxxxxx Finished 06.05.2022 15:20:11

LIS-BW-VB_APPLICATION_11_100 xxxxxxxx Canceled 06.05.2022 15:20:11

LIS-BW-VB_APPLICATION_03_100 xxxxxxxx Finished 06.05.2022 15:18:11

LIS-BW-VB_APPLICATION_11_100 xxxxxxxx Canceled 06.05.2022 15:16:02

LIS-BW-VB_APPLICATION_45_100 xxxxxxxx Canceled 06.05.2022 15:15:05

LIS-BW-VB_APPLICATION_13_100 xxxxxxxx Canceled 06.05.2022 15:12:11

==============

Job log overview for job: LIS-BW-VB_APPLICATION_11_100 / 1510112X

Date Time Message text Message class Message no. Message type

06.05.2022 15:20:11 Job LIS-BW-VB_APPLICATION_11_100 1510112X started 00 516 S

06.05.2022 15:20:11 Step 001 started (program RMBWV311, variant , user ID xxxxxxxx) 00 550 S

06.05.2022 15:20:11 Queue processing started (MCEX11, 1.000, , 0) MCEX 153 S

06.05.2022 15:20:11 Extraction queue processing started MCEX11 with 5 LUWs MCEX 154 S

06.05.2022 15:20:11 Internal session terminated with a runtime error MESSAGE_TYPE_X (see ST22) 00 671 A

06.05.2022 15:20:11 Job canceled 00 518 A

==============

any idea?

[christoph_ostrop]

additional info:

=======================================================
i recognized a difference in bgRFC-Destination (SM59)

but not in XTRACTDWx RFC, the difference is in bgRFC_<SID> RFC-Destination:

still on S/4Hana-1909-02, but upgrade planned:
PROD-System (ERP100) SM59 RFC-Destination bgRFC_ERP
Serialisierung => C = classic serializer
Outbound bgRFC Verhalten => 2 = convert from outbound bgRFCC to qRFC

after upgraded to S/4Hana-2020-03:
TEST-system (ERT100) SM59 RFC-Destination bgRFC_ERT
Serialisierung => C = classic serializer
Outbound bgRFC Verhalten => 1 = no outbound bgRFC

=======================================================

may this cause such an issue ?

[christoph_ostrop · Accepted solution]

after opening a ticket, we got the answer from SAP-Support:

during upgrade to S/4Hana-2020-03, SAP had changed the RFC-processing,

https://launchpad.support.sap.com/#/notes/2711163 
https://launchpad.support.sap.com/#/notes/2315100

therefor during S/4Hana-2020 Upgrade there were several existing RFCs changed automatically

from (before in S/4Hana-1909) 'Convert outbound bgRFC to qRFC'

were changed to (now in S/4Hana-2020) => to 'No Outbound bgRFC'

======

in our case, we have (external Software) and some steps to generate RFCs after upgrade,

but RFC creating default-value is still the old one 'Convert outbound bgRFC to qRFC'

so the new generated RFCs have the wrong setting in serializer-option (in default)

======

after changing that serializer-option to (now in S/4Hana-2020) => to 'No Outbound bgRFC'

=> and the execution of that pgm (see DUMP) runs fine again! 🙂

Thanks

[raymond_giuseppi]

Call SM59 and display your RFC destination, in the 'Select Protocol' block, select the 'Classic with tRFC' option.

[christoph_ostrop]

Hi, Raymond,

thanks for your answer, but it actually has this configuration

(in production on S/4Hana-1909-02 works fine, in Test-QS-System on S/4Hana-2020-03 issue comes up, it does not work)

both system had identically configuration: RFC-Destination => select protocoll:

Serializer => C = classic serializer

Outbound bgRFC Behavior => 2 = convert outbound bgRFC to qRFC

======================================================

in S/4Hana-2020, there are only this options to select: (for serialisation)

B = basXML serializer

C = classic serializer

F = fast serializer

O = force basXML serializer

======================================================

the option mentioned in sapnote 2571259 => https://me.sap.com/notes/0002571259

is not shown anymore "classic with tRFC" (see possible options above)

or is the same as "classic serializer"

======================================================