Search Results oe_oe_form_header




Overview
Explore in AI Chat

Overview

APPS.OE_OE_FORM_HEADER is a server-side PL/SQL package in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that supports the Oracle Order Management (ONT) order entry form (OEXOEORD) and its attendant business logic. The package encapsulates header-level processing for sales orders, including attribute defaulting, attribute changes, validation, row locking, cascading updates, and lookup-driven field derivation. It is classified under ETRM as an OTHER API, signifying that it is primarily an internal helper package rather than a public, standalone integration API. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling session, and it references Oracle Applications public APIs such as OE_ORDER_PUB for the canonical header record structures.

Within the order management flow, OE_OE_FORM_HEADER provides the form-level plumbing that prepares and persists the OE_ORDER_PUB.Header_Rec_Type, Header_Val_Rec_Type, and related DFF records before the core order API processes the transaction.

Key Procedures and Functions

The ETRM registry documents 28 procedures and functions. Representative entries include:

Parameter lists are intentionally omitted; naming and purpose reflect the documented metadata.

Tables Accessed

The package reads and writes through APPS synonyms. Customer and party information is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CONTACT_POINTS, and HZ_PHONE_FORMATS, supporting ship-to and invoice-to resolution and contact data. Accounting and currency context comes from AR_SYSTEM_PARAMETERS, AR_SYSTEM_PARAMETERS_ALL, and GL_DAILY_CONVERSION_TYPES. Descriptive flexfield structures are read from FND_ID_FLEX_STRUCTURES, and lookup values from FND_LOOKUP_VALUES. User identity is obtained from FND_USER, and AD_BUGS supports internal diagnostic and patch-tracking logic.

Usage Notes

OE_OE_FORM_HEADER is typically invoked indirectly by the Order Management order entry form rather than called directly by external integrations. Customizations that extend the order entry form—such as additional header-level validations, defaulting rules for DFFs, or cascading attribute propagation—may invoke its procedures from form-level triggers or custom PL/SQL. Because it is categorized as OTHER and depends on form session state, custom code should treat it as an internal helper and prefer the public OE_ORDER_PUB APIs for external integrations, invoking OE_OE_FORM_HEADER only where form-equivalent behavior is required. The package is referenced by two other packages, reinforcing its role as a shared form-support layer. Debug procedures (SET_DEBUG_LEVEL, RESET_DEBUG_LEVEL) are useful when diagnosing header behavior during implementation or support.