Capability Check

The capability check is an order delivery estimate based upon an organization's constraints. It is an advanced order promising engine which primarily verifies whether a requested delivery date for a customer order or sales quotation line can be fulfilled or not. If the requested delivery date cannot be fulfilled, a new possible delivery date is calculated. The capability check considers available stock and open supplies, and optionally the available capacity after deducting already planned workload on finite work centers and labor classes. It handles both single and multi-level product structures as well as single and multi-site setups.

The capability check is not just a check; optionally it enables saving interim orders to hold material as well as capacity. This way, the chances of fulfilling the delivery date as planned increases significantly.

The capability check is primarily designed for make-to-order and configure-to-order operations.

Settings Affecting the Capability Check

The following settings impact how capability check runs when it is started automatically:

The following settings impact how capability check runs and are set when it is started manually using the Capability Check dialog:

The following settings also have an impact of how the capability check runs, both when it is started automatically and manually:

Note: It is only recommended to enable Run MRP and Run CRP if it is necessary to create allocations and book capacity for parts in the structure which are planned to stock immediately after the capability check is done to prevent another capability check to use same material and capacity. It can have a negative impact on the performance of the application and also interfere with the material and production planning processes since requisitions and load for requisitions can change at unpredictable times. If appropriate schedule MRP to run, perhaps integrated with CRP, at specific times instead of after each capability check.

Start Capability Check

To run the capability check, below prerequisites must be fulfilled:

The capability check can be started either automatically or manually. If the inventory part linked to the sales part has Capability Check set to either Reserve and Allocate, Allocate only or Neither Reserve nor Allocate, the capability check is automatically started with the selected reservation and allocation option when a new customer order line with supply code DOP Order, Shop Order, Int Purch Trans or Int Purch Dir is saved, or an existing line is edited. The other capability check related settings on Inventory Part/Manufacturing also impact how the capability check runs when it is started automatically. Capability check cannot be run automatically for a sales quotation line.

If Capability Check is set to No Automatic Capability Check, you must manually start the capability check by selecting the relevant customer or sales quotation line, click Capability Check and then Run Capability Check. Before clicking OK in the Capability Check dialog, define the appropriate settings in the Options section:

Capability Check Algorithm

The capability check consists of three different phases, an initial phase, a planning phase and a final phase. It uses an interim order structure that is built in the initial phase. The planning phase includes four planning steps, but all steps are not executed in each capability check. The first planning step is always executed. It contains a netting procedure and evaluates if the requested delivery date on the source customer order/sales quotation line can be fulfilled or not. If the requested delivery date can be fulfilled, all other planning steps are skipped. Else the second planning step is executed followed by either the third planning step or the fourth planning step, depending on the Optimize New Delivery Date setting. The purpose of the second planning step is to calculate a completion date that is possible to fulfill. If Optimize New Delivery Date is disabled, the third planning step is used to reschedule the interim order structure based on the possible completion date that was calculated. If Optimize New Delivery Date is enabled, the fourth planning step is used to calculate an optimized completion date, which might be earlier than the possible completion date, and to schedule the interim order structure based on this optimized completion date. When the planning phase of the capability check is done, the outcome is saved in the final phase. If the requested delivery date was not possible to fulfill, a new delivery date will be set on the source line based on the possible completion date (if Optimize New Delivery Date is disabled) or the optimized completion date (if Optimize New Delivery Date is disabled).

In the picture below, the different phases of the capability check algorithm are visualized.

The sections below describe how the interim order structure that is used in the capability check is built, what happens in each of the four planning steps and how the outcome of the capability check is saved. In addition, detailed information about how the Create Pegged Orders at Release field is set for an interim order, how an interim order is netted, how an interim order is reserved and allocated, how an interim order is planned and how interim order operations are scheduled is given.

Building an Interim Order Structure

