Status

OwnerVAN OS-ext, Nico 
StakeholdersNajaite Nidboufker

Issue

For Road Freight order placement, tendering, track and trace and carrier settlement regions utilise the following TMS solutions:

  • EMEA - Transwide
  • NAM - BlueJay
  • LAM - n/a
  • APAC - n/a

For these functions SAP offers a cloud based solution: SAP Business Network for Logistics (BNL).

This document is to provide more information on the SAP BNL solution. BNL could be considered to replace Transwide and possibly BluJay for Road Freight.
As LAM and APAC is currently not using a TMS solution, BNL could be utilised in these regions.



Recommendation

As BNL is THE solution for SAP to integrate with trucking companies, it makes sense for Syensqo to include it in the To-Be landscape.

As the functionality of BNL is overlapping with Transwide, then this system will be retired.

For North America the decision is solely based on the decision what is going to happen with BluJay (KDD). If BluJay stays operational, then it makes sense to integrate with BluJay.


Background & Context

Overview of SAP TM with BNL

To be be able to assess if SAP TM with integration to BNL is a fitting solution for Syensqo, an understanding of the SAP TM processes is essential. In this section a more detailed explanation is provided how the process works in this system configuration.

System Landscape

SAP Business Network for Logistics is SAP's new collaborative cloud network that empowers logistics businesses to work together. There are two submodules within BNL:

SAP Business Network Freight Collaboration improves supply chain efficiency by connecting business partners on a collaborative network that supports jointly managing transactions, exchanging documents, and sharing insights across the value chain. For instance, upon invitation from a shipper, a carrier can onboard onto the network and collaborate with shippers on freight tendering, subcontracting, freight settlement and dock appointment scheduling.

The aim of SAP Business Network Global Track and Trace is to capture, process and store tracking information about tracked business processes. Then, it allows business users to get real-time transparency of the execution of those processes. They can query any tracked process and display its retrieved data from end to end.

Following image provides a simplified view of the system landscape:

Process Flow

The functionality of this setup will be explained by the following process steps:


Transportation Planning

During Transportation Planning, Freight Orders (Road and Rail) or Freight Bookings (Air and Ocean) are created. These transportation orders are the starting point for integration to BNL and communication with carriers. There are multiple ways how these transportation orders are created:

  1. Manual Planning in the Transportation Cockpit.
  2. Manual creation from the Freight Unit or Container Unit.
  3. Short cut planning where a Freight Order is created directly from delivery.
  4. Automated planning.


Tendering

 SAP TM supports peer-to-peer tendering, broadcast tendering or a combination of the two.

Peer-to-Peer Tendering initiates the tendering process with one or more carriers sequentially. This means that the system will wait for a (negative) response from the first carrier before contacting the second (or third and so on) carrier.

Broadcast Tendering is executed in which several carriers are contacted simultaneously. With a 'best offer' mechanism the carrier is selected that quoted the best price within a pre-defined timeframe. With a 'first acceptable offer' mechanism the carrier is selected that has the fastest response with a quote below a specific price limit (price limits can be communicated or can be hidden from carrier).

With a combination of the two tendering approaches, the most likely process is that first a peer-to-peer tendering step is completed. If these carriers are not accepting the orders, then a broadcast tender can be performed to a selected group of carriers.

The tendering approach is defined in a Tendering Profile. This tendering profile can be selected by the user in the Freight Order, or it can be automatically selected by the system.

Example of Tendering Profile:

Monitoring tendering status with response of carriers in Freight Order:

Example of Request for Quotation that is send to carrier for response:


Dock Appointment Scheduling

As a shipper, you can use dock appointment scheduling functionality in SAP Business Network Freight Collaboration to book dock appointments for a loading point on behalf of the carrier for loading or unloading services in the docking locations of your organization.

Key features:

  • Enable collaboration on dock appointments and gate-in and gate-out processes
    Starting from planning and scheduling of dock appointments to check-in and check-out at the gates as
    well as loading and unloading.

  • Share responsibilities between shipper and (external) warehouse / yard operators
    Share master data as well as operational data instantly across the involved parties.

  • Integrate into logistics backend systems for seamless processes
    Open APIs available for integration into SAP Logistics suite and 3rd party systems. Standard integration
    available for SAP Yard Logistics.

  • Manage dock appointments centrally
    Configure master data and share with business partners e.g. on appointment creation, define docking
    locations and loading points.
    Leverage calendar view and color coding to keep track of dock appointment status.

  • Manage gate processing centrally
    Maintain gate master data related to docking locations and docking points.
    View dock appointments and access worklists to assign gates, perform check-in, add notes and
    attachments.

 


Transportation Execution

Transportation execution comprises all activities involved with handling and documenting shipments in transit. It is more than just tracking a vehicle on the road, and includes recording any changes to the planned transport and handovers to other business partners or entities.

With the SAP Business Network Global Track and Trace solution, you can seize each moment by connecting the physical movement of orders and goods with the flow of information – providing situational awareness beyond milestone reporting

