SAP Knowledge Base Article - Preview

3737363 - SM12 shows persistent '!enq_context_exists' lock entries with context owner BO (BC-ESI-ESF-GW)

Symptom

  • Multiple exclusive lock entries remain in SM12 with table name "!ENQ_CONTEXT_EXISTS".
  • Locks show context owner "BO" and context component "BC-ESI-ESF-GW".
  • Lock arguments are of the form "BO...".
  • Session key is displayed, but no active user sessions are present when locks are observed.
  • Locks appear to persist beyond the end of the originating user session or work process.


Read more...

Environment

SAP S/4HANA

Product

SAP S/4HANA all versions

Keywords

SM12, !ENQ_CONTEXT_EXISTS, durable locks, RAP, draft, enqueue lock, BC-ESI-ESF-GW, context owner BO, I_SLSPRICINGCONDITIONRECORDTP, lock persistence, lock expiry, relative to last change, P7D, orphaned locks perception, S/4HANA locks , KBA , BC-ESI-ESF-GW , REST Integration für CDS und BOPF via SADL , Bug Filed

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.