CapabilityIntegration & MessagingABAP Cloud

Async processing

Doing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.

Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP

Overview

SAP SHIPS

ABAP Cloud answers this with two released mechanisms: the Background Processing Framework (bgPF), built on bgRFC and paired with RAP to register a background process the moment RAP's own COMMIT WORK completes, and the application job framework, whose released CL_APJ_RT_API schedules a class for "long-running, repeated jobs" rather than short, frequent ones. A job scheduled from inside a RAP business object cannot use an immediate start, because the API itself performs an implicit COMMIT WORK.

Not covered: It stops at Standard ABAP's own asynchronous mechanisms: bgRFC and CALL FUNCTION ... STARTING NEW TASK are function-module features SAP-samples/abap-cheat-sheets places in Standard ABAP and not in ABAP for Cloud Development, and SM36 batch jobs run executable programs, which the same source states are not allowed in the restricted ABAP language scope.

SourceSAP-docs/btp-cloud-platform: Background Processing Frameworkchecked 2026-09-14

THE COMMUNITY ADDS

ABAP-PRC is a process framework on top of the two: it runs each processed object and each step as its own decoupled unit, through the background processing framework or as an application job, and a retry job resumes the objects that failed on a lock.

ABAP-PRC