Results for “cannot_cancel_reason”

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

Overview

PO_MASSCANCEL_INTERIM is a temporary staging table owned by the PO schema within the Oracle Purchasing module. It supports the Mass Cancel concurrent program, which allows purchasing users to cancel large volumes of purchase orders, purchase agreement releases, and requisitions in a single controlled operation. Rather than canceling documents directly, the program collects candidate documents—typically identified through selection criteria such as buyer, vendor, date range, or document range—into this interim table, validates each row against business rules, and then processes the qualifying records. The table therefore acts as a working set that persists validation state, error explanations, and processing context for the duration of a mass cancellation run.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure suggests this object behaves as a link. Its foreign keys reference independent business entities—purchase order headers, requisition headers, vendors, and currencies—so the table primarily records associations and processing attributes between a cancellation request and the source documents, rather than describing a single durable entity of its own.

Key Information Stored

The table contains 23 documented columns. The most operationally significant include:

• NAME, OBJECT_TYPE, OBJECT_ID — the composite primary key (PO_MASSCANCEL_INTERIM_PK). OBJECT_TYPE distinguishes purchase orders from requisitions, while OBJECT_ID is the surrogate identifier of the underlying document header.
• OBJECT_NUMBER — the human-readable document number. It forms a unique business key together with NAME and OBJECT_TYPE (PO_MASSCANCEL_INTERIM_UK2) and is referenced against PO_HEADERS_ALL and PO_REQUISITION_HEADERS_ALL.
• DISTRIBUTIONS_INCLUDED — indicates whether distribution-level detail participates in the cancellation.
• FULLY_IN_RANGE_FLAG — records whether the entire document qualifies under the selected range criteria.
• DEFAULT_CANCEL_FLAG — the default cancel indicator applied to the row.
• CANNOT_CANCEL_REASON — stores the validation failure message for rows that cannot be canceled.
• AUTHORIZATION_STATUS — the approval state of the document at validation time.
• CURRENCY_CODE — foreign key to FND_CURRENCIES for the document currency.
• PO_VENDOR_ID — foreign key to PO_VENDORS, identifying the supplier.
• CANCEL_REQS_ON_PO_CANCEL_FLAG — controls whether associated requisitions are canceled along with the purchase order.
• DML/audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_CREATION_DATE.
• Concurrent program context — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and ONLINE_REPORT_ID, which tie the interim rows to the originating batch process.

Common Use Cases and Queries

The primary use case is troubleshooting and monitoring the Mass Cancel program. Support teams query this table to identify why specific documents were rejected, and reporting teams extract eligibility statistics before a run is committed.

• List documents that failed validation:

  SELECT object_number, object_type, cannot_cancel_reason
  FROM   po.po_masscancel_interim
  WHERE  cannot_cancel_reason IS NOT NULL;

• Count purchase orders versus requisitions staged for a given concurrent request:

  SELECT object_type, COUNT(*)
  FROM   po.po_masscancel_interim
  WHERE  request_id = :request_id
  GROUP BY object_type;

• Join staged rows to PO_HEADERS_ALL on OBJECT_ID or OBJECT_NUMBER to display buyer and status detail for the cancellation set.
• Verify how many staged documents are fully in range versus partially selected using FULLY_IN_RANGE_FLAG.

Because the table is a temporary working structure, queries should typically be scoped by REQUEST_ID to isolate the current or most recent mass cancellation job.

Related Objects

The most relevant dependencies, as documented through the foreign key relationships, are:

• PO_HEADERS_ALL — joined via OBJECT_ID and OBJECT_NUMBER for purchase order documents.
• PO_REQUISITION_HEADERS_ALL — joined via OBJECT_ID and OBJECT_NUMBER for requisition documents.
• PO_VENDORS — joined via PO_VENDOR_ID.
• FND_CURRENCIES — joined via CURRENCY_CODE.
• FND_CONCURRENT_REQUESTS — implicitly referenced through REQUEST_ID to associate rows with the executing concurrent request.
• PO_MASSCANCEL_INTERIM_PK / PO_MASSCANCEL_INTERIM_UK2 — the unique indexes enforcing surrogate and business key integrity.

In practice, the Mass Cancel concurrent program itself is the principal consumer, reading and writing these rows during validation and execution, while the related header tables supply the authoritative document and vendor attributes displayed to the user.