Study guide

17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Product Master and Released Products

1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups

2 Chapter 2: Bills of Materials (BOM) and Formulas

2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling

3 Chapter 3: Product Prerequisites and Dimension Groups

3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups

4 Chapter 4: Additional Product Details and Warehouse Fit

4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions

5 Chapter 5: Inventory Costing and Pricing

5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding

6 Chapter 6: Inventory Journals and Core Transactions

6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals

7 Chapter 7: Inventory Operations, Blocking, and Closing

7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification

8 Chapter 8: Quality Management and Nonconformance

8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders

9 Chapter 9: Asset Management: Setup and Maintenance

9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption

10 Chapter 10: Procurement and Sourcing Configuration

10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal

11 Chapter 11: Purchase Order Lifecycle and Consignment

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders

12 Chapter 12: Landed Cost and Inbound Logistics

12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances

13 Chapter 13: Sales Management and Order Processing

13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates

14 Chapter 14: Warehouse Setup and Core Infrastructure

14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences

15 Chapter 15: Warehouse Execution Processes

15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

16 Chapter 16: Transportation Management and Logistics

16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation

17 Chapter 17: Warehouse Management Mobile App

17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

18 Chapter 18: Master Planning and Planning Optimization

18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management

17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

Key Takeaways Explain This Topic AI

Mobile device step detours enable material handlers to branch away from an active warehouse work task into an auxiliary menu item (such as an inquiry, movement, or label print) without losing work session state or cancelling the primary task.

Detours are configured on Mobile device steps using Field value pass-through (sending current work context like Item ID or Location to the detour) and Return value mapping (pasting detour results back into the primary work step).

Common step detour scenarios include checking alternate locations when a primary pick face is empty, printing replacement pallet labels mid-pick, and changing inventory status to quarantine damaged items.

GS1 barcode parsing in D365 SCM uses standardized Application Identifiers (AIs)—such as AI (01) GTIN, AI (10) Batch, AI (17) Expiration, and AI (30) Quantity—to capture multiple inventory dimensions in a single physical barcode scan.

Variable-length GS1 fields (such as batch numbers and serial numbers) require the FNC1 Group Separator character ( <GS> / ASCII 29) to delimit data elements when concatenating multiple AIs into a single 1D or 2D barcode string.

Last updated: September 2026

17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

Quick Answer: Mobile device step detours enable contextual branching within the Warehouse Management mobile app, allowing an operator to temporarily navigate away from an active work task (e.g., sales picking) into an auxiliary menu item (e.g., Location inquiry , Item inquiry , or Inventory status change ) without cancelling the work order. Data is shared seamlessly across flows via Field value pass-through (sending active work fields to the detour) and Return value mapping (pasting detour selections back into the work step). Concurrently, modern scanning leverages GS1 barcode parsing , utilizing standardized Application Identifiers (AIs) —such as AI (01) for GTIN, AI (10) for Batch number, and AI (17) for Expiration date—to ingest multiple tracking dimensions and quantities in a single physical scan.

1. Mobile Device Step Detours: Architecture and Concepts

In traditional warehouse management systems, if a material handler encounters an exception while executing work—such as arriving at a pick face only to find it depleted, discovering a torn pallet barcode, or encountering damaged goods—the operator is forced to abort the work order, exit back to the root menu, locate an inquiry or movement menu item, resolve the issue, and then attempt to re-acquire the original work.

Mobile device step detours solve this operational friction by providing contextual branching. While remaining within the active work transaction, the worker can tap a promoted button to "detour" into a secondary menu item. The system preserves the state of the primary work order, passes relevant contextual data into the detour, executes the auxiliary task, and seamlessly returns the worker to the exact step where they branched, optionally returning updated values.

Core Components of a Step Detour

Mobile Device Step : The specific step within a work flow (e.g., ItemPick , ScanLicensePlate , PutLocation ) where the detour button is exposed.

Target Menu Item : The indirect or work menu item that is launched during the detour (e.g., Location inquiry , Item inquiry , Print label , Movement ).

Field Value Pass-Through (Send from Main Work) : Maps field values from the active work step directly into the target detour screen, eliminating redundant scanning.

Return Value Mapping (Paste back to Main Work) : Takes values generated or selected during the detour and writes them back into the active work step (e.g., returning an alternate picking location).

2. Configuring Step Detours Step-by-Step

Configuring step detours involves linking mobile device steps to menu items and defining data pass-through rules.

