Short Order Transfer
Content was last updated in 06.22.07-00
Revision
History
Let's
go back to your college days. Imagine you have borrow a book to study
for semester. The book is due for return to the library on July 22nd.
Although, your own work is done, by 18th, you lend the book further to
your roommate who decides to keep it until July 28th.
Now,
there are two things happening due to this —
First, obviously, the book is overdue at the library by 6 days. Secondly,
anyone who may have requested or reserved the book for 23rd is still waiting
for it. So, until there are ample number of copies available on the library
shelf, on 23rd the 'net availability' for the book goes -1,
just because you decided to delay returning the book, despite a due date.
In
all aspects, that's exactly what is wrong in this approach. And, there
is only one way to fix it —
When the return date on a borrowed item is due, 'returning it back to
the original place' should take higher preference.
Overall Scenario
A
Transfer Order is created from site A to site B, to fullfil a reservation
order (Order 1) at site B.
At
site B, when it is time to return the borrowed items to site A, another
order at site B (Order 2) comes up, requesting the item to reserved for
it.
However,
since the MAIN Transfer Order (at site A), has already reserved the item
for its Return Transfer Order (from site B to site A), so no items are
reserved for Order 2.
Thereby
completing the TO lifecycle at site A and creating a shortfall for Order
2 at site B.
Table
2.0 Sample Scenario
Order Site |
Order
Type |
Qty |
|
Order line Prep-Return Dates |
0 |
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 >>> |
10 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
10 |
10 |
10 |
10 |
10 |
10 |
San Jose |
Transfer
Out |
2 |
|
Trf
Order to London |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remaining Qty @ Site >>> |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
-2 |
-2 |
-2 |
-2 |
-2 |
-2 |
-2 |
-2 |
-2 |
London |
Rental |
2 |
|
|
|
|
|
ORD-1121 |
|
|
|
|
|
|
|
|
|
|
Return Transfer |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Return to San Jose |
|
|
|
|
|
|
Rental |
2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ORD-1122 |
Behavior of Items/Assets
- When they are on a Transfer Order (TO)
While creating
a Two-way Transfer Order (A TO
with a Return Transfer Order)
System validates the availability of
the equipment being transferred in the sending site for the required
period of the equipment and Reserve it on the Main Transfer Order.
And if it is able to reserve it on Main
Transfer Order, it also Reserves it on the Return Transfer Order without
verifying any availability in the Receiving Site.
When creating One-way Transfer Order (A TO without
Return Transfer Order)
 |
if
the required quantity is available ONLY partially, then system
blocks its availability accordingly.
If items are directly added to the Return
Transfer Order, then the system
If the TO is edited (lines deleted, quantity
modified, dates modified) system would adjust the availability
accordingly.
If the TO is filled using Force Reserve,
system would overlook the availability in Main TO as well as Return
TO |
 |
The
above behavior is retained irrespective of the access point of
preparing the Transfer Order:
Main
Transfer window Transfer
Detail window Add
Items option Add
and prep Readfile/Readdata
Also, the behavior works for all types
of Kits/Items - both serial and non-serial |