Share
Report
147Hello community,
I would like to confirm a specific behavior in D365 F&O (Planning Optimization) related to pegging of manually created purchase orders.
Scenario:
- We have an existing, manually created Purchase Order (not firmed from a planned PO).
- Master planning runs and identifies future demand from Production Orders.
- We have an existing, manually created Purchase Order (not firmed from a planned PO).
- Master planning runs and identifies future demand from Production Orders.
Question:
Is it correct that master planning will only peg this manual PO to future demand (e.g., a production order requirement date in the future), and never backward to a past or already-consumed demand?
Is it correct that master planning will only peg this manual PO to future demand (e.g., a production order requirement date in the future), and never backward to a past or already-consumed demand?
What we have tested:
We tested across multiple coverage group settings (Requirement/Period, action messages, ) and in all cases, the manual PO only pegged forward to future demand. It never pegged to any past demand.
We tested across multiple coverage group settings (Requirement/Period, action messages, ) and in all cases, the manual PO only pegged forward to future demand. It never pegged to any past demand.
What Microsoft Learn implies:
From the Net Requirements and Pegging documentation, the framework is sorted by requirement date and is forward-looking by design. The coverage time fence is always calculated forward from the current date. Positive/negative days also operate on future-facing logic.
From the Net Requirements and Pegging documentation, the framework is sorted by requirement date and is forward-looking by design. The coverage time fence is always calculated forward from the current date. Positive/negative days also operate on future-facing logic.
However, we could not find a single Microsoft article that explicitly states: 'A manually created PO will never peg backward to past demand.'
Could anyone confirm:
1. Is this forward-only pegging behavior by design and documented anywhere officially?
2. Is there any edge case or setting where a manual PO could peg to past demand?
1. Is this forward-only pegging behavior by design and documented anywhere officially?
2. Is there any edge case or setting where a manual PO could peg to past demand?
Any pointers to official Microsoft documentation, FastTrack notes, or TechTalk sessions would be greatly appreciated.
Thank you!
Categories:
I have the same question (0)
All responses (
Answers (
