Results for “chv_create_authorizations”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CHV_CREATE_AUTHORIZATIONS is a PL/SQL package body owned by the APPS schema that supports the buyer authorization functionality within Oracle Purchasing and the supplier scheduling components of Oracle E-Business Suite. Its documented status is VALID, and its API classification is OTHER, indicating that it is not a public, documented open interface but rather an internal utility package used by the application to generate and maintain authorization records. In the context of Oracle EBS 12.1.1 and 12.2.2, the package operates alongside the CHV (Purchasing supplier scheduling and authorization) schema objects, creating the authorization rows that control whether purchasing documents and item orders may proceed. The package is a dependency-level object: it references standard application tables and is referenced by two other packages, but it is not itself referenced by any additional database object per the ETRM dependency report.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions within the package body. The documented name is NAME, which reflects the internal identifier carried in the source metadata export. The package is structured so that its callable units are responsible for the creation of authorization records: they evaluate the relevant purchasing or scheduling context and insert or update the corresponding rows in the authorization table. Because the package body is classified as OTHER and its parameter lists are not exposed in the ETRM extract, the procedures should be treated as internal entry points invoked by the parent package and by dependent application code rather than as a supported public API. Customizations should not call these units directly without validating the exact signature against the installed source.

Tables Accessed

The package reads and writes two documented application tables through APPS synonyms:

• CHV_AUTHORIZATIONS — the primary target table. Rows are created and maintained here to record buyer or scheduling authorizations that permit downstream purchasing activity.
• CHV_ITEM_ORDERS — the item order and scheduling table consulted to determine which orders require authorization and to link the resulting authorization back to the originating item order.

Additional dependencies visible in the dependency listing include FND_GLOBAL, used to establish the application, responsibility, and user context required for WHO column population and security, and PO_MESSAGE_S, the Purchasing message table used to store or retrieve user-facing messages. Standard SYS dependencies (STANDARD) indicate use of standard PL/SQL constructs. No other application tables are recorded as referenced by this package body.

Usage Notes

CHV_CREATE_AUTHORIZATIONS is typically invoked by the application rather than by end users directly. The most common invocation paths are:

• Dependent packages — the metadata confirms this package is referenced by two other packages, which call its procedures as part of a larger authorization workflow.
• Purchasing and supplier scheduling forms — authorization creation is triggered when item orders or purchasing documents are processed, using the FND_GLOBAL context that the calling form has already established.
• Concurrent or batch processing — where authorization records must be mass-generated, the parent package that wraps this logic is scheduled rather than calling the body directly.

Because the package uses FND_GLOBAL, any invocation from custom code must set the application and responsibility context before calling, or the WHO columns and messages produced via PO_MESSAGE_S will be incorrect. The package is not referenced by any database object, so there is no trigger, view, or constraint that depends on it; this makes it relatively safe to review for customization, but changes should still be avoided inside the seeded APPS schema. In 12.2.2, the ETRM record shows the same owner, status, and table dependencies as in 12.1.1, so behavior across the two releases is expected to be consistent.