User-configured IBA
In user-configured IBA, rules can be defined to provide sequences and conditions to orders and order lines. A condition can be created, and orders matching this condition will be given priority.
For example, in the following table, Buyer1, Buyer 2, and Buyer3 are competing for inventory.
Purchase order | Item | Node | Qty | ETA | Sales order | Item | Node | Qty | Demand ship date | Order date | Buyer org |
---|---|---|---|---|---|---|---|---|---|---|---|
PO1 | Item1 | Node1 | 5 | 11/15/08 | SO1 | Item1 | Node1 | 5 | 11/16/08 | 11/03/08 | Buyer1 |
PO2 | Item1 | Node1 | 5 | 11/20/08 | SO2 | Item1 | Node1 | 5 | 11/21/08 | 11/05/08 | Buyer2 |
PO3 | Item1 | Node1 | 5 | 11/21/08 | SO3 | Item1 | Node1 | 5 | 11/22/08 | 11/10/08 | Buyer3 |
PO4 | Item1 | Node1 | 5 | 11/25/08 | SO4 | Item1 | Node1 | 5 | 11/26/08 | 11/15/08 | Buyer4 |
The following table shows that if Buyer3 is configured for priority, the demand ship date for Buyer3 will change to 11/16/08, giving Buyer3 priority over Buyer2 and Buyer4. Because user-configured priorities are completed, the FIFO priorities take effect, with Buyer2 and Buyer 4 competing for inventory. Buyer2 gets the earlier demand ship date due to its earlier order date.
Purchase order | Item | Node | Qty | ETA | Sales order | Item | Node | Qty | Demand ship date | Order date | Buyer org |
---|---|---|---|---|---|---|---|---|---|---|---|
PO1 | Item1 | Node1 | 5 | 11/15/08 | SO1 | Item1 | Node1 | 0 | N/A | 11/03/08 | Buyer1 |
PO2 | Item1 | Node1 | 5 | 11/20/08 | SO2 | Item1 | Node1 | 5 | 11/21/08 | 11/05/08 | Buyer2 |
PO3 | Item1 | Node1 | 5 | 11/21/08 | SO3 | Item1 | Node1 | 5 | 11/16/08 | 11/10/08 | Buyer3 |
PO4 | Item1 | Node1 | 5 | 11/25/08 | SO4 | Item1 | Node1 | 5 | 11/22/08 | 11/15/08 | Buyer4 |