Study guide
12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
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
12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
Key Takeaways Explain This Topic AI
Goods in transit (GIT) orders record legal inventory ownership transfer at the port of origin (e.g., FOB shipping point) by posting vendor invoices prior to physical warehouse receipt.
Posting a voyage vendor invoice moves inventory into a virtual Goods in Transit warehouse associated with the destination warehouse while establishing accounts payable liability.
The Tracking Control Center automates schedule adjustments, updating voyage statuses, downstream leg lead times, and purchase order confirmed delivery dates when milestone dates change.
Physical receipt from a Goods in Transit order transfers stock from the virtual warehouse to the physical destination warehouse using desktop journals or the Warehouse Management Mobile App.
Over/under delivery tolerance rules determine whether quantity discrepancies during container receipt are accepted, rejected, or automatically canceled to close out open GIT balances.
Last updated: September 2026
12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
Quick Answer: The Goods in Transit (GIT) architecture in Dynamics 365 Supply Chain Management (D365 SCM) enables companies to assume legal ownership of purchased goods at the overseas shipping point (such as under Incoterms FOB Shipping Point or EXW ). By posting the vendor invoice directly from the voyage prior to physical arrival, D365 SCM records accounts payable liability and places items into a virtual Goods in Transit warehouse . The Tracking Control Center acts as the automation engine, dynamically cascading milestone dates across journey legs and updating supply delivery dates. When cargo arrives, Goods in transit receiving moves items into physical inventory, while Over/under delivery tolerances control the resolution of shipping discrepancies.
1. Goods in Transit (GIT) Orders and Ownership Transfer
In standard domestic procurement, legal title and inventory ownership transfer when the goods are delivered and physically receipted at the warehouse dock. However, global international trade operates under strict Incoterms (International Commercial Terms):
FOB Origin / Shipping Point (Free On Board) or EXW (Ex Works) : Legal ownership, title, and transit risk transfer to the buying enterprise the moment goods are loaded onto the vessel or transport carrier at the overseas port of departure.
Balance Sheet Requirement : GAAP and IFRS auditing standards require the purchasing enterprise to recognize both the asset (inventory) and the corresponding commercial liability (accounts payable) upon title transfer, even if the vessel will be crossing oceans for 30 to 60 days.
Why Standard PO Receiving Fails for Inbound Imports
Under standard D365 SCM Purchase Order processing, an invoice cannot be posted until a product receipt is generated, or posting an invoice immediately triggers physical inventory receipt at the destination warehouse. If used for ocean imports, this practice incorrectly inflates on-hand warehouse availability, leading warehouse staff to attempt picking and shipping inventory that is physically in the middle of the Pacific Ocean.
Landed Cost resolves this dilemma through Goods in Transit (GIT) Orders :
The vendor submits the commercial invoice upon vessel departure.
The accounts payable clerk posts the invoice directly from the voyage.
The system records the vendor liability in Accounts Payable.
The system automatically creates a Goods in Transit Order , transferring the inventory into a dedicated, virtual Goods in Transit Warehouse . +-------------------------------------------------------------------------+
- | PURCHASE ORDER LINE: 1,000 UNITS |
- +------------------------------------+------------------------------------+
- │
- ▼ [Post Invoice from Voyage]
- +------------------------------------+------------------------------------+
- | PURCHASE ORDER LINE STATUS = INVOICED |
- | - Financial Liability Posted to Accounts Payable |
- | - Physical Purchase Order Line Closes |
- +------------------------------------+------------------------------------+
- │ (Generates)
- ▼
- +------------------------------------+------------------------------------+
- | GOODS IN TRANSIT (GIT) ORDER |
- | - Virtual Warehouse: WH-GIT-24 (Transit Asset Account) |
- | - Quantity: 1,000 Units (In Transit Balance Sheet Asset) |
- | - Destination: WH-24 Dallas Distribution Center |
- +------------------------------------+------------------------------------+
- │
- ▼ [Physical Arrival & Receiving]
- +------------------------------------+------------------------------------+
- | DESTINATION WAREHOUSE: WH-24 (PHYSICAL ON-HAND) |
- | - Issues from WH-GIT-24 (Clears Transit Asset) |
- | - Receipts into WH-24 Location/License Plate (Available On-Hand) |
- +-------------------------------------------------------------------------+
- 2. Configuring the Goods in Transit Infrastructure
To operationalize Goods in Transit orders, specific warehouse and parameter prerequisites must be established in D365 SCM.
1. The Virtual Goods in Transit Warehouse
Every physical destination warehouse that receives international shipments requires a paired virtual Goods in Transit warehouse.
Navigation : Inventory management > Setup > Inventory breakdown > Warehouses
Create a new warehouse record (e.g., WH-GIT-24 ).
In the General FastTab, set the Type field to Goods in transit .
2. Linking GIT Warehouse to Destination Warehouse
Open the master record for the physical destination warehouse (e.g., WH-24 Dallas Distribution Center ).
Expand the Warehouse management or General FastTab.
In the Goods in transit warehouse field, select the virtual transit warehouse ( WH-GIT-24 ).
Important
If the destination warehouse does not have a linked Goods in Transit warehouse, D365 SCM will block invoice posting on the voyage and generate a validation error stating that no transit warehouse is defined for the delivery location.
3. Posting the Vendor Invoice on a Voyage
Navigate to Landed cost > Voyages > All voyages .
In the Action Pane, open the Invoicing tab and click Post invoice .
The system validates that the voyage lines are associated with valid folios and containers.
The posting executes two simultaneous financial actions:
Merchandise Vendor Invoice: Debits Goods in Transit Inventory Asset; credits Vendor Accounts Payable.
Landed Cost Accruals: Debits Goods in Transit Inventory Asset; credits Landed Cost Accrual / Clearing accounts for all estimated auto-costs.
3. The Tracking Control Center: Dynamic Schedule Automation
The Tracking Control Center is the central rules engine in Landed Cost that monitors logistics milestones and automates operational updates across the system.
- Navigation : Landed cost > Setup > Tracking control center
- Tracking Rules and Trigger Mechanics
A tracking rule consists of a Source table / trigger , a Condition , and an Action :
Trigger Events : Entering or modifying dates on journey legs (e.g., Actual departure date , Actual arrival date , Estimated departure date ).
Target Entities : Voyage headers, Shipping containers, Folios, Purchase order lines, or Transfer order lines.
Primary Tracking Control Actions
Lead Time and Milestone Cascading :
When an ocean carrier reports a delay and the user updates the Actual departure date on Leg 2 (Ocean transit), the Tracking Control Center automatically evaluates downstream legs.
It adds configured lead times to calculate revised Estimated arrival dates for Leg 3 (Port customs) and Leg 4 (Inland rail).
Synchronizing Supply Delivery Dates :
Changes to the final leg's arrival date automatically update the Confirmed delivery date on the underlying purchase order lines.
Master Planning (Planning Optimization) immediately recognizes the updated delivery date, recalculating safety stock time fences and pegged sales order promising dates.
Automated Status Progression :
Populating the Actual departure date on Leg 1 automatically changes the Voyage Status from Created to In transit .
Populating the Actual arrival date at the destination port transitions container statuses from At sea to At port .
Tracking Control Center Configuration Matrix
Source Table Trigger Field Condition / Leg Action Executed by System
Voyage leg Actual departure date Leg 1 (Ocean Departure) Update Voyage Status to In transit ; cascade estimated arrival dates.
Voyage leg Actual arrival date Leg 2 (Port of Entry) Update Container Status to At port ; notify customs broker.
Voyage leg Actual arrival date Final Leg (Warehouse Dock) Update Purchase Order line Confirmed Delivery Date; advance status to Arrived .
Tracking date Customs release date Leg 3 (Customs Dwell) Update Folio Status to Customs Cleared .
4. Receiving Goods in Transit at the Destination Warehouse
When shipping containers physically arrive at the destination warehouse facility, the inventory must be transferred out of the virtual Goods in Transit warehouse and into available on-hand stock.
Receiving Workflows in D365 SCM
Warehouse operations can execute Goods in Transit receiving through two distinct mechanisms:
Method A: Desktop Client Receiving
Navigate to Landed cost > Inquiries > Goods in transit orders .
Locate the active Goods in Transit order matching the container or voyage.
In the Action Pane, click Receive goods in transit .
Enter the quantity received, destination location, and inventory batch/serial numbers.
Click OK to post the receipt journal.
Method B: Warehouse Management Mobile App (WMA)
For advanced warehouse management (WMS) facilities utilizing mobile barcode scanners:
Configure a Mobile Device Menu Item under Warehouse management > Setup > Mobile device > Mobile device menu items .
Set Mode to Work .
Set Work creation process to Goods in transit receiving (or Goods in transit item receiving ).
The mobile worker scans the Voyage ID, Container ID, or License Plate.
The worker confirms received quantities and scans items directly into receiving staging locations. Directed putaway work is generated to move items to final bulk or pick locations.
Financial Impact of Receiving Goods in Transit
Debit : Destination Warehouse Inventory Asset (increases physical on-hand valuation).
Credit : Goods in Transit Inventory Asset (clears the temporary in-transit balance sheet asset).
No accounts payable or landed cost accrual entries are posted during this step, as those liabilities were recognized during invoice posting at the shipping point.
Handling Damaged or Lost In-Transit Stock
If physical counts reveal missing or destroyed items upon opening the container seal:
Partial Receiving : The worker receipts only the undamaged, verified quantity into available stock.
In-Transit Write-Off : The remaining damaged/missing quantity remains in the Goods in Transit order. Under Goods in transit orders > Write-off , the inventory controller executes a write-off journal, posting the lost stock directly to an in-transit loss or insurance claims P&L account.
5. Over/Under Delivery Tolerances in Landed Cost
Discrepancies frequently occur between purchase order quantities and physical container shipments due to vendor packaging variations, bulk liquid evaporation, or container volume constraints.
- Navigation : Landed cost > Setup > Over/under tolerance setup
- Tolerance Configuration Matrix
Tolerances can be defined across five structural hierarchy levels:
Item : Specific released product.
Item group : Item landed cost group.
Vendor : Specific vendor account.
Vendor group : Vendor procurement group.
All : Enterprise-wide global default.
Over-Delivery vs. Under-Delivery Mechanics
Parameter Operational Definition System Behavior When Threshold Is Met Exceeding Threshold Behavior
Under-delivery Tolerance The allowable percentage shortfall on an inbound shipment (e.g., 5 % 5\% 5% under-delivery). When received quantity is within tolerance (e.g., 96 units of 100 received), the system automatically cancels and closes the remaining 4 units , closing the Goods in Transit order and purchase order line completely. If received quantity falls below the minimum tolerance (e.g., 85 units received), the remaining 15 units stay open in the Goods in Transit order for subsequent delivery or manual review.
Over-delivery Tolerance The allowable percentage excess on an inbound shipment (e.g., 10 % 10\% 10% over-delivery). The warehouse worker can receive excess units up to the tolerance limit (e.g., 110 units of 100 received) without requiring managerial purchase order modification. Receipts exceeding the over-delivery percentage are blocked by the mobile scanner, preventing unapproved stock from entering the facility.
Note
Automatic under-delivery closure is vital for master planning hygiene. Without under-delivery tolerances, small unreceived residual balances (e.g., 2 missing units out of 5,000) remain open indefinitely in virtual transit warehouses, causing Planning Optimization to anticipate phantom inbound supply and fail to trigger necessary replenishment.
6. Implementation Scenarios and Common Exam Traps
Tip
Exam Tip — Vendor Invoicing Sequence: In standard D365 procurement questions, the correct sequence is always Purchase Order -> Product Receipt -> Vendor Invoice . In Landed Cost international import questions, the sequence is inverted : Purchase Order -> Voyage Creation -> Vendor Invoice (Generating Goods in Transit) -> Physical Goods in Transit Receipt . Memorize this reversal for MB-330.
Warning
Exam Trap — Master Planning Visibility of GIT: Goods in transit orders are treated as confirmed inbound supply by Planning Optimization. If a voyage is delayed at sea and the Tracking Control Center updates the arrival date, running Master Planning will automatically reschedule dependent production orders and customer sales order promises without requiring manual order maintenance.
Important
Exam Tip — Warehouse Mobile App Setup: To receive Goods in Transit stock using handheld RF scanners, do not use standard Purchase order item receiving . You must configure dedicated mobile menu items using Goods in transit receiving or Goods in transit item receiving .