Key features:

  • Track your order fulfillment progress and goods in-transit
    Monitor shipments standalone (Freight Orders and Freight Bookings) or as part of the end-to-end order fulfillment (Sales Orders and Purchase Orders) for maximum insight with milestone monitoring and exception management

  • Understand the impact of deviations from the plan
    Conduct impact analysis and view the document flow. Benefit from event correlation between orders, deliveries, shipments and external identifiers

  • Inform stakeholders of progress and exceptions
    Set up exception and information notifications, such as an email with tracking link upon order confirmation, and notify stakeholders when an exception occurs

  • Enrich milestones monitoring by real-time visibility
    Perform geolocation tracking with predictive expected time of arrival across multiple modes of transport, integrated out-of-the-box with visibility vendors for parcel, road, ocean and air

  • Ease transacting with your logistics service providers
    Receive milestone updates via API or EDI (ANSI X12)

  • Flexible and extensible setup, supported by standard apps & templates
    Supports customer-defined fields, event types and event-to-action scripts. Or build custom scenarios from scratch

  • Integrate with your ERP and logistics systems for seamless transparency
    Standard / extractor-based integration via Idocs. Provide insights to end users in their preferred working environment



Dispute Management

A freight settlement dispute case is an individual business document that captures differences in logistics item quantities or charge amounts in a freight order or carrier invoice. As a requester of transportation services, such as a shipper, you own the information in the freight order. Your provider of transportation services, such as your carrier, checks the accuracy of the charge and logistics details in your freight order.

In the self-billing process, the service provider uses the SAP Business Network for Logistics to create a dispute case against a freight order.

In the invoice submission process, the process of settlement between you and your service provider is based on an invoice that your service provider submits to you for a freight order. Your service provider can use the SAP BNL portal to submit such an invoice. For example, your service provider can submit an invoice that contains changes to logistics details such as gross weight or gross volume, or changes to charge details such as rate or an additional charge line for an unplanned charge. In these situations, the system captures the changes in a dispute case and links the dispute case to the invoice your service provider submits.

If the dispute case fails the tolerance limits you specify in Customising, you must manually review the dispute case on the Freight Settlement Dispute Cases app.


Self-Billing / Carrier Invoicing

Depending on your system integration with SAP Business Network for Logistics, carriers can submit their invoices based on self-billing process or upload their freight-order based invoices to your system.

Self-Billing

Once the Freight Order is sent to the carrier, a new document is created within the "Invoice Freight Document" app, marked with the status "To Be Invoiced." Subsequently, the carrier user can generate an invoice for this document by utilizing the "Create Invoice" button within the app. This action triggers the creation of an invoice document in the "Manage Invoice" app, labelled with the status "Draft," concurrently adjusting the Freight Order status to "Invoicing in Progress." As the carrier submits the invoice, the document status transforms to "Submitted," while the Freight Order status evolves to "Awaiting Ordering Party Response."

At this juncture, the system initiates the transmission of the invoice to the Transportation Management (TM) system. Upon successful creation of the invoice in TM, the carrier invoicing status undergoes an update within the Freight Order, subsequently relayed to BNL. This transition culminates in setting the Freight Order status to "Completely Invoiced," marking the successful completion of the invoicing process.

Carrier Invoicing

Carrier can create an invoice for freight orders using the Provider API for Invoicing. Additionally, users can view the freight order for invoicing in the Invoice Freight Documents app in SAP BNL. If there is any mismatch in the charges, the system creates a dispute either in the ordering party’s SAP Business Network for Logistics ordering party tenant or the external transportation system depending on the settings.

 


Carrier On-Boarding to SAP Business Network for Logistics

The Invite Business Partners app is designed for managing all the business partners that you want to be part of your network. You can use this app to select and invite business partners to join your business network and check their participation status.

Carriers can choose to use BNL from the launchpad (online), or they can set up integration using the following API's (EDI is also available):

  • Provider and consumer API for Freight Tendering to accept or reject a freight request for quotation.
  • Provider and consumer API for Freight Subcontracting to integrate freight order subcontracting.
  • Provider and consumer API for Freight Booking to integrate freight booking subcontracting.
  • Provider and consumer API for Order Events or Order Tracking to post events.
  • Provider API to create an invoice



Alternative 1: SAP TM integrated with Transwide

Transwide is the current TMS solution used in Europe and a few countries outside of Europe. The features used in from Transwide are:

  • Tendering
  • Carrier Determination
  • Slot Scheduling
  • Status Tracking
  • Exception Management
  • Additional Cost and Settlement

Transwide is currently only used for road transportation, but can be extended to other modes of transport.

Transwide is owned by Alpega and the solution has been renamed to Alpega TMS. Alpega TM is a combination of Inet and Transwide.


When integrating with Transwide, the integration objects will be Freight Order and Freight Booking. Once these documents are created, they are interfaced to Transwide for further processing.

For track and trace functions the design will follow similar design as with BNL, where Project 44 is integrated with Transwide and Syensqo internal systems also send updates to Transwide where required. From Transwide the updates are propagated to SAP system.

