Results for “lock_header_row”

8 results




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

Overview

APPS.OE_BLANKET_FORM_CONTROL is a forms-support PL/SQL package body that underpins the Oracle Order Management blanket sales agreement (blanket order) maintenance form in Oracle E-Business Suite 12.1.1 and 12.2.2. The package implements the "form control" layer that the Blanket Sales Agreements window calls to translate form field values into the underlying Order Management public API record structures, enforce entity validation, manage partial-row persistence, and apply header- and line-level security. It is classified in ETRM as an OTHER API, indicating it is not intended as a standalone public integration API but rather as an internal engine driving the OA Framework / Forms UI.

The naming and the "blank kit form" association arise because the same form-control mechanism handles the entry and maintenance of blanket agreement headers and their associated lines, including configurations where a blanket line is a kit or model with components. The package relies on the record types exposed by OE_BLANKET_PUB and OE_ORDER_PUB, converting form input into those canonical structures before persisting through the base tables.

Key Procedures and Functions

Tables Accessed

The package operates against the core blanket agreement and order tables through APPS synonyms. It reads and writes OE_BLANKET_HEADERS and OE_BLANKET_HEADERS_ALL for agreement header data, and OE_BLANKET_LINES for line-level agreement data. It references OE_ORDER_HEADERS and OE_ORDER_LINES, reflecting the shared order capture model used for blanket orders. OE_TRANSACTION_TYPES_ALL supplies order type validation and defaulting, while PLITBLM is the standard multi-language / translation support table used for descriptive attributes. These accesses align with the convert-validate-persist flow driven by OE_BLANKET_PUB.

Usage Notes

OE_BLANKET_FORM_CONTROL is invoked primarily from the Oracle Order Management Blanket Sales Agreements form and is referenced by two other packages. It should not normally be called directly by customers; supported integration should use the documented OE_BLANKET_PUB APIs. Custom extensions that must intervene during blanket order entry typically do so through form personalization or by wrapping OE_BLANKET_PUB rather than calling this form-control package, which assumes an active Forms session, session-level security context, and the package globals being initialized before use.