Search Results oe_sales_can_util




Overview
Explore in AI Chat

Overview

OE_SALES_CAN_UTIL is a utility package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It encapsulates the business logic required to cancel sales order lines, cancel remaining quantities on partially fulfilled orders, and manage the fulfillment and workflow consequences of those cancellations. The package is classified as a UTIL (utility) component within the Oracle Order Management (OM) module, meaning it provides reusable internal services consumed by higher-level order entry, scheduling, and configuration packages rather than exposing a formal public API. Its responsibilities span order line cancellation, canceled quantity computation, service line updates, workflow activity termination, and price adjustment cleanup.

The package forms part of the internal architecture supporting the Cancel Line and Cancel Order flows available from the Sales Orders form and related concurrent programs. It is not intended to be called directly by external integrations; Oracle's supported public interfaces remain OE_ORDER_PUB and its related APIs, one of which (OE_ORDER_PUB) this package itself depends on.

Key Procedures and Functions

The ETRM documentation identifies eleven documented program units within OE_SALES_CAN_UTIL. Their names and functions are as follows:

  • PERFORM_CANCEL_ORDER — Orchestrates the cancellation of an entire order, driving the subsequent cancellation steps across its lines.
  • CANCEL_REMAINING_ORDER — Cancels the unfilled remaining quantity of an order that has been partially shipped or fulfilled.
  • CANCEL_WF — Terminates or otherwise handles the Oracle Workflow processes associated with the order or line being canceled.
  • CALL_PROCESS_FULFILLMENT — Invokes fulfillment processing logic in the context of the cancellation, ensuring downstream fulfillment tasks are correctly resolved.
  • CHECK_CONSTRAINTS — Validates business constraints that must be satisfied before a cancellation is permitted.
  • UPDATE_SERVICE — Updates associated service lines or service references when a parent order line is canceled.
  • CAL_CANCELLED_QTY and CAL_CANCELLED_QTY2 — Compute canceled quantities, providing the arithmetic basis used to determine how much of a line or order remains to be canceled.
  • PERFORM_LINE_CHANGE — Applies the line-level changes required as part of the cancellation transaction.
  • QUERY_ROWS — Retrieves the rows (lines, sets, or workflow records) that the cancellation logic must process.

The package depends on FND_API, STANDARD, and OE_ORDER_PUB, and is referenced by nine other packages, including OE_CONFIG_PVT, OE_CONFIG_SCHEDULE_PVT, OE_DELAYED_REQUESTS_PVT, OE_HEADER_UTIL, OE_INTERNAL_REQUISITION_PVT, OE_LINE_SECURITY, OE_LINE_UTIL, OE_OE_FORM_CANCEL_LINE, OE_SCHEDULE_UTIL, and itself.

Tables Accessed

Through APPS synonyms, the package reads and writes the core Order Management tables that define order structure and pricing:

Usage Notes

OE_SALES_CAN_UTIL is an internal utility and is not documented as a public API; Oracle does not support direct invocation from custom code. In practice it is invoked indirectly through the Sales Orders form (notably via OE_OE_FORM_CANCEL_LINE), through Order Management concurrent programs, and by peer packages such as OE_HEADER_UTIL, OE_LINE_UTIL, and OE_SCHEDULE_UTIL that manage order lifecycle events. When customizations must cancel lines, the supported approach is to call the public OE_ORDER_PUB APIs, which in turn reach this utility. Because the package manipulates workflow statuses and pricing associations directly, any changes to its behavior can affect order holds, fulfillment, and price adjustments, so it should be treated as Oracle-owned code and never modified. References to it in the data dictionary are useful primarily for dependency and impact analysis after patches or upgrades.