web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Supply chain | Supply Chain Management, Commerce
Suggested Answer

Purpose of delays in coverage time fence

(4) ShareShare
ReportReport
Posted on by 242
hi Experts,
Can anyone explain the purpose of both fields in delay in coverage groups in D365
 
I have the same question (0)
  • Suggested answer
    Peter Kulikov (N.progression) Profile Picture
    579 Super User 2025 Season 2 on at
    Hi!

    Planning Optimization doesn't use the following parameters or options on the Coverage groups page:

    • Delays FastTab:

      • Calculated delays â€“ This parameter isn't considered because delays are always calculated for the coverage group.
      • Calculate delays time fence (days) â€“ This parameter isn't considered because delays are calculated for the Coverage time fence (days)
  • Pranav Teja Profile Picture
    242 on at
    HI Peter Kulikov,
     
    Thanks for responding. Do you mean to say that if planning optimization is used, D365 F&O will never show if a sales order is delayed in net requirements. (say for example in a situation where due to updating confirmed receipt date in a firmed purchase order)
     
    I remember until the time when planning optimization was introduced, D365 showed delays in above scenario and parallelly action to advance against corresponding purchase order. -- in net requirements
     
     
    Thanks,
    Pranav
     
     
  • Suggested answer
    Peter Kulikov (N.progression) Profile Picture
    579 Super User 2025 Season 2 on at
    Hi Pranav,
    No, what I mean is that delays will always be calculated regardless of the value of the Calculate delays parameter. That is, in your example, the order execution delay will be calculated based on the supply delay. However, the number of days for delay calculation is now determined by a different parameter, which I highlighted in the screenshot:
  • Pranav Teja Profile Picture
    242 on at
    Hi Peter Kulikov,
     
    Coverage time fence? ->> for number of days for delay calculation. This is strange. Is this the field that you intend to convey.
     
    Pranav
  • Suggested answer
    Peter Kulikov (N.progression) Profile Picture
    579 Super User 2025 Season 2 on at
    Hi Pranav,
    Yes, that's what it says in the official Microsoft source, at the link I provided below at the first reply.
    • Calculate delays time fence (days) â€“ This parameter isn't considered because delays are calculated for the Coverage time fence (days)

    I didn't check it by myself.
  • Pranav Teja Profile Picture
    242 on at
    HI Peter Kulikov,
     
    Thanks for clarifying. Finally can u explain the meaning of below statement with an example.
     
     
    • Calculate delays time fence (days) â€“ This parameter isn't considered because delays are calculated for the Coverage time fence (days)

    Pranav
  • Suggested answer
    Peter Kulikov (N.progression) Profile Picture
    579 Super User 2025 Season 2 on at
    Hi Pranav,

    As I mentioned earlier, I don’t have practical experience with modifying this parameter, so my response and example will be based solely on theoretical information from the learn.microsoft.com portal.
    Following this link: https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/planning-optimization/coverage-time-fence you can find such information: Coverage time fences affect only input data for master planning. If delays occur, the resulting planned orders might have a date that is after today's date plus the coverage time fence.

    Thus, the coverage time fence defines the maximum possible date for a planned order. In other words, if due to delays, the planned order date exceeds the current date by more than 100 days, such a planned order will not be created.

    For example:
    Today is January 27, 2025.
    The delivery was originally scheduled to arrive on March 30, 2025.
    A planned order had a date of March 31, 2025, because it is 64 days from the current date. This falls within the 100-day range set in the parameter.

    As a result of the delay, the delivery date changed to May 20, 2025.
    That means that the planned order could not be ready earlier than May 21, 2025, which is 114 days from the current date (January 27, 2025). Since the number of days exceeds the set limit (100), such a planned order will not be created.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Laurens vd Tang Profile Picture

Laurens vd Tang 301 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 118 Super User 2025 Season 2

#3
Siv Sagar Profile Picture

Siv Sagar 105 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans