Finite Horizon heirarchy

We have experimented with extending our finite horizon on our MRP runs. We did this by editing both the finite horizon on site maintenance, and on the individual resources.

If we reduce the finite horizon in site maintenance, will Epicor use that value even though it will be less than what is on the resource group settings?

Can anyone explain the heirarchy of Epicor honoring the finite horizon setting?

Thanks in advance.

According to the Scheduling Technical Reference guide on EpicWeb for 10.2.600:

1 Like

We will test this shortly. Thanks for looking into this! Have you any real world experience in how it actually works in the software?

We don’t have the Finite Horizon set on any of our Sites, Resource Groups, or Resources any more (they are all set to 0) – we finitely schedule our entire schedule. We used to have a finite horizon of 14 days set for some Resource Groups while the Site setting was 0, and Epicor used the 14 day value for those groups.