When SWO Leads to a 'Conflict'
In the most colloquial verbatim - A conflict is like a cat-fight. Two or more people claiming their right on a common object.
In R2, this happens when two or more orders reserve the same asset. Thus, to resolve this there need to be rules in place which help draw a line in stone, and address who can assert their claim on the named asset.
We are using the term 'Inflicts' to refer that — A SWO became a cause/source/reason for a conflict to get generated.
As briefed in the Conflicts description above, even in the case of SWO, a conflict may arise at Site Level or at Pool Level.
A Site Level Conflict happening means, an item which is being requested by an Order, is already 'In-repair' with an SWO, and the SWO is not done yet or is Overdue (the Due Date is in past). Explained below are the situations in which a SWO may cause a Conflict, and what would be affects of it.
Prerequisite Data:
Create Stock at Site London with San Francisco with 10 quantity.
Workflow Executed:
SWO [CO1505794913] was created on 1st and was expected to be done on 5th.
Rental Order [ORD-4683] was scheduled to start on 10th.
On 6th the SWO [CO1505794913] goes overdue, and does not get resolved until 11th, by when the Rental Order, has short-fall. Which leads to a conflict.
Table 1.0: Negative Conflicts impacted by Site scenario
Scenario # | Order Site | Line Shipping Site | Order ID | Order Type | Line Status | Order line Prep-Return Dates | ||||||||||||||||||||||||||||||
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 | |||||
SWO was created first. Then SWO dates were modified | London | London | CO1505794913 | SWO | Repair | SWO CO1505794913 is due on 5th. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
London | London | ORD-4863 | Rental | Reservation |
|
|
|
|
|
|
|
|
| ORD-4863 has reserved the same Serial Asset as it is on SWO. |
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||
London | London | CO1505794913 | SWO | Repair | SWO CO1505794913 has gone over due on 6th and is not resolved until 11th. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||||||
Figure 1.0: Conflicts displayed in Warehouse > Conflicts window
If the Site at which the SWO was created belongs to a 'Pool', then — any Rental, Sale or Transfer orders at other sites of the Pool may get impacted; when the SWO becomes overdue, leading to the SWO 'Inflicting' a 'Pool Level Conflict'.