• Create recurring blockers from entity settings on an active loading point with daily, weekly, and monthly periods
• Change existing recurrence series
• Delete existing recurrence series

Enable shipping users to view recurring blockers using the Manage Dock Appointments app:

• Display the recurring blockers instances as blocks
• Enable deletion of individual blocks
• Enable carrier users to view updated capacity information in the time slot table using the Self-Book Dock Appointments app.

This doesn't affect the existing imported business content, you can still display them in dashboards.

• Planned Gross Duration
• Planned Net Duration

It informs you of the party who reported the event. You can click the link to view its detailed contact information in a popover.

It’s an alternative option to existing IDOC message. You can use it to send documents from the TM embedded in SAP S/4HANA to SAP Business Network Global Track and Trace for tracking. The GTT system converts the SOAP message into GTT shipment event JSON payloads, ensuring seamless downstream processing.

You must raise a ticket under SBN-LBN-INT to ensure the message can be sent to the GTT system.

You can check the message status in the Monitor Message Logs and Monitor Integration Logs apps. For more information, see Using SOAP Messages.

The following Message Implementation Guidelines have been updated:

• Message Implementation Guideline (ANSI X12 214 FC)
• Message Implementation Guideline (ANSI X12 214 GTT)

 We added the geocoordinates in the MS1 segment.

 In the Provider API for Order Events (GTT) and Provider API for   Order Events (FC), special characters such as “asterisk (*)” and “question         mark (?)” aren’t allowed in the attachment file name.

 For a complete list of unsupported characters, see SAP Business Accelerator Hub

* Geo Position Updates

* Map View

 As part of the harmonization effort, the new manage Freight execution app is   available for shippers in SAP Business Network for Freight collaboration and   carriers. It contains the tracking relevant freight documents from both solutions   so  that carriers can see all documents assigned to them for reporting. It replaces   the following apps, which have been deprecated and will be sunset as of May   16,2026.

* Tracking Freight Movement

* Freight Orders for reporting

For more information, see Tracking Harmonization. As a solution owner in SAP Business Network Global Track and Trace, you must enable manual reporting for your carriers via the event-to-action script in the GTT standard model “gttft1”. Then, your carriers can receive your shipment and report events on your shipments. For more information, see Enable Manual Reporting for Carriers

• In the Emissions table of the Shipment Details page, you can now see calculated GHG emissions if the values are provided from TM in SAP S/4HANA.

• On the header of the Shipment Details page, you can now see a comparison between the reported and calculated GHG emissions or carbon emissions

 In the Manage Gate Operations app, you can now restrict access to gate   logbooks based on the yard location ID.

 For more information, see Available Roles for Shippers and Enabling Role-Based   Access.

 In GTT models, a new attribute “Visible” is added to model fields to control their   visibility in the fulfillment tracking apps. If you tip the Visible checkbox, the   corresponding field can be displayed in the fulfillment tracking apps, otherwise,   it can’t.

 As of now, you can only manage the visibility settings for user-defined fields.

 Please ensure your requests won’t exceed these limits. Otherwise, they might be   rejected. For more information, see Rate Limiting

• Message Implementation Guideline (IFTMIN D96A)

 We enhanced the EDI mapping logic to map the notes at item level to the   FTX   field. This enhances the communication by allowing more detailed  information   to be included in freight orders and freight bookings.

 We added the business partner ID to the mapping logic so that the issuer of an   invoice (II) and the invoicee (IV) are now part of it.

 Following company-wide top level domain change for SAP-owned SaaS   applications and SAP Business Network domain naming conventions, the     domain name in the application URLs of SAP Business Network for Logistics has   been updated from the previous “cfapps.<data“logistics.<data   center>.business-network.cloud.sap”.

 It allows you to easily recognize SAP brand by the URL and seamlessly navigate   between SAP SaaS Applications without changing cookie settings.

 You will be redirected to the new URL automatically when accessing the     applications with old URLs. Remember to update your bookmark as needed.

For more information, see Shipment Details Page

