Search Results submit_subrequests
Overview
AD_CONC_UTILS_PKG is a utility package owned by the APPS schema in Oracle E-Business Suite, documented in ETRM for both release 12.1.1 and 12.2.2 with a status of VALID. The package body implements the compiled logic behind the AD_CONC_UTILS_PKG specification and forms part of the Applications DBA (AD) layer that governs concurrent processing and request submission within the EBS environment. Its classification in the ETRM repository is OTHER, indicating that it is an internal infrastructure utility rather than a published business API. The primary purpose of the package is to provide reusable programmatic constructs for submitting and managing concurrent requests, encapsulated in the single documented routine SUBMIT_SUBREQUESTS.
The dependency footprint recorded for this package body is deliberately narrow. It references only APPS.AD_CONC_UTILS_PKG itself and SYS.STANDARD, and the metadata explicitly notes that it is not referenced by any database object in the conventional sense, despite being identified by 36 other packages across the E-Business Suite. This pattern is characteristic of a low-level utility that is called dynamically or embedded at runtime rather than through hard-coded dependency chains.
Key Procedures and Functions
The documented interface exposes one callable routine:
- SUBMIT_SUBREQUESTS — the sole documented procedure in the package body. Its purpose is to submit a set of subordinate concurrent requests, enabling a parent process to spawn child requests as part of a multi-step concurrent workflow. This is the mechanism used when a concurrent program must break its work into smaller units that are dispatched independently to the concurrent managers, allowing parallel execution, staged processing, or dependent request chains. Specific parameter lists are not published in the ETRM metadata and are not reproduced here.
Because no additional procedures or functions are documented, the package should be treated as a focused, single-purpose utility rather than a broad toolkit.
Tables Accessed
The ETRM metadata for AD_CONC_UTILS_PKG does not enumerate any direct table references through APPS synonyms. This absence is consistent with the dependency record, which lists only the package itself and SYS.STANDARD. In practice, a routine such as SUBMIT_SUBREQUESTS operates against the concurrent processing data model managed by the Application Object Library. The canonical targets for such activity are FND_CONCURRENT_REQUESTS, which holds request definitions and status, and FND_CONCURRENT_PROGRAMS, which defines the executable programs being launched. Any table interaction is therefore expected to occur indirectly via FND APIs or through synonym resolution at runtime rather than through statically declared references.
Usage Notes
AD_CONC_UTILS_PKG is an internal Applications DBA utility. It is not intended as a supported public API and should not be invoked directly from customer forms or concurrent programs without careful review. Its practical consumption is by the 36 other packages that the ETRM repository identifies as callers, which rely on SUBMIT_SUBREQUESTS to orchestrate child request submission from within a larger processing flow. Typical invocation scenarios include Oracle Applications Manager operations, AD utilities that rebuild or validate the file system, and other AD-layer packages performing request fan-out.
From a support and patching perspective, the package body is maintained under the APPS schema and is subject to change with Applications DBA patches. Customizations should avoid direct modification of this object; where sub-request submission is required, developers should evaluate the documented EBS concurrent APIs and the FND_REQUEST interface instead. Because the package carries a VALID status in both 12.1.1 and 12.2.2, its behavior is expected to be consistent across those releases.
-
PACKAGE BODY: APPS.AD_CONC_UTILS_PKG
12.2.2
-
PACKAGE BODY: APPS.AD_CONC_UTILS_PKG
12.1.1
-
PACKAGE: APPS.AD_CONC_UTILS_PKG
12.1.1
-
PACKAGE: APPS.AD_CONC_UTILS_PKG
12.2.2
-
PACKAGE BODY: APPS.AMS_UPGRADE_RECORDS_PKG
12.1.1
-
PACKAGE BODY: APPS.AMS_UPGRADE_RECORDS_PKG
12.2.2
-
PACKAGE BODY: APPS.PAY_PRG_PROCESS_EVENTS
12.2.2
-
APPS.CST_SLA_UPDATE_PKG dependencies on STANDARD
12.1.1
-
APPS.CST_SLA_UPDATE_PKG dependencies on FND_GLOBAL
12.1.1
-
APPS.CST_SLA_UPDATE_PKG dependencies on STANDARD
12.2.2
-
APPS.PAY_BALANCE_FEED_DEL_PKG dependencies on STANDARD
12.2.2
-
APPS.PAY_PRG_PROCESS_EVENTS dependencies on STANDARD
12.2.2
-
PACKAGE BODY: APPS.CST_SLA_UPDATE_PKG
12.1.1
-
APPS.PAY_SLA_UPDATE_PKG dependencies on STANDARD
12.2.2
-
APPS.AMS_UPGRADE_RECORDS_PKG dependencies on AD_CONC_UTILS_PKG
12.1.1
-
APPS.AMS_UPGRADE_RECORDS_PKG dependencies on AD_CONC_UTILS_PKG
12.2.2
-
PACKAGE BODY: APPS.CST_SLA_UPDATE_PKG
12.2.2
-
APPS.PAY_SLA_UPDATE_PKG dependencies on STANDARD
12.1.1
-
APPS.PAY_PRG_PROCESS_EVENTS dependencies on FND_GLOBAL
12.2.2
-
APPS.AD_CONC_UTILS_PKG dependencies on AD_CONC_UTILS_PKG
12.1.1
-
APPS.PAY_BALANCE_FEED_DEL_PKG dependencies on FND_GLOBAL
12.2.2
-
APPS.AD_CONC_UTILS_PKG dependencies on AD_CONC_UTILS_PKG
12.2.2
-
PACKAGE BODY: APPS.PAY_BALANCE_FEED_DEL_PKG
12.2.2
-
APPS.PAY_SLA_UPDATE_PKG dependencies on FND_GLOBAL
12.1.1
-
APPS.PAY_SLA_UPDATE_PKG dependencies on FND_GLOBAL
12.2.2
-
PACKAGE BODY: APPS.PAY_SLA_UPDATE_PKG
12.1.1
-
PACKAGE BODY: APPS.PAY_SLA_UPDATE_PKG
12.2.2
-
APPS.PAY_SLA_UPDATE_PKG dependencies on FND_API
12.1.1
-
APPS.PAY_PRG_PROCESS_EVENTS dependencies on FND_API
12.2.2
-
APPS.PAY_BALANCE_FEED_DEL_PKG dependencies on FND_API
12.2.2
-
APPS.PAY_SLA_UPDATE_PKG dependencies on FND_API
12.2.2
-
APPS.CST_SLA_UPDATE_PKG dependencies on FND_API
12.1.1
-
APPS.CST_SLA_UPDATE_PKG dependencies on FND_FILE
12.2.2
-
APPS.CST_SLA_UPDATE_PKG dependencies on FND_API
12.2.2