2605 Resource: Feature Names and Descriptions Page for SAP Business Network Logistics

SAP Business Network for Logistics 2605
Release

Describes new or changed features included in the 2605 release.


	General Features - 2602 Service Pack
	Feature Name and Description
	Loading Point from TM - Additional Address to Fix Loading Point for Appointment Booking The subcontracting process was enhanced to pass the loading point ID and unloading point ID from the transportation management system (TM) to SAP Business Network for Logistics. This is done through the Location field under Additional Address at Source Location or Additional Address at Destination Location in TM, which is sent through the InternalID fields under DetailedLoadingLocation or DetailedUnloadingLocation in the ProviderAPItoCreate Freight Order for Subcontracting (TransportationOrderRequest_Out). If the internal ID matches an existing loading point ID, the system preselects and fixes this loading point. It then cannot be changed by the shipper or carrier in SAP Business Network for Logistics
	Enhanced appointment booking validation through API When an appointment booking request is received through the GenericAppointment_In API, the system now performs an advanced validation of available time blocks and capacity: Automatic Confirmation: If there is no existing time block for the requested slot and sufficient capacity is available, the system automatically confirms the booking. A confirmation message (GenericAppointment_Out) is sent with status code '03'. Clear Error Handling: If a time block already exists or if there is not enough capacity to fulfill the request, the system does not confirm the appointment. Instead, it sends a GenericAppointment_Out message with detailed error information, ensuring transparency and clarity for your scheduling process.
	New fields available for Microsoft Excel upload and download in Manage Entities app In the Manage Entities app, the following fields are now included in a Microsoft Excel upload and download: Use Derived Appointment Duration (on a loading point) Max. Capacity (on a loading point - block time) Include Overbooking (on a loading point - block time)
	Recurring Blocks In the Manage Entities app, you can now create time blocks with daily, weekly and monthly recurrence for a loading point. This enables you to block time for special occasions, such as public holidays, maintenance, or cleaning. Daily: You can, for example, create a block that occurs every third day, and blocks for all-day appointments that can span several days. Weekly: You can, for example, create a block that occurs every third month on a specific day of the week. Monthly: You can choose between the following options: Day: A specific day of the week, such as every first Monday of the month. Date: A calendar date, such as 1 for the first day of the month. When you create a new recurring block, the system checks if there are any conflicts with existing appointments or blocks. Note that you cannot import or export recurring blocks to or from Microsoft Excel.
	Blocks with maximum capacity and overbooking In the Manage Entities app, shippers can now create blocks for appointments that apply to the maximum capacity of the loading point, including overbooking. Typical use cases for this kind of blocks are public holidays or maintenance. The settings for maximum capacity and overbooking are shown for docking locations in the Manage Dock Appointments app so that you cannot book appointments during the blocked time. We also introduced capacity validations. If a new block leads to a capacity clash, the system will ask you to reduce the capacity of the block or cancel existing blocks or appointments.
	Auto-Loading of worklist items on scrolling For the worklists of the following apps, additional results now load automatically as you scroll to the bottom of the list: Freight Request for Quotation Freight Quotations Freight Orders for Confirmation Confirm Freight Bookings Confirm Freight Bookings Manage Freight Execution This eliminates the need for manual clicks to view more items,creating a smoother and more efficient browsing experience
	Generation of PDF language versions The process to download PDF versions of translated guides has changed. As of now, you need to manually create PDF language versions of the Administration Guide for Logistics Providers and Activate Your Account guides. To do so, choose PDF Create Custom PDF on the product page on SAP Help Portal.
	Cross data center connections supported The Manage Freight Execution app now also supports the cross data center connection between shippers and carriers. This means, as a shipper, after you create a freight order or report events on it, this freight order and the events are now visible in the Mange Freight Execution app for carriers on different data centers. Similarly, the events reported in the Manage Freight Execution app by these carriers are also visible in the Manage Freight Execution app for shippers and the Track Shipments app for solution owners.
	Two new filters available In the Manage Freight Execution app, you can now filter freight documents by Arrival State and Departure State. The enhancement gives you greater flexibility when searching for freight documents based on addresses.
	Generation of PDF language versions The process to download PDF versions of translated guides has changed. As of now, you need to manually create PDF language versions of the Getting Started Guide for Network Participants and Data Contributors. To do so, choose PDF Create Custom PDF on the product page on SAP Help Portal.
	Harmonization of predefined analytics content for SAP Business Network Freight Collaboration The predefined analytics content for SAP Business Network Freight Collaboration was previously available as Predefined stories in the Manage Analytic Stories app for use with embedded analytics. Business contents that can be imported into your SAP Analytics Cloud tenant. To reduce duplication between the two, as of November 15, 2025, the business content was already deprecated and you can't import them into SAP Analytics Cloud. With this release, you can’t even display the imported business content in SAP Analytics Cloud dashboards. Instead, you can use story dashboards within intelligent insights that integrates embedded analytics toolsets for data analysis. The following guides are updated accordingly: Administration Guide Application Help


	General Features - 2603 Service Pack
	Feature Name and Description
	New field In the Consumer API for Freight Subcontracting, the following new field is added to the item's dangerous goods text collection node - dangerous GoodsText: typeCode: it indicates the dangerous goods text type.
	Additional Driver Phone Number added to the UI of several apps A new field for the Additional Driver Phone Number was added under the Driver Details in the Self-Book Dock Appointments, Manage Dock Appointments, and Manage Gate Operations apps. The driver and additional driver information is replicated from the Freight Orders for Confirmation app to the Dock Appointment Scheduling apps, if available
	Display History Additionally toggle renamed Display History Additionally toggle was renamed as View History in the Self-Book Dock Appointments and Manage Entities apps.
	Integration with SAP Logistics Management SAP Business Network Freight Collaboration now supports SAP Logistics Management as your backend system for logistics planning. It offers out-of-the- box connectivity to shippers with SAP Logistics Management. As a shipper, you can send freight requests for quotation and consignment orders from SAP Logistics Management to SAP Business Network Freight Collaboration for tendering and subcontracting respectively. As a carrier, you can process requests for quotation in the Freight Requests for Quotations app. After your quotation is accepted, moving forward, you can see consignment orders sent to you for confirmation in the Freight Orders for Confirmation app. You can confirm and reject them as you process other normal freight orders.
	EDI documentation (EDIFACT) The following document was updated: Message Implementation Guideline (IFTMIN D96A) The dangerous goods text type mapping to EDI format was enhanced with two new text types: DEL and SPH. The default code for any customized dangerous goods text type in SAP S/4HANA is mapped to DEL, which may differ from the dangerous goods name AAD. The mapping now distinguishes between dangerous goods names and special information, enabling carriers to accurately identify different text types in EDIFACT IFTMIN transmissions. This prevents confusion when multiple dangerous goods text elements use the same code, improving data clarity for carrier systems.
	EDI Documentation (ANSI) The following guide was updated: How to Integrate with SAP Business Network Freight Collaboration (ANSI X12) We added information about new Message Implementation Guidelines (MIGs).
	EDI Documentation (ANSI) The following Message Implementation Guidelines (MIGs) are now available: Message Implementation Guideline (ANSI X12 303), used for Booking Cancellation (Ocean) Message Implementation Guideline (ANSI X12 310), used for Freight Receipt and Invoice (Ocean) Message Implementation Guideline (ANSI X12 315), used for Status Details (Ocean)
	New event types and event reason code In the Consumer API for Order Tracking (GTT) and Consumer API for Order Tracking (FC), Provide API for Order Events (GTT) and Provide API for Order Events (FC), the following enhancements are made: Three new event types are supported: CHECK_IN (Check-In) SUB_VEHICLE_READY (Subsequent Vehicle Ready) GATEIN_HOLD (Gate Check-In on Hold) In the Track Shipments app, you can view events of these types in the tracking timeline and Events table if they are planned or reported. These events can't be synchronized back to TM in SAP S/4HANA. In the Manage Freight Execution app, you can also report these events of these types. The following new event reason code is supported: BAD_ORDER (Bad Order)
	Standard Point Location Code (SPLC) supported as an alternative location ID The Standard Point Location Code (SPLC) is now supported as an alternative location ID that can help identify a location. In the Manage Locations app, you can maintain it as an alternative location ID when creating a location. For more information, see Creating a Location.
	Migration of authentication from XSUAA to IAS SAP Cloud Identity services are SAP's strategic solution for enterprise-grade identity and access management in customers' SAP cloud landscapes. It includes the Identity Authentication service (IAS). To consume new capabilities such as Joule, SAP's generative AI copilot, you, as an existing customer, must migrate the authentication from the previous SAP Authorization and Trust Management (XSUAA) to IAS. For more information on how to migrate, see Migration of Authentication from XSUAA to IAS. For new customers who onboard after 2603 release, the new IAS authentication will be enabled automatically during the onboarding process. Thus, you don't have to do the migration. For more information, see Establish Trust Between Your Subaccount and Identity Authentication Tenant.
	Rail tracking The following enhancements are made to support the rail tracking: In the Provide API for Order Events (GTT), the object trackedObject now supports a new resource type - RAILCAR_ID. In the Track Shipments apps, you can view the railcar ID of a shipment in the Tracked Objects table and the Tracking Units table. In the code list documentation, the code list Tracked Object Type is enhanced to include this new type. In the Provide API for Order Events (GTT), the Location object now supports another new location field - SPLC. It helps identify where the event occurs during the rail tracking. The system uses this location code to retrieve the related location information from the master data. In the Track Shipments app, you can view SPLC in the Events table and Event Details page.
	Container item tracking The standard extractor is enhanced to support shipment tracking based on container item. In such scenario, container ID is maintained within the individual container item on freight booking, instead of as a separate business document, like container unit. Tracking units are generated per container item and sent to the logistics service provider for tracking. When events are reported on this tracking unit, they will be reflected in the corresponding freight unit and freight booking. For more information on the configuration, see Scenario 5: Generate Tracking Units based on Container Item in How to Send Documents from SAP S/4HANA to SAP Business Network Global Track and Trace.
	Onboarding guide changes To improve the user experience and readability, the onboarding guide has been refined with the following enhancements: The following onboarding scenario no longer applies with the new IAS authentication enablement and thus removed: Scenario 2: Test/SI Tenant Onboarding Using SAP ID Service The following onboarding scenario is merged with the productive onboarding and thus removed as well: Scenario 3: Test/SI Tenant Onboarding Using Identity Authentication
	EDI Documentation (ANSI) The following guide was updated: How to Integrate with SAP Business Network Global Track and Trace (ANSI X12) We added information about the new Message Implementation Guideline (ANSI X12 315)
	EDI Documentation (ANSI) The following Message Implementation Guideline (MIG) is now available: Message Implementation Guideline (ANSI X12 315), used for Status Details (Ocean)
	New connection type In the System Connections app, the following connection type is now available: Material Traceability API. This new authentication method supports client ID and secret credentials instead of certificates. This provides buyers and suppliers with a simpler alternative to certificate-based authentication when setting up inbound connections.


	General Features - 2604 Service Pack
	Feature Name and Description
	New roles for use in role collections (optional) The following roles are now available: ManageDockAppointmentsDisplayTemplate: This role enables the user to open the Manage Dock Appointments app and view appointments. ManageDockAppointmentsProcessTemplate: This role enables the user to open the Manage Dock Appointments app and edit appointments. ManageGateOperationsDisplayTemplate: This role enables the user to open the Manage Gate Operations app and view the gate logbook details. ManageGateOperationsProcessTemplate: This role enables the user to open the Manage Gate Operations app and edit the gate logbook details. These roles are offered as an alternative to the following existing roles: ManageAppointmentDisplayTemplate ManageAppointmentProcessTemplate GateLogBookDisplayTemplate GateLogBookProcessTemplate The existing roles also enable the user to open other apps and edit the details. You can continue to use the existing roles. However, if you want to grant users only the minimum level of authorization needed for the Manage Dock Appointments and Manage Gate Operations apps, you can switch to the new roles.
	Driver fields renamed In the Freight Orders for Confirmation app, the Primary Driver was renamed as Driver, and the Secondary Driver was renamed as Additional Driver, to harmonize the field names across our apps.
	New fields for truck ID and trailer ID You can now separately capture truck IDs, trailer IDs, and license plates needed for logistics operations. This feature enables the documentation of truck units by distinguishing between the truck and the trailer, eliminating manual gate entry and reducing operational friction for carriers and guest users. When you enter the truck ID and trailer ID in the Freight Orders for Confirmation app, these data are sent to the Dock Appointment Scheduling apps provided that no edits have already been made in these apps. To enable this feature, we made the following changes in the Freight Orders for Confirmation, Self-Book Dock Appointments, Manage Dock Appointments, and Manage Gate Operations apps: New Resource Details section to display the Truck ID and Trailer ID. The License Plate / Country or Region of Registration field was moved from the Driver Details to the Resource Details. We also enhanced our Consumer API for Dock Appointment Scheduling (GenericAppointment_Out) and the Consumer API to Manage Gate Operations (GenericGateProcess_Out) with the new fields.
	Communication of Gate Check-In on Hold status The Manage Gate Operations app now sends the Gate Check-In on Hold status to the Manage Freight Execution app to communicate when trucks are prevented from completing gate check-in. This provides shippers with complete visibility into shipment execution status and delays caused by documentation, scheduling, operational, or compliance holds at the gate.
	EDI Documentation (EDIFACT) We enhanced the mapping of product item descriptions in EDIFACT IFTMIN documents. This feature enables product item descriptions at the top level to be mapped to FTX segments, supporting transportation orders with standalone products not contained within packages or containers.
	Establishing a connection between logistics providers and test shippers You can now establish a connection between logistics providers (carriers and data contributors that followed the new onboarding process as of release 2405) and a test shipper to enable self-service testing without requiring shipper involvement for each integration test. This feature reduces the workload on shippers.
	SPLC supported for exporting In the Manage Locations app, when exporting locations from the worklist, the column - SPLC is now available in the spreadsheet.
	SPLC added in location popovers In fulfillment tracking apps, you can view SPLC in location popovers as well if it's available.
	Visibility control of standard model fields in fulfillment tracking apps In the standard model gttft1 of the Manage Models app, you can control the visibility of the standard model fields of tracked process in fulfillment tracking apps. If you don't check the Visible checkbox, the corresponding standard model field is hidden in the following UI interfaces of fulfillment tracking apps: Filter and the worklist settings Information tab of the detail pages
	Forwarding events back to TM in SAP S/4HANA enhanced The standard logic for forwarding actual events to TM embedded in SAP S/4HANA is enhanced. For planned events, only the last correlated actual event is now forwarded back. This optimization ensures data consistency between TM and SAP Business Network Global Track and Trace and reduces unnecessary data transmission.
	Searching shipments based on their tracking unit's Carrier Reference Document ID On the worklist page, you can now search for shipments based on carrier reference document IDs from the tracking unit-level. This means that a shipment can also be returned in results when only its tracking unit's carrier reference document ID matches the defined condition.
	User-defined tables added in the Tracking Unit Details page with Adapt UI On the Tracking Units Details page, you can now add user-defined tables (if they are available) under the Information tab with the Adapt UI function. This allows you to provide additional information. For more information, see Adapting the UI.

This information reflects the status of SAP Business Network planning as of May 2026 and the features discussed are subject to change at any time without notice. SAP assumes no responsibility for errors or omissions and nothing in this web page should be construed to represent any commitment by SAP to include any specific new features in any version of the SAP solutions.