SAP Knowledge Base Article - Public

3802887 - Custom Application Job template running slow on S/4HANA Cloud Public Edition – ABAP Profiler trace collection

Symptom

  • A custom Application Job template takes significantly longer to complete than its established baseline runtime
  • The job finishes with status Finished or Canceled/Error, but the job log contains no explicit error message indicating the cause of the delay
  • The duration of one or more job steps has increased substantially compared to previous executions (e.g., from ~2 hours to 5–7 hours)
  • The issue may be intermittent — some executions complete within normal time while others are significantly slower
  • The custom job template is based on a class implementing the interface IF_APJ_RT_RUN
  • No infrastructure alert or system-wide performance incident has been raised

Environment

  • Product: SAP S/4HANA Cloud Public Edition
  • Development environment: ABAP Development Tools (ADT) for Eclipse
  • Deployment type: Public Cloud

Reproducing the Issue

The issue cannot be reliably reproduced on demand as it may be dependent on data volume, system load, or logic conditions at runtime. To capture data for analysis, proceed directly to the Resolution section to configure and activate an ABAP Profiler trace before the next scheduled job execution.

Cause

The performance bottleneck resides in the custom ABAP business logic of the class implementing IF_APJ_RT_RUN. The EXECUTE method is the entry point called at runtime. Common causes include:

  • Unoptimized or missing database indexes causing full table scans as data volume grows
  • Inefficient internal table processing or nested loops over large datasets
  • Missing buffering or repeated execution of expensive SELECT statements
  • External service calls or RFC calls that block job progress
  • Significant growth in the volume of records processed since the baseline was established

The root cause cannot be determined without a runtime trace. The ABAP Profiler in ADT is the correct tool to identify runtime-intensive statements in SAP S/4HANA Cloud Public Edition.

Note: Transaction SAT (Runtime Analysis, component BC-DWB-TOO-RTA) is the on-premise equivalent but is not available in SAP S/4HANA Cloud Public Edition. For cloud systems, use the ABAP Profiler in ADT as described in the Resolution section.

Resolution

Step 1 — Open the ABAP Profiler in ADT

  1. Open ABAP Development Tools (ADT) for Eclipse
  2. Connect to your SAP S/4HANA Cloud system
  3. Navigate to Window → Show View → Other → ABAP Development → ABAP Profiler
  4. The ABAP Profiler view opens in your ADT workspace

Step 2 — Create a trace configuration

  1. In the ABAP Profiler view, click New Trace Configuration
  2. Set the Type to target the custom class implementing IF_APJ_RT_RUN used by your Application Job
  3. Configure the trace scope as needed (e.g., full statement-level trace for maximum detail)
  4. Save the configuration

Step 3 — Activate the trace and run the job

  1. Activate the trace configuration in the ABAP Profiler view
  2. Trigger the next scheduled execution of your custom Application Job (or wait for the next scheduled run)
  3. Once the job has finished, return to the ABAP Profiler view

Step 4 — Analyze the trace results

  1. Open the Trace Results section in the ABAP Profiler view
  2. Review the results to identify:
    • Runtime-intensive ABAP statements
    • Expensive database SELECT operations
    • The program call hierarchy and where execution time is concentrated
  3. Export the trace results using File → Export for sharing with SAP Support if further analysis is required

Step 5 — Share the trace with SAP Support

Attach the exported trace file to your SAP support case. Include the following context:

  • Job name and template name
  • Date and time of the traced execution
  • Duration of the traced execution vs. the normal baseline duration
  • Any known changes to data volume or system configuration since the slowdown began

For full step-by-step guidance on the ABAP Profiler, refer to SAP Help: Profiling ABAP Code

See Also

Keywords

Application Job, slow, performance, ABAP Profiler, ADT, IF_APJ_RT_RUN, EXECUTE method, runtime analysis, S/4HANA Cloud Public Edition, BC-SRV-APS-APJ, long running, job duration, trace collection, ABAP Development Tools , KBA , BC-SRV-APS-APJ , Catalog based application job , BC-ABA-LA , Syntax, Compiler, Runtime , How To

Product

SAP S/4HANA Cloud Public Edition 2602 ; SAP S/4HANA Cloud Public Edition 2608