*Note: decision for North America for replacement of old BluJay is not taken into account in this KDD. Next to Transwide new BluJay could be part of system landscape.


Alternative 2: SAP TM integrated with BluJay deployed internationally

BluJay is the current TMS solution used in North America. BluJay is a complete, integrated software solution that manages the entire logistics operation from front to back, handling multiple languages, currencies, and time zones. It allows shippers to manage all multimodal transportation activities for one shipment. BluJay is used by most GBU's in North America region.

Features:

  • Contracts & tariffs management
  • Load optimisation
  • Mode and carrier determination
  • Electronic booking
  • Freight cost calculation (planned & unplanned costs)
  • Collaborative status tracking
  • Transport reporting (carrier compliance, freight costs, KPIs…)
  • Freight audit
  • Freight payment


More detail on BluJay and BluJay replacement is provided in KDD048 - Way Forward with BluJay.

Part of this KDD is to consider new BluJay version to be deployed globally. In that case Transwide would be replaced and all Freight Orders and Freight Bookings are integrated with new BluJay version.








SAP Business Network for Logistics is SAP's new collaborative cloud network that empowers logistics businesses to work together more easily than ever before. It consists of the solutions and add-ons below. SAP Business Network for Logistics is a cloud-service solution based on SAP Business Technology Platform.

SAP Business Network Freight Collaboration

SAP Business Network Freight Collaboration improves supply chain efficiency by connecting business partners on a collaborative network that supports jointly managing transactions, exchanging documents, and sharing insights across the value chain. For instance, upon invitation from a shipper, a carrier can onboard onto the network and collaborate with shippers on freight tendering, subcontracting, freight settlement, milestone reporting and dock appointment scheduling.

SAP Business Network Global Track and Trace

The aim of SAP Business Network Global Track and Trace is to capture, process and store tracking information about tracked business processes. Then, it allows business users to get real-time transparency of the execution of those processes. They can query any tracked process and display its retrieved data from end to end.

SAP Business Network Logistics Provider

SAP Business Network for Logistics is a cloud-based suite of solutions specifically built to connect logistics business partners to collaborate across companies and jointly manage transactions, exchange documents, and share insights. This page is the central entry point for carriers and data contributors into SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace to find all relevant assets regarding activation, integration and operation of SAP Business Network for Logistics.

SAP Business Network Material Traceability

SAP Business Network Material Traceability improves transparency, visibility, sustainability, and efficiency by connecting the entire supply chain. It is augmented by blockchain technology.

SAP Business Network, Intelligent Insights Add-On

SAP Business Network, intelligent insights add-on is a highly-customizable data visualization and reporting platform that presents real-time insights on your supply chain execution.

SAP Business Network, project44 Add-Ons

With the add-ons for project44 visibility services, SAP Business Network for Logistics users can benefit from the availability of actual shipment execution insights, such as shipment location and event status updates for full truckload, air and ocean shipments, as well as real-time milestone status for less than truckload shipments.


Assumptions

Selfy FDTMS and Mobile Apps can be integrated with Transwide or BluJay.

Integration from TW and BluJay to SAP TM.

Constraints

SAP Inputs that are required

Some information is available online, but SAP might be better able to give more insight into the following points.

  • Is there a way to determine which Syensqo carriers are currently using BNL?
  • How does BNL integrate back to TM directly, or should Event Management be included?

Capture any additional constraints that the chosen alternative (i.e. the decision made) might impose on other parts of the overall design, solution, or processes.


Impacts

  • Infrastructure: Integration with cloud based BNL needs to be set up.
  • Project scope: Account for about 30 days of consulting to set up basic BNL integration.


Business Rules

n/a

Options considered

Options

Pros and Cons

Comments

Option 1

Exclude BNL from project scope. SAP TM will be integrated with Transwide and BuJay.

(plus) This will limit project scope

(plus) Users will keep using their current system

(minus) No deployment of TMS functions in LAM and APAC.

  • Integration will be built from Freight Order to Transwide and BluJay.
  • Orders can be placed with truckers using Transport Order Forms and emails.
  • No integration on track and trace.

Option 2

Include BNL as project scope for LAM and APAC. Integrate with Transwide and BluJay.

(plus) Option for integrated network for LAM and APAC.

(plus) Flexibility for regions on how to organise their transport.

(minus) Multiple systems that have similar functions.


Option 3

Replace Transwide and deploy BNL to LAM and APAC. Integrate with BluJay.

(plus) Transwide can be retired

(plus) Option for integrated network for LAM and APAC.

(plus) NAM can keep using BluJay, which they are familiar with.

(minus) Dual solution.


Option 4

Global rollout of BNL and replace Transwide and BluJay for road freight.

(plus) Transwide can be retired

(plus) Option for integrated network for LAM and APAC.

(minus) Higher scope and project risk for successful deployment.

(minus) Can BNL be a good enough replacement for BluJay?

(minus) Other modes of transport might keep the integration with BluJay necessary.


Evaluation

n/a

Change log

Version 

Date

Author

Change log

0.1

13 Jun 24

Nico van Os

Initial version









Workflow history