Search Results oe_blanket_header_security




Overview
Explore in AI Chat

Overview

OE_BLANKET_HEADER_SECURITY is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It is a server-side security and attribute-resolution utility for blanket sales agreements (blanket headers) in Oracle Order Management. Its central responsibility is to determine, for a given blanket header, which order-entry attributes are constrained (restricted or defaulted) through the Order Management Personalization (PC) framework, and to return the enforced value for each constrained attribute. In this way the package protects agreement integrity by preventing users from overriding terms that the blanket was defined to lock, such as price list, currency, payment terms, or shipping method.

The package status is documented as VALID in ETRM 12.2.2, indicating a compiled, functioning object. It is classified as OTHER rather than a public API, confirming that it is an internal utility invoked by other Order Management components rather than by external integrations. It is not referenced by any other database object directly, yet is documented as referenced by 83 other packages, reflecting broad internal consumption across order entry, versioning, and personalization logic.

Key Procedures and Functions

The documented interface exposes 74 subprograms. Most are single-attribute accessors that return the constrained or default value for a specific blanket header attribute. Representative accessors include ACCOUNTING_RULE, CONVERSION_TYPE, CUST_PO_NUMBER, DELIVER_TO_ORG, FREIGHT_TERMS, INVOICE_TO_ORG, INVOICING_RULE, ORDER_TYPE, PACKING_INSTRUCTIONS, PAYMENT_TERM, PRICE_LIST, SALESREP, SHIPPING_INSTRUCTIONS, SHIPPING_METHOD, SHIP_FROM_ORG, SHIP_TO_ORG, SOLD_TO_CONTACT, SOLD_TO_ORG, and TRANSACTIONAL_CURR. Each resolves the attribute value as restricted by the blanket agreement definition.

IS_OP_CONSTRAINED is the principal control function, testing whether a named operating-unit or order-entry attribute is constrained for the blanket. It gates the individual accessors, allowing callers to branch between a fixed agreement value and normal user entry. Parameter lists are not reproduced here; callers should obtain signatures from the ETRM reference or the data dictionary.

Tables Accessed

The confirmed table reference is OE_PC_CONSTRAINTS, reached through APPS synonyms. This table stores personalization constraint definitions, and the package reads it to discover which blanket header attributes are restricted and what values apply. The dependency list also cites the OE_PC_CONSTRAINTS_ADMIN_PVT package and OE_PC_GLOBALS, indicating shared access to the constraint administration and global setup. OE_AK_BLANKET_HEADERS_V and QP_LIST_HEADERS_VL appear among dependencies, supplying blanket header and price list views used during attribute resolution.

Supporting dependencies include FND_API, FND_GLOBAL, FND_MESSAGE, OE_BLANKET_PUB, OE_BLANKET_UTIL, OE_CODE_CONTROL, OE_DEBUG_PUB, OE_GLOBALS, OE_MSG_PUB, OE_SYS_PARAMETERS, and OE_VERSIONING_UTIL, which provide error handling, debug messaging, operating-unit context, and versioning support.

Usage Notes

OE_BLANKET_HEADER_SECURITY is invoked internally by Order Management forms and logic during blanket agreement entry, order capture, and versioning, where it enforces constrained attributes and supplies default values. It is called by OE_BLANKET_PUB and related packages rather than directly by end users. Because it is classified as OTHER with no public API contract, custom code should not depend on it. Developers needing constrained-value behavior should use the supported blanket public APIs, which call this package transitively. Behavior is consistent across EBS 12.1.1 and 12.2.2.