---
article_id: KB1476649
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/KB1476649
connect_url: https://support.ariba.com/item/view/KB1476649?min=1
sap_for_me_url: https://me.sap.com/notes/KB1476649
---

# How do I report shipment tracking and status updates in SAP Business Network for Logistics?

## Symptom

How do I report pickup, in-transit status, delays, and ETA updates to my shipper through SAP Business Network for Logistics (BN4L) while my shipment is in transit?

## Environment

SAP Business Network for Logistics (BN4L)

## Resolution

##### Key milestones to report

| Milestone | When |
| --- | --- |
| PICK\_UP | Driver has loaded and departed from the origin |
| IN\_TRANSIT | Shipment is en route |
| DELAY | Any significant deviation from the scheduled ETA |
| ETA Update | When estimated arrival changes materially |
| ARRIVAL\_AT\_STOP | Multi-stop FOs: on arrival at each stop |
| DELIVERY | Cargo delivered — see Phase 7 for POD |

##### Method A — DAS Driver App

1. Driver opens the SAP BN4L Driver App and selects the active FO
2. Taps the relevant status button (Pickup, En Route, Delay, Arrived)
3. App captures GPS automatically and uploads the event to BN4L in real time

##### Method B — Portal

1. Navigate to Freight Collaboration → Manage Freight Execution → open the FO
2. Navigate to the Tracking or Events tab → click Add Status Event
3. Select the event type, enter date/time and notes → click Save

##### Method C — EDI (ANSI X12)

Send EDI 214 (Transportation Carrier Shipment Status) with the appropriate status code:

| Status | Code |
| --- | --- |
| Picked up | X3 |
| In transit | X4 |
| Out for delivery | X6 |
| Delivery delay | D1 |

EDIFACT: Use IFTSTA with the equivalent status qualifier.

##### Method D — Carrier API

`POST /tracking-events` — include `freightOrderId`, `eventType`, `eventTime`, and optionally `location` (lat/long).

Common issues:

| What you see | Likely cause | Action |
| --- | --- | --- |
| Update rejected | FO not in In Execution status or insufficient role | Verify FO status; check user role |
| Shipper sees no tracking | EDI 214 rejected or wrong FO reference in API call | Check EDI acknowledgement (997); verify FO ID |
| ETA deviation alert from shipper | Your ETA deviated from scheduled window | Update ETA in portal and contact shipper proactively |

## See Also

[SAP Community: Carrier Side EDI Setup for BN4L](https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/sap-business-network-for-logistics-carrier-side-ansi-x12-edi-setup-and/ba-p/13606802)

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) | \<\<  <br>[Dispatch](https://support.ariba.com/item/view/KB1481616) | \<Current>  <br>Tracking | >>  <br>[Proof of Delivery](https://support.ariba.com/item/view/KB1481620) |
| --- | --- | --- | --- | --- | --- | --- |
