Skip to main content
Solved

Past-Due Master Schedule Records and SORs Automatically Deleted During MS Run

  • May 29, 2026
  • 1 reply
  • 10 views
N
Hero (Employee)
Forum|alt.badge.img+7

During execution of the IFS Master Schedule (MS) process, we observed that past-due MS By Part records and their related Shop Order Requisitions (SORs) are automatically deleted by the system. This creates planning and supply chain risks, as the linkage between the Master Schedule and generated SORs is lost.

All affected parts are configured as buildable, plannable, and MS Level 1. However, the system only allows future dates for MS By Part lines, and when “Run MS – One Part” is executed, past-due records are removed together with the dependent SORs.

Although SORs can be recreated manually, this breaks the traceability between the MS record and the generated requisitions.

Has anyone experienced similar behavior?

Is there any recommended approach, configuration, or workaround to retain past-due Master Schedule records and prevent the related SORs from being deleted or re-planned?

Best answer by Prabashwari

Hi ​@NiroshanKIFS,

Master Scheduling does not consider past-due expected demands for supply creation. The system displays demands that fall within the Demand Time Fence (DTF); however, it does not create requisitions for past-due records. Therefore, deletion of past-due MS records is the current and expected standard behavior when the demand is considered expected demand rather than actual demand.

Master Scheduling is primarily designed to keep the production plan stable and predictable. It evaluates forecasts, customer demand, available supply, and planning time fences to determine when supply should be created either as proposals or as fixed schedules. During each MS run, the system reviews future requirements and automatically generates the necessary supply orders, such as Shop Order Requisitions (SORs) or Purchase Requisitions, to help ensure material availability before production starts.

For past-due scenarios, the recommended approach is to convert the Shop Order Requisition into a Shop Order once the demand becomes actual demand. If the SOR has been released and converted into a Shop Order, it will not be deleted by the MS process. Instead, the system will display messages in the Action Messages tab of the Master Schedule by Part window, such as:

  • “Supply is past due”
  • “Actual Demand is past due”

In addition, if there is a Fixed MPS/SOR within the “slushy zone” (between the Demand Time Fence and Planning Time Fence), it should also be converted into a Shop Order as part of the planning process.

When reviewing Shop Order Requisitions generated from Master Scheduling, planners can use the Shop Order Requisitions page and sort records by Start Date to effectively prioritize and manage past-due supplies.

This behavior was discussed with the Product Development team, and the recommended approach is to follow the process outlined above.

    1 reply

    P
    Sidekick (Employee)
    Forum|alt.badge.img+5
    • Prabashwari
    • Sidekick (Employee)
    • Answer
    • May 29, 2026

    Hi ​@NiroshanKIFS,

    Master Scheduling does not consider past-due expected demands for supply creation. The system displays demands that fall within the Demand Time Fence (DTF); however, it does not create requisitions for past-due records. Therefore, deletion of past-due MS records is the current and expected standard behavior when the demand is considered expected demand rather than actual demand.

    Master Scheduling is primarily designed to keep the production plan stable and predictable. It evaluates forecasts, customer demand, available supply, and planning time fences to determine when supply should be created either as proposals or as fixed schedules. During each MS run, the system reviews future requirements and automatically generates the necessary supply orders, such as Shop Order Requisitions (SORs) or Purchase Requisitions, to help ensure material availability before production starts.

    For past-due scenarios, the recommended approach is to convert the Shop Order Requisition into a Shop Order once the demand becomes actual demand. If the SOR has been released and converted into a Shop Order, it will not be deleted by the MS process. Instead, the system will display messages in the Action Messages tab of the Master Schedule by Part window, such as:

    • “Supply is past due”
    • “Actual Demand is past due”

    In addition, if there is a Fixed MPS/SOR within the “slushy zone” (between the Demand Time Fence and Planning Time Fence), it should also be converted into a Shop Order as part of the planning process.

    When reviewing Shop Order Requisitions generated from Master Scheduling, planners can use the Shop Order Requisitions page and sort records by Start Date to effectively prioritize and manage past-due supplies.

    This behavior was discussed with the Product Development team, and the recommended approach is to follow the process outlined above.

      Terms & ConditionsAccessibility statement