SAP Business One Route Optimization with SuiteFleet

1. Start with the SAP Business One order

Open the source order 1256 for Harbor Office Products and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains two lines with quantities 4 and 6 in the units shown.

Review the sales order’s customer, delivery date, ship-to address, availability, and open item quantities. Create a Delivery for the intended quantities through the supported base-document workflow. Do not use manual Close as a delivery event.

Business One distinguishes visible DocNum from internal DocEntry. Preserve base-document relationships when copying a sales order to a Delivery. A single customer can have several orders and delivery documents with the same address; matching by customer code and address alone is unsafe. SAP Business One sales orders.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Treat Delivery Date as a requested date, and obtain a receiving window explicitly. Resolve warehouse codes to actual departure points rather than routing from the business partner’s billing address.

3. Select eligible stops and available drivers

Open Workbench for the intended date and filters. Inspect task, driver, and hub layers; resolve tasks without a location before optimization. Use geographic selection to choose the intended area, then confirm the selected task set contains only released work.

Choose Plan & Optimize when assigning eligible tasks across drivers, or Optimize Existing Routes when retaining assignments and improving stop sequence. Review enabled drivers, shift windows, departure hubs, and the displayed task-capacity limits. Do not assume those limits represent weight or volume.

Business One distinguishes visible DocNum from internal DocEntry. Preserve base-document relationships when copying a sales order to a Delivery. A single customer can have several orders and delivery documents with the same address; matching by customer code and address alone is unsafe.

4. Review objectives, constraints, and results

Choose the supported objective: Fastest Completion, Shortest Distance, Fewest Vehicles, or Balanced Workload. Review Respect Time Windows, Reassign Assigned Tasks, and Time Per Stop before running the preview. Select the objective that matches the dispatch plan and confirm which routing constraints are enabled.

Inspect the returned driver assignments, stop sequence, projected completion, and every unassigned task. Check stop times against driver shifts as well as customer windows; confirm that the proposed schedule is feasible. Missing locations and conflicting requirements need explicit resolution.

Review the Dallas–Fort Worth planning example, with distances in miles and local receiving times. Dispatchers should check stop sequence, road access, and unresolved work before applying a plan.

5. Execute the route and process actual outcomes

Keep assignment and planned arrival separate from customer delivery. Monitor failed, rescheduled, and completed stops during execution. A route application must not post inventory, close an order, or trigger billing by itself.

If 4 cases are copied to one Delivery and 6 remain open, only the first Delivery should receive the completed task result. A retry must not create a second Delivery document for the same goods.

After a stop completes, match its task ID to the source shipment, review required proof, and reconcile accepted quantities. Record actual event time and a separate sync outcome. If the source changes after planning, compare the change with the dispatched allocation before overwriting operational data.

6. Verify the result in SAP Business One

Write verified last-mile results to Delivery user-defined fields or a related delivery record supported by the implementation. Keep the Delivery’s native document state separate from the custom Delivered result. Check the original order’s remaining open quantities instead of treating Closed as proof of receipt. SAP Business One sales orders.

Read back the linked record and review every outstanding allocation before marking the full order delivered. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.