ECC Classic Constrained Plan Pegging On Hand To Future Demands While Planned Orders Pegged To Earlier Demands (Cross Pegging) - Non Project Environment

(Doc ID 2333189.1)

Last updated on NOVEMBER 28, 2017

Applies to:

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

Symptoms

On 12.2.5 Constrained Planning in All instances:

Users are running an ECC Classic Constrained classic plan and have applied 12.2.5.2 patching. This plan is using priority pegging, where the demand priority rule is by schedule date. The bucketing is entirely in weeks (52 weeks).
The supply/demand includes cross-pegging results.  Planned order has earlier demand pegged to it than on Hand and a higher priority demand of sales order.  Example data

1. Order number transaction id for planned order qty = 900 due 20-OCT-2017
Org = EME:700
Item = 143215
trans id = 172220400

2. Horizontal plan

Org = EME:700
Item = 143215

With all the lead time rollups done and the backward/forward firm supply allocation windows set to 10 and the align component pegging profile = No users still have early planned order on the anchor date of the plan

Total Demand on 20-OCT - anchor date = 3,155.00
Supply
A. We should exhaust all on hand qty = 1,695.10 first - however we can see many demands in the future pegged to this supply
B. Second we should exhaust firm PO in receiving qty = 900 due 23-OCT since it's within the 10 day forward period for demand - At this point we only need another 559.9 qty to satisfy demand. There's an unfirm PO qty = 900 also due on 20-OCT-2017 and that would leave us +340.1 PAB -
C. however there is a planned order qty = 900 due on 20-OCT-2017 and users don't understand why it's so early

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