Example 1: Regeneration

This example demonstrates how the system assigns order numbers for a simple case of regeneration only.

  1. You plan for a group of items for the first time.

    No planned orders exist in the transaction system.

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

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

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

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

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