Results for “hist_type_code”

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

Overview

ONT.OE_ORDER_LINES_HISTORY is a transactional audit table in the Oracle Order Management (ONT) module that stores the history of attribute changes for order lines. Where OE_ORDER_LINES_ALL holds the current, live state of every order line, OE_ORDER_LINES_HISTORY preserves prior versions of the same line records, capturing what changed each time a line attribute was modified, cancelled, split, or otherwise re-versioned. The table is owned by the ONT schema and is valid in both Oracle E-Business Suite 12.1.1 and 12.2.2; the documented 12.2.2 physical schema exposes 375 columns, mirroring closely the structure of OE_ORDER_LINES_ALL with the addition of history-specific audit columns such as HIST_TYPE_CODE, HIST_COMMENTS, HIST_CREATION_DATE, and HIST_CREATED_BY.

From a Data Vault modeling perspective, the mined FK structure suggests classifying this object as a link artifact, since it principally records relationships between a line and the customer, contact, site, item, and other reference entities that the line pointed to at a point in time. In practice it behaves as a satellite-like history store attached to the OE_ORDER_LINES_ALL hub, holding descriptive and relational state keyed by the line identifier.

Key Information Stored

The table carries both a full copy of order line attributes and dedicated history metadata. The most significant columns include:

• LINE_ID — the surrogate key linking the history row back to OE_ORDER_LINES_ALL; it is a foreign key and the primary business join key.
• HEADER_ID — identifies the parent order header for the line version.
• LINE_NUMBER and SHIPMENT_NUMBER — the business line and shipment identifiers as they existed for the version.
• HIST_TYPE_CODE — classifies the nature of the history event (for example, change or cancellation).
• HIST_COMMENTS — free-text remarks describing the change.
• HIST_CREATION_DATE and HIST_CREATED_BY — when and by whom the historical version was recorded.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, and CANCELLED_QUANTITY — the quantity state at the time of the version.
• ORDERED_ITEM and INVENTORY_ITEM_ID — the ordered item and its inventory reference.
• SHIP_TO_ORG_ID, SHIP_TO_CONTACT_ID, and END_CUSTOMER_ID — destination and end-customer references preserved per version.
• UNIT_SELLING_PRICE, UNIT_LIST_PRICE, PRICING_DATE, and PRICE_LIST_ID — pricing attributes at the time of the change.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY — standard who-columns.

While the table includes a large number of CONTEXT/ATTRIBUTE, GLOBAL_ATTRIBUTE, PRICING_ATTRIBUTE, INDUSTRY_ATTRIBUTE, RETURN_ATTRIBUTE, and TP_ATTRIBUTE columns for extensibility, these are descriptive rather than key-bearing. The documented relationships confirm LINE_ID as the principal lineage key to OE_ORDER_LINES_ALL.

Common Use Cases and Queries

This table is typically queried to reconstruct the lifecycle of an order line, audit who changed critical attributes, or reconcile quantities and dates across versions. A typical pattern joins the history to the current line:

• Change audit: retrieve all history rows for a line ordered by HIST_CREATION_DATE to show an evolution of ORDERED_QUANTITY, SHIP_TO_ORG_ID, or pricing.
• Quantity reconciliation: compare SHIPPED_QUANTITY and CANCELLED_QUANTITY across versions against the current OE_ORDER_LINES_ALL values.
• Reporting by order: filter on HEADER_ID to list every historically recorded version for orders in a given period.
• Comment review: surface HIST_TYPE_CODE and HIST_COMMENTS to explain why a line was altered or cancelled.

A representative query is SELECT h.line_id, h.line_number, h.hist_type_code, h.hist_creation_date, h.ordered_quantity, h.ship_to_org_id FROM ont.oe_order_lines_history h WHERE h.line_id = :p_line_id ORDER BY h.hist_creation_date;. Because the table is wide, projections should always name columns explicitly rather than using SELECT *.

Related Objects

The documented foreign keys define the principal dependencies of this table:

• OE_ORDER_LINES_ALL — referenced via LINE_ID; the current-state counterpart of the history rows.
• HZ_CUST_ACCOUNT_ROLES — referenced by SHIP_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, INTMED_SHIP_TO_CONTACT_ID, and END_CUSTOMER_CONTACT_ID.
• HZ_CUST_ACCOUNTS — referenced by END_CUSTOMER_ID.
• HZ_CUST_SITE_USES_ALL — referenced by END_CUSTOMER_SITE_USE_ID.
• IBE_MSITES_B — referenced by MINISITE_ID.
• PO_LINE_TYPES_B — referenced by LINE_TYPE_ID.
• PN_PAYMENT_TERMS_ALL — referenced by PAYMENT_TERM_ID.
• MTL_CUSTOMER_ITEMS — referenced by CUSTOMER_ITEM_ID.
• PON_OFFER_COMMITMENTS — referenced by COMMITMENT_ID.
• AR_DEFERRAL_REASONS — referenced by CONTINGENCY_ID.

These relationships make the table a useful bridge for reporting that requires the customer, contact, and item context of an order line as it existed at a specific historical point in time.