• GTT_TS_EVENT_TYPES_IN_EXEC

This variable defines a list of event types that can trigger the execution status update for shipments, freight units, and tracking units. When an actual event of these event types is reported, the execution status changes from “Not Started” to “In Execution”. Previously, the status changes to “In Execution” only when a planned event is reported. This ensures that the status is consistent between GTT and external systems, such as TM in SAP S/4HANA.

You can customize this list of event types that better meet your business needs in User Script before Standard Script section.

For more information, see “In Execution” Status Customization.

 The rate limit of Read Service API is changed to the following and will take   effect as of December 13, 2025:

• For each product tenant, you can send up to 200 requests per minute.
• For each test tenant, you can send up to 60 requests per minute.

 Please ensure your requests won’t exceed these limits. Otherwise, they might be   rejected.

 Note this doesn’t impact your use of Fulfillment Tracking Apps.

 For more information, see Rate Limiting.

The following Message Implementation Guidelines have been updated:

• Message Implementation Guideline (ANSI X12 214 FC)
• Message Implementation Guideline (ANSI X12 214 GTT)

We added a field for the container ID to be used in shipment tracking.

 SAP Business Network for Logistics is switching its root Certificate Authority   to   DigiCert TLS RSA4096 Root G5 for the domain *.logistics.*.business-   network.cloud.sap to enhance security and trust. This change requires   customers to ensure their systems trust the new certificate to maintain seamless   connectivity and user access before January 14, 2026:

• B2B Connectivity: The sender systems must trust both the old root certificate (DigiCert Global Root G2) and the new root certificate (DigiCert TLS RSA4096 Root G5). Without this, the inbound communication to SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace will be impacted.
• End User UI: The browser certificate store must contain both the old root certificate (DigiCert Global Root G2) and the new root certificate (DigiCert TLS RSA4096 Root G5). Without this, the end user sign-in to SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace will be impacted. To check if you are impacted, try to access the following URL: https://digicert-tls-rsa4096-root-g5.chain-demos.digicert.com. If your browser loads the page without warning, it trusts the DigiCert TLS RSA4096 Root G5 and no further action is required on your end.

 For more information, see SAP Note 3688060 

 To enjoy the features provided by SAP Cloud Identity services, such as applying   instance-based authorization on the Manage Freight Execution app using its   Authorization Management, you must migrate the authentication from SAP   Authorization and Trust Management (XSUAA) to SAP Identity Authentication   service (IAS) at tenant level. This affects the way of sign-in to the apps on the   Fiori Launchpad for SAP Business Network Freight Collaboration.

• The Consumer API for Freight Subcontracting is enhanced to populate the following fields:

  • preferredLoadingStartDateTime
  • preferredLoadingEndDateTime
  • preferredUnloadingStartDateTime
  • preferredUnloadingEndDateTime

  We recommend using these fields in the payload instead of the following ones, which are unavailable in the API yet still supported:

  • requestedLoadingStartDateTime
  • requestedLoadingEndDateTime
  • requestedUnloadingStartDateTime
  • requestedUnloadingEndDateTime
• The priceUnitUoM within CalculationBasis now supports the following UoM code lists:

  • Length
  • Quantity
  • Temperature
  • Volume
  • Weight
  • Currency
    For more information on the codes, see Code Lists.

 The Provider API for Invoicing has been enhanced to allow ocean carriers to   submit invoices more easliy. This is especially useful when the carriers do not   execute the freight documents themselves but mandate someone else. Carriers   can now use either the master bill of lading and container ID, or the booking   reference and container ID, as alternate IDs, eliminating the need for the     shipper's internal freight booking ID.

 The Invoice Freight Documents and Freight Orders for Confirmation apps   expect one of the following document reference type codes: BREF (booking   reference), CONT (container) or T52 (master bill of lading) to identify a unique   freight document. This feature streamlines the invoicing process by utilizing   globally recognized references, ensuring accurate matching to the correct freight   document and reducing administrative burdens for carriers.

 The Provider API for Freight Subcontracting and the Consumer API for   Freight Booking have been enhanced to support the ocean tendering scenario.   You can now confirm an ocean freight booking with a price proposal.

 For more information, see:

