Search Results hist_comments




Overview
Explore in AI Chat

Overview

APPS.OEBV_ORDER_CANCELLATIONS is a read-only reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes line-level order cancellation records from Oracle Order Management. The view is owned by the APPS schema and is defined as a restricted projection over OE_ORDER_LINES_HISTORY, isolating the subset of history rows where the history type code equals 'CANCELLATION' and where a positive cancelled quantity exists. In effect, it acts as a filtered, security-aware window onto the order line history table, removing the need for report authors and integrators to reimplement the cancellation filter, the quantity threshold, and the sold-to-org security predicate themselves.

Because the view filters on CANCELLED_QUANTITY (the column referenced in the user's search), it is the primary supported source for answering questions about how much of an ordered line was cancelled in a given transaction. Typical consumers include order management dashboards, revenue and returns analyses, exception reports, OBIEE or BI Publisher data models, and custom PL/SQL that must reconcile cancelled quantities against ordered and shipped quantities.

Underlying Base Objects

The documented base object is OE_ORDER_LINES_HISTORY, accessed through a synonym in the APPS schema. This table stores the audit and history trail of order lines, with each row recording a change event qualified by HIST_TYPE_CODE. The view selects only rows where HIST_TYPE_CODE = 'CANCELLATION', ensuring that only true cancellation events are returned.

Two additional predicates are baked into the view definition:

  • NVL(CANCELLED_QUANTITY, 0) > 0 — excludes cancellation history rows that carry no positive cancelled quantity, eliminating no-op or informational entries.
  • '_SEC:SOLD_TO_ORG_ID' IS NOT NULL — a substituted security predicate that enforces Oracle EBS Multi-Org Access Control (MOAC), so that a query returns only cancellations for organizations the executing responsibility is permitted to see.

The view is declared WITH READ ONLY, so no insert, update, or delete operations are permitted through it; all maintenance must occur against the base table by the appropriate Order Management processes.

Key Columns

  • CANCELLED_QUANTITY / CANCELLED_QUANTITY2 — the cancelled amount on the line, expressed in the primary and secondary (dual unit of measure) quantities respectively. These are the columns of direct interest to the user's search.
  • HEADER_ID — identifier of the parent order header; joins to OE_ORDER_HEADERS_ALL.
  • LINE_ID — identifier of the order line; joins to OE_ORDER_LINES_ALL.
  • ORG_ID — the operating unit that owns the transaction, used by the MOAC security predicate.
  • HIST_COMMENTS — free-text comments recorded at the time of cancellation.
  • HIST_CREATION_DATE / HIST_CREATED_BY — when and by whom the cancellation history record was created.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE — standard EBS audit columns.
  • CHARGE_PERIODICITY_CODE — periodicity code associated with the line's charge, relevant for service and subscription lines.
  • Reason (display column) — the first selected expression applies a lookup label to OE_ORDER_LINES_HISTORY.REASON_CODE against the OE_LOOKUPS lookup type CANCEL_CODE, returning the MEANING as the cancellation reason. This column appears under a derived label rather than a physical column name.

Common Use Cases and Queries

A frequent requirement is to list all cancellations for an order line, including the reason and quantity:

  • Cancelled versus ordered quantity analysis: join the view to OE_ORDER_LINES_ALL on LINE_ID and compare CANCELLED_QUANTITY with ORDERED_QUANTITY to derive open or net quantities.
  • Cancellation trend reporting: aggregate CANCELLED_QUANTITY by ORG_ID or by HIST_CREATION_DATE period to identify cancellation patterns.
  • Reason code analysis: use the derived reason column to group cancellations by CANCEL_CODE meaning.
  • Integration extracts: feed downstream systems with cancellation events, relying on the built-in MOAC predicate for data security.

A representative query is:

SELECT header_id, line_id, org_id, cancelled_quantity, cancelled_quantity2, hist_creation_date, hist_comments FROM apps.oebv_order_cancellations WHERE header_id = :p_header_id ORDER BY hist_creation_date;

Because the view enforces both the cancellation filter and organization security, such queries remain correct and compliant with EBS access rules without additional predicates. For historical reconciliation, note that the view reflects only cancellation history entries; current line status must still be obtained from OE_ORDER_LINES_ALL. The view is available in both 12.1.1 and 12.2.2, with the underlying table remaining OE_ORDER_LINES_HISTORY.