CO (Cancelled Orders) Event Processing

CO (Cancelled Orders) Event Processing

The system creates a tickler for the CO tickler event when an order is cancelled or contains an order line that is cancelled and the order qualifies for a CO event rule.

When is the CO event evaluated? The system evaluates the CO event when you or the system cancels an order or order line during:

• order maintenance

• Working with Backorders Pending Cancellation (WBPC)

• Processing Item Substitutions (PSUB)

• Working with Credit Card Cancellations (WCCC)

• Processing Auto Soldout Cancellations (MASO)

Allowing multiple ticklers for the CO event:

• If you allow multiple ticklers, the system creates multiple ticklers for an order that is cancelled or contains cancelled order lines; a separate tickler is created for each event rule whose criteria are met.

• If you do not allow multiple ticklers, the system creates only 1 tickler per order ship to that contains a cancelled order/order line, for example if 1 tickler is created during order maintenance another tickler cannot be created during Process Auto Soldout Cancellations.

CO Event Rule Criteria

You can define the following criteria for a CO event rule.

Note: The system creates a separate tickler for each ship to order that has a cancelled order line and meets the rule’s criteria, regardless of the Allow multiple ticklers setting. When you cancel an order, the system creates a separate tickler for each ship to order you cancel.

Criterion	Event rule set up
The order or order line is cancelled, regardless of whether it is by a batch process or interactively.	Unselect the Batch process only field.
The order or order line is cancelled by a batch process and not interactively.	Select the Batch process only field. You can cancel an order/order line during a batch process using: • Processing Item Substitutions (PSUB) • Working with Credit Card Cancellations (WCCC) • Processing Auto Soldout Cancellations (MASO)
The life-to-date order dollars for the sold to customer (the $ orders LTD field in the Customer Sold To Order History table) on the order meets the comparison criteria on the event rule.	Enter a comparison value (GT greater than, GE greater than or equal to, LT less than, LE less than or equal to) in the Comparison field and a dollar amount in the LTD order dollars field. You can only define a whole number for the life-to-date order dollars. You can review the life-to-date order dollars for a sold to customer at the Display Customer Order History Screen.
The customer class for the sold to customer on the order matches the customer class on the event rule.	Enter a customer class in the Customer class field. Note: The system does not look at the customer class defined for the ship to customer.
The item and/or SKU on the cancelled order line matches the item and/or SKU on the event rule.	Enter an item code in the Item field and optionally, a SKU code in the SKU field. If you define an item but not a SKU code and the cancelled item contains SKUs, the system creates a tickler for the item if any of the SKUs for the item are cancelled. If you define both an item and SKU, the system creates a tickler only if that specific SKU is cancelled.
The item status for the item on the cancelled order line matches the item status on the event rule.	Enter an item status in the Item status field.
The item class for the item on the cancelled order line matches the item class on the event rule.	Enter an item class in the Item class field.
The cancel reason on the cancelled order line/order matches the cancel reason on the event rule.	Enter a cancel reason code in the Cancel reason field.
The ship via for the cancelled order/order line matches the ship via on the event rule.	Enter a ship via code in the Ship via field. The system evaluates the ship via on the detail line first, then the ship via on the order header. If you enter a Ship via, you cannot define a Ship via priority for the event rule. Note: To create a tickler for each ship to order, the ship via for the ship to customer must match the ship via on the event rule.
The priority of the ship via for the cancelled order/order line matches the ship via priority on the event rule.	Enter a ship via priority number in the Ship via priority field. The system evaluates the priority of the ship via on the detail line first, then the priority of the ship via on the order header. If you enter a Ship via priority, you cannot define a Ship via for the event rule. Note: To create a tickler for each ship to order, the priority of the ship via for the ship to customer must match the ship via priority on the event rule.

CO Event Examples

Example 1: Allow multiple ticklers is unselected for the CO event.

The following event rules are defined for the CO event, displayed in processing sequence order.

• Event rule 1: Batch process only is selected

• Event rule 2: Item is A123

• Event rule 3: LTD order dollars is greater than 500

• Event rule 4: Ship via is 1

You enter an order and:

• the ship via on the order header is 1.

• the items on the order are A123 and B456.

• the sold to customer’s life-to-date order dollars is $75.00.

• in order maintenance, you cancel order line 1 for item B456.

• in Processing Item Substitutions (PSUB), you cancel item A123.

In this scenario, the system creates 1 tickler during order maintenance for rule 4: Ship via is 1. The system does not create a tickler for the other rules whose criteria are met. The system does not create a tickler during Process Substitute Items since a CO tickler already exists for the order/order ship to.