• Provider API for Freight Subcontracting
• Consumer API for Freight Booking

 In the Manage Freight Execution app, you can apply instance-based     authorization to restrict access to freight orders. Different from the previous role-   based authorization practice, you must use Authorization Management of SAP   Cloud Identity Services to configure these instance-based authorizations   centrally as policies. After you assign policies to users, they can only view   documents that match the policy settings.

For more information, see Applying Instance-Based Authorization

 As a shipper, you can create a consignment order and subcontract it in TM in   S/4HANA. Now you can send the order to your carrier using the SOAP interface   "TransportationOrderRequest_Out".

 As a carrier, you can view 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.

  In the ordering party's external system, when a freight booking that has been   sent for confirmation to the carrier has been cancelled, the corresponding freight   booking is cancelled in the Freight Bookings for Confirmation (Ocean) app   and the Invoice Freight Documents app.

 Note that the freight booking can be cancelled only when there is no active   dispute or an invoice document corresponding to the freight booking.

 We harmonized the display of Incoterm information across the Manage Dock   Appointments, Self-Book Dock Appointments and Manage Gate   Operations apps. This ensures consistent display of Incoterm codes and   locations, enhancing clarity and usability. Users benefit from streamlined access   to location data, with expandable text for lengthy descriptions, improving   efficiency in managing appointments and operations.

  In detail, the following changes were made:

• In the Manage Dock Appointments app, the Incoterm field was added.
• In the Manage Dock Appointments app, the Incoterm Location Description field was deleted.
• In the Self-Book Dock Appointments app, the Incoterm and Incoterm Location fields were added.
• In the Manage Gate Operations app, the Incoterm field was added.

 We also enhanced the application help with further explanations.

 We made the following changes:

• In the Provider API for Dock Appointment Scheduling (GenericAppointment_In) and the Consumer API for Dock Appointment Scheduling (GenericAppointment_Out), we extended the length of the LoadingPointId field from 40 characters to 255 characters.

• In the Provider API for Dock Appointment Scheduling (GenericAppointment_In), we added the missing fields for non-stackable cargo (NonStackable) and over dimensional cargo (Oversize).

• In the Consumer API for Dock Appointment Scheduling (GenericAppointment_Out), we adjusted the following indicators:

  • HighValueIndicator was renamed as HighValue

  • StackableIndicator was renamed as NonStackable

  • OversizeIndicator was renamed as Oversize.

 This change ensures proper handling of appointment data (fields for non-   stackable, high value and over dimensional cargo) when sending and receiving   through the Provider and Consumer APIs for Dock Appointment Scheduling.

 To get the updated API definitions, you must download the WSDL file from SAP   API Business Hub.

  The Confirm Freight Bookings (Ocean) app has been enhanced to support       the ocean tendering scenario. Carriers can now confirm an ocean freight booking   with a price proposal. New fields have been added in the worklist page and the   detail view to support the ocean tendering scenario.

 Shippers can now tender their ocean freight bookings to SAP Business Network   for Logistics.

 For more information, see:

• Confirm Freight Bookings (Ocean)

This avoids time-consuming manual configuration and potential inconsistencies during account onboarding. It reduces setup time, ensures consistency across environments, minimizes human error, and allows for quick replication of proven configurations from test to production accounts.

To learn more, open the in-app help by selecting  within the Import/Export Configuration app.

To use the new app, ask your system administrator to add the following roles to your role collection:

• AdministratorConfigurationCategoriesUpdateTemplate

• AdministratorConfigurationPropertiesUpdateTemplate

• AdministratorConfigurationSharedDataUpdateTemplate

The application ID for the material traceability network includes your role name in the network plus alphanumeric characters:

• Premium: mt-premium-live or -test + <alphanumeric characters>
• Standard: mt-standard-live or -test + <alphanumeric characters>