3398189 - Lock issues during SUM S/4HANA conversion due to wrong Enqueue Server in use

During an S/4HANA conversion using SUM, lock (Enqueue) issues occur. For example:

- Module:              MAIN_NEWBAS/Downtime II: Conversion, Main Import, XPRAs
- Phase Name:          MAIN_NEWBAS/PARRUN_MKPF1_S4
- Phase Log File:      PHASE_PARRUN.LOG
- Error Message:       Last error code set:
RFC system IED nr 60 function 'SUBST_START_REPORT_IN_BATCH'
RFC failed with code 5 key VARIANT_INSERT_VARIANT_LOCKED:
ID:DB Type:I Number:301 SAP_MKPF101

The command "sapcontrol -nr XX -function GetProcessList" (where "XX" is the instance number of the ASCSxx instance) reveals that the Standalone Enqueue Server v1 (ENSAv1) is still used:

> sapcontrol -nr XX -function GetProcessList

[date and time]
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, GREEN, Running, 2023 09 23 13:24:41, 1083:24:26, 9714
enserver, EnqueueServer, GREEN, Running, 2023 09 23 13:24:41, 1083:24:26, 9715

>

The ENSAv1 is not supported as of ABAP Release 7.55 (ABAP Platform 2020) / SAP kernel 781.

The Standalone Enqueue Server v2 (ENSAv2) must be used.

• ABAP Platform based product
• SAP S/4HANA

Standalone Enqueue Server 2, Standalone Enqueue Server, ENSAv1, ENSAv2 , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-CST-EQ , Enqueue , Problem