Navigation : Warehouse management > Setup > Mobile device > Mobile device steps . ┌──────────────────────────────────────────────────────────────────────┐

  • │ Step Detour Configuration Flow │
  • └──────────────────────────────────────────────────────────────────────┘
  • Step 1: Open Mobile Device Steps
  • ┌────────────────────────────────────────────────────────┐
  • │ Step ID: ItemPick (or ScanLocation, PutLocation) │
  • └───────────────────────────┬────────────────────────────┘
  • │
  • Step 2: Add Promoted Detour Options
  • ┌───────────────────────────┬────────────────────────────┐
  • │ Menu Item: Sales Picking │ Detour: Location Inquiry │
  • └───────────────────────────┴────────────────────────────┘
  • │
  • Step 3: Configure Field Value Pass-Through (Send)
  • ┌───────────────────────────┬────────────────────────────┐
  • │ Source Field (Main Work) │ Target Field (Detour) │
  • │ Location (e.g. BULK-01) │ Location │
  • └───────────────────────────┴────────────────────────────┘
  • │
  • Step 4: Configure Return Value Mapping (Paste)
  • ┌───────────────────────────┬────────────────────────────┐
  • │ Source Field (Detour) │ Target Field (Main Work) │
  • │ Selected Location │ Location (Override) │
  • └───────────────────────────┴────────────────────────────┘
  • Step-by-Step Configuration Procedure

Open Warehouse management > Setup > Mobile device > Mobile device steps .

Locate the Step ID corresponding to the operational prompt where the detour is needed (e.g., select ItemPick for item picking steps).

In the Promoted detour options FastTab, add the mobile device menu item that executes the work (e.g., Sales picking ).

Under Select detours , choose the auxiliary menu item that the worker should access (e.g., Location inquiry ).

Select Field value pass-through :

Add a line: Send from Sales picking -> set source field to Location -> Paste in Location inquiry -> set target field to Location .

When the picker detours to Location inquiry, the mobile app automatically populates the current bin location without requiring the worker to scan it.

Select Return value mapping (if applicable):

If the detour allows the worker to select an alternate location or a new target license plate, specify the source field from the detour to map back into the primary work step.

Loading diagram... Mobile Device Step Detour Execution Flow

3. Practical Detour Use Cases and Walkthroughs

Step detours transform common warehouse floor bottlenecks into streamlined, zero-abort workflows:

Use Case 1: Empty Pick Face Investigation and Alternate Location Sourcing

Scenario : An order picker is directed to pick 10 eaches of an item from PICK-01-A . Upon arrival, the bin is empty due to an unrecorded inventory discrepancy.

Detour Execution :

The picker taps the Item inquiry detour button directly on the ItemPick screen.

The system passes the Item ID into the inquiry automatically. The screen displays that 50 units exist in adjacent reserve location BULK-04-B .

The picker returns from the detour. Because the worker profile has Allow override location enabled, the worker enters BULK-04-B , confirms the pick, and completes the sales order line without supervisor intervention.

Use Case 2: On-Demand Pallet and Shipping Label Printing

Scenario : A forklift operator is executing purchase order putaway. During pallet transport, the physical license plate label is torn or smudged by the forklift mast.

Detour Execution :

On the PutLocation step, the driver taps a detour for Print label .

The system passes the active License Plate ID into the label printing menu item.

The print request triggers document routing, producing a replacement ZPL barcode label on the mobile forklift printer.

The driver affixes the new label, closes the detour, and completes the putaway.

Use Case 3: Damaged Stock Quarantining

Scenario : A picker notices that three cartons of liquid detergent on a picking shelf are leaking.

Detour Execution :

From the pick step, the worker launches a detour configured for Inventory status change .

The worker transfers the 3 damaged cartons from status Available to Damaged (which applies an inventory blocking disposition).

The worker returns to the pick step to pick undamaged units from the remaining balance.

4. GS1 Barcode Parsing Architecture and Application Identifiers

Traditional 1D barcode scanning requires multiple physical scans: scan the item barcode, scan the batch lot barcode, scan the serial barcode, and manually type the received quantity. GS1 barcode parsing consolidates these steps into a single physical scan. ┌──────────────────────────────────────────────────────────────────────┐

  • │ GS1-128 Barcode Architecture │
  • └──────────────────────────────────────────────────────────────────────┘
  • (01)00614141999996(10)LOT-2026-X(17)261231(30)50
  • │ │ │ │
  • │ │ │ └─ AI (30): Quantity = 50
  • │ │ │ (Variable len, up to 8 digits)
  • │ │ └─────────── AI (17): Expiration Date = Dec 31, 2026
  • │ │ (Fixed length, 6 digits: YYMMDD)
  • │ └───────────────────────── AI (10): Batch Number = LOT-2026-X
  • │ (Variable length, terminated by <FNC1>)
  • └────────────────────────────────────────── AI (01): GTIN = 00614141999996
  • (Fixed length, 14 digits)
  • Standard GS1 Application Identifiers (AIs)

