We are implementing the manufacturing modules of DBA.  We are debating which scheduling choice to use.  Firm due dates are important to us.  We have mulitples of the same machine within a workcenter.  We have multiple different workcenters.  We are leaning towards finite scheduling to take advantage of the parent-child workcenter relationship.  Would someone who has experience (good or bad) with these choices, please give me feedback on this?

We are trying to use finite scheduling and have been at it for quite some time.  Problem with the due date, is it doesn't show up in a lot of the reports, the finish date shows up.  When we create a work order, we have had to remove the part number description and replace it with our heat code and order due date in order to "see" this info on reports. (a lot of maintenance that kills me when the info is there but just can't be seen)
 
When you run "Finite Schedule", the system moves the finish date based on capacity, etc.  So far for us, it still takes someone massaging the report and deciding what will actually go into the machine 1st, 2nd, 3rd...  The good thing, is that the parts are at least on a list for production.
 
Another problem we run into is that the scheduling time is relieved by the pieces/hours going through on the time cards.  If payroll falls behind in entering, then the scheduling reports are off by that time.  Also, even though the operation is designated as complete, it still shows up on the schedule if one or two parts are not accounted for.

The only report that will show you the assignment of work orders to the Child Work Centers is SH-O.