How To Investigate Pegging Via SQL For An Item OR When We See Planned Orders Created Too Early (Doc ID 1511919.1)

Last updated on MARCH 28, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

Case #1

Pegging in the plan is not correct and need SQL output to see results for one item in the plan.
This is standard SQL used by DEV to help understand the pegging in the plan output

Then we show item SQL to check for Order Modifiers which could be effecting how the item is pegging

Case #2

We are reviewing the Plan output and see that planned orders are appearing early in the plan.
When we review the pegging, we see that some orders have pegging lines that are more than 30 days into the future and we want to be able to get SQL output that will help us identify these orders throughout the plan and investigate/determine the possible cause(s)?

Solution

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