Search Results base_line_number




Overview

The SO_ORDER_CANCELLATIONS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Order Management (OE – Order Entry) module. It exposes cancellation activity recorded against sales order lines, resolving the raw transactional data stored in the underlying SO_ORDER_CANCELLATIONS table into a denormalized, business-friendly format. In EBS 12.1.1 and 12.2.2 the view is documented as VALID and is widely consumed by forms, concurrent programs, and custom reports that require a consolidated picture of order line cancellations, cancelled quantities, and cancellation reasons.

Because the view joins header, line, order type, item, and lookup information into a single rowset, it removes the burden of assembling these relationships manually. The user search term cancel_code is directly relevant: CANCEL_CODE is a core column exposed by the view and is joined to the SO_LOOKUPS lookup type 'CANCEL_CODE' to provide the descriptive cancellation reason (CANCEL_MEANING). This makes the view the canonical source when reporting why and how much of an order was cancelled.

Underlying Base Objects

Per the documented metadata, SO_ORDER_CANCELLATIONS_V is defined over the following base objects:

The view text further indicates a UNION ALL, meaning cancellation records from distinct line categories (such as standard lines and their shipment schedules) are combined into one normalized result set.

Key Columns

  • ROW_ID — the rowid of the source cancellation record; useful for direct updates or deduplication.
  • HEADER_ID / LINE_ID — the sales order header and line identifiers forming the transactional key.
  • CANCEL_CODE — the lookup code identifying the cancellation reason; the column most directly tied to the user's search term.
  • CANCEL_MEANING — the descriptive text resolved from SO_LOOKUPS for the CANCEL_CODE.
  • CANCELLED_BY / CANCEL_DATE — the user who performed the cancellation and the timestamp.
  • CANCELLED_QUANTITY — the quantity cancelled on the line.
  • CANCEL_COMMENT — free-text remarks entered during cancellation.
  • STATUS / PROCESSED_FLAG — workflow/processing state indicators.
  • ORDER_NUMBER, ORDER_TYPE_NAME, ITEM, BASE_LINE_NUMBER, SHIPMENT_SCHEDULE_NUMBER, OPTION_LINE_NUMBER, ITEM_TYPE_CODE — descriptive and hierarchical context for reporting.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, PROGRAM_ID, REQUEST_ID — standard WHO and concurrent-program audit columns.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield segment columns.

Common Use Cases and Queries

Typical scenarios include cancellation trend analysis, root-cause reporting by cancel reason, and reconciliation of cancelled quantities against order lines.

Retrieve all cancellations with their reasons:

  • SELECT order_number, line_id, cancel_code, cancel_meaning, cancelled_quantity, cancelled_by, cancel_date FROM apps.so_order_cancellations_v WHERE cancel_code = '&cancel_code' ORDER BY cancel_date DESC;

Summarize cancelled quantities by reason for a date range:

  • SELECT cancel_code, cancel_meaning, SUM(cancelled_quantity) total_cancelled FROM apps.so_order_cancellations_v WHERE cancel_date BETWEEN :from_date AND :to_date GROUP BY cancel_code, cancel_meaning ORDER BY total_cancelled DESC;

Analyze cancellation by order type and item:

  • SELECT order_type_name, item, COUNT(*) cancel_count, SUM(cancelled_quantity) qty FROM apps.so_order_cancellations_v GROUP BY order_type_name, item;

Because the view joins MTL_SYSTEM_ITEMS_KFV using the SO_ORGANIZATION_ID profile, results reflect the organization context of the session; queries should therefore be executed under the appropriate operating unit responsibility to ensure correct item resolution.