SAP Knowledge Base Article - Public

3795690 - Automatic (Pagination) extraction fails with ExtractionJob failed error when the delta sub-query returns no results in SAP Process Intelligence

Symptom

  • Extraction fails with ExtractionJob failed for a table configured with Automatic (Pagination) where the delta sub-query uses a MIN or MAX aggregate (for example, CDPOS using a CDHDR-based sub-query)
  • The error cause field is empty in the pipeline run log
  • The On-Premises Package log contains: Caused by: java.util.NoSuchElementException at AggregationFuncHandler.applyAggregateFunction
  • Other tables in the same pipeline that use a different delta strategy (for example, a direct date-column sub-query) succeed
  • The issue occurs on days when no records match the delta sub-query filter for the extraction window

Cause

On-Premises Package versions prior to v1.1839.0 did not handle the case where an Automatic (Pagination) MIN or MAX aggregate sub-query returns zero rows. Instead of completing with zero rows extracted, the extraction failed with an unhandled exception.

Resolution

  1. Upgrade the On-Premises Package to version v1.1839.0 or later. From this version onwards, a zero-row result from the delta sub-query is handled correctly and the extraction completes with zero rows extracted — the expected outcome when no records match the delta filter for the extraction window.
  2. Upgrading to the latest available version is recommended.

Keywords

soe, ExtractionJob failed, NoSuchElementException, AggregationFuncHandler, Automatic Pagination, P0, CDPOS, CDHDR, delta extraction, empty result set, On Premises Package, OPP, sub-query, MIN, MAX, extraction error, empty cause , KBA , BPI-SIG-PI-INT , Integration / Schedules / SQL Filter / Delta criteria , Known Error

Product

SAP Signavio Process Intelligence all versions