13.1 Shipping Agents, Locations & Vendor Lead Times

13.1 Shipping Agents, Locations & Vendor Lead Times

Quick Summary: Dynamics 365 Business Central synchronizes logistics fulfillment and inbound procurement through time-phased master data. Outbound order promising pairs Shipping Agents and Shipping Agent Services (defining transit time date formulas like 2D or 1W) with Inbound/Outbound Warehouse Handling Times configured on Location cards or Company Information. Multi-site logistics are managed using Ship-to Addresses for customer delivery destinations and Order Addresses for vendor dispatch origins, while replenishment lead times resolve through a strict hierarchy anchored by Stockkeeping Units (SKUs) and the Item Vendor Catalog.

---

Customer Logistics Master Data: Shipping Agents & Services

Fulfilling customer orders reliably requires Business Central to calculate when goods must leave the warehouse to meet customer delivery expectations. This order promising engine relies on two foundational tables:

UI Navigation Path:
Tell Me (Alt+Q) -> Shipping Agents (Page 428 / Table 291)
Select Agent -> Related -> Agent -> Shipping Agent Services (Page 429 / Table 5790)

1. Shipping Agents (Table 291): Represents external freight carriers, courier services, or internal delivery fleets (e.g., DHL, FEDEX, UPS, OWN TRUCK). Key fields include:

   • Code & Name: Alphanumeric identifier and description.
   • Internet Address: Tracking URL with token %1 (e.g., https://www.tracking.carrier.com?trackno=%1). When a package tracking number is entered on a posted sales shipment, users click the link to jump directly to the carrier's tracking page.
   • Account No.: The corporate account number held with the carrier.

2. Shipping Agent Services (Table 5790): Defines specific transit levels offered by an agent (e.g., STANDARD, EXPRESS, NEXTDAY). Each service specifies:

   • Shipping Time: A DateFormula specifying transit duration (e.g., 1D, 2D, 1W).
   • Base Calendar Code: An optional working-day calendar (excluding weekends and statutory holidays) used when calculating transit days.

Warehouse Handling Times & Order Promising Engine

Shipping transit time alone does not account for internal warehouse operations. Business Central introduces handling times configured at two levels:

• Location Card (Page 5703 / Table 14): Specifies Outbound Whse. Handling Time (picking, packing, staging) and Inbound Whse. Handling Time (unloading, inspection, put-away) specific to that distribution facility.
• Company Information (Page 1 / Table 79): Acts as the global fallback when a sales or purchase document line specifies a blank location code.

Outbound Order Promising Timeline:

[Shipment Date] ──(+ Outbound Handling Time)──► [Planned Shipment Date] ──(+ Shipping Time)──► [Planned Delivery Date]
      ▲                                                    ▲                                            ▲
(Picking/Packing Begins)                           (Leaves Loading Dock)                       (Customer Receives)

When a customer requests a specific delivery date (Requested Delivery Date), Business Central calculates backwards:

$\text{Planned Delivery Date} = \text{Requested Delivery Date}$ $\text{Planned Shipment Date} = \text{Planned Delivery Date} - \text{Shipping Time}$ $\text{Shipment Date} = \text{Planned Shipment Date} - \text{Outbound Whse. Handling Time}$

If the resulting Shipment Date is earlier than the Order Date, the delivery date cannot be honored. Business Central then calculates forward from the earliest available date to propose a Promised Delivery Date.

Shipping Advice: Partial vs. Complete

Configured on the Customer Card (Shipping FastTab) and copied to the Sales Order Header:

• Partial: Allows sales lines to be shipped in multiple partial shipments as inventory becomes available.
• Complete: Mandates that all lines on the sales order must be shipped together. In advanced warehouse environments, Business Central blocks posting a Warehouse Shipment if any order line remains unfulfilled.

---

Customer Delivery Infrastructure: Ship-to Addresses

A customer enterprise frequently operates multiple stores, regional offices, job sites, or distribution depots. While commercial contracting and accounts receivable are centralized under a single Customer Card (Table 18), physical shipments must route to specific geographic destinations.

UI Navigation Path:
Tell Me (Alt+Q) -> Customers -> Select Customer -> Related -> Customer -> Ship-to Addresses (Page 300 / Table 222)

Overrides Provided by Ship-to Addresses

Selecting a Ship-to Code on a Sales Header automatically overrides defaults without altering the customer's financial identity:

[!IMPORTANT] Assigning a Ship-to Code on a sales document alters delivery routing and sales tax calculation, but leaves the Bill-to Customer No. unchanged. Accounts receivable ledgers, credit limit checks, and invoicing remain linked to the parent billing customer.

---

Vendor Procurement Logistics: Order Addresses & Default Locations

Similar to customers, vendors often maintain corporate sales offices distinct from their manufacturing facilities, shipping docks, or regional dispatch depots.

UI Navigation Path:
Tell Me (Alt+Q) -> Vendors -> Select Vendor -> Related -> Vendor -> Order Addresses (Page 368 / Table 224)

Vendor Master Data Triad

1. Buy-from Vendor (Table 23): The primary commercial relationship entity placed on purchase orders.
2. Pay-to Vendor: The financial entity receiving invoices and payments (configured on the Invoicing FastTab of the Buy-from Vendor).
3. Order Address (Table 224): The physical dispatch origin from which the vendor ships goods.

When creating a Purchase Order, selecting an Order Address Code on the General FastTab populates the vendor's physical dispatch address on the purchase order document. Remittance advice and 1099/tax reporting remain tied to the Pay-to Vendor.

Vendor Default Location Code

On the Vendor Card under the Receiving FastTab, the Location Code field defines the default receiving warehouse. When a purchase order is generated for this vendor, this location code automatically defaults onto the purchase header and lines, eliminating manual warehouse selection.

---

Vendor Lead Time Calculation & Inbound Logistics Engine

The Lead Time Calculation is a DateFormula (e.g., 5D, 2W, 1M) specifying the elapsed time between issuing a purchase order and receiving physical stock at the warehouse dock.

Inbound Receipt Calculation Timeline:

[Order Date] ──(+ Lead Time Calculation)──► [Planned Receipt Date] ──(+ Inbound Whse. Handling Time)──► [Expected Receipt Date]
      ▲                                             ▲                                                    ▲
(PO Placed with Vendor)                    (Goods Arrive at Dock)                              (Put-Away & Available for Sale)

Hierarchy of Lead Time Resolution

Business Central resolves vendor lead time through a deterministic four-tier hierarchy, moving from the most specific context to the most general:

Lead Time Resolution Hierarchy:

Tier 1 (Highest): Stockkeeping Unit (SKU) Card (Table 5700 / Page 5701) [Item + Location + Variant]
       │
       ▼ (If SKU lead time is blank)
Tier 2:           Item Vendor Catalog (Table 99 / Page 114) [Item No. + Vendor No.]
       │
       ▼ (If no Item Vendor record exists)
Tier 3:           Item Card (Table 27 / Page 30) [Replenishment FastTab]
       │
       ▼ (If Item Card lead time is blank)
Tier 4 (Lowest):  Vendor Card (Table 23 / Page 26) [Receiving FastTab]

1. Stockkeeping Unit (SKU) Card: Governs when an item has distinct vendor lead times depending on which internal warehouse location receives the goods.
2. Item Vendor Catalog (Page 114): Specifies the lead time contracted with a specific vendor for a specific item, alongside the Vendor Item No..
3. Item Card: Defines the general inbound procurement lead time for the item regardless of supplier.
4. Vendor Card: Serves as the global fallback lead time for all items purchased from that supplier when no item-specific lead time exists.

---

Step-by-Step UI Configuration Workflows

Workflow A: Configuring Shipping Agents, Services, and Warehouse Handling Times

1. Press Alt+Q, type Shipping Agents, and choose the related link.
2. Click New, enter Code DHL, Name DHL Express, and Internet Address https://www.dhl.com/track?id=%1.
3. With DHL selected, choose Related -> Agent -> Shipping Agent Services.
4. Add Service Code 2DAY, Description DHL 2-Day Guaranteed, and set Shipping Time to 2D.
5. Press Alt+Q, type Locations, open the WEST warehouse card, expand Warehouse, and set Outbound Whse. Handling Time to 1D and Inbound Whse. Handling Time to 1D.

Workflow B: Configuring a Customer Ship-to Address with Tax and Logistics Defaults

1. Press Alt+Q, type Customers, and open customer 10000.
2. Choose Related -> Customer -> Ship-to Addresses, then click New.
3. Enter Code STORE-02, Name Downtown Retail Store, and fill in street and postal address.
4. In the Shipping section, set Location Code to WEST, Shipping Agent Code to DHL, and Shipping Agent Service Code to 2DAY.
5. In the Tax section, set Tax Area Code to CALIFORNIA.

Workflow C: Setting Up Multi-Tier Vendor Lead Times

1. Open Vendor 20000 and set Lead Time Calculation on the Receiving FastTab to 3W.
2. Open Item 1920-S, choose Related -> Item -> Purchases -> Vendors (Item Vendor Catalog).
3. Add Vendor 20000, enter Vendor Item No. V-9941, and set Lead Time Calculation to 10D.
4. Create a Stockkeeping Unit for Item 1920-S at Location WEST and set Lead Time Calculation to 5D.

---

Common Pitfalls & Exam Traps

• Pitfall 1: Confusing Planned Receipt Date with Expected Receipt Date. Goods arriving at the loading dock on the Planned Receipt Date are not yet available for picking. Only after adding Inbound Whse. Handling Time does the item reach the Expected Receipt Date, which is the actual date checked by order reservation and availability engines.
• Pitfall 2: Overwriting the Bill-to Customer Instead of Selecting a Ship-to Address. Changing the customer address on the General FastTab of a sales order changes billing liability. To change physical delivery, users must leave the Sell-to and Bill-to untouched and select a code in the Ship-to Code field.
• Pitfall 3: Assuming the Vendor Card Lead Time Overrides the Item Vendor Catalog. Candidates often assume the Vendor Card is the primary procurement authority. In reality, the Item Vendor Catalog and SKU cards both take precedence over the Vendor Card.
• Pitfall 4: Neglecting Base Calendars in Date Formula Additions. Adding 2D via a Shipping Agent Service ignores weekends unless a Base Calendar Code is attached to the service or location, which can cause Business Central to schedule shipments or deliveries on non-working days.