Search Results g_applsys_schema




Overview
Explore in AI Chat

Overview

OE_PC_CONC_REQUESTS is a technical PL/SQL package body in the Oracle E-Business Suite Order Management (OE) module. It supports the Order Capture / Product Catalog (PC) feature set by providing runtime services for the dynamic creation, compilation, and validation of PL/SQL packages used in order capture validation processing. The package operates as a utility and infrastructure component rather than as a business-facing API; it is not classified as a public API (API classification: OTHER) and is referenced by no other packages according to ETRM metadata. Its primary responsibility is to take a package definition held in a temporary buffer and instantiate it as a compiled database package, then report any compilation errors. This pattern is common in Oracle EBS where runtime-configurable validation logic must be generated and deployed dynamically. The package includes the version string $Header: OEXPCRQB.pls 120.0 2005/05/31 23:37:04 appldev noship $, indicating it has existed in a stable form across multiple EBS releases, including 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents one procedure or function associated with this package: CREATE_VALIDATION_PACKAGES. Based on the package's internal structure, this routine is responsible for orchestrating the generation and validation of PL/SQL validation packages at runtime. Internally, the package body contains several local procedures that support this work:

  • Put_Line — A logging utility that writes diagnostic text to the concurrent manager log file when the package is executing in concurrent request mode. It uses FND_FILE.PUT_LINE to direct output to the log, and determines concurrent mode by checking whether the CONC_REQUEST_ID profile value is set.
  • Init_Applsys_Schema — This is the routine associated with the user's search term "init_applsys_schema." It resolves the APPLSYS schema name at runtime by calling FND_INSTALLATION.GET_APP_INFO for the FND product, caching the result in the package-level variable G_APPLSYS_SCHEMA. This is necessary because dynamically generated DDL may need to qualify objects with the correct APPLSYS schema prefix.
  • Create_Package_From_Buffer — Accepts a buffer (LONG), package name, and a flag indicating whether the object is a package specification or body. It iterates through the buffer line by line, invokes AD_DDL.BUILD_PACKAGE to construct the package, and queries USER_ERRORS to capture compilation failures.

The documented CREATE_VALIDATION_PACKAGES procedure likely calls these helpers in sequence: resolve the APPLSYS schema, build the validation package from buffered source, compile it via AD_DDL, and report errors.

Tables Accessed

ETRM metadata identifies three tables referenced through APPS synonyms:

  • OE_PC_VALIDATION_PKGS — The primary data store for validation package definitions. It is read to obtain the source text or configuration used to generate the runtime validation package.
  • AD_DDL — The Oracle Application Object Library DDL utility. It is invoked, not read as a data table, to build and compile PL/SQL source at runtime.
  • USER_ERRORS — Queried via a declared cursor to detect and report PL/SQL compilation errors for the generated package. The cursor filters by package name and type (PACKAGE or PACKAGE BODY) based on the p_is_pkg_body flag.

Usage Notes

OE_PC_CONC_REQUESTS is typically invoked indirectly, most commonly from a concurrent program or an administrative process that regenerates order capture validation logic. The name itself suggests concurrent (CONC) execution. The Put_Line procedure's dependency on CONC_REQUEST_ID confirms that the package is designed to run under the concurrent manager, writing progress and diagnostic messages to the request log. Because it performs DDL (package creation and compilation), it should be invoked by a privileged account such as APPS with the necessary privileges. In Oracle EBS 12.1.1 and 12.2.2, the package remains valid; however, administrators invoking it under the 12.2 online patching architecture should be aware that DDL operations against the APPLSYS schema during an active patch cycle may be restricted. The routine is not part of a public API contract and should not be called from custom forms or concurrent programs without Oracle support guidance.