OO (Aged Open Orders) Event Processing
The system creates a tickler for the OO tickler event when an aged open order exists.
An aged open order is:
• an order whose order header is open or held, and
• the order contains one or more order lines that are open or held, and
• the order line is not reserved (Quantity reserved is 0) or is reserved but not printed (Quantity reserved is greater than 0 and Quantity printed is 0), and
• the order is older than a specified number of days, based on entered date or arrival date defined for the order lines on the order.
One tickler is created for each ship to customer on an aged open order that qualifies for an OO event rule; if an aged open order qualifies for more than 1 event rule, the system creates 1 tickler for the first event rule, in processing sequence order, that qualifies.
Note: The system does not allow multiple ticklers for the OO event (the Allow multiple ticklers field must be unselected).
When is the OO event evaluated? The system evaluates the OO event when you run the Evaluate Create/Resolve Tickler periodic function (program name PFR0072).
Graduating OO ticklers: Each time you run the Evaluate Create/Resolve Tickler periodic function, the system determines is any existing OO ticklers should be graduated.
• If an OO tickler exists for an aged open order and the aged open order qualifies for a new event rule, based on processing sequence order, the system keeps the existing tickler open and applies the new event rule to the tickler.
• If an OO tickler exists for an aged open order and the aged open order qualifies for the event rule currently assigned to the existing tickler, the system does not create a new tickler and keeps the existing tickler without any updates.
• If an OO tickler exists for an aged open order and the aged open order no longer qualifies for the current event rule and does not qualify for any other OO event rules, the system resolves the tickler; see Resolving OO Ticklers.
The system updates the existing tickler with the information related to the event rule that is now associated with the tickler:
• Rule number updates to the new event rule assigned to the tickler.
• Category updates to the category for the new event rule.
• Priority updates to the priority for the new event rule.
• Assigned to updates to the assigned to user/group for the new event rule.
• Assigned date updates to the date the tickler is graduated.
• Supervisor group updates to the supervisor group for the new event rule.
• Date to notify supervisor updates, based on the new supervisor group assigned.
• Tickler procedures updates to the procedures for the new event rule.
• if the tickler was in-process, the system changes the status back to open.
• if the Notify user/group field is selected for the new event rule, the system sends a Tickler Reassignment email; see Tickler Notification for a sample email. Note: The system sends a Tickler Reassignment email only if the new event rule has a different assigned to user/group from the previous event rule assigned to the tickler.
• the system creates a tickler history record, indicating the tickler has been graduated from one event rule to another.
You can define the following criteria for an OO event rule.
The Orders older than date setting is used with all other criteria you define for an event rule. For example, if you define a ship via, the aged open order must match the specified ship via and the order’s entered/arrival date must be older than the system date by the number of days defined.
Note: The system creates a separate tickler for each ship to order that has an order line that qualifies; the system does not create a separate tickler for each order line that qualifies.
Criterion |
Event rule set up |
The order line’s entered date/arrival date is older than the current date by the number of days on the event rule. |
Enter a date indicator code (E = entered date, A = arrival date) in the Date indicator field and enter a number in the Orders older than field. The system requires you to enter a date indicator and number of days. Note: The system evaluates the entered date/arrival date on the order detail line; the system does not evaluate the entered date/arrival date on the order header. |
The ship via for the aged open order 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 define a ship via for the event rule, you cannot define a ship via priority. 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 aged open order 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 define a ship via priority for the event rule, you cannot define a ship via. 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. |
The following event rules are defined for the OO event rule, in processing sequence order.
• Event rule 1: Orders older than 5 days by Arrival date and Ship via is 2
• Event rule 2: Orders older than 1 day by Arrival date and Ship via is 2
You run the Evaluate Create/Resolve Ticklers periodic function and:
• Order # 6599 qualifies for event rule 2 (an order line’s arrival date is older than 1 day and the ship via is 2)
• Order # 6601 qualifies for event rule 2 (an order line’s arrival date is older than 1 day and the ship via is 2)
The system creates an OO tickler for each order.
You run the Evaluate Create/Resolve Ticklers periodic function again and:
• Order # 6599 qualifies for event rule 1 (an order line’s arrival date is older than 5 days and the ship via is 2)
• Order # 6601 qualifies for event rule 2 (an order line’s arrival date is older than 1 day and the ship via is 2)
The system graduates the existing tickler for order # 6599 to event rule 1; the existing tickler for order # 6601 continues using rule 2.
You run the Evaluate Create/Resolve Ticklers periodic function again, and:
• order # 6599 qualifies for event rule 1 (an order line’s arrival date is older than 5 days and the ship via is 2)
• order # 6601 does not qualify for any rules (a pick has been generated)
The existing tickler for order # 6599 continues using rule 1. The system resolves the existing tickler for order # 6601.
An OO tickler is resolved when you:
• select Resolve for a tickler at the Work with Tickler Screen (user/group view) or Workflow Management Screen.
• run the Evaluate Create/Resolve Ticklers periodic function (program name PFR0072), if the tickler no longer applies to any OO event rules. For example, the order is now cancelled.
• generate a pick slip for the order. Note: When you generate a pick slip for the order, the system resolves the tickler automatically and does not wait until you run the Evaluate Create/Resolve Ticklers periodic function.