The capability check starts with building an interim order structure for the source customer order or sales quotation line if no interim order structure that is possible to use already exists. The Required Date on the topmost interim order header will be set to the planned due date needed to fulfill the requested delivery date on the source line. For a non-configured part, the manufacturing structures and routings are used. For a configured part, the configuration attributes specified for the source line along with the part’s configured structures and routings are used. The revision used, is the valid revision for the supply date on the current interim order.

The interim order structure is created with all parts at all levels and sites. However, an exception occurs in case a component part to an interim order in the structure has Promise Planned set to Not Promised. Then the interim order for that component part is created without any components and operations. If there are component parts supplied by another site, a separate interim order structure is built at the primary supplier site. An interim order structure at a supply site becomes a child to an interim order structure at a demand site.

Exception: When the supply code of the source line is Int Purch Dir, the Required Date on the topmost interim order header will be set differently. The topmost interim order header will be created at the demand site and contain one interim order. The Required Date for this interim order header will be set equal to the planned delivery date on the source line instead of the planned due date. In this way, the Required Date of the interim order header at the supply site will become equal to the supply site due date on the source line.

If you have created an interim order structure for the source line before running the capability check (typically for a configured part) and no component parts are supplied by another site, the capability check will use this interim order structure, including changes, instead of creating a new. If you are running capability check repeatedly times for the same line, an already existing interim order structure will always be deleted and replaced with a new interim order structure. This means that if you modify an existing interim order structure after running the capability check, and then re-run the capability check, all your changes will be lost.

Before continuing to the planning phase of the capability check, the Create Pegged Orders at Release field is set for each interim order in the structure depending on whether pegged supply orders will be created for the interim order part when the connected customer order is released. For more information see Setting Field Create Pegged Orders at Release for Interim Order.

Planning Step 1: Backwards Planning

The first planning step in the capability check evaluates if the requested delivery date can be fulfilled or not. Starting with the topmost interim order, the interim orders are netted and planned backwards down in the interim order structure from the planned due date needed to fulfill the requested delivery date. This date is the same as the Required Date on the topmost interim order header.

For each interim order in the interim order structure, starting with the topmost interim order, and then going downwards level by level, starting with the interim order with the lowest ID on each level, the following steps are done:

  1. The Scheduled Supply Date is set. For the topmost interim order, it is set to the Required Date on the topmost interim order header. For the child interim orders, it is set to the parent’s Scheduled Start Date.
  2. Netting is done against available stock and open supplies available up to and including the Scheduled Supply Date. Net Qty is set to the quantity that remains to be supplied. If a quantity is netted, adjusted quantities are propagated downwards to child interim orders. For more information see Netting an Interim Order. Depending on the selected Reservation and Allocation Options, reservations and allocations are made. For more information see Reserving and Allocating an Interim Order.
  3. The Scheduled Start Date is calculated through backwards planning from the Scheduled Supply Date. For more information see Planning an Interim Order.
  4. The Start Date is set to the same date as the Scheduled Start Date and the Supply Date is set to the same date as the Scheduled Supply Date.

If all leaf nodes in the interim order structure have a Start Date that is not earlier than the first workday after today’s date according to the site manufacturing calendar, it means that the requested delivery date can be fulfilled, and the planning part of the capability check is done. Else, the capability check continues with the second planning step followed by either planning step three or four.

Planning Step 2: Forwards Planning

The second planning step in the capability check is done when the requested delivery date cannot be fulfilled and calculates a completion date that is possible to fulfill. Starting with the lowest level interim orders with Net Quantity > 0, the interim orders are planned forwards up in the interim order structure from the first workday after today’s date according to the site manufacturing calendar.

For each interim order in the interim order structure with Net Quantity > 0, starting with the lowest level interim orders and then going upwards level by level, starting with the earliest interim order on each level, the following steps are done:

  1. The Scheduled Start Date is set. For the lowest level interim orders with Net Quantity > 0, it is set to the first workday after today’s date. For the parent interim orders, it is set to the child’s latest Scheduled Supply Date.
  2. The Scheduled Supply Date is calculated through forwards planning from the Scheduled Start Date. For more information see Planning an Interim Order.

The result after this step is a possible completion date, that is the same date as the Scheduled Supply Date on the topmost interim order. This date will be later than the Required Date on the topmost interim order header.

Planning Step 3: Backwards Planning

The third planning step is done after the second planning step when Optimize New Delivery Date is disabled. It schedules the interim order structure based on the possible completion date that was calculated in the second planning step.

For each interim order in the interim order structure, starting with the topmost interim order, and then going downwards level by level, starting with the interim order with the lowest ID on each level, the following steps are done:

  1. The Scheduled Supply Date is set. For the topmost interim order, it is set to the possible completion date. For the child interim orders, it is set to the parent’s start date.
  2. The Scheduled Start Date is calculated through backwards planning from the Scheduled Supply Date. For more information see Planning an Interim Order.

Planning Step 4: Iterated Backwards Planning

The fourth planning step is done after the second planning step when Optimize New Delivery Date is disabled. It calculates an optimized completion date and schedules the interim order structure based on this optimized completion date. The optimized completion date will be later than the Required Date on the topmost interim order header and earlier than or equal to the possible completion date that was calculated in the second planning step. In order to find which date within this date interval that is the optimized completion date a backwards planning and netting procedure of the interim order structure, similar to the first planning step, is iterated from different dates within the interval until the optimized completion date has been found. By doing so, open supplies which become available for interim orders when they are planned with later Scheduled Supply Dates than used in the first planning step are considered. Larger quantities of the interim orders can be netted and that might decrease the time it takes to manufacture/purchase the interim orders.

The optimized completion date will be the earliest iterated date for which the backwards planning and netting procedure results in Scheduled Start Dates equal to or later than the first workday after today’s date according to the site manufacturing calendar for all interim orders in the structure. If the last iterated date is not equal to the optimized completion date, an additional iteration is done from the optimized completion date to redo the netting and reschedule the interim order structure based on the optimized completion date. Depending on the selected Reservation and Allocation Options, reservations and allocations are made before the fourth planning step ends. For more information see Reserving and Allocating an Interim Order.

The next iteration date is set using the split half method for the date interval. This means the next iteration date is set to the date between the start date and the end date of the interval. Before the first iteration, the start date of the interval will be equal to the Required Date on the topmost interim order header and the end date of the interval will be equal to the possible completion date. If no date between the start date and the end date of the interval exists, the optimized completion date has been found. It will be equal to the current end date of the interval.

In each iteration the following procedure is executed. For each interim order in the interim order structure, starting with the topmost interim order, and then going downwards level by level, starting with the interim order with the lowest ID on each level, the following steps are done:

  1. The Scheduled Supply Date is set. For the topmost interim order, it is set to the current iteration date. For the child interim orders, it is set to the parent’s Scheduled Start Date.
  2. Netting is done against available stock and open supplies available up to and including the Scheduled Supply Date. Net Qty is set to the quantity that remains to be supplied. If a quantity is netted, adjusted quantities are propagated downwards to child interim orders. For more information see Netting an Interim Order.
  3. The Scheduled Start Date is calculated through backwards planning from the Scheduled Supply Date. For more information see Planning an Interim Order.

Before finishing the current iteration the interval is split in half. If all leaf nodes in the interim order structure have a Scheduled Start Date that is not earlier than the first workday after today’s date according to the site manufacturing calendar, the current iteration date is possible to fulfill, and an even earlier date might be possible to fulfill. Then the end date of the interval is updated to the current iteration date. Else, the current iteration date is not possible to fulfill, but a later date will be. Then the start date of the interval is updated to the current iteration date.

Saving Outcome

When the planning phase is finished, the outcome from the capability check is saved as a capability check result. Information created during the capability check about the interim orders in the interim order structure is saved to the database. However, some or all of the actual interim orders that were created might be deleted or partly discarded. If the Reservation and Allocation Options specified when running the capability check is:

