In D365, Planning Optimization (Net Requirements), we are observing inconsistent and incorrect calculation of Action Days along with discrepancies between Requirement Date and Requested Date (pegging), even though no issue margin or safety margin is configured (issue margin = 0). The system does not consistently follow the expected logic of calculating Action Days based on the difference between requested date and requirement date, resulting in unexpected values (e.g., showing -14 instead of a much larger delay like -62) and, in some cases, returning -1. Additionally, the behavior is inconsistent across items under the same setup, where some items show correct results while others do not, which makes planning outputs unreliable and difficult to trust.

Key Symptoms:

• Action Days do not follow the expected calculation logic (Requested Date – Requirement Date)
• Significant differences between expected and actual values (e.g., -14 instead of a much larger delay like -62)
• Some records return -1 unexpectedly
• Inconsistent behavior across items under the same setup:
• Some items show correct results
• Others show incorrect or inconsistent values

Configuration Context:

• Issue margin = 0 (no safety or issue margin applied)
• No configuration changes influencing the behavior