Preserve Pre-Released Production Dates
Select this option to specify that APS should not move out a job or production schedule item's Projected date to account for changes in the availability of material components. In effect, selecting this field removes the internal requirement that a Firm job or Planned production schedule must have a material on a bill of material before it can be completed (which can push out the Projected date on the parent demand while the demand waits on the material). Therefore, when this field is selected, the Projected date remains the same as the job or production schedule's End/Due date.
Do not select this option to allow APS to recalculate a projected date that is later than the End/Due date, in the situation where the required material components become delayed. In this case, the system moves the demand's Projected date out to account for the delay.
You should consider selecting this field if you expect the dates on Firm jobs and Planned production schedules to remain fixed. However, be aware that when lateness occurs, instead of automatically moving out the dates, APS will generate an exception message; you will need to deal with the lateness manually.
See the table below for more information about how this field affects when the demand consumes material components and when the job supply will be available.
Status | Quantity | Material Components Consumed at... | Job Supply Available at... | Description |
---|---|---|---|---|
PLN | n/a | Job's projected start date. This date is controlled by APS and is not visible in SyteLine. This is the date the system "thinks" the job can start, based on the latest plan data. This date may change. | Job's projected end date (controlled by APS) | Planned orders display on the Planning Detail and Material Planner Workbench forms. |
Firm, not scheduled AND Preserve Pre-Released Production Dates parameter not selected | Fixed | Job's projected start date (controlled by APS). | Projected date (displayed to the user in the Projected field) | The lack of a component or resource capacity on an operation may push the job start or end date out (the reason for this will not be evident on the Job Orders form, but may be visible in the Analyzer). |
Firm, not scheduled AND Preserve Pre-Released Production Dates parameter selected | Fixed | Job's Start date (user-entered) | End date (calculated with lead time or by incremental planning) | APS plans the operations, and if they extend past the job End date, it generates an exception message. You can see planned operation dates in the Analyzer |
Released, not scheduled AND Plan Materials at Operation Start parameter not selected | Fixed | Job's Start date (user-entered) | End date (calculated with lead time or by incremental planning) | APS plans the operations, and if they extend past the job End date, it generates an exception message. You can see planned operation dates in the Analyzer |
Released, not scheduled AND Plan Materials at Operation Start parameter selected | Fixed | Job operation's Start date | End date (calculated with lead time or by incremental planning) | APS plans the operations, and if they extend past the job End date, it generates an exception message. You can see planned operation dates in the Analyzer |
Scheduled (Firm or Released) | Fixed | Job operation's Start date or the Job Start date if the operation Start date is blank | End date (calculated with lead time or by incremental planning) | At this point, the Scheduler takes full control of the job. |
Affect on Jobs and Production Schedules with No Routing and Alternates in the Bill of Material
For Firm jobs with no routing/BOM and Planned production schedule releases with no routing/BOM (whose PS item has no routing/BOM), this parameter affects whether the system considers any alternates present in the BOM (Preserve Pre-Released Production Dates=Not selected) or only uses the primary materials (Preserve Pre-Released Production Dates=Selected).
Default: Do Not Select