Example 3: Net Change Example

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.

  1. 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

  2. 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.

  3. 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.