CCNA Implement Warehouse and Transportation Management Questions

A Wave template requires a specific query to identify which orders should be processed. If the query does not include the relevant warehouses or sales order statuses, the system will ignore all orders, even if the automation flags are correctly enabled in the template.

Every work template must define a complete cycle of picking inventory from a location and putting it into another. If a sequence is missing a Put action after a Pick action, the system cannot complete the transaction, leading to validation errors during template configuration or execution.

The location directive evaluates criteria, including product attributes or categories, to determine the optimal put-away location. By using a query to filter by item category, the system will identify the desired zone's locations for the put-away work, meeting the requirement for automated, category-based inventory placement during receipt.

The error 'no location found' usually happens when the query criteria in the location directive (such as zone, location profile, or warehouse) cannot be satisfied by any active, capacity-available locations in the system, forcing the engine to return a null result for the destination.

The 'Replenish' method requires a replenishment template to define how replenishment work is generated, such as which items to replenish and from where. Without assigning a replenishment template, the 'Replenish' method cannot function. Therefore, this configuration is necessary to enable automatic replenishment during wave processing, along with adding the method itself.

The Movement mobile device menu item type allows workers to move inventory between warehouse locations without a source document. It prompts for the from and to locations, item, quantity, and can be configured to require a reason code. This exactly matches the requirement to move items from receiving to staging with audit tracking.

In Dynamics 365 Supply Chain Management, a rate master can have a rate flow that defines the sequence of rate bases to apply. If the rate flow only includes the weight rate base, the distance rate base is ignored even if it is assigned to the rate master. To apply both, the rate flow must include both rate bases, either sequentially or combined. This matches the symptom where only weight is applied.

A transit time engine defines the transit times for different routes or carriers. It calculates the expected delivery date and time based on origin, destination, and carrier. To select the best carrier based on transit time, you must configure a transit time engine. It works with the rate master to provide both cost and time factors for carrier selection.

When 'License plate counting' is enabled on a cycle count menu item, the system treats the LP as the unit of count. Scanning an LP counts the entire LP without prompting for individual items or quantities. This matches the scenario where the LP is immediately marked as counted. Disabling this option would force item-level counting and prompt for item and quantity.

A rate base with a break master of type 'Weight' allows you to define tiered rates based on weight ranges. You configure rate breaks for different weight tiers, and the system applies the appropriate rate per pound or flat rate for that tier. This matches the requirement of decreasing cost per pound as weight increases. The break master defines the break points, and the rate base stores the rates for each tier.

Directive code sorting rules let you sequence outbound work lines by location profile, so pickers are routed in a congestion-aware order rather than the default line order. Assigning these rules to the location directive enforces the physical picking sequence the narrow-aisle constraint demands.

The rate master contains the specific freight rates and the logic for how those rates are applied, such as per-mile or per-weight costs. It is the core component used by the transportation engine to determine the cost of shipping for a given route.

A mobile device menu item defines the workflow a worker follows on the mobile device, including the order of steps such as scanning an item, confirming quantity, and scanning a license plate. By configuring the menu item with the appropriate work creation process and step sequence, the company can enforce the required scanning order. This is the correct component to control the mobile user experience.

The CustomRateEngine allows you to plug in a custom .NET assembly that implements the rating logic. You can write code to call the external REST API, parse the JSON response, and return the cost. This is the designed extensibility point for integrating third-party rating engines. It meets the requirement to use the external API and store the cost.

Mobile device steps define the exact sequence of scans and data entry for a menu item. By adding steps that prompt for item number and then purchase order line, you enforce scanning both. This ensures the worker cannot proceed without scanning, reducing errors and speeding up receiving. It matches the requirement to enforce scan of item and PO line.

A cross-docking template is required to define the criteria under which inbound items are redirected to an outbound staging area. It links the inbound supply to the outbound demand, automatically triggering the necessary work to bypass normal put-away processes and move goods directly to the shipping bay.

Location profiles establish fundamental rules for groups of locations, including allowing mixed items, mixed inventory statuses, and multiple license plates. Enabling the allow multiple license plates setting on the location profile permits stacking pallets in designated bulk storage racks.

