MB-330 — frequently asked questions

Cost represents acquisition price, whereas the ABC model focuses on value generation through Revenue, Value, and Margin.

Margin is the specific percentage or amount used by the system for classification, while Profit is a broader financial concept not directly used as a code.

Four zones would only cover the four damaged-product bins. The production-line (finished goods) test flow and the outbound test flow each need their own zone, which raises the total to six.

No. Apparel is not part of the nutritional supplement or energy drink testing requirements, so it does not create an additional quarantine zone in the design.

Registering consumption is a transactional action taken when fuel is actually used. To 'track' it for scheduling, you must first configure the Counter Type that defines what is being measured.

No. An Asset BOM lists the parts needed for repair. It does not store metadata about the complexity or duration of the service, which is best handled by Attributes.

Stop Item blocks all transactions, preventing any tracking or reporting of the specific damaged cost. It is too broad for this scenario.

No, Dynamics 365 requires proper inventory activities like movement journals to update inventory status and ensure accurate costing and traceability.

Use a maintenance round for recurring, location-based tasks (like vehicle checks). Use a maintenance plan for time or meter-driven preventive tasks on specific assets.

No. Maintenance plans are for scheduled preventive actions. Unexpected breakdowns require reactive maintenance via a new work order.

Separate line items do not automatically update the production BOM without additional configuration, leading to potential manufacturing errors.

No, it is inefficient and violates standard workflows; configurations should be set during sales order creation.

Price Groups are used for standard, recurring pricing structures like customer tiers. Trade Agreements are for temporary promotions, discounts, or allowances.

Trade Allowance is for complex promotions requiring claims or marketing actions. This question asks for basic tier configuration, which uses Price Groups.

Voyage tracks the vessel's journey, while Folio tracks the specific shipment. Exporter details are needed per shipment for compliance, making Folio the correct granularity.

Yes, a single purchase order can result in multiple folios if items are shipped separately or from different locations, each requiring its own exporter data.

If companies have different WMS requirements, a single global storage group may not fit both. Assigning it per company during release allows for necessary differences.

It is generally not recommended. Tracking groups should be defined correctly during the initial release to ensure data consistency and avoid potential system errors.

Item Sampling automates the inspection trigger based on defined percentages, ensuring consistent enforcement across all purchase orders without relying on worker discretion.

Yes, Quality Orders allow you to record detailed inspection results, including specific failure reasons such as damage, which helps in identifying trends for items like chalk and blackboards.

Audit master controls the matching logic and tolerance for freight bills, while Reconciliation reason defines the specific GL accounts used to post variances.

It is typically found under Transportation management > Setup > Reconciliation > Reconciliation reasons.

Deviation limits only define the acceptable variance for cycle count adjustments; they do not evaluate on-hand inventory or create counting work when stock falls below a threshold.

Cycle count plans define the counting frequency and workers, while cycle count thresholds create work automatically when inventory falls below configured minimum levels.

A cycle count plan with a frequency/interval for the relevant locations or items defines the schedule; groupings only assign workers and locations to the resulting work.

Threshold-based creation is controlled by cycle count plan threshold settings (on-hand below a defined level), not by the worker/location grouping record, which has no such trigger logic.

A cycle count plan with a weekly frequency produces scheduled count work, and cycle count thresholds on items or locations trigger counts when on-hand quantity drops below the set level.

It only generates outbound issue work such as picking and packing when a sales order is released; it never creates count work or monitors inventory levels against a minimum.

Detours allow workers to temporarily leave their current mobile transaction flow to perform a lookup or check information, such as finding a PO by item, before returning to the original process.

It dynamically filters query results based on the worker's current session context, specifically limiting data to the warehouse assigned to that user, ensuring they only see relevant inventory.

License plate consolidation only merges on-hand inventory from multiple plates onto one target plate; it does not suspend and restore a mobile app flow, which is what detours provide.

On the mobile device menu item itself, in the detours setup, where you add the menu items a worker is allowed to jump to and then return from.

Intune allows centralized, automated deployment to thousands of devices, which is essential when IT staff is limited and rapid weekend deployment is needed.

The JSON file allows you to import connection settings and configurations for the Warehouse Management app in bulk, ensuring consistent setup across all deployed devices.

Plans create counts on a schedule; they do not monitor on-hand quantities. Thresholds automatically generate counting work when stock falls below a configured level.

Both are part of Warehouse management cycle counting setup, where plans define recurring count work and thresholds define quantity or percentage triggers.