The picture below displays an example of which interim orders in the structure that are saved in case the supply code of the source line is DOP Order and the Reservation and Allocation Options is Reserve and Allocate or Allocate only. All interim orders with parts which are planned to order and have default supply type set do DOP have Create Pegged Orders at Release set to Yes. These interim orders and their component interim orders are saved. The saved interim orders which are planned to stock and have another default supply type than DOP have Create Pegged Orders at Release set to No. For these interim orders only the interim order demands are kept.

The saved interim orders hold reservations and allocations of available material and, in case Schedule and Create Load for Interim Order Operations is enabled for the site and load not discarded, also available capacity through the generated workload. That prevents future capability checks to net from the same stock and open supplies and schedule operations using the same capacity as already used by these interim orders. Since no interim order allocations of available material or available capacity are hold for the deleted interim orders, a risk is that future capability checks net from the same stock and open supplies and schedule operations using the same capacity as already used by these deleted interim orders. However, running MRP and CRP after the current capability check and disabling Include Only Firm Demands in future capability checks will prevent that from happening.

If capability check was started with Run MRP enabled, a background job for running a selective MRP (or project MRP) for the demanded part is triggered to create allocations for the parts in the structure which are planned to stock. In case there are component parts supplied by another site, selective MRP will also run for these component parts at the supplying site. In case the demanded part is master scheduled, master scheduling will run for the specific part before the selective MRP (or project MRP) is started. This is done to make sure the demand from the source line consumes the master schedule forecast demand before MRP runs and hence, avoid calculating with double demands.

Note: A selective project MRP is run for the demanded part instead of a selective MRP if the source line is connected to a project activity. In case the structure contains component parts at the primary demand site which are not project planned, the selective project MRP will be followed by selective MRP for these parts. In case there are component parts supplied by another site, selective MRP will run for these component parts at the supplying site.

If also Run CRP was enabled when starting the capability check, CRP will run integrated with the selective MRP (or project MRP) and book machine and/or labor capacity for the parts in the structure which are planned to stock in the same background job.

The source customer order or sales quotation line is updated. If the requested delivery date is not possible to fulfill, the Scheduled Supply Date on the topmost interim order in the interim order structure is used to set the new Planned Due Date on the source line. If Optimize New Delivery Date is disabled, this Scheduled Supply Date will be the same as the possible completion date that was calculated in the second planning step. Else, the date will be equal to the optimized completion date that was calculated in the fourth planning step. Other dates on the line, e.g., the Planned Delivery Date/Time, are calculated forwards based on this new Planned Due Date. The earliest Scheduled Start Date in the interim structure will be set as the Latest Release Date on the source line. This is the date when manufacturing must start, or the first part must be purchased.

Exception: When the supply code of the source line is Int Purch Dir, the Scheduled Supply Date on the topmost interim order minus the External Transport Lead Time defined between the primary supply site and the customer is used to set the new Planned Due Date on the source line. In this way, the supply site due date on the source line will become equal to the Scheduled Supply Date of the topmost interim order at the supply site (belonging to the second interim order header).

The capability check will finally give you a message if the delivery date is changed. Otherwise, you are simply informed that the delivery date can be fulfilled as planned.

Setting Field Create Pegged Orders at Release for Interim Order

Before finishing the build interim order structure step, the Create Pegged Orders at Release field is set for each interim order in the structure. The field is set to Yes for the interim orders for parts for which pegged supply orders will be created when the customer order is released. For the other interim orders for parts for which pegged supply orders will not be created, the field is set to No. How to set the field is depending on different settings. Also whether the interim order belongs to the topmost header or to another header at a lower level in the interim order structure impacts.

Netting an Interim Order