The 'Create work' wave step is essential for generating picking work. Without this step, the wave will not create work for the released sales order lines. This step instructs the system to create work based on the location directives and work template. It is a mandatory component for automatic work creation in a wave template.

Scanning a single license plate representing a container of multiple items is significantly faster than scanning each individual item. This allows warehouse workers to move entire pallets or bins with one action, leading to massive gains in productivity and reduced potential for scanning errors.

A cluster profile manages the structure of the cluster, including the number of positions and the sorting logic. By configuring this, the system allows the worker to pick multiple items for different orders in one go, drastically increasing picking efficiency for smaller, high-velocity order profiles.

A rate engine script in transportation management allows you to define custom logic using X++ code to calculate rates. You can use it to evaluate conditions, such as total weight exceeding 1000 kg, and apply a discount percentage. This is the appropriate component for complex, conditional rate adjustments that cannot be achieved with standard rate bases or flows. It provides the flexibility needed for this scenario.

Setting 'AllowSplit' to false restricts the system to picking from a single location. If the requested quantity exceeds what is available in one specific location, or if the stock is fragmented, the system cannot fulfill the demand, resulting in an error or blocked work creation for the warehouse user.

Work assignment is a feature that automatically assigns work to users based on criteria such as workload, skills, or priority. You configure work assignment rules that define how work is distributed. When work is created, the system evaluates the rules and assigns the work to the appropriate user. This meets the requirement of automatic assignment based on workload without manual intervention.

The load building workbench uses load templates to automatically group shipments into loads based on criteria such as carrier service and route. Configuring a load template with those grouping criteria lets the transportation manager generate multiple carrier-specific loads in one planning run, each rated and tendered independently. This matches the requirement to ship partial loads with different carriers without manually selecting shipments.

License plate movement is a mobile device menu item specifically designed to move a license plate from one location to another. The worker scans the license plate and the destination location, and the system moves the entire pallet without requiring item-level scanning. This is ideal for moving received pallets to bulk storage efficiently, as it treats the license plate as a single unit.

The Rate and route process uses the transportation engine to calculate shipping rates based on the carrier services and applicable rate masters. It is the mandatory step to determine the financial cost of shipping and to select the best possible route for the delivery.

An accessorial charge of type 'Fuel surcharge' can be configured to calculate as a percentage of the base freight charge. By assigning it to the rate route, the system automatically applies it during rating. The percentage is defined in the accessorial charge setup, and the base for the percentage is typically the freight charge. This meets the requirement of automatically adding the surcharge when the shipment is rated.

A cluster profile is the configuration entity that controls the cluster behavior, such as how many positions are available in the cluster and whether the cluster is system-generated or user-directed. Without this profile, the mobile device cannot execute cluster picking workflows.

The Process work method is necessary to automatically process the created work and generate picking lists. Without it, work would remain in an open status and would not be ready for picking. This method ensures that the work is released for execution on the mobile device.

License plate receiving is the correct method because it enables workers to receive items against a purchase order and associate them with a license plate. It supports full or partial receiving and prompts for the purchase order, item, and license plate in sequence, exactly as the scenario requires.

The Distance rate base type is used to calculate charges based on the distance traveled, such as miles or kilometers. In this scenario, the $0.50 per mile component is a mileage-based charge, so you must use a Distance rate base to capture that. The base rate of $100 can be handled by a separate flat rate base.

Location sorting allows you to define a specific sequence (e.g., Aisle, Rack, Shelf, Bin) for a location profile. When workers pick, the system uses these values to order the pick lines, ensuring the worker follows a logical, optimized physical path through the warehouse.

Location directives serve as the logic engine that tells the system where to move inventory. Whether it is a raw material put-away or a sales order pick, the location directive queries the warehouse layout to provide a specific, valid location for the task.

Directive codes act as a bridge between the work template and location directives. By tagging the put-away step with a code and creating a corresponding location directive for that code, you force the system to select the specific secure location for those items.