Multiple requirements for 1 planned order with coverage period of 1 day

Finance and Operations/AX User Forum
1

Hi,

Can someone explain how the pegging is working looking if I am looking it from a Planned purchase or production order ( path: planned order / pegging tab vs looking it from Released item ? ( Path: release item/ Plan / Net requirements/ pegging tab)

It is really confusing and I dont have results I expect. Exemple: For Coverage period of 1 day, system creates a planned order that are pegging multiple production orders ( # required date) and I dont understand why.

2

The pegging screen simply shows why the demand has been created/suggested. The net requirements pegging shows the same view I believe - are you saying they are showing you different results or you simply don’t understand them? As per the other post you need to post an example of what you don’t understand and why. My guess is you have run it on one day and firmed demand and then run it again, demand falls in the same window and you do not get an action message to update, instead you get a create new, so you do and therefore you have two orders on the same day for a single coverage which will be pegged to potentially 2 sales orders each depending upon the view as you are period setup and not requirement, so it will soft allocate to get the net requirements correct.

3

Hi ,

It looks like I have the same issue.

I have an item XYZ that has the following settings:

Coverage Code = Period – 1 day and I don’t understand why I have 2 planned orders for the same requirement which is only 1 production order on a specific date.

Can someone have an idea? Thanks



Planned Order #

Part

Warehouse

QTY

Pegged Req

Req Date

Delivery Date

Start Date

End Date

Order Date

Pegged Req Date


PLN-01

‪‪‪ABC

WH1

1.5

PRD-0001

5/30

5/29

5/22

5/29

5/22

5/30


PLN-02

ABC

WH1

8.5

PRD-0001

5/30

5/29

5/22

5/29

5/22

5/30
4

When you say it looks like you have the same issue, it was yours originally.

You need to tell us about the demand, the item coverage settings, and how you are marking in the parameters etc. There are so many reasons this can be like this.