During the first planning step in the capability check, netting is done for each interim order in the interim order structure that are supposed to be netted and have Promise Planned set to Promised. Netting is also done during the fourth planning step of the capability check. Which interim orders to net are decided based on different settings. Also whether the interim orders belong to the topmost header or to another header at a lower level in the interim order structure impacts.

Note: Interim orders with Promise Planned set to Not Promised are never netted.

Netting of an interim order is done against available stock and open supplies available up to and including the Supply Date of the interim order, without driving the projected quantity negative within the cumulative lead time for manufactured parts and within the expected lead time for purchased parts. The netting occurs after the Scheduled Supply Date (used to set the Supply Date) of the interim order has been calculated but before calculating the Scheduled Start Date (used to set the Start Date).The netting procedure starts by analyzing available quantity in three different calculations:

The netting procedure starts by analyzing available quantity in three different calculations:

Note: In case the source line is connected to a project activity, an interim order belonging to the topmost interim order header in the structure can be project planned. The topmost interim order is always project planned and for the other interim orders it depends on the supply code of the source line and the Create Pegged Orders at Release and the Std Planned Item settings. An interim order cannot be project planned unless the parent interim order also is project planned. When the supply code is DOP Order, an interim order with a project planned parent interim order is also project planned if Create Pegged Orders at Release is set to Yes and/or if Std Planned Item is set to No. When the supply code is not DOP Order, an interim order with a project planned parent interim order is also project planned if Std Planned Item is set to No. A project planned interim order will be supplied from stock and supplies connected to the same project activity as the source line is connected to. During the three calculations above, only stock, supplies and demands which are connected to that same project activity are considered. If the project has Material Allocation set to Within Project, also stock connected to other activities for the same project are considered in the first calculation. For an interim order that is not project planned, only stock, supplies and demands which are not connected to any project activity are considered during the three calculations. Interim orders belonging to another interim order header than the topmost are never project planned.

However, driving the projected quantity negative within the cumulative lead time for manufactured parts and within the expected lead time for purchased parts is not allowed. Therefore, the lowest ATP, which is calculated in calculation 3 is of high importance. If the lowest ATP is equal to zero or less than zero, it won’t be possible to net any quantity at all. Else if the lowest ATP is less than the sum of available stock and open supplies, it is not possible to net a bigger quantity than the lowest ATP. Else it will be possible to net the sum of available stock and open supplies. Consequently, if the netted quantity is bigger than the lowest ATP, the netted quantity is adjusted according to the following formulas:

If Lowest ATP ≤ 0, use formula:

Else if Lowest ATP < Netted Qty use formula:

The Net Qty, which is the quantity that remains to be supplied for the interim order after netting from existing stock and open supplies, is finally set according to the following formula:

Example:

Assume that an interim order with Supply Qty equal to 10 should be netted and that the expected/cumulative lead time for that interim order part is 6 days. In the picture below, calculation 1 gives the result that the available stock is 4. In calculation 2, the summarized supply up until the Supply Date minus the summarized demands up until the Supply Date results in available open supplies up until the Supply Date equal to 8. This means that the incoming balance is 12 on the Supply Date. That is used in calculation 3, that results in -10, when the lowest ATP beyond the Supply Date but within the cumulative/expected lead time is found after calculating the ATP for each day within the period.

When using the first formula for calculating the net quantity without considering driving the projected quanitity negative the result is 10. See formula:

However, the netted quantity must be adjusted to avoid driving the projected quantity negative. Since the lowest ATP is less than zero, the netted quantity is adjusted to zero. See formula:

This means that the Net Qty will be equal to 10. See formula:

Reserving and Allocating an Interim Order

After the netting procedure, during the first planning step in the capability check, reservations and allocations are done for each interim order in the interim order structure with Promise Planned set to Promised. Reservations and allocations are also done before the fourth planning step ends.

Reservations and allocations are done depending on the Reservation and Allocation Options principle that is used.

