Search Results enable_conc_mod




Overview
Explore in AI Chat

Overview

PO_CLM_UPG_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The suffix _PVT indicates that the package is classified as private within Oracle's object taxonomy: it is not a published, supported integration point exposed to external callers, but rather an internal utility that supports Oracle's purchasing document lifecycle, specifically the Contract Lifecycle Management (CLM) and document styles upgrading path. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking user rather than the definer, which is typical for internal upgrade and maintenance routines that must respect the caller's security context when touching partitioned or multi-org purchasing data.

The name and shipped header ($Header: PO_CLM_UPG_PVT.pls 120.2.12020000.2 2013/02/10) indicate the package was introduced as a one-time or repeatable conversion mechanism associated with document styles and contract terms. Its principal role is to reconcile and prepare purchasing document records — headers, lines, distributions, and drafts — so that concurrent (parallel) processing can be enabled for the affected document style.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit.

  • ENABLE_CONC_MOD — Accepts a document style identifier (p_style_id, a NUMBER) and performs the enablement of concurrent processing mode for documents associated with that style. The procedure manipulates the purchasing document style definition and the related transactional records so the style can participate in concurrent or parallel processing. Because it takes only a style ID and returns nothing, it is designed to be invoked once per style, typically from an upgrade or setup driver.

No functions are documented, and no additional procedures are exposed in the package specification beyond ENABLE_CONC_MOD. Any other logic resides in the package body and is not part of the documented interface.

Tables Accessed

The package references a broad set of purchasing and attachment tables through APPS synonyms. The transactional core includes PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL, with their draft counterparts (PO_HEADERS_DRAFT_ALL, PO_LINES_DRAFT_ALL, PO_LINE_LOCATIONS_DRAFT_ALL) and PO_DRAFTS, indicating that both approved and in-progress (draft) documents are processed. Distribution-level data is handled through PO_DISTRIBUTIONS_ALL and PO_DISTRIBUTIONS_DRAFT_ALL. Style and contextual metadata is read from PO_DOC_STYLE_HEADERS and EGO_FND_DSC_FLX_CTX_EXT (the extensible attribute context table used by CLM document styles). Concurrency control relies on PO_ENTITY_LOCKS and PO_ENTITY_LOCKS_S, which store the locking records used to prevent conflicting updates during parallel processing. Supporting joins include PO_HEADERS_ALL_EXT_B for header extension attributes and FND_ATTACHED_DOCUMENTS for attachments tied to the affected documents. Collectively, these tables allow the procedure to propagate the concurrent-mode setting introduced at the style level down to existing header, line, location, and distribution records.

Usage Notes

As a private (PVT) package, PO_CLM_UPG_PVT is not intended for direct invocation by customer code, forms personalizations, or custom concurrent programs. It is referenced by one other Oracle package, which is the supported entry point that Oracle's own upgrade or maintenance logic calls. Typical invocation occurs during the CLM/document-style upgrade path in Release 12.2, where the calling routine iterates over document styles and passes each style ID to ENABLE_CONC_MOD.

Because the package uses AUTHID CURRENT_USER and manipulates draft and locking tables, callers must run under an APPS-equivalent privilege set with the correct multi-org context. Direct calls risk leaving entity locks or draft records inconsistent, and Oracle does not guarantee stability of private interfaces across patches. Administrators encountering this object during troubleshooting should treat it as an internal dependency and pursue the controlling concurrent program or patch driver rather than executing the procedure manually.