Overview
Oracle Order Management provides the features you need to cancel sales orders, returns, internal orders, and service orders. The order cancellation feature of Order Management enables you to specify who has the authority to perform a cancellation request.
You can cancel entire orders or returns, or individual lines. A cancellation within Order Management is considered any reduction that occurs to existing order line quantity when an enabled processing constraint is invoked by an Order Management function during order processing. Therefore, any Order Management processing constraints you wish to use to control order quantity decrements must use the CANCEL operation.
If you choose to cancel sales orders or reduce existing order quantities, then Order Management attempts to perform the cancellation based upon the existing enabled Order Management processing constraints or user defined processing constraints. However, there can be certain points in order processing after which it is not logical or possible to cancel an order or line. For instance, you cannot cancel an order or line after it has been invoiced.
Order Management enables you to decide after which point lines can be cancelled, or after which point cancellation of lines needs to be prevented. You can define the cancellation point by enabling a constraint on operation Cancel, with "Require Reason and Require History" user action and a particular template such as "Entered" or "Booked". The particular template that you specify stands as the point after which reduction in quantity is considered cancellation and Order Management requires a reason for the change. However, if quantity is reduced before the line reaches the applicable cancellation point, then the application treats it as a mere reduction in quantity and not a cancellation.
Ensure that you define the cancellation point. Order Management provides "Booked" as the predefined cancellation point. The application treats attempts at both partial and complete cancellation prior to booking as changes of quantity and does not perform a cancellation. After booking, the application cancels the order or line and requires a reason at the time of cancellation.
Note: When you choose to cancel the remaining lines, an attempt is made to cancel all lines that are unfulfilled and unshipped on the order, however if one line fails to cancel then it would fail the entire operation. This is not intended to cancel lines that are cancellable.
Your processing constraints for orders and returns determine whether you can:
Cancel orders, returns, and associated lines based on their workflow status
Reduce existing order line quantity
Note: Order Management processing constraints exist for reducing order line quantity once a line has been interfaced to Oracle Shipping Execution.
See: Order Changes
See: Oracle Order Management Implementation Manual, Defining Processing Constraints.
You can cancel:
An entire line
A partial line quantity
A complete order or return, provided all lines are cancellable (including orders and returns that have existing lines which are already cancelled)
Internal orders
Service orders
Drop shipments
Cancelling Partially:
Releases reservations
Reprices lines
Voids Oracle Payment credit card authorizations
Cancelling Completely:
Releases reservations
Sets line statuses to Cancelled and sets open quantities to zero
Releases all holds on the order or line
Closes order lines
You can cancel using:
The Sales Order and Order Summary windows for on-line cancellations
Cancellations of complete lines can be made via the Sales Order window using the Actions button, or by directly modifying the quantity. You also can use multi-select functionality to cancel multiple orders or order lines. Selecting Cancel from the Action button will:
Cancel the entire order line, if selected from the Lines tab
Cancel the complete order, if selected from the Orders Header tab
The Order Import process and the Mass Change window for batch cancellations
Custom workflows that you create to cancel orders and lines under specific circumstances
You can require a reason for the cancellations based on the status of the order or line. For example, you may want to capture the reason for the cancellation if the line has been scheduled and may not require a reason if the line is booked. Reasons are defined in Quick Codes.
As long as an order is not subject to other restrictions that keep it from being cancelled, you can cancel an order:
With a line that has been cancelled
With a line that has reservations but has not been pick confirmed (reservations are automatically adjusted)
An order or line cancelled will have a status of Cancelled, and a workflow status of Closed.
Use processing constraints against the CANCEL operation to:
Grant permission to certain people to perform cancellations
Specify the situations under which individuals can perform cancellations. For example, you can enable cancellations after booking until time of pick release, you can enable cancellations after pick release before shipping, or you can forbid cancellations for lines which are shipped, received, invoiced, or closed.
To place the minimum restrictions on the cancellation process:
Do not create user constraints: Instruct individuals to reduce unneeded line quantities to zero. They do not need to provide reasons, however, if they do, order processing will record the reasons. For example, to use cancellation:
Create a user constraint to require a cancellation reason if a line is booked. Before booking, a quantity decrement to zero is not a cancellation and you are not required to select a reason but order processing records provided reasons. After booking, a quantity decrement to zero is a cancellation and you must select a reason.
Create a user constraint to forbid cancellation if a line is picked.
To record history for the cancellation, create processing constraints that require recording of history. The order processing includes the cancelled quantity in the history notation.
In addition to your processing constraints, there are system defined rules (system constraints) which forbid cancellation in certain instances. Oracle Order Management honors processing constraints which are stricter than the system constraints and ignores processing constraints which conflict with the system constraints: The system constraints forbid cancellation if:
An order or line is closed
An order or line is already cancelled
A order line is shipped or invoiced
A return line quantity is received or credited
A drop shipment has been received (receipt Generated in Oracle Purchasing) for the order line
You can define processing constraints for cancellations. Depending on how you set up constraints, the system may or may not have a cancellation concept.
To set up a system without cancellation, define a system constraint that says cancel is not enabled after the line is shipped, and there are no user constraints. Decrementing is not allowed after the line is shipped, and all decrements in quantity before shipping will be treated as decrements, not cancellations. The reason for the change is recorded when provided by the user but it is not required for proper processing.
To use cancellation, you can define a system constraint that says cancel is not enabled after the line is shipped, and a user constraint that says cancellation requires a reason if the line is booked. Then, cancellation is not enabled if this line is picked. In this case:
Cancellation is not enabled after the line is shipped because of a system constraint.
If quantity is decremented before the line is booked, then it is a decrement of quantity and not a cancellation. This reason is stored if provided, but it is not mandatory.
If quantity is decremented after the line is in a booked status, the reason is required and the system treats the revised quantity as a cancellation.
Warning: You can prevent some responsibilities from cancelling, and you can enable some responsibilities to cancel if a reason is provided. This requires setting up two constraints.
Oracle Release Management (RLM) utilizes the processing constraints setup in Order Management (OM). Following two constraints are required for preventing order quantity update on pick released lines.
UPDATE -- Not Allowed for Pick Released Lines
CANCEL -- Not Allowed for Pick Released Lines
A request for decrease of order quantity on pick released lines will generate an exception message during demand processing. The order quantity will not be decreased. The request for increase in Order Quantity would insert a new order line with the incremental quantity.
If the CANCEL constraint is not setup, a quantity increase would result into insertion of a new delivery line but a quantity decrease would actually reduce the quantity on the pick released line.
The following processes describe enabling and disabling cancellation by responsibility.
Navigate to the Processing Constraints window in Oracle Order Management.
Select the entity to be constrained.
Select the operation to be constrained.
Select the action to be taken if this constraint occurs.
Enter the constraining conditions.
Enter the responsibility constrained from performing this operation.
Save the constraint.
Navigate to the Processing Constraints window in Oracle Order Management.
Select the entity to be constrained.
Select the operation to be constrained.
Enter the constraining conditions.
Select the responsibilities authorized to perform this operation.
Save the constraint.
Oracle Order Management Implementation Manual, Overview of Processing Constraints.
Oracle Order Management Implementation Manual, Defining Processing Constraint, Order Management Processing Constraints Listing Appendix.
You can cancel:
Models: Oracle Order Management cancels the option classes, option items, and included items in proportion to the cancelled model quantity.
Option classes: Oracle Order Management cancels the kit and included items. You can cancel components of an option class, an option class, as well as included items. You can cancel option classes in quantities which are in the same ratio as the model quantities.
You cannot cancel an order line created for a ATO configuration after booking or scheduling. Most actions against a configuration line are disabled; you should perform the action on the model line.
Kits: Kits, consisting of PTO items, can be cancelled as a whole or item-wise. Like option classes, you can cancel kits in quantites which are in the same ratio as model quantities.
If you have shipped partial quantities of components in a pick-to-order configuration, you can cancel the leftover incomplete configurations.
If a model (top level) is completely cancelled, configuration validation routines are executed. If you attempt to perform a partial or complete cancellation of an order line that is part of a model or kit, complete configuration validations will be executed to ensure the model configuration is still valid.
You cannot cancel:
Mandatory option classes or the last option item of a mandatory option class.
Partial quantities of option lines that would result in incomplete configurations. Proportional quantities for any children of a model must be a whole integer equivalent.
Included items: You cannot cancel, update, or delete included items.
If you use either Oracle Configurator or the Order Management Options window to create configurations:
You can use Oracle Order Management to cancel the configuration and its parts.
Oracle Configurator re-validates and re-configures the configuration after the cancel.
Included items are automatically cancelled when you cancel the kit or model with which they are associated. If you have shipped some included items before their corresponding kit, class, or model and you attempt to cancel the kit, class, or model, Oracle Order Management automatically cancels the remaining included items. However, if you have shipped some required-for-revenue included items, your cancel quantity allowed on the included items' parent may be restricted to allow you only to cancel a parent quantity that includes whole ratios of any remaining required-for-revenue included items.
You cannot cancel the received quantity of a return line. Since return processing splits a partially received line, you can cancel the unreceived quantity portion of a line.
For returns of pick-to-order items, cancelling the model does not cancel the complete configuration because the return configuration is in individual return lines. To cancel a complete configuration, cancel the model line, option class lines, option item lines and included item lines.
You can partially or fully cancel the line quantities on internal sales orders.
You can make the following attribute changes after an internal sales order has been generated:
Update Scheduled Shipment Date
Decrement order line quantity
Note: If you cancel an internal sales order, order line, or backordered order line that is linked to an internal requisition, manually cancel the internal requisition. The order cancel processing issues a reminder. If you have used the 'Line Flow - Generic, Bill Only with Inventory Interface' workflows for the internal sales orders, then the application does not relieve the corresponding reservations for the internal sales order lines, does not receive the corresponding internal requisitions, and hence does not close them.
When cancelling service orders and lines:
You can partially cancel a serviceable item or an assemble-to-order or pick-to-order model with service attached without cancelling the service itself.
If you fully cancel a standard item, the service is cancelled.
You can fully cancel service that was attached to a line at order entry.
You cannot partially cancel service that was attached to a line at order entry.
You cannot cancel a service order that was generated through the Oracle Service in Oracle Order Management. You must cancel it using Oracle Service.
If you cancel a drop shipment line for which you have not shipped the entire quantity, the order processing splits the line. The first line contains the quantity shipped and the second line contains the non-shipped quantity in backorder. You can cancel the second line.
While cancelling multiple drop ship lines, the application does not cancel any of the lines if cancellation of all the related purchase orders fails. However, if any such purchase order is cancelled successfully, then the application cancels all the selected drop ship lines. In this case, Order Management delinks, from itself, the purchase orders that cannot be cancelled.
Oracle Order Management Implementation Manual, Defining Order Management QuickCodes