Note: In case the source line is connected to a project activity, an interim order belonging to the topmost interim order header in the structure can be project planned. The topmost interim order is always project planned and for the other interim orders it depends on the supply code of the source line and the Create Pegged Orders at Release setting and the Std Planned Item setting defined in the BOM. An interim order cannot be project planned unless the parent interim order also is project planned. When the supply code is DOP Order, an interim order with a project planned parent interim order is also project planned if Create Pegged Orders at Release is set to Yes and/or if Std Planned Item is set to No. When the supply code is not DOP Order, an interim order with a project planned parent interim order is also project planned if Std Planned Item is set to No. A project planned interim order will be supplied from stock and supplies connected to the same project activity as the source line is connected to. For a project planned interim order, reservations will only be done from stock connected to the same project activity as the source line is connected to. In addition, the interim order demand and supply which are created to allocate available stock and open supplies will be connected to that same project activity. If the project has Material Allocation set to Within Project, also stock connected to other activities for the same project can be reserved. For an interim order that is not project planned, reservations will only be done from stock which are not connected to any project activity and the created interim order demand and supply will not be connected to any project activity. Interim orders belonging to another interim order header than the topmost are never project planned.

Planning an Interim Order

In the planning phase the interim orders in the interim order structure are planned. The first, third and fourth planning steps are done using backwards planning while the second planning step uses forwards planning. When backwards planning an interim order, the Scheduled Supply Date is known, and the Scheduled Start Date is calculated. When forwards planning an interim order, the Scheduled Start Date is known, and the Scheduled Supply Date is calculated. The Scheduled Start Date in backwards planning and the Scheduled Supply Date in forwards planning are calculated in different ways depending on whether the interim order part is purchased externally, purchased internally and delivered from supply site to demand site, purchased internally and delivered from supply site directly to customer or manufactured. When the part is manufactured also the site setting Schedule and Create Load for Interim Order Operations and the work center and labor class settings Finite Capacity are of importance.

If the inventory part on the interim order is:

Scheduling Interim Order Operations

During all four planning steps in the capability check, interim order operations are scheduled when Schedule and Create Load for Interim Order Operations is enabled for the site. At the same time as an operation is scheduled, work center and/or labor load is created. The scheduling works similar to how a shop order operation is scheduled, but can also consider the remaining work center and/or labor capacity for each day in order to schedule finite. Whether finite or infinite scheduling is performed is depending on the Finite Capacity settings for the work center, setup labor class and runtime labor class of the operation. When Finite Capacity is enabled the operation will be scheduled according to the remaining capacity for each day after subtracting already existing load. No new overload will be created on individual days and the total load during the scheduled period of the interim order will not be higher than the total available capacity during the same period.

Example 1: Backwards scheduling at finite work center with infinite labor class

In this example an interim order operation is backwards scheduled at a work center with Finite Capacity enabled. The labor class of the operation, which is the same for both setup and runtime, has Finite Capacity disabled. The operation has 2 hours machine setup time, 4 hours labor setup time, 20 hours machine run time and 40 hours labor run time. The available capacity of the work center is 8 hours each day and the available capacity of the labor class is 16 hours each day.

The charts below visualize how work center load is created and scheduled during backwards scheduling from the Scheduled Finish Date at 5:00 PM day 7. Since Finite Capacity only is enabled for the work center, the scheduling is performed according to the remaining work center capacity for each day after subtracting already existing load. Remaining labor class capacity is not considered. The fictive load in the work center load graph illustrates how the already existing overload at day 5 is fictively distributed to an earlier working day, to avoid that the total load gets bigger than the total available capacity during the scheduled period of the interim order operation. If forwards scheduling would have been performed, the existing overload at day 5 would have been fictively distributed to a later working day instead of an earlier. The result of the backwards scheduling is that the Scheduled Start Date of the operation is set to 4:00 PM at day 2. The preceding interim order operation will get a Scheduled Finish Date set to 4:00 PM at day 2, or earlier.

