Understanding PeopleSoft Supply Planning Planned Order Numbering
This section discusses the numbering schemes that the system uses to keep planned orders in the planning instance synchronous with numbering schemes in the transaction system.
PeopleSoft Supply Planning retains two sets of order numbers for each planned order. The first number is unique for a planning instance. The second number is unique within the transaction system. Both numbers reside on the transaction system table and planning instance table, one number is a key, the other number is a reference.
Planning Instance Sequence Number
When you run the Load Planning Instance process (PL_LOAD_OPT) with a run type defined as Regenerative, the process sets the planned sequence number equal to the transaction system sequence number when it inserts these orders into the planning instance tables.
After the Load Planning Instance process inserts all of the orders into the planning instance tables, it updates the next available planning sequence number on the Planning Instance table to equal the last planning sequence number used, plus one, and increments this number each time that you add new planned orders to the planning instance tables.
Transaction System Sequence Number
In the planning instance tables, the system populates the transaction sequence number with the sequence number from the transaction system table record. The system populates this field with a zero for new orders created in the planning instance. Because multiple planning instances can post data back to the transaction system, it is possible that the same planning sequence number can exist in more than one planning instance. To keep orders unique in the transaction system, PeopleSoft Supply Planning also assigns a transaction sequence number.
When you run the Post Updates process, the transaction system stores the next available transaction sequence number by order type on the Installation - Planning table (INSTALLATION_PL). Existing planned orders retain the transaction sequence number assigned when they were first added into the transaction system.
This example demonstrates how the system assigns order numbers for a simple case of regeneration only.
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, using these values:
Planning Instance = MRP.
Business Unit = US008.
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
MRP
US008
1
0
MRP
US008
2
0
These are the next available sequence numbers in the Planning Instance table:
Planning Instance Next Available Planning Sequence Number = 3.
Transaction System Next Available Transaction Sequence Number = 1.
You commit the planning data, 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
MRP
1
US008
2
MRP
2
These are the next available sequence numbers in the transaction system table:
Planning Instance Next Available Planning Sequence Number = 3.
Transaction System Next Available Transaction Sequence Number = 3.
You run Load Planning Instance process again with the run type defined as Regenerative.
Planning Instance
Business Unit
Planning Sequence Number
Transaction Sequence Number
MRP
US008
1
1
MRP
US008
2
2
These are the next available sequence numbers in the Planning Instance table:
Planning Instance Next Available Planning Sequence Number = 3.
Transaction System Next Available Transaction Sequence Number = 3.
You commit the planning data, including the two planned orders, back to the transaction system immediately after the Load Planning Instance process.
Because each planned order has an assigned transaction sequence number, the system assigns no new numbers:
Business Unit
Transaction Sequence Number
Planning Instance
Planning Sequence Number
US008
1
MRP
1
US008
2
MRP
2
These are the next available sequence numbers in the transaction system table:
Planning Instance Next Available Planning Sequence Number = 3.
Transaction System Next Available Transaction Sequence Number = 3.
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.
A limited number of scenarios exist where you import planned order changes into the planning instance with a run type of Net Change. These include:
Converting a planned order into an actual order. The order is deleted from the planning instance.
Adding a planned PO within PeopleSoft Collaborative Supply Management (PeopleSoft CSM). Orders added by PeopleSoft CSM have a blank planning instance and a planning sequence number defined as zero.
Changing an existing planned PO within PeopleSoft CSM.
In this example, you are working with the data from example 2:
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
and:
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
You add a planned order in the transaction system:
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
US008
7
Blank
0
The transaction system's next available Transaction Sequence Number is now = 8.
You convert transaction sequence numbers 5 and 6 into actual POs and run the Load Planning Instance process with a run type of Net Change for problem instance ALLITEMS.
These actions occur:
The Load Planning Instance process deletes all of the planning orders with a transaction sequence equal to zero.
The order number ALLITEMS/US008/5 (planning instance/business unit/transaction sequence number) exists in the planning instance table. Therefore, the system deletes planned order ALLITEMS/US008/5 from the planning instance.
The order number ALLITEMS/US008/ 6 does not exist in the planning instance table. No action occurs.
The order number ALLITEMS/US008/ 7 does not exist in the planning instance table. In the transaction system, planned order US008/7 does not map to any planning instance order. Therefore, the system adds this new order as ALLITEMS/US008/7.
Using the same logic for planning instance GROUP1, the system deletes all of the orders from the planning instance and adds transaction sequence numbers 1, 2, 3, 4, and 7; the system sets the next available planning sequence number to 8.
Using the same logic for planning instance GROUP2, the system deletes all of the orders from the planning instance and adds transaction sequence numbers 1, 2, 3, 4, and 7; the system sets the next available planning sequence number to 8.