Results for “oe_order_pub”

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

Overview

APPS.OE_Order_PUB is the public PL/SQL package body that exposes Oracle Order Management's core order-processing API in Oracle E-Business Suite 12.1.1 and 12.2.2. In the ETRM classification it is registered as a PUB API, meaning it is intended for external invocation by forms, concurrent programs, Oracle's own dependent packages, and customer-written extensions. The package encapsulates the validated business rules used to create, update, book, and otherwise manipulate order headers and their associated lines, price adjustments, sales credits, and lot/serial assignments within the Order Management transactional model.

A defining characteristic of the package is its use of the FND_API "G_MISS" convention. The OE_Order_PUB body defines a family of record-level constructors that return fully populated record structures whose every attribute is initialised to the sentinel values FND_API.G_MISS_CHAR, FND_API.G_MISS_NUM, or FND_API.G_MISS_DATE. Callers use these constructors so that the API layer can distinguish attributes the caller deliberately intends to set from those it wishes to leave untouched during an update, which is essential to the partial-update semantics of the Order Management schema.

Key Procedures and Functions

The documented interface comprises 43 procedures and functions, of which the metadata excerpt most prominently identifies the G_MISS record constructors. These are grouped by the entity they populate:

• G_MISS_CUSTOMER_INFO_REC — returns an initialised customer information record.
• G_MISS_HEADER_REC — returns the header-level record; the excerpt shows it seeding fields such as accounting_rule_id, agreement_id, attribute1 through attribute20, booked_flag, cancelled_flag, conversion rate attributes, cust_po_number, and audit columns. This is the record type that underpins the header_payment_tbl_type usage sought by the searcher.
• G_MISS_HEADER_ADJ_REC, G_MISS_HEADER_PRICE_ATT_REC, G_MISS_HEADER_ADJ_ATT_REC, G_MISS_HEADER_ADJ_ASSOC_REC, G_MISS_HEADER_SCREDIT_REC — header adjustment, pricing attribute, adjustment attribute, adjustment association, and sales credit records.
• GET_G_MISS_LINE_REC and G_MISS_LINE_ADJ_REC, G_MISS_LINE_PRICE_ATT_REC, G_MISS_LINE_ADJ_ATT_REC, G_MISS_LINE_ADJ_ASSOC_REC, G_MISS_LINE_SCREDIT_REC — the parallel set for order lines.
• G_MISS_LOT_SERIAL_REC — the lot and serial number assignment record for inventory-controlled items.
• G_MISS_HEADER_VAL_REC, G_MISS_HEADER_ADJ_VAL_REC, G_MISS_HEADER_SCREDIT_VAL_REC, G_MISS_LINE_VAL_REC, G_MISS_LINE_ADJ_VAL_REC, G_MISS_LINE_SCREDIT_VAL_REC — validation record variants used during pre-processing validation of header, line, adjustment, and sales credit payloads.

Collectively these constructors provide the canonical record templates that every OE_Order_PUB call depends upon.

Tables Accessed

The ETRM metadata documents a single referenced table for this package body: PLITBLM, reached through an APPS synonym. In the Order Management design the PLITBLM synonym resolves to the PL/SQL index-by table used for bulk line, lot, and serial processing, allowing large multi-line orders to be passed into the API without exceeding PL/SQL collection limits. The remainder of the package's persistence activity is routed through companion private packages and the OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and related attribute tables, which this body does not name directly.

Usage Notes

OE_Order_PUB is invoked whenever an application must transact against Order Management programmatically. Typical callers include the Order Management forms, order import and interface concurrent programs, pricing and shipping integration flows, and custom PL/SQL extensions. The package is referenced by 301 other packages, confirming its position as a foundational dependency rather than a leaf utility. Its header revision string (120.24.12020000.5, dated 2013/01/23) indicates the 12.2 line of the codebase. Because it is a public API, it should always be called in preference to direct DML, and initialisation of input records must begin from the appropriate G_MISS constructor so that update semantics behave correctly.