Search Results create_validation_packages

Overview

APPS.OE_PC_CONC_REQUESTS is a standalone PL/SQL package in the Oracle E-Business Suite Order Management (OE) module. Its name associates it with the Order Capture (OE_PC) family of program units used by Oracle's configuration and validation infrastructure, and the "_CONC_REQUESTS" suffix indicates its role as a concurrent-request-side utility: it generates or refreshes the PL/SQL validation packages that the Order Capture validation framework depends upon. The package is declared AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, a common pattern for packages that must read and write data dictionary objects under the caller's security context. The header comment ($Header: OEXPCRQS.pls 120.0 2005/05/31 ...) shows the source has remained at version 120.0 since the 11i era, and it is shipped unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes a single documented procedure:

• CREATE_VALIDATION_PACKAGES — The sole public entry point. It accepts standard concurrent-program OUT parameters (ERRBUF and RETCODE) so that it can be registered and executed as an Oracle EBS concurrent program. Its purpose is to build, or rebuild, the generated PL/SQL validation packages used by Order Capture validation logic. Because the metadata exposes only the signature and not the body, no further parameter detail is documented; the two OUT parameters follow the conventional FND_CONCURRENT contract, where ERRBUF returns a completion/error message and RETCODE returns success or failure to the concurrent manager.

No other procedures or functions are declared in the specification, so the package is intentionally narrow in scope.

Tables Accessed

ETRM documents three objects reached through APPS synonyms:

• OE_PC_VALIDATION_PKGS — The driving table. It stores the definition and metadata of the validation packages that the procedure compiles or generates. The procedure reads these rows to determine which packages require creation or refresh.
• AD_DDL — The Applications DDL interface table used to submit dynamic DDL/DML statements to the database. The generated validation packages are built by inserting the appropriate CREATE OR REPLACE PACKAGE statements into AD_DDL and then executing them.
• USER_ERRORS — The data dictionary view of compilation errors for the current user's stored objects. After DDL execution, the procedure queries USER_ERRORS to confirm that the newly created validation packages compiled cleanly, and it can surface those errors through the ERRBUF parameter.

The read/write pattern is therefore: read definitions from OE_PC_VALIDATION_PKGS, submit generated code through AD_DDL, then validate the result against USER_ERRORS.

Usage Notes

Because the package is a concurrent-request utility, it is normally invoked by the concurrent manager rather than called directly from forms. The typical deployment is a host or PL/SQL concurrent program registered against OE_PC_CONC_REQUESTS.CREATE_VALIDATION_PACKAGES, scheduled after patches, upgrades, or changes to Order Capture validation rules, so that the derived validation packages are regenerated against current metadata. It may also be called from custom PL/SQL or installation scripts that need to force regeneration during a migration or setup step. The procedure should not be run concurrently with other sessions that are compiling or using the same validation packages, since AD_DDL submissions and the subsequent compile check are not designed for parallel execution. ETRM reports that no other packages in the E-Business Suite reference OE_PC_CONC_REQUESTS, confirming it is a top-level utility with no internal callers and is therefore invoked only explicitly by administrators or by its registered concurrent program.