Extending the Original Receive Dates
View Affected Orders - Due to Modification of Receive Dates on Transfer Orders
Content was last updated in 06.22.03-00
Revision History
Version No. | Reference No. | Changes |
06.22.03-00 | R2-18460 | Tracking orders that get affected due to unavailability of items, because returned date on some existing Transfer Order is extended. |
You can now view how an extension in the Receive (Delivery) Date of a Transfer Order, can affect other rental or transfer order, not just in the same site but at other sites as well. This is applicable for both One-Way and Two-Way Transfer Orders.
There are however multiple methods how the Receive (Delivery) Date on either type of Transfer order can be modified.
Two way Transfers
Main Transfer Order Receive (Delivery) Date extended from Main Transfer Order window
Return Transfer Order Receive (Delivery) Date extended from Main Transfer Order window
Return Transfer Order Receive (Delivery) Date extended from Return Transfer Order window
One way Transfers:
Main Transfer Order Receive (Delivery) Date extended from Main Transfer Order window
This conflict arises when the Receive (Delivery) Date of a Transfer Order is changed, it alters the availability of the items, since the required quantity is no longer available at the specific site on the expected dates; the shortfall subsequently restricts other order from being fulfilled..
The affected orders can be:
Rental Orders & Transfer Outs in Transfer To Site of T-Out whose receive date is extended
Rental Orders & Transfer Outs in Transfer To Site of Transfer Outs that affected in the above case (Second level affected Orders).
The above listed information can be viewed under Affected Orders, in Accounts module.
Pre-requisites
Create four sites: San Jose, London, Berlin, and Auckland.
Create stock [SKU-TEST-01] at each of the sites as: San Jose (11), London(4), Berlin(3), and Auckland(1). See
Create orders at each of the sites as per details given in the following See Summary
Process these Orders to Out, Filled, or Overdue status.
This clause ensures that the items are actually out from the Site's inventory, and only the residual stock at the site is considered for any subsequent Order created or any existing Order modified. These Orders are termed as Inflicting Orders.
Linguistically speaking, they are the source/reason of the shortfall trouble, and are imposing (making the impact happen) the shortfall on other Orders.
Table 2.0 Initially Created Scenarios
Initial Situation: No return dates are changed | Order Site | Order Type | Order Qty | Order line Prep-Return Dates | Result(s) | ||||||||||||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | |||||
Remaining Qty @ Site >>> | 11 | 11 | 11 | 11 | 11 | 7 | 7 | 5 | 5 | 5 | 5 | 5 | 7 | 3 | 3 | 0 | 0 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | Since there is NO short-fall of quantity at any site on any given day, all the Rental Orders and Transfer Orders get processed without any hindrance. | |||
San Jose | Transfer | 4 |
|
|
|
|
| TRF-Berlin |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
| Rental | 4 |
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-111 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||
| Transfer | 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TRF-London |
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
| Return | 2 |
|
|
|
|
|
|
| TRF-Berlin (Return) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||
Remaining Qty @ Site >>> | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 0 | 0 | 0 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | ||||
London | Rental | 4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-221 |
|
|
|
|
|
|
|
|
|
| ||||
| Transfer | 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TRF-Auckland |
|
|
|
|
|
|
|
|
| |||||
Remaining Qty @ Site >>> | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 7 | 3 | 3 | 2 | 2 | 4 | 4 | 4 | 4 | 4 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | ||||
Berlin | Rental | 4 |
|
|
|
|
|
|
|
| ORD-331 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||
| Transfer | 1 |
|
|
|
|
|
|
|
|
|
| TRF-Auckland |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
| Transfer | 2 |
|
|
|
|
|
|
|
|
|
|
|
| TRF-Auckland (Return) |
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||
Remaining Qty @ Site >>> | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 4 | 4 | 4 | 4 | 2 | 2 | 5 | 5 | 5 | 5 | 4 | 3 | 1 | 1 | 2 | 3 | 5 | 5 | 5 | ||||
Auckland |
| 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-441 |
|
|
|
|
| |||||
|
| 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-442 |
|
|
|
| |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-443 |
|
|
|
Sample Workflow
Change the begin/return dates for rental orders as follows.
Table 3.0: Sample Order Information
Order Site | Order# | Original End Date | Modified End Date |
San Jose | TRF-Berlin | 8th | 16th |
TRF-Berlin (Return) | 12th | 16th |
You can change the dates of the Orders at a site, using any of the following access points.
Order > Dates Tab > Edit Dates
Order > Actions > Change Dates > All Lines/ Selected Lines
Order (Double click) > Line Edit Dates
Order Search > Order Dates Edit
Single Order
Multiple Order
Also, ensure that 'View Affected Orders' checkbox is selected in the window where you had change the return date for the Order.
Changing the above dates, disrupts the availability of the items at the four sites, since the required quantity is no longer available on the expected dates.
The 'Extension Duration' of the Order has been depicted as in the table below.
The 'Impacted Order' due to short-fall in quantity has been depicted as Red Block in the table below.
At Site 'Auckland' the two ORD-442 and ORD-443 depicted as Red Block are 3rd Level affected orders, that's why they do not appear in Figure 5.0
The 'Numbers in Negative' (in Remaining Qty @ Site row) refer to the shortfall quantity.
Table 4.0 Scenarios After dates are modified
Subsequent Situation: No return dates are changed | Order Site | Order Type | Order Qty | Order line Prep-Return Dates (Modified) | Result(s) | ||||||||||||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | |||||
Remaining Qty @ Site >>> | 11 | 11 | 11 | 11 | 11 | 7 | 7 | 5 | 5 | 5 | 5 | 5 | 5 | 1 | 1 | -2 | -2 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | Since there is NO short-fall of quantity at any site on any given day, all the Rental Orders and Transfer Orders get processed without any hindrance. | |||
San Jose | Transfer | 4 |
|
|
|
|
| TRF-Berlin |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||||||
| Rental | 4 |
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-111 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||
| Transfer | 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TRF-London |
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
| Return | 2 |
|
|
|
|
|
|
| TRF-Berlin (Return) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||||
Remaining Qty @ Site >>> | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 0 | 0 | 0 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | ||||
London | Rental | 4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-221 |
|
|
|
|
|
|
|
|
|
| ||||
| Transfer | 3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TRF-Auckland |
|
|
|
|
|
|
|
|
| |||||
Remaining Qty @ Site >>> | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 7 | 3 | 3 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | ||||
Berlin | Rental | 4 |
|
|
|
|
|
|
|
| ORD-331 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||
| Transfer | 1 |
|
|
|
|
|
|
|
|
|
| TRF-Auckland |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
| Transfer | 2 |
|
|
|
|
|
|
|
|
|
|
|
| TRF-Auckland (Return) |
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||
Remaining Qty @ Site >>> | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 4 | 4 | 4 | 4 | 2 | 2 | 5 | 5 | 5 | 5 | 4 | 3 | 1 | 1 | 2 | 3 | 5 | 5 | 5 | ||||
Auckland |
| 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-441 |
|
|
|
|
| |||||
|
| 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-442 |
|
|
|
| |||||
|
| 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ORD-443 |
|
|
|
If 'View Affected Orders' checkbox is selected, then when you attempt to perform the change dates, system gives you the following prompt.
Upon further confirmation, the Affected Order(s) window are shown (Only if there are 1 or more orders which gets affected, this window is displayed).

Figure 5.0 List of 'Affected Orders' when 'Return Date' for TRF-Berlin is modified

Figure 6.0 List of 'Affected Orders' when 'Return Date' for TRF-Berlin (Return) is modified
In case of E-Pool Orders, the site that is considered for checking conflict is Ship and Return site of the Inflicting line.
In case of Orders impacted due to an inflicting transfer order, the system considers a lock-in period of 15-days, from the first instance of transfer order.
For Example:
Let's consider, an Order from Site A to Site B cannot be processed (assumed as cancelled) because an Order at Site A is not getting returned on its original schedule.
Thus subsequently, at Site B, an order cannot be processed, due to unavailability of required stock quantity.
In such situation, system will consider ONLY those orders as 'Impacted/Affected Orders' whose ship date falls within 15 days counting from the ship date of first Impacted/Affected order at site B.
You can expand-collapse the line, to show any 2nd level inflicting order.
For Example:
Using the scenario from previous example, both the Transfer order (Site A) and the Return order (Site A) will be deemed as inflicting orders.
Both of these Orders will appear in an expand/collapse section (in the inflicting Order column) under impacted Orders for Site B. See Figure 5.0