Search Results check_book_reqd_attributes

Overview

APPS.OE_CNCL_VALIDATE_HEADER is a server-side PL/SQL validation package within the Oracle Order Management (OM) module of Oracle E-Business Suite. It is classified under the ETRM taxonomy as an "OTHER" API, meaning it is not a public, callable business API intended for external integration, but rather an internal validation utility consumed by other Order Management packages. Its declared purpose, as reflected in the package signature and accompanying header comments, is to perform header-level validation logic during the order cancellation workflow — the "CNCL" in its name denotes cancellation. Specifically, the package governs whether a sales order header may be cancelled by evaluating required booking attributes, detecting duplicate customer purchase order references, and executing entity- and attribute-level validations against the order header data structure OE_ORDER_PUB.Header_Rec_Type. Because the package is declared AUTHID CURRENT_USER, it executes with the privileges of the invoking session rather than the definer, which is consistent with Oracle's standard validation-layer design for internal OM utilities.

Key Procedures and Functions

The ETRM metadata documents four callable units within this package.

• Check_Book_Reqd_Attributes — A procedure that validates the attributes required for booking in the context of a cancellation request. It accepts a header record of type OE_Order_PUB.Header_Rec_Type and returns a status indicator via an OUT NOCOPY parameter. This is the unit surfaced by the user's search term "check_book_reqd_attributes" and represents the package's principal public entry point.
• Is_Duplicate_PO_Number — A Boolean function that returns TRUE if the supplied customer purchase order number is already referenced on another order for the same customer. It evaluates the customer PO number against the sold-to organization and the current header identifier to detect duplicates.
• Entity — A procedure that performs entity-level validation on the order header, returning a status indicator and accepting a header record. Entity validation typically confirms that referenced entities such as customer accounts, sites, and contacts are valid and active.
• Attributes — A procedure that validates attribute-level data on the header record. It returns a status, accepts an IN OUT NOCOPY header record (allowing corrections to be propagated back to the caller), and accepts a validation level parameter defaulting to FND_API.G_VALID_LEVEL_FULL.

Tables Accessed

The package reads from a defined set of Order Management and Trading Community (HZ) tables, accessed through APPS synonyms. Customer master data is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_RELATE, HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES, HZ_CUST_SITE_USES_ALL, and HZ_PARTY_SITES. These support entity validation of the customer, account relationships, and site usage assignments tied to the order header. Order data is drawn from OE_ORDER_HEADERS and OE_ORDER_LINES, which underpin the duplicate PO number check and header status evaluation. DUAL is referenced for scalar evaluations. No documented table is written to; the package is predominantly a read-and-validate utility.

Usage Notes

OE_CNCL_VALIDATE_HEADER is invoked by two other packages according to the documented reference metadata, confirming its role as an internal dependency rather than a standalone API. It is typically called during the order cancellation flow — for example, when the Order Management responsibility processes a cancellation request and the header must be validated before the cancellation is committed. Because it is declared AUTHID CURRENT_USER and is not registered as a public API, custom extensions should not call it directly unless the calling code runs under an APPS-privileged session and accepts the risk of dependency on an internal, version-sensitive interface. Developers searching for "check_book_reqd_attributes" are most likely tracing cancellation validation errors or extending order cancellation logic; the recommended approach is to invoke the supported Order Management public APIs and allow this package to execute as part of the standard validation chain, rather than bypassing it.