This example shows what happens when the system check for existing procurement transactions when generating collective purchase order items. For the sake of simplicity, we’ll look at one issue document only. The example involves a warehouse order with one item and several schedule lines.
Warehouse order |
Item |
Article |
Schedule line |
Quantity |
Delivery date |
Delivery generated on |
1 (store 1) |
1 |
Chocolate |
1 |
100 |
11.10. |
09.10. |
1 |
Chocolate |
2 |
250 |
12.10. |
10.10. | |
1 |
Chocolate |
3 |
150 |
13.10. |
11.10. |
When the collective purchase order is generated, there is stock on-hand (unrestricted-use stock) and an open vendor order item for the article "chocolate". The order item is to be out away at goods receipt.
Date |
Situation/transaction |
Qty in transaction |
Available qty |
05.10. (today) |
Stock on-hand |
100 |
100 |
10.10. |
Planned goods receipt for PO |
200 |
300 (total) |
A collective purchase order is generated on 05.10. and has the following data:
The system now checks availability on the delivery generation date for each schedule line in the warehouse order item.
Date |
Situation/transaction |
Qty in transaction |
Available qty |
Order quantity |
05.10. (today) |
Stock on-hand |
100 |
100 |
|
09.10. |
Delivery generated for schedule line 1 |
100 |
0 |
0 |
10.10. |
Planned goods receipt for PO |
200 |
200 |
0 |
10.10. |
Delivery generated for schedule line 2 |
250 |
0 |
50 |
11.10. |
Delivery generated for schedule line 3 |
150 |
0 |
200 (total) |
The total quantity of the collective purchase order item is 250.
(This quantity may be divided among several schedule lines in the collective purchase order, depending on the interval between the individual schedule lines.)