Extending the Production Order Data Model

The following Scheduling Settings are added to the Production Order data model:

Schedule Start Field: the reference field that will be used for all scheduling operations. This could e.g. be the delivery date retrieved from the ERP system that is used for backward scheduling.
Schedule Type: Backward or Forward scheduling when used on the production order. A combination of backward and forward scheduling when used on the operation level.
Schedule Simulation Order: Flag that allows you to also asses the impact of simulated orders. This can e.g. be used to simulate the impact on capacity of sales orders that are not yet confirmed.
Schedule: flag to start the scheduling. The check on the production order will be removed once the scheduling has been completed.
Schedule from Operation: Number of the operation of this production order that should serve as the basis for operation-based scheduling. This field holds an Id with a lookup to that operation.
Schedule from Production order: Set during the scheduling of production orders in batch 'SchedMtoProdOrdersBatch'. Unset when 'SchedMtoProdOrdersBatch' is finished. This way you can create the required conditions in flows/triggers to make sure these are not triggered while Production Order Scheduling is ongoing.

Extending the Operation Data Model

In some use cases, you will need to extend the operation data model, more specifically in use case when the duration (touch time) for an operation depends on other parameters. As an example, the touch time for a specific product can depend on the specific machine on which it is produced.

For such use cases, the Operation object data model needs to be extended with 2 fields:

Dynamic Duration Object Name: API name of the object that contains the dynamic duration. This way the Dynamic grouping knows where to look for the correct record.
Dynamic Duration Record Id: This is the record where the dynamic duration of the operation can be found.

More information on this use case can be found in the MTO Custom Metadata documentation section.