BO (Backorders) Event Processing

The system creates a tickler for the BO tickler event when an item on an order is placed on backorder and the order qualifies for a BO event rule.

When is the BO event evaluated? The system evaluates the BO event when you or the system place an item on backorder:

• during order entry processing

• during order maintenance processing

• during batch order entry (this includes orders received via the phone order interface and ecommerce)

• when you void and unreserve a pick ticket in order maintenance or in the Reprinting and Voiding Pick Slips (WVRP or WSVP) menu option

• when you unreserve an item during the Working with Interactive Reservation (MIRV) menu option

Allowing multiple ticklers for the BO event:

• If you allow multiple ticklers, the system creates multiple ticklers for an order that contains one or more backordered items; 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 one or more items on backorder, regardless of whether the backordered order qualifies for more than one event rule; the system does not create a separate tickler for each transaction that backorders an item on the order.

BO Event Rule Criteria

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

Note: The system creates a separate tickler for each ship to order that has a backordered item that meets the rule’s criteria, regardless of the Allow multiple ticklers setting.

Criterion	Event rule set up
An item is placed on backorder by a batch process, such as voiding and unreserving a pick ticket or unreserving an item during Interactive Reservation.	Unselect the Initial backorder field.
The backordered item was initially backordered in order entry/maintenance and not by some other program.	Select the Initial backorder field.
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 (valid values are 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 backorder 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 item contains SKUs, the system creates a tickler for the item if any of the SKUs for the item are on backorder. If you define both an item and SKU, the system creates a tickler only if that specific SKU is on backorder.
The item status for the item on backorder matches the item status on the event rule.	Enter an item status in the Item status field.
The item class for the item on backorder matches the item class on the event rule.	Enter an item class in the Item class field.
The ship via for the order line or order where the item on backorder is located 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 must match the ship via on the event rule.
The priority of the ship via for the order line or order where the item on backorder is located 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 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 priority for the ship to must match the ship via priority on the event rule.

BO Event Examples

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

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

• Event rule 1: Item is A123.

• Event rule 2: Item status is B.

• Event rule 3: LTD order dollars is greater than $100.

• Event rule 4: Customer class is CC.

You enter an order and:

• item A123 is on backorder.

• item B456 is on backorder and the item status is B.

• the sold to customer’s class is CC and life-to-date order dollars is $500.

The system creates 1 tickler for rule 1: Item is A123.

In this scenario, the system creates only 1 tickler for the order containing backordered items even though the order qualified for all of the event rules.

 

Example 2: Allow multiple ticklers is selected for the BO event.

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

• Event rule 1: Item is A123.

• Event rule 2: Item status is B.

• Event rule 3: LTD order dollars is greater than $100.

• Event rule 4: Customer class is CC.

You enter an order and:

• item A123 is on backorder.

• item B456 is on backorder and the item status is B.

• the sold to customer’s class is CC and life-to-date order dollars is $500.

The system creates 4 ticklers for the order:

• the first tickler is created for rule 1: Item is A123.

• the second tickler is created for rule 2: Item status is B.

• the third tickler is created for rule 3: LTD order dollars is greater than $100.

• the fourth tickler is created for rule 4: Customer class is CC.

In this scenario, the system creates 4 ticklers for the order containing backordered items; a separate tickler is created for each rule whose criteria are met.

 

Resolving BO Ticklers

A BO tickler is resolved when you or the system:

• select Resolve for a tickler at the Work with Tickler Screen (user/group view) or Workflow Management Screen.

• receive inventory for the backordered item.

• cancel the order containing the backordered item.