Schedule Agent and BackOrderReprocess Interval explained

Resolving The Problem

Yantra handles backorders always in two sweeps.
The first sweep puts an entry into the Task_q with current sysdate as the availabledate
The second sweep makes a determination on an existing backorder and pushes it out to backordered date+BackReprocessInterval.

The actual steps followed are as follows

1. Order in a Released/Sent to Node status is Backordered from Node.

New entry is created in TASK_Q for SCHEDULE.0001. Avl Date is set to Sysdate1, Also in YFS_ORDER_RELEASE_STATUS YORS a new entry is created for Status 1300, Modifyts=Sysdate1. This 1300.modifyTS has implications down the line.

2. 5 mins later At say Sysdate2, When Schedule Agent is run.
It first checks if Task_q.Available_Date < Sysdate2. (In this case Yes, so proceed)<br>It then finds out that this order has atleast one backordered line. and checks if the agent criteria (New vs backordered) allows the agent to work on this Order.<br>It then checks if sufficient time 12 hrs (BackOrderReprocessInterval) has passed since the last backordered event YORS.1300.modifyTS.<br><br>If 12 hrs hasn't passed. It doesnt even try to schedule (even though Inventory might be available)<br>Also at this time, It resets the TaskQ AvailableDate to YORS.1300.modifyTS+12hrs<br><br>So the Schedule Agent will not pick this order for the next 12 hrs.<br><br>3. Now at say Sysdate 3 which is after the stipulated 12 hrs.<br>Lets say you run the Schedule Agent again.<br>The system checks if Task_Q.Available_date , Sysdate3 (In this case Yes, So proceed)<br>It then checks to see if there is a backordered line. Yes.<br>It then checks to see if sufficient time has passed since the last backordered event 1300modifyTS. Yes 12 hrs has passed)<br>Now it tries to Schedule. ( Lets say Inventory is NOT available)<br>This means it is supposed to be backOrdered again.<br><br>Now the system puts a new task_q entry for Schedule.0001 with available_date=Sysdate3, and also resets 1300.modifyTS =Sysdate3<br>