Search Results conc_fail

Overview

APPS.AD_CONC_UTILS_PKG is a public utility package supplied by Oracle Application Object Library (AD) to standardize the behavior of concurrent programs that function as parent or driver processes. Its primary business function is to spawn a controlled set of parallel worker concurrent requests — subrequests — from a single parent concurrent program, allowing long or high-volume batch work to be divided across multiple concurrent managers and database sessions. The package does not itself perform any business logic; it exists solely to orchestrate submission of child requests and to provide the canonical completion-code constants used by EBS concurrent programs.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than as the definer. In practice it is invoked from custom or Oracle-supplied concurrent programs registered under the APPS schema, so effective privileges resolve against APPS and its synonyms. The documented source header places the package at version 115.0 (2004), indicating a stable, long-lived interface carried forward essentially unchanged into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents a single callable routine:

• SUBMIT_SUBREQUESTS — the driver procedure that submits a batch of worker concurrent requests. It accepts the standard concurrent-program OUT parameters for error buffer and return code, the concurrent program short name and application short name of the worker to be executed, a batch size controlling how many logical units each worker processes, the number of parallel worker requests to submit, and up to seven additional positional arguments (arguments 4 through 10) passed through to the worker program, each defaulting to null. Internally it calls the FND submission APIs; the source comment directing that CHR(0) not be altered reflects the requirement that concatenated argument strings retain the FND_SUBMIT delimiter behavior.

The package additionally declares three constants that are the origin of the search term conc_fail:

• CONC_SUCCESS CONSTANT NUMBER := 0 — successful completion.
• CONC_WARNING CONSTANT NUMBER := 1 — completed with warning.
• CONC_FAIL CONSTANT NUMBER := 2 — completed with error / failure.

These constants let a parent program compare X_retcode against symbolic names rather than hard-coded integers, which is the recommended practice for any program coordinating subrequests.

Tables Accessed

The ETRM metadata records no direct table references for this package through APPS synonyms, which is consistent with its design: all persistence is delegated to the FND concurrent processing APIs and their underlying FND tables. The worker requests it creates are recorded in the standard concurrent request infrastructure, and the package's observable effects are visible through the concurrent manager request screens and FND_CONCURRENT_REQUESTS rather than through direct DML in this package.

Usage Notes

AD_CONC_UTILS_PKG.SUBMIT_SUBREQUESTS is typically invoked from the PL/SQL body of a custom parent concurrent program executed by the Concurrent Manager, or from a form or custom code that needs to fan out work programmatically. A calling program normally executes SUBMIT_SUBREQUESTS, then calls FND_CONCURRENT.WAIT_FOR_REQUEST to monitor the children, aggregates their individual return codes, and finally maps the aggregate to CONC_SUCCESS, CONC_WARNING, or CONC_FAIL before returning to the Concurrent Manager. The referenced-by count of 36 other packages confirms widespread internal reuse, so the package should be treated as a supported API. Its interface is stable across 12.1.1 and 12.2.2, and Oracle's proprietary/confidential notice in the source documentation means the body should not be modified.