SAP Clean Core ABAP Daemons, Long-Running Background Workers & PCP Messaging Guide

1. The Limitations of Classic Background Execution

In traditional SAP development, background workloads rely on batch jobs (SM36/SM37). While suitable for nocturnal mass processing, batch jobs have significant drawbacks for modern real-time architectures:

• Scheduling Lag: Starting a batch job takes several seconds of scheduler overhead.
• Dialog Timeouts: Triggering asynchronous RFCs (STARTING NEW TASK) from user sessions is vulnerable to dialog work process timeout limits.
• Session Fragility: When user sessions terminate, child tasks are often abruptly severed.

2. Anatomy of the ABAP Daemon Framework

ABAP Daemons (introduced in modern SAP NetWeaver and standard in ABAP Cloud) are event-driven, persistent processes executing in specialized non-dialog background sessions:

• Inherit from cl_abap_daemon_ext_base.
• Run indefinitely on the application server instance until explicitly stopped.
• React to asynchronous Push Channel Protocol (PCP) messages sent from any user session or application job.
• Feature automated restart and error recovery hooks (on_error).

3. The Push Channel Protocol (PCP) Interface

To deliver instructions to a running daemon, callers use if_ac_message_type_pcp. Unlike plain strings, PCP messages provide structured key-value headers and typed payloads:

DATA(lo_msg) = cl_ac_message_type_pcp_factory=>create_message( ).
lo_msg->set_field( i_name = 'EVENT_TYPE' i_value = 'ORDER_CREATED' ).
lo_msg->set_text( '{"orderId": "1002931"}' ).

cl_abap_daemon_client_manager=>send(
  i_class_name = 'ZCL_EVENT_DAEMON'
  i_name       = 'INSTANCE_01'
  i_message    = lo_msg
).

4. Enterprise Use Cases in Clean Core

ABAP Daemons serve three primary architectural patterns in Clean Core landscapes:

1. Continuous Transactional Outbox Dispatching: Periodically sweeps local outbox tables every few seconds to publish events to SAP Event Mesh without batch job latency.
2. Shared Memory Cache Refresh: Reacts to cross-system invalidation events to pre-warm application server SHMA buffers.
3. WebSocket Stream Aggregation: Consumes high-frequency IoT sensor telemetry and aggregates readings before persisting to SAP HANA.