Site level Conflict
Whenever a conflict occurs at site level, the system prioritizes the conflict resolution on the basis of only one preference criteria.
It considers the PrepDate in Ascending Order as 1st preference and then considers the CreatedDate in Ascending order as 2nd.
For better understanding of the Order preference for conflict resolution, lets go through few scenarios from the given figure.
Table 1.0: Sample Possible - Site Conflict scenarios
Order of preference for conflict resolution - PrepDate in Ascending Order (1st), CreatedDate in Ascending (2nd) | ||||||||||||||||
| ||||||||||||||||
Examples of Conflicts within the same site | ||||||||||||||||
Sites: San Francisco and Los Angeles. | ||||||||||||||||
Scenario# | Order Site | Line Shipping Site | Order# | Line Status | Qty on Order | Order line Prep-Return Dates | Short Qty | Date Added | Order of conflict Resolution | Result | ||||||
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
| ||||||||
Scenario 1: All Reserved lines |
|
|
|
| San Francisco Avail -> | 10 | 5 | -2 | -10 | -5 | -6 | -6 |
|
|
| Order# O-111, O-333, and O-444 show in conflict |
San Francisco | San Francisco | O-111 | Reserved | 8 |
|
|
|
|
|
|
| 6 | 27-Oct | 4 | ||
San Francisco | San Francisco | O-222 | Reserved | 5 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
San Francisco | San Francisco | O-333 | Reserved | 7 |
|
|
|
|
|
|
| 2 | 28-Oct | 2 | ||
San Francisco | San Francisco | O-444 | Reserved | 8 |
|
|
|
|
|
|
| 8 | 28-Oct | 3 | ||
Scenario 2: |
|
|
|
| San Francisco Avail -> | 0 | -1 | -1 | -1 | 0 | 10 | 10 |
|
|
| Order# O-222 shows in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 10 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
San Francisco | San Francisco | O-222 | Reserved | 1 |
|
|
|
|
|
|
| 1 | 27-Oct | 2 | ||
Scenario 3: |
|
|
|
| San Francisco Avail -> | -9 | -9 | -9 | -9 | -9 | 10 | 10 |
|
|
| Order# O-111 shows in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 9 |
|
|
|
|
|
|
| 9 | 28-Oct | 2 | ||
San Francisco | San Francisco | O-222 | Reserved | 10 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
Scenario 4: |
|
|
|
| San Francisco Avail -> | -10 | -10 | -10 | -10 | -10 | 10 | 10 |
|
|
| Order# O-222 shows in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 10 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
San Francisco | San Francisco | O-222 | Reserved | 10 |
|
|
|
|
|
|
| 10 | 28-Oct | 2 | ||
Scenario 2: All Reserved lines
To resolve the conflict, system first validates if the conflict is happened in a site or pool.
Since the conflict is within the site in scenario 2, system checks the second order of preference i.e, prep dates for both the Orders.
Since the Order# O-111 prep date is earlier, system resolves the conflict of the O-111 and then the O-222.