During the backwards scheduling load is also created and scheduled for the labor class. Since Finite Capacity is disabled for the labor class, the labor load is scheduled according to when the machine load was scheduled, without consideration of the remaining labor capacity for each day. How the labor load is created and scheduled is visualized in the charts below.

Example 2: Backwards scheduling at finite work center with finite labor class

In this example an interim order operation is backwards scheduled at a work center with Finite Capacity, similar to previous example, but this time also the labor class of the operation, that is the same for both setup and runtime, has Finite Capacity enabled. The operation has 2 hours machine setup time, 4 hours labor setup time, 20 hours machine run time and 40 hours labor run time. The available capacity of the work center is 8 hours each day and the available capacity of the labor class is 16 hours each day.

The charts below visualize how both work center and labor load are created and scheduled for the operation during backwards scheduling from the Scheduled Finish Date at 5:00 PM day 7. Since Finite Capacity is enabled both for the work center and the labor class, it is not enough to only schedule according to the remaining work center capacity for each day after subtracting already existing load. For each day when there is remaining work center capacity, also the remaining labor class capacity for the day after subtracting already existing load must be considered. By comparing the work center load graph with the labor class load graph, you can see whether the remaining work center or labor class was the limiting factor for each day. E.g., at day 7 the remaining work center capacity was 4, but only 2 machine hours could be scheduled at that day because of the limiting remaining labor class capacity that was only 4 hours. The result of the backwards scheduling is that the Scheduled Start Date of the operation is set to 3:00 PM at day 1, one day earlier than in previous example. The preceding interim order operation will get a Scheduled Finish Date set to 3:00 PM at day 1, or earlier.

Schedule using Advanced Planning Board (APB)

When the capability check calculation has been completed, and a Reservation and Allocation Options was used that saved the interim structure, the interim order operations can be scheduled using IFS/Advanced Planning Board (APB). This allows more advanced scheduling considering finite machine, labor and tool capacity as well as material constraints. When the APB schedule is saved back, the Scheduled Start Date and Scheduled Supply Date of the affected interim orders are updated as well as the Planned Due Date of the source line.

View the Result of a Capability Check

You can analyze the result of a capability check on the Capability Check Result page where the interim order information that was saved during the saving outcome phase of the capability check algorithm is displayed. For more information see activity Analyze Capability Check Result.

When the capability check has been performed with Reservation and Allocation Options set to Reserve and Allocate or Allocate only, and the interim orders have been scheduled (using either APB, or having Schedule and Create Load for Interim Order Operations enabled for the site), the estimated workload is saved. This load appears as Promised or Promised Interim Order and can be analyzed using the Visual Capacity Requirements Planning page.

Note that the load from an interim order operation may be distributed into several segments over multiple days according to the remaining capacity for each day when finite loading has been enabled for the work center or labor class.

Edit a Capability Checked Line

If you change any of the fields that have effects on the dates before the customer order is released or sales quotation line is either lost or converted to customer order, the system will remove the value in the Latest Release Date field, clear the Capability Check indicator and delete the interim structure. Also reservations, allocations and load that potentially were created during the capability check are removed. If the automatic capability check is activated, the system will start a new capability check automatically. The same happens if you change the supply code or the sales quantity.

Create a Customer Order from a Capability Checked Sales Quotation Line

If you create a customer order from a capability checked sales quotation line, the result of the capability check is transferred to the new customer order line. If the customer order is created in the Released status the system behaves as described in Release a Capability Checked Customer Order.

Release a Capability Checked Customer Order

You cannot release a customer order when the Latest Release Date is in the past. The order will remain in status Planned. Instead, you should do a new capability check.

When a capability checked customer order is released and the capability check was performed with Reservation and Allocation Options set to Neither Reserve nor Allocate, the system behaves similar as if no capability check was performed.

If the capability check was performed with Reservation and Allocation Options set to Reserve and Allocate or Allocate only, the interim order structure is deleted when the customer order is released. The supply code will impact the behavior as per below:

Limitations