Example 2: Multiple Problem Instances, Exclusive Items, and Regeneration Only
This example demonstrates the order numbering assignment during a more complex scenario, with multiple planning instances, exclusive items, and a run type defined as Regenerative.
-
You plan for a group of items for the first time.
No planned orders exist in the transaction system.
-
You run the Load Planning Instance process with the run type defined as Regenerative, and use these values:
-
Planning Instance = GROUP1.
-
Business Unit = US008.
-
Planning Instance Next Available Planning Sequence Number = 1.
-
Transaction System Next Available Transaction Sequence Number = 1.
-
-
You run a planning solver, which adds two planned orders:
Planning Instance Business Unit Planning Sequence Number Transaction Sequence Number GROUP1
US008
1
0
GROUP1
US008
2
0
These are the next available sequence numbers in the Planning Instance table:
-
Planning Instance GROUP1 Next Available Planning Sequence Number = 3.
-
Transaction System Next Available Transaction Sequence Number = 1.
-
-
You plan for a second group of items for the first time.
No planned orders exist in the transaction system.
-
You run the Load Planning Instance process with the run type defined as Regenerative, using these values:
-
Planning Instance = GROUP2.
-
Business Unit = US008.
-
Planning Instance Next Available Planning Sequence Number = 1.
-
Transaction System Next Available Transaction Sequence Number = 1.
-
-
You run a solver, which adds three planned orders:
Planning Instance Business Unit Planning Sequence Number Transaction Sequence Number GROUP1
US008
1
0
GROUP1
US008
2
0
GROUP2
US008
1
0
GROUP2
US008
2
0
GROUP2
US008
3
0
These are the next available sequence numbers in the Planning Instance table:
-
Planning Instance GROUP2 Next Available Planning Sequence Number = 4.
-
Transaction System Next Available Transaction Sequence Number = 1.
-
-
You commit the planning data for planning instance GROUP1, including the two planned orders, back to the transaction system.
The new planned orders do not have a transaction sequence number, so the system assigns each planned order a transaction sequence number:
Business Unit Transaction Sequence Number Planning Instance Planning Sequence Number US008
1
GROUP1
1
US008
2
GROUP1
2
The transaction system's next available Transaction Sequence Number is now = 3.
-
You commit the planning data for planning instance GROUP2, including the three planned orders, back to the transaction system.
The new planned orders do not have a transaction sequence number, so the system assigns each planned order a transaction sequence number:
Business Unit Transaction Sequence Number Planning Instance Planning Sequence Number US008
1
GROUP1
1
US008
2
GROUP1
2
US008
3
GROUP2
1
US008
4
GROUP2
2
US008
5
GROUP2
3
The transaction system's next available Transaction Sequence Number is now = 6.
-
You create a new planning instance that represents all of the items.
-
You run the Load Planning Instance process with the run type defined as Regenerative, using these values:
-
Planning Instance = ALLITEMS.
-
Business Unit = US008.
-
Planning Instance Next Available Planning Sequence Number = 1.
-
Transaction System Next Available Transaction Sequence Number = 6.
-
-
You run the Load Planning Instance process with the run type defined as Regenerative, which produces these results:
Planning Instance Business Unit Planning Sequence Number Transaction Sequence Number GROUP1
US008
1
0
GROUP1
US008
2
0
GROUP2
US008
1
0
GROUP2
US008
2
0
GROUP2
US008
3
0
ALLITEMS
US008
1
1
ALLITEMS
US008
2
2
ALLITEMS
US008
3
3
ALLITEMS
US008
4
4
ALLITEMS
US008
5
5
These are the next available sequence numbers in the Planning Instance table:
-
Planning Instance ALLITEMS next available Planning Sequence Number = 6.
-
Transaction system next available Transaction Sequence Number = 6.
-
-
You freeze all of the orders in planning instance ALLITEMS, run a solver, and assume one additional order is added:
Planning Instance Business Unit Planning Sequence Number Transaction Sequence Number GROUP1
US008
1
0
GROUP1
US008
2
0
GROUP2
US008
1
0
GROUP2
US008
2
0
GROUP2
US008
3
0
ALLITEMS
US008
1
1
ALLITEMS
US008
2
2
ALLITEMS
US008
3
3
ALLITEMS
US008
4
4
ALLITEMS
US008
5
5
ALLITEMS
US008
6
0
These are the next available sequence numbers in the Planning Instance table:
-
Planning Instance ALLITEMS next available Planning Sequence Number = 7.
-
Transaction system next available Transaction Sequence Number = 6.
-
-
You import the planning data for planning instance, ALLITEMS, back to the transaction system.
The ALLITEMS planning instance represents the items in GROUP1 and GROUP2; therefore, orders exist in this group that also exist in the transaction system. To distinguish between new planned purchase orders (POs) and existing planned POs in the transaction system, the system:
-
Deletes from the transaction system—on an item-by-item basis—any planned POs that do not exist in the imported planning instance.
-
Updates the transaction system records for existing planned POs with relevant data in the planning instance table records.
-
Inserts new planned POs—orders in the planning instance that have a transaction sequence number defined as zero—into the transaction system tables.
In this example, the system has previously assigned the first five orders transaction sequence numbers. The system updates these orders with any relevant changes.
For planned transfer and production orders, the system deletes all of the orders from the transaction system and inserts planned orders into the transaction system tables.
The last order does not have an assigned transaction sequence number. This new order is inserted into the transaction system table and assigned a transaction sequence number from the Installation - Planning table.
Business Unit Transaction Sequence Number Planning Instance Planning Sequence Number US008
1
ALLITEMS
1
US008
2
ALLITEMS
2
US008
3
ALLITEMS
3
US008
4
ALLITEMS
4
US008
5
ALLITEMS
5
US008
6
ALLITEMS
6
The transaction system's next available Transaction Sequence Number is now = 7.
-