Results for “so_order_cancellations”

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

Overview

SO_ORDER_CANCELLATIONS is an Oracle Order Entry (OE) transactional table that stores order and order line cancellation records within Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the OE schema and carries a VALID status in the ETRM repository. The table captures the audit trail of cancellations applied against sales orders and their lines, preserving who cancelled the order, when the cancellation occurred, the reason code, and the quantity affected. This makes it a critical source for order lifecycle analytics, cancellation trend reporting, and reconciliation of order status transitions.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying SO_ORDER_CANCELLATIONS as a link entity. It connects header-level (SO_HEADERS_ALL), line-level (SO_LINES_ALL), and user (FND_USER) hubs. This classification is a heuristic suggestion derived from the FK topology rather than a formally documented Data Vault designation.

Key Information Stored

The table contains 34 documented columns. The composite primary key SO_ORDER_CANCELLATIONS_PK is defined on HEADER_ID and LINE_ID, forming the surrogate identifier for each cancellation record. Note that the only documented unique index is SYS_IL0000040985C00034$$, an internal LOB index associated with CANCEL_COMMENT; no separate business-key unique constraint is documented beyond the composite PK.

The most significant columns include:

• HEADER_ID — foreign key to SO_HEADERS_ALL; identifies the cancelled order header.
• LINE_ID — foreign key to SO_LINES_ALL; identifies the cancelled order line.
• CANCEL_CODE — reason code driving the cancellation.
• CANCELLED_BY — foreign key to FND_USER; the user who performed the cancellation.
• CANCEL_DATE — timestamp of the cancellation event.
• CANCELLED_QUANTITY — quantity of the line affected by the cancellation.
• STATUS — processing status of the cancellation record.
• PROCESSED_FLAG — indicator of whether the cancellation has been processed.
• CANCEL_COMMENT — free-text commentary stored as the LOB column.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) segments for extensible attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program context identifying the originating request.

Common Use Cases and Queries

Typical scenarios include reporting cancellation rates by order, line, or user; auditing reason codes; and tracing concurrent program runs that produced cancellations. A representative join to resolve header and user details follows:

• SELECT c.HEADER_ID, c.LINE_ID, c.CANCEL_CODE, c.CANCELLED_QUANTITY, c.CANCEL_DATE, u.USER_NAME FROM OE.SO_ORDER_CANCELLATIONS c, FND_USER u WHERE c.CANCELLED_BY = u.USER_ID;
• Trend analysis grouped by CANCEL_DATE and CANCEL_CODE to identify recurring cancellation drivers.
• Reconciliation of unprocessed records using PROCESSED_FLAG and STATUS to detect incomplete cancellation flows.
• Program-level audit filtering by REQUEST_ID or PROGRAM_ID to trace batch cancellations.

Related Objects

The table participates in the following documented relationships:

• SO_HEADERS_ALL — referenced via SO_ORDER_CANCELLATIONS.HEADER_ID.
• SO_LINES_ALL — referenced via SO_ORDER_CANCELLATIONS.LINE_ID.
• FND_USER — referenced via SO_ORDER_CANCELLATIONS.CANCELLED_BY.
• Order Entry concurrent programs and the Order Management APIs that insert cancellation rows, identifiable through PROGRAM_ID and REQUEST_ID.
• Reporting views and DFF definitions layered over CONTEXT and the ATTRIBUTE columns.