GS1 standards define standardized two- to four-digit prefixes enclosed in parentheses called Application Identifiers (AIs) that tell the parser what type of data follows:

Application Identifier (AI) Data Content Description Field Format & Length Dynamics 365 SCM Mapping

AI (01) Global Trade Item Number (GTIN) Fixed, 14 numeric digits Released product Item number or Barcode table.

AI (10) Batch / Lot number Variable, alphanumeric up to 20 chars Tracking dimension: Batch number ( InventBatchId ).

AI (17) Expiration date Fixed, 6 numeric digits ( YYMMDD ) Inventory tracking: Expiration date.

AI (21) Serial number Variable, alphanumeric up to 20 chars Tracking dimension: Serial number ( InventSerialId ).

AI (30) Variable count / Transaction quantity Variable, numeric up to 8 digits Transaction quantity received or picked.

AI (00) Serial Shipping Container Code (SSCC) Fixed, 18 numeric digits License plate tracking ( LicensePlateId ).

AI (15) Best before date Fixed, 6 numeric digits ( YYMMDD ) Inventory tracking: Best before date.

AI (310x) Net weight in kilograms (variable weight) Fixed decimal, 6 digits Catch weight inventory transaction quantity.

Fixed-Length vs. Variable-Length AIs and the FNC1 Delimiter

Fixed-Length AIs : Fields such as AI (01) (always 14 digits) and AI (17) (always 6 digits) have predefined lengths. The D365 SCM parser knows exactly how many characters to ingest before evaluating the next AI.

Variable-Length AIs : Fields such as AI (10) (Batch number) and AI (21) (Serial number) can vary in length. When a variable-length field is followed by another AI in a combined barcode, GS1 requires a special termination character: the Function 1 Symbol Character (FNC1) or Group Separator ( <GS> , ASCII character 29 / ). The parser uses the FNC1 delimiter to identify where the batch string ends and the next AI begins.

Configuring GS1 Parsing in D365 SCM

Define Application Identifiers :

Navigate to Warehouse management > Setup > Mobile device > Bar code setup > GS1 application identifiers .

Verify standard AIs (01, 10, 17, 21, 30) or create custom identifiers. Define length, data type (String, Numeric, Date), and decimal placement.

Configure Generic Barcode Setup :

Navigate to Warehouse management > Setup > Mobile device > Bar code setup > Bar code generic .

Create a barcode parsing policy and link it to the configured GS1 Application Identifiers.

Assign to Mobile Device Scanning Profiles :

Under Warehouse management > Setup > Mobile device > Mobile device scanning profiles , link the GS1 parsing policy to the scanning profiles utilized by warehouse worker devices.

5. Barcode Scanning Optimization in the Mobile App

Optimizing scanning mechanics ensures high transaction throughput and eliminates operator keystroke bottlenecks:

1D vs. 2D Symbologies : While linear 1D barcodes (Code 128, GS1-128) are widely used, high-density 2D GS1 DataMatrix and GS1 QR codes can store extensive concatenated data (GTIN, Batch, Expiry, Serial, Quantity) in a compact footprint that fits on small medical vials or electronic components.

Hardware Scanner Wedges : Industrial scanners (Zebra, Honeywell) should be configured to transmit scanned data via an Android Intent or optimized hardware wedge rather than basic keyboard emulation. Basic keyboard wedges can strip non-printable ASCII delimiters like the FNC1 <GS> character, causing GS1 parsing to fail.

Scan Validation and Check Digits : Enable check digit validation on locations and GTINs to catch transmission drops before the app submits transactions to D365 SCM.

6. Implementation Scenarios and Exam Traps

Important

Exam Tip — Step Detour Pass-Through Matching : When configuring field value pass-through for step detours, the data types and conceptual targets must align. For example, if detouring from an ItemPick step to a Location inquiry , you must pass the Location field from the picking step to the Location field of the inquiry. Passing the Item ID into a Location inquiry will cause the inquiry screen to fail or prompt the worker to overwrite the input.

Warning

Exam Trap — Missing FNC1 Delimiters : If warehouse workers report that scanning a composite GS1-128 barcode successfully captures the GTIN but fails to parse the batch number or returns corrupted batch text that includes subsequent AI codes, inspect the physical scanner's barcode wedge profile. The scanner hardware is dropping the hidden ASCII 29 ( <GS> ) FNC1 delimiter, preventing D365 SCM from parsing variable-length fields.

Tip

Best Practice — Promoting Detours : Always configure detours under the Promoted detour options FastTab rather than burying them inside standard overflow menus. Promoted detours render as prominent, colored action buttons on the mobile interface, enabling material handlers to trigger exception workflows with a single touch.