Search Results update_header_cache

Overview

OE_BLANKET_FORM_CONTROL is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It serves as the server-side form control layer for the Blanket Sales Agreement (blanket order) windows in Oracle Order Management. Its role is to bridge the Oracle Forms user interface for blanket agreements with the underlying Order Management public APIs, most notably OE_BLANKET_PUB and OE_ORDER_PUB, both of which appear as documented dependencies of the package.

Where OE_BLANKET_PUB encapsulates the business logic and DML for blanket headers and lines, OE_BLANKET_FORM_CONTROL provides the supporting infrastructure the Blanket Sales Agreements form requires: row-level insert, update, and delete handling; entity validation; attribute defaulting; security checks against header and line attributes and entities; caching; concurrency locking; and value conversion for LOV-driven fields. In EBS 12.1.1 and 12.2.2 the package is reported as VALID in the APPS schema, and it is referenced by the views OE_BLKT_HEADERS_HIST_V and OE_BLKT_LINES_HIST_V.

Key Procedures and Functions

The ETRM metadata documents 41 procedures and functions. The principal groups are:

• Value conversion: HEADER_VALUE_CONVERSION and LINE_VALUE_CONVERSION translate between form-level display values and their internal stored representations for header and line attributes.
• ID population: POPULATE_HEADER_VALUES_ID and POPULATE_LINE_VALUES_ID resolve and populate internal identifiers for header- and line-level values.
• DML and navigation support: INSERT_ROW, UPDATE_ROW, and DELETE_ROW manage the creation, modification, and removal of blanket agreement records from the form; DEFAULT_ATTRIBUTES applies standard defaulting; and PROCESS_OBJECT drives the overall processing of the current entity.
• Validation: VALIDATE_ENTITY performs entity-level validation prior to committing changes.
• Security checks: CHECK_SEC_HEADER_ATTR, CHECK_SEC_LINE_ATTR, CHECK_SEC_HEADER_ENTITY, and CHECK_SEC_LINE_ENTITY enforce attribute- and entity-level security for header and line records.
• Caching: UPDATE_HEADER_CACHE and UPDATE_LINE_CACHE maintain the form's cached header and line data.
• Concurrency: LOCK_HEADER_ROW and LOCK_LINE_ROW obtain row-level locks to prevent conflicting updates.
• Query support: LOAD_BLANKET_LINE_NUMBER and LOAD_BLANKET_HEADER_REC load blanket line numbering and header records, respectively, for form display.

Tables Accessed

The package references the following objects through APPS synonyms:

• OE_BLANKET_HEADERS / OE_BLANKET_HEADERS_ALL: the blanket agreement header tables that store agreement-level terms, customer, and pricing information.
• OE_BLANKET_LINES: the blanket agreement line tables holding item, quantity, and pricing details.
• OE_ORDER_HEADERS and OE_ORDER_LINES: the order tables that provide context for releases and references derived from blanket agreements.
• OE_TRANSACTION_TYPES_ALL: supplies the transaction type definitions validated against blanket agreements.
• PLITBLM: the standard EBS PL/SQL table used for temporary in-memory storage during form processing.

Usage Notes

OE_BLANKET_FORM_CONTROL is invoked primarily by the Oracle Forms-based Blanket Sales Agreements windows in Order Management, where it handles user-driven INSERT, UPDATE, and DELETE actions, validation, defaulting, and security enforcement. It is also referenced by the historical views OE_BLKT_HEADERS_HIST_V and OE_BLKT_LINES_HIST_V, and by two additional packages within the APPS schema. It should not normally be called directly by custom code; implementers extending blanket agreement functionality are advised to use the documented public APIs OE_BLANKET_PUB and OE_ORDER_PUB. Customizations that call this package directly risk breaking on patch application because its procedures are form-support internals rather than a published interface.