Inventory Availability Constraints for Multi-Level BOMs with MxAPS

Skip to main content

Inventory Availability Constraints for Multi-Level BOMs with MxAPS

You are here:

Inventory Availability Constraints for Multi-Level BOMs

Overview

To prevent finishing lines from scheduling work prior to sub-assemblies being built, items must possess Availability Constraints. This locks components chronologically all the way down the operational tracking tree.

Step-by-Step Configuration

  1. Open the target Item Card in Business Central and locate the MxAPS Constraint Fields block near the footer.

  2. Set Constraint Type to Constraint.

    (Avoid setting this to “Track”, which is purely diagnostic and fails to sequence the real schedule engine).

  3. Define the Fence Type according to your procurement path:

    • For Semi-Finished/Sub-Production Items: Select Global. This explicitly prevents auto-replenishment calculations within active scheduler margins, forcing the engine to wait entirely on upstream parent production order output metrics.

    • For Purchased/Raw Goods Vendor Items: Select Item. This dictates constraints using the standard replenishment card Lead Time field calculation when immediate stock counts are insufficient.

Fence Type Option Core Usage Profile Core Scheduling Calculation Mechanic
Global Multi-level Sub-assemblies Matches scheduling margins against absolute global execution constraints.
Item Purchased Raw Vendor Supplies Uses vendor lead time bounds to predict raw material arrival dates.
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Need help?
Tags:

Leave A Comment

Table of Contents
Go to Top