Availability adjustment during Transfer Orders for Assets having SWO
Through this feature, for any Asset with active SWOs when transferred, the availability would reflect appropriately at the Receiving Site and also in the Sending Site during Transit.
To Understand this features, let's get the prerequisites
There are two Sites: Sending Site [Budapest] and Receiving Site [Vienna].
A Serial Asset is Created and stock count is as follows:
Item Stock Details | Stock Count | Asset IDs |
At Budapest | 2 | SR1506903225, SR1506903227 |
At Vienna | 0 | NA |
To understand how Asset consumption on the SWO and TO, affects the overall availability we will look at the following 6 scenarios.
Scenario #1: When...
A SWO (SWO#1) is created at Budapest for Asset [SR1506903225] and the Status for SWO is changed to 'OPEN'.
Also the Same Asset is 'Reserved' on TO#1 from Budapest to Vienna.
Table 1.0: When SWO1 is in Open/Scheduled and Start Date/Scheduled Date is after Receive Date and Filled on the TO
Service Site | Availability Site | Order Type | Stock Status |
Start/End Dates for SWO and Prep/Receive Dates for TO
| ||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ||||
|
| TO | In-Transfer |
|
|
|
|
|
|
|
|
|
|
| TO #1 |
|
|
|
|
|
| |||
Budapest | Vienna | SWO | In-Repair |
|
|
|
|
|
|
|
|
|
| SWO #1 |
| |||||||||
|
| |||||||||||||||||||||||
Remaining Qty @ Budapest | Total | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | ||
| Available | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | ||
| T-Out | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
|
| |||||||||||||||||||||||
Remaining Qty @ Vienna | Total | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| Available | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| T-Int | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
The above Gantt Chart explains that...
Repair shows at Budapest as no asset is not yet filled on TO.
Repair shows between SWO Start Date and Due Date at Budapest.
T-Out as well as Repair reduces availability at Budapest Site, since system does not know you are going to fill the Repair Asset.
T-In at Vienna increases the availability at Vienna.
The same information when viewed in the EUV Window is displayed as follows:
Scenario #2: When...
A SWO is created at Budapest for Asset [SR1506903225] and the Status is changed to 'OPEN'.
Also the Same Asset is 'Filled' on TO#1 from Budapest to Vienna. Not yet received at Vienna.
Table 2.0: When SWO1 is in Open/Scheduled and Start Date/Scheduled Date is after Receive Date and Filled on the TO
Service Site | Availability Site | Order Type | Stock Status |
Start/End Dates for SWO and Prep/Receive Dates for TO
| ||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ||||
|
| TO | In-Transfer |
|
|
|
|
|
|
|
|
|
|
| TO #1 |
|
|
|
|
|
| |||
Budapest | Vienna | SWO | In-Repair |
|
|
|
|
|
|
|
|
|
| SWO #1 |
| |||||||||
|
| |||||||||||||||||||||||
Remaining Qty @ Budapest | Total | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | ||
| Available | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| T-Out | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
|
| |||||||||||||||||||||||
Remaining Qty @ Vienna | Total | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| Available | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | ||
| T-Int | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
The above Gantt Chart explains that...
Repair shows at Vienna as asset you filled is a repair asset.
Repair shows at Vienna between TO#1 line Receive Date and Due Date.
T-Out reduces availability at Budapest and Repair reduces availability at Vienna, since system knows what you have filled is the Repair Asset.
T-In at Vienna increases the availability at Vienna.
The same information when viewed in the EUV Window is displayed as follows:
Scenario #3: When...
A SWO is created at Budapest for Asset [SR1506903225] and the Status is changed to 'OPEN'.
Asset on TO#1 is 'Shipped' from Budapest and 'Received' at Vienna.
Table 3.0: When SWO1 is in Open/Scheduled and Start Date/Scheduled Date is after Receive Date and Filled on the TO
Service Site | Availability Site | Order Type | Stock Status |
Start/End Dates for SWO and Prep/Receive Dates for TO
| ||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ||||
|
| TO | In-Transfer |
|
|
|
|
|
|
|
|
|
|
| TO #1 |
|
|
|
|
|
| |||
Budapest | Vienna | SWO | In-Repair |
|
|
|
|
|
|
|
|
|
| SWO #1 |
| |||||||||
|
| |||||||||||||||||||||||
Remaining Qty @ Budapest | Total | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Available | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| T-Out | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
| |||||||||||||||||||||||
Remaining Qty @ Vienna | Total | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Available | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | ||
| T-Int | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
The above Gantt Chart explains that...
Repair shows at Vienna as asset you filled is a repair asset.
Repair shows at Vienna between TO#1 line Receive Date and Due Date.
T-Out reduces availability at Budapest and Repair reduces availability at Vienna, since system knows what you have filled is the Repair Asset.
T-In at Vienna increases the availability at Vienna.
The same information when viewed in the EUV Window is displayed as follows:
Scenario #4: When...
A SWO is created at Budapest for Asset [SR1506903225] and SWO is in Open/Scheduled
Asset is 'Received' at Vienna through the Transfer Order.
Table 4.0: When SWO1 is in Open/Scheduled and Asset is 'Received' at Vienna through the TO
Service Site | Availability Site | Order Type | Stock Status |
Start/End Dates for SWO and Prep/Receive Dates for TO
| ||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ||||
|
| TO | In-Transfer |
|
|
|
|
|
|
|
|
|
|
| TO#1 |
|
|
|
|
|
| |||
Budapest | Vienna | SWO | In-Repair |
|
|
|
|
|
|
|
|
|
| SWO#1 |
| |||||||||
|
| |||||||||||||||||||||||
Remaining Qty @ Budapest | Total | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Available | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| T-Out | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
| |||||||||||||||||||||||
Remaining Qty @ Vienna | Total | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Available | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | ||
| T-In | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
The above Gantt Chart explains that...
Repair shows at Vienna as the asset you filled is a repair asset.
Repair shows at Vienna between TO#1 line SWO#1 Start Date and Due Date
T-Out reduces availability at Budapest Site and Repair reduces availability at Vienna Site, since the system knows what you have filled is the Repair Asset.
T-In at Vienna increases the availability at Vienna.
The same information when viewed in the EUV Window is displayed as follows:
Scenario #5: When...
A SWO is created at Budapest for Asset [SR1506903225] and the Status is changed to 'OPEN'.
Asset is 'Un-Filled' on TO#1 at Budapest, and Transfer is not completed.
Table 5.0: When SWO1 is in Open/Scheduled and Start Date/Scheduled Date is after Receive Date and Filled on the TO
Service Site | Availability Site | Order Type | Stock Status |
Start/End Dates for SWO and Prep/Receive Dates for TO
| ||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ||||
|
| TO | In-Transfer |
|
|
|
|
|
|
|
|
|
|
| TO #1 |
|
|
|
|
|
| |||
Budapest | Vienna | SWO | In-Repair |
|
|
|
|
|
|
|
|
|
| SWO #1 |
| |||||||||
|
| |||||||||||||||||||||||
Remaining Qty @ Budapest | Total | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | ||
| Available | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | ||
| T-Out | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
|
| |||||||||||||||||||||||
Remaining Qty @ Vienna | Total | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| Available | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| T-Int | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
The above Gantt Chart explains that...
Repair shows at Vienna as asset you filled is a repair asset.
Repair shows at Vienna between TO#1 line Receive Date and Due Date.
T-Out reduces availability at Budapest and Repair reduces availability at Vienna, since system knows what you have filled is the Repair Asset.
T-In at Vienna increases the availability at Vienna.
The same information when viewed in the EUV Window is displayed as follows:
Scenario #6: When...
A SWO is created at Budapest for Asset [SR1506903225] SWO is in Open/Scheduled
Start Date/Scheduled Date is after Receive Date and Filled on the TO
Table 6.0: When SWO1 is in Open/Scheduled and Start Date/Scheduled Date is after Receive Date and Filled on the TO
Service Site | Availability Site | Order Type | Stock Status |
Start/End Dates for SWO and Prep/Receive Dates for TO
| ||||||||||||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ||||
|
| TO | In-Transfer |
|
|
|
|
|
|
|
|
|
|
| TO #1 |
|
|
|
|
|
| |||
Budapest | Vienna | SWO | In-Repair |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWO #1 |
| ||
|
| |||||||||||||||||||||||
Remaining Qty @ Budapest | Total | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | ||
| Available | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
| T-Out | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | ||
|
| |||||||||||||||||||||||
Remaining Qty @ Vienna | Total | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||
| Available | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | ||
| Repair | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | ||
| T-In | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | ||
The above Gantt Chart explains that...
Repair shows at Vienna as the asset you filled is a repair asset.
Repair shows at Vienna between TO#1 line SWO#1 Start Date and Due Date
T-Out reduces availability at Budapest Site and Repair reduces availability at Vienna Site, since the system knows what you have filled is the Repair Asset.
T-In at Vienna increases the availability at Vienna.
The same information when viewed in the EUV Window is displayed as follows:
Some additional scenarios when Repair asset is filled on TO
Situation | Outcome |
When SWO is in Estimate and Fill the asset on TO | We will change Availability Site upon filling and Service Site to Receiving Site upon receiving same as other status SWOs |
When SWO1 is in Scheduled and Fill/Ship the asset on TO | This case is same as what we have described above when SWO1 is Open. |
When SWO is in Estimate and Fill/Ship the asset on TO and then convert the SWO to Scheduled | We will do not allow to change the SWO status to scheduled when asset status is In-Transfer |
When SWO is in Scheduled and Fill/Ship the asset on TO and then convert the SWO to Open | We will do not allow to change the SWO status to either Estimate / Open when asset status is In-Transfer |
When SWO is in Open/Scheduled and Due Date is in the past of Receive Date and try to Fill the asset on TO | We will not allow to fill such asset on TO. |