Maintaining Planning Instances

This topic provides an overview of planning instance maintenance and lists the pages that are used to maintain planning instances.

Pages Used to Maintain Planning Instances

Page Name Definition Name Usage

Copy Planning Instance Page

PL_COPY_PI_REQ

Copy a source planning instance to a new or existing target planning instance.

Understanding Planning Instance Maintenance

Delete Planning Instance Page

PL_DEL_PI_REQ

Delete a planning instance and elect to remove or preserve the corresponding planning instance definition and security.

Understanding Planning Instance Maintenance

Understanding Planning Instance Maintenance

PeopleSoft Supply Planning enables you to copy and delete planning instances.

Planning Instance Copies

When you copy a planning instance, you can enter a new value into the Target Planning Instance field to create a new planning instance definition or enter an existing planning instance to refresh with data from the source planning instance.

When copying planning instances, consider that:

  • If planning instance user-level security is in effect, you can access only those target planning instances that you created, pending expansion of security by an administrator.

  • You must enter a valid source planning instance.

  • The system deletes in its entirety and regenerates the target planning instance.

  • If the target planning instance is loaded into the planning engine, the system stops the process and requires removal of the planning instance from the planning engine before copying.

  • You can produce one copy of a planning instance at a time.

    You cannot make multiple target copies from one source planning instance during a single run.

  • The system deletes the Extra Demand table from existing target planning instances; PeopleSoft Supply Planning does not retain this data.

Planning Instance Deletions

When deleting planning instances, consider that:

  • The system deletes data from tables that are keyed by planning instance only.

  • Staging tables resulting from the Post Updates process that are pending transaction system approval are not affected.

  • You can delete only one planning instance at a time.

  • If the system loads the target planning instance into the planning engine, it stops the process and requires removal of the planning instance from the planning engine before deleting.