Microsoft Dynamics 365 Supply Chain Management Free Sample Questions

The most direct and standard way to achieve this is by setting a default inventory status on the released product or warehouse item settings. By creating an inventory status such as 'Awaiting QC' and disabling 'Inventory blocking' for it, you ensure that any new receipts for this item are automatically assigned this status. This makes the inventory non-nettable and unavailable for issue until manually updated by an authorized user after quality control processes are complete. While a quality association can trigger a quality order, it doesn't inherently change the inventory status upon receipt by default. Using item model groups affects costing and other policies but not the initial receipt status. A location directive guides movement but does not control inventory status.

The key to this requirement is a system-wide parameter that governs how work orders are created from functional locations. In the Asset management parameters, the 'Create work order from functional location' setting controls this behavior. Setting it to 'One work order per asset' instructs Dynamics 365 to automatically create a separate work order for every asset installed at the selected functional location when a work order is initiated from that location. This creates the desired parent-child structure automatically, linking all asset-specific work orders to the functional location. Other options require significant manual intervention or do not create the comprehensive structure requested.

To apportion landed costs by volume, two key configurations are required. First, a cost type code (e.g., 'Freight') must be configured with an apportionment method of 'Volume'. This tells the system how to distribute the cost. Second, the system needs the volumetric data to perform the calculation. This data is pulled from the 'Volume' field on the 'Manage inventory' fast tab of the released product master. Without both of these pieces of information, the system cannot correctly apportion the freight cost based on volume.

Detours are designed to allow workers to temporarily interrupt a primary task to perform a secondary one. By creating a detour for attaching a document (which is a standard feature) and configuring it as a global detour, it becomes available from any step in any workflow on the mobile device. This meets the requirement for the action to be optional and accessible throughout the receiving process. An indirect menu item is for activities not related to work (like inquiries), a custom work exception is for handling problems, and page scripts are for customizing UI elements, not for adding functionality like this.

This statement is false. The 'Firming' time fence automatically firms any newly created planned orders that fall within the specified number of days from the planning run date. It does not prevent Planning Optimization from suggesting changes (e.g., action messages) to already firmed orders, whether they were firmed manually or automatically. The purpose is to automate the firming of near-term supply, not to create a frozen zone for existing firmed orders.

The correct process for a standard cost rollup is sequential and structured. First, a new costing version is created to contain the pending cost changes. Then, the cost of the component (the raw material) must be updated and activated first. Once the raw material has a new active standard cost, the BOM calculation for the finished good can be run. This calculation will pull the new active cost of the component to accurately calculate the rolled-up cost of the finished product. Finally, the new calculated cost for the finished good must be activated to be used in future transactions.

The standard functionality to manage in-transit inventory for transfer orders is by using a transit warehouse. A virtual warehouse should be created for this purpose. This transit warehouse is then assigned in the 'Transit warehouse' field on the main warehouse's setup page (specifically, the source warehouse in the shipping relationship). When a transfer order is shipped, the system automatically moves the inventory from the source warehouse to this designated transit warehouse, where it remains until it is received at the destination. This provides both physical and financial visibility of in-transit stock.

The 'Purchase order vendor confirmation' workflow is specifically designed to manage the approval process for POs confirmed by vendors through the collaboration portal. This workflow can be configured with conditional steps. You can add a condition that checks if the 'Confirmed delivery date' on the PO line is more than 5 days after the 'Delivery date'. If this condition is met, the workflow can route the confirmation to a specific user or user group (like the purchasing manager) for approval. This directly addresses the requirement to handle exceptions based on delivery date changes.

This process involves three distinct stages supported by specific menu items. First, 'Sales picking' (or a similar picking process) is used to pick items into the tote. Second, at the packing station, a 'Packing' process menu item is used to scan the tote and move its contents into a new shipping container. Finally, after packing is complete, a 'Container close/reopen' process is needed to finalize the shipping container, which typically triggers label printing and updates the shipment status.

This requirement is met by configuring a cycle count plan. The plan should be filtered using a query to only include items where the ABC code is 'A'. The 'Days between cycle counting' field ensures that once an item is counted, it won't be suggested again for 7 days. The 'Maximum number of cycle counts' field limits the generated work to 3 items per run. Finally, scheduling the 'Cycle count work by plan' periodic job ensures this logic is executed automatically every day to generate the required work.