The October 2026 release of SAP Business Network for Logistics brings a focused set of enhancements across both SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace. This post walks through the highlights — what's new, what it means for you, and where to find more detail.
Cross SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace
Feature enhancement for integration logs
The ‘Manage Integration Log' app has been upgraded. You can switch to it by clicking the ‘New Version' button in the upper right corner of the app.
The old version is deprecated with this release but remains available alongside the new one for several months, giving you time to make the transition at your own pace. The end-of-life date for the old version will be communicated once confirmed.
What's new in the app:
- Improved search: new header search fields for ‘Document ID’, ‘Type Description’, ‘Scenario’, and ‘Correlation ID’ make it faster to find specific entries in high-volume environments.
- Richer filtering: the header now includes ‘Overall Status’ and ‘Business Partner’ filters alongside the existing ‘Document ID’ and ‘Received On’ filters.
- Built-in Analytics: a new ‘Analytics’ tab shows the volume and status of application message types — such as ‘TransportationOrderRequest’ for Freight Collaboration or ‘TrackedProcessAndEvent’ for Global Track and Trace — giving you an at-a-glance operational picture.
- Expanded exports: higher export limits reduce manual filtering and support complete dataset retrieval for audit, compliance, and operational reporting.
- Clearer error handling: when you select multiple messages for reprocessing, error messages are now displayed individually per correlation ID in a more readable format — making troubleshooting significantly easier.
Why it matters: integration logs are central to managing the health of your network connections. The new analytics capability in particular turns the app from a reactive troubleshooting tool into a proactive monitoring dashboard. Higher export limits are especially valuable for customers running high transaction volumes who need complete datasets for compliance reporting.
2027 Release Schedule Now Available
The release schedule for 2027 is now published for both SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace. Planning ahead for system maintenance windows just got easier.
SAP Business Network Freight Collaboration
Action Required: Migrate to SAP Data Privacy Integration Next Generation Service
This one requires your attention. SAP Business Network Freight Collaboration is migrating from the Personal Data Manager to the Next Generation Data Privacy Integration service ahead of schedule (now October 17, 2026), requiring shippers to subscribe to the ngdpi plan and carriers to use the new Manage Personal Data app via a dedicated URL.
For shippers:
- In your SAP Cloud Platform subaccount, subscribe to the Data Privacy Integration Next Generation service (application plan name: `ngdpi`).
- Assign the `DPI_NextGen_Information_DataPrivacy_Administrator` role collection to users responsible for personal data management.
For full documentation, refer to Personal Data Record SAP Data Privacy Integration Next Generation Service on the SAP Help Portal.
For carriers:
You can use the ‘Manage Personal Data’ app of the Data Privacy Integration Next Generation service. The app is accessible at:
https://<your-subdomain>.app.<region(eu10/us20/us30)>.ngdpi.dpp.cloud.sap.
For more information, see Personal Data Record in the SAP Help Portal.
Why it matters: Staying on the current DPI service means relying on a deprecated integration path. Migrating to ngDPI ensures continued compliance with data privacy regulations and access to the latest capabilities for managing personal data records across your network.
Planning and Subcontracting Process Enhanced
This release brings several improvements to the freight subcontracting process, spanning API and EDI capabilities.
Product ID sharing via the Consumer API:
The ‘Consumer API for Freight Subcontracting’ now supports sharing the ‘Product ID’ with the carrier. This closes an information gap that previously required manual workarounds, enabling carriers to better plan and execute shipments for products requiring specific handling.
Richer date/time fields in the Provider API:
The ‘Provider API for Freight Subcontracting’ now exposes pickup start/end date and time as well as delivery start/end date and time as new fields. This gives carriers and logistics partners a much more precise picture of the time constraints associated with each leg of a subcontracted shipment — reducing misalignments and improving execution accuracy.
Star-shaped stage sequences in outsourced planning:
Outsourced planning for freight units now supports star-shaped and reverse star-shaped stage sequences — a common freight network topology where shipments converge to a hub before being distributed, or vice versa.
Notes and instructions via EDI 204:
It is now possible to share notes and instructions with carriers via EDI 204 using a new NTE node, supporting up to 20 segments. This expands the capacity to include additional notes or instructions in shipment EDI messages, which is useful for carriers and shippers exchanging richer data in complex multi-stop payloads
Why it matters: These enhancements collectively reduce friction in the subcontracting process. More data flowing between shippers and carriers via both API and EDI means fewer manual touchpoints, less room for misinterpretation, and ultimately better on-time performance.
Improved Booking Accuracy in Dock Appointment Scheduling
The ‘Manage Dock Appointments’ and ‘Self-Book Dock Appointments’ apps now display the ‘Location Description’ alongside the ‘Loading Point ID’ in edit mode, helping you make more accurate booking selections.
The location description is shown only when a location has been assigned to the loading point and a description was available at the time of the assignment.
Why it matters: A location description sounds like a small addition, but in practice it makes a real difference when multiple dock locations or warehouse areas share similar names. Displaying the description directly in booking details gives carriers and warehouse staff the context they need to arrive at the right location — reducing delays and misrouted arrivals.
SAP Business Network Global Track and Trace
Standard Extractor Enhancements: More Data Flowing from SAP S/4HANA
Three new data points are now transferred from SAP Transportation Management in SAP S/4HANA to SAP Business Network Global Track and Trace via the standard extractor:
- Administrative audit data: ‘Created By/On’ and ‘Changed By/On’ fields are now included in the data transferred to GTT. This supports traceability and audit requirements by making it clear when a freight order or booking was created and who made changes — directly within the GTT visibility layer.
- Container details: ‘Container ID’ and ‘Container type’ can now be sent to GTT via the container table. This information can be used for visibility providers to calculate carbon emissions. By default, the feature is disabled. You can enable it manually. For more information, see Send Containers Table to the GTT System.
- Ordering party: The ‘Ordering Party’ for freight orders and bookings is now transferred to GTT. This supports more accurate downstream reporting and visibility, especially in complex multi-party logistics scenarios where the ordering party differs from the shipper.
For more information, see 3763702
Why it matters: Better data in GTT means better visibility. Audit data supports compliance; container details unlock more accurate sustainability metrics; and the ordering party field closes an attribution gap in multi-party logistics flows. These are steady improvements to data completeness that pay dividends across reporting, compliance, and operational monitoring.
Improved Shipment Visibility: EDI 214 Carrier Tracking Numbers Now Visible
Carrier tracking numbers sent by carriers via EDI 214 (L11 segment) are now automatically visible in SAP Business Network Global Track and Trace.
A new mapping was added between two data points:
- EDI side: The L11 segment with qualifier CI (Unique Consignment Identifier) — this is where carriers include their tracking number in an EDI message
- API side: The carrierDocumentReference field in the POST /OrderEvents API — this is how GTT (Global Track and Trace) receives that tracking number
Why it matters: Previously, if a carrier sent a tracking number via EDI, it would not be passed through to GTT. Now it is — meaning the tracking number travels end-to-end from the carrier's EDI message all the way into SAP Business Network Global Track and Trace, giving shippers and logistics teams better shipment visibility without needing to look up tracking numbers elsewhere.
What's Coming Next: Join Our 2611 Webcast
Already curious about what comes after 2610? We are too — and we want to share it with you directly. On Wednesday, November 18, 2026, our product and development experts will walk you through the high-impact features arriving with the 2611 release of SAP Business Network for Logistics. You'll get first-hand insight into:
- Outbound flow for e-Invoicing in SAP Business Network Freight Collaboration
- Time-based notifications in SAP Business Network Global Track and Trace
- Unified, adaptive company profile for carriers — available across both Freight Collaboration and Global Track and Trace
The session starts at 11:30 AM CET — the session will be recorded in case you cannot join at this time. Register now for the SAP Business Network for Logistics 2611 Webcast
—————————————————————————————————————————————————————————-
Where to learn more
For the complete feature list and technical details, refer to the SAP Business Network for Logistics documentation on SAP Help Portal.
As always, feel free to leave a comment below with any questions or feedback — or connect via the SAP Community.
Source link
