EBS: PS: PS Model is Not Published, If a Collections is Run After The PS Plan is Launched

(Doc ID 2021334.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Production Scheduling
Information in this document applies to any platform.

Symptoms

PS Model becomes invalid for publishing, if a Collections is run after the PS Plan is launched, which forces the Users to synchronize multiple PS Plans rather than independent Plans.

Below are the scenario's associated with the issue:

After completing Collections1 and launching PS Plan1:
1. if you Approve & Publish PS Model before the Collections2 is triggered, then you would observe WIP Mass Load and the SCP Integration log would be updated with LOADED_JOBS and RESCHED_JOBS, publishing the PS Model.
2. if you Approve & Publish PS Model after the Collections2 is completed, then WIP Mass Load is not triggered and SCP Integration log would be updated with zero LOADED_JOBS and RESCHED_JOBS. PS Model is not published.
3. if you Approve & Publish PS Model after the Collections2 is triggered (before the Planning ODS Load), then you would observe WIP Mass Load and the SCP Integration log would be updated with LOADED_JOBS and RESCHED_JOBS, publishing the PS Model.
4. if you Approve & Publish PS Model after the Collections2 is triggered (after Planning ODS Load), then WIP Mass Load is not triggered and SCP Integration log would be updated with zero LOADED_JOBS and RESCHED_JOBS. PS Model is not published.

With the above scenarios, steps 2 & 4 are invalidated and PS Model is not published. Require a feature/functionality such that even with Steps 2 & 4 being followed, PS Model is published appropriately.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms