---
article_id: KB1476647
article_type: FAQ
component_ids:
  - SBN-LBN-FC-MFE
component_descriptions:
  - Business Network for Logistics > Freight Collaboration > Manage Freight Execution
products:
  - SAP Business Network for Logistics
personas:
  - Supplier
language: en
created: 2026-11-10
updated: 2026-11-10
source: Knowledge Base
url: https://support.ariba.com/item/view/KB1476647
connect_url: https://support.ariba.com/item/view/KB1476647?min=1
sap_for_me_url: https://me.sap.com/notes/KB1476647
---

# How do I set up dispatch and generate a Driver App Service access code in SAP Business Network for Logistics?

## Symptom

How do I assign a driver and vehicle to a confirmed freight booking and generate a Driver App Service (DAS) access code so my driver can report status updates from their phone?

## Environment

SAP Business Network for Logistics (BN4L)

## Resolution

##### Step 1: Open the confirmed Freight Order

1. Navigate to Freight Collaboration → Manage Freight Execution
2. Open the FO in status Confirmed
3. Navigate to the Execution or Dispatch tab

##### Step 2: Assign driver and vehicle

- Enter the driver's name and optionally their mobile number (needed for the DAS app)
- Enter the vehicle plate number and trailer number (if applicable)

##### Step 3: Generate and send the DAS access code

The DAS Driver App (SAP Logistics Business Network Driver App — available on iOS and Android) allows your driver to report status milestones and submit digital proof of delivery from their phone.

1. In the Dispatch tab, click Generate Code in the DAS Access Code section
2. A unique code is created for this specific FO
3. Send the code to your driver by SMS or messaging — the driver enters it in the app to access the FO

> Note: The DAS access code is unique per FO. Generate a new code if the driver changes.

##### Step 4: Review special instructions

Check the FO for: temperature requirements, hazmat/ADR documentation, site access restrictions, and customer-specific requirements.

##### Step 5: Save dispatch details

Click Save or Confirm Dispatch. Proceed to [Phase 6: Tracking & Status Updates](https://support.ariba.com/item/view/KB1476649).

Common issues:

| What you see | Likely cause | Action |
| --- | --- | --- |
| No Dispatch tab visible | Insufficient user role | Request Carrier Dispatcher role from your BN4L admin |
| DAS code not generated | FO not in Confirmed status or DAS not enabled by shipper | Verify FO status; confirm DAS is configured with your shipper |
| Driver cannot log into DAS app | Incorrect code; wrong app installed | Re-send code; confirm driver has the SAP BN4L Driver App |

## See Also

Carrier Shipment Lifecycle — Freight Order to Invoice:

Explore your entire journey in this process:

| \<\<  <br>[Get Started](https://support.ariba.com/item/view/KB1481604) | \<\<  <br>[Receive Freight Order](https://support.ariba.com/item/view/KB1481607) | \<\<  <br>[Tendering](https://support.ariba.com/item/view/KB1481609) | \<\<  <br>[Booking](https://support.ariba.com/item/view/KB1481613) | \<Current>  <br>Dispatch | >>  <br>[Tracking](https://support.ariba.com/item/view/KB1481618) | >>  <br>[Proof of Delivery](https://support.ariba.com/item/view/KB1481620) |
| --- | --- | --- | --- | --- | --- | --- |
