Pool level Conflict
Whenever a conflict occurs at Pool level, the system automatically prioritizes the conflict resolution on the basis of following two preference criterion.
The first criteria is selected on the basis of where (location) the conflict has happened.
First priority = Site conflicts
Second priority = Pool conflicts
The second criteria is selected on the basis of when (event timeline) the conflict has happened.
First Priority = Prep Date in ascending sequence
Second Priority = Order created Date in ascending sequence
The below figure lists all the possible scenarios of Negative Conflicts with Pool conflicts and the Order of preference for conflict resolution.
Table 2.0: Sample Possible - Pool Conflict scenarios
Order of preference for conflict resolution | ||||||||||||||||
| ||||||||||||||||
Examples of Negative Conflicts impacted by Pool scenario | ||||||||||||||||
Pool: California has 2 sites | ||||||||||||||||
Scenario# | Order Site | Line Shipping Site | Order# | Line Status | Quantity On Order | Order line Prep-Return Date | Short Quantity | Date Added | Order of conflict Resolution | Result | ||||||
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
| ||||||||
Scenario 1: |
|
|
|
| Pool Avail -> | -2 | -2 | -2 | 15 | 15 | 15 | 15 |
|
|
| Order# O-333 shows in conflict |
San Francisco | San Francisco | O-111 | Reserved | 10 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
Los Angeles | Los Angeles | O-222 | Reserved | 5 |
|
|
|
|
|
|
|
| 29-Oct | 2 | ||
Los Angeles | California | O-333 | Pool | 2 |
|
|
|
|
|
|
| 2 | 27-Oct | 3 | ||
Scenario 2: |
|
|
|
| Pool Avail -> | -30 | -30 | -30 | 15 | 15 | 15 | 15 |
|
|
| Order# O-111, O-222, and O-333 shows in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 15 |
|
|
|
|
|
|
| 5 | 28-Oct | 1 | ||
Los Angeles | Los Angeles | O-222 | Reserved | 15 |
|
|
|
|
|
|
| 10 | 29-Oct | 2 | ||
Los Angeles | California | O-333 | Pool | 15 |
|
|
|
|
|
|
| 15 | 27-Oct | 3 | ||
Scenario 3: |
|
|
|
| Pool Avail -> | 5 | 0 | -2 | 8 | 13 | 15 | 15 |
|
|
| Order# O-333 shows in conflict |
San Francisco | San Francisco | O-111 | Reserved | 10 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
Los Angeles | Los Angeles | O-222 | Reserved | 5 |
|
|
|
|
|
|
|
| 28-Oct | 2 | ||
Los Angeles | California | O-333 | Pool | 2 |
|
|
|
|
|
|
| 2 | 27-Oct | 3 | ||
Scenario 4: |
|
|
|
| Pool Avail -> | -2 | -2 | -2 | 15 | 15 | 15 | 15 |
|
|
| Order# O-222 shows in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 10 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
Los Angeles | Los Angeles | O-222 | Reserved | 7 |
|
|
|
|
|
|
| 2 | 27-Oct | 2 | ||
Scenario 5: |
|
|
|
| Pool Avail -> | 5 | -5 | -12 | -2 | 8 | 15 | 15 |
|
|
| Order# O-111 and O-333 shows in conflict |
San Francisco | California | O-111 | Pool | 10 |
|
|
|
|
|
|
| 10 | 27-Oct | 3 | ||
San Francisco | San Francisco | O-222 | Reserved | 10 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
Los Angeles | Los Angeles | O-333 | Reserved | 7 |
|
|
|
|
|
|
| 2 | 28-Oct | 2 | ||
Scenario 6: |
|
|
|
| Pool Avail -> | 10 | -5 | -10 | -5 | 10 | 15 | 15 |
|
|
| Order# O-222 shows in conflicts |
Los Angeles | California | O-111 | Pool | 5 |
|
|
|
|
|
|
|
| 27-Oct | 2 | ||
San Francisco | California | O-222 | Pool | 15 |
|
|
|
|
|
|
| 10 | 28-Oct | 3 | ||
San Francisco | San Francisco | O-333 | Reserved | 5 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
Scenario 7: |
|
|
|
| Pool Avail -> | 10 | -5 | -15 | -10 | 5 | 15 | 15 |
|
|
| Order# O-222 and O-333 shows in conflicts |
Los Angeles | California | O-111 | Pool | 5 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
San Francisco | California | O-222 | Pool | 15 |
|
|
|
|
|
|
| 5 | 27-Oct | 2 | ||
San Francisco | California | O-333 | Pool | 10 |
|
|
|
|
|
|
| 10 | 27-Oct | 3 | ||
Scenario 8: |
|
|
|
| Pool Avail -> | -15 | -15 | -15 | 15 | 15 | 15 | 15 |
|
|
| Order# O-222 and O-333 show in conflict |
San Francisco | California | O-111 | Pool | 5 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
Los Angeles | California | O-222 | Pool | 15 |
|
|
|
|
|
|
| 5 | 27-Oct | 2 | ||
San Francisco | California | O-333 | Pool | 10 |
|
|
|
|
|
|
| 10 | 27-Oct | 2 | ||
Scenario 9: |
|
|
|
| Pool Avail -> | -30 | -30 | -30 | 15 | 15 | 15 | 15 |
|
|
| Order# O-111 and O-222 show in conflicts |
Los Angeles | California | O-111 | Pool | 15 |
|
|
|
|
|
|
| 15 | 29-Oct | 3 | ||
San Francisco | California | O-222 | Pool | 15 |
|
|
|
|
|
|
| 15 | 28-Oct | 2 | ||
San Francisco | California | O-333 | Pool | 15 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
Scenario 10: |
|
|
|
| Pool Avail -> | 5 | 0 | -10 | 0 | 5 | 15 | 15 |
|
|
| Order# O-333 shows in conflicts |
Los Angeles | California | O-111 | Pool | 10 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
San Francisco | California | O-222 | Pool | 5 |
|
|
|
|
|
|
|
| 27-Oct | 2 | ||
San Francisco | California | O-333 | Pool | 10 |
|
|
|
|
|
|
| 10 | 27-Oct | 3 | ||
Scenario 11: |
|
|
|
| Pool Avail -> | -10 | -10 | -10 | 15 | 15 | 15 | 15 |
|
|
| Order# O-333 shows in conflicts |
Los Angeles | California | O-111 | Pool | 10 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
San Francisco | California | O-222 | Pool | 5 |
|
|
|
|
|
|
|
| 27-Oct | 2 | ||
San Francisco | California | O-333 | Pool | 10 |
|
|
|
|
|
|
| 10 | 28-Oct | 3 | ||
Scenario 12: |
|
|
|
| Pool Avail -> | 0 | 0 | 0 | 15 | 15 | 15 | 15 |
|
|
| Order# O-222 shows in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 8 |
|
|
|
|
|
|
|
| 28-Oct | 1 | ||
Los Angeles | Los Angeles | O-222 | Reserved | 7 |
|
|
|
|
|
|
|
| 27-Oct | 2 | ||
Scenario 13: |
|
|
|
| Pool Avail -> | -2 | -2 | -2 | 15 | 15 | 15 | 15 |
|
|
| Order# O-222 and O-333 show in conflicts |
San Francisco | San Francisco | O-111 | Reserved | 8 |
|
|
|
|
|
|
|
| 27-Oct | 1 | ||
Los Angeles | Los Angeles | O-222 | Reserved | 3 |
|
|
|
|
|
|
| 2 | 28-Oct | 2 | ||
Los Angeles | Los Angeles | O-333 | Reserved | 6 |
|
|
|
|
|
|
|
| 27-Oct | 3 | ||
Scenario 2: Reserved + Pool lines
For all the three Orders, the prep dates are same and need 15 stock items.
In this case, system first resolves the conflict for site level orders, Hence Order# O-111 and Order# O-222 takes preference.
Again, since the prep dates for both the orders are same, system considers the date on which the Order was created.
Hence, within the site level orders, system resolves the Order# O-111 first. since the created date for that order is earliest one among the two site level orders.
Next, the system proceeds to resolve for Order# O-222 since it is next in line for site level conflict.
In the end, the system picks Order# O-333 since its is pool order and carries the least preference as per the defined criteria.
Scenario 7: All Pool lines
Since all the Orders O-111, O-222, and O-333 has pool lines, system considers the prep date in ascending sequence to resolve the conflict.
Scenario 11: All Pool lines and same prep date
Since all the Orders O-111, O-222, and O-333 has pool lines and prep dates and created date are same, system resolves them on the basis on the timeline sequence they were created.
If Site restriction is defined for an employee
Additionally, if the Site policy is defined for an employee, only the records belonging to the allowed site displays in the conflicts window.
Table 3.0: Conflicts records displays based on the site policy
Site tagged in Site Policy | Conflicts displayed in Conflicts window for the employee |
Region | Employee can view the conflict records for the allowed region. |
Sub-Region | Employee can view the conflict records for the allowed sub-region. |
Site | Employee can view the conflict records for the allowed site. |
All Sites | Employee can view all the conflicts regardless of the Site/ Sub-Region/ Region. |
Along with site policies defined, employee is allowed to view the conflict records for the site tagged on employee edit window as well.
The Site Policy defined makes no difference for conflicts generation. System just controls the visibility of the data of the logged in employee based on the site policy