...
For Syensqo, it has been decided by the business to use SAP Business Network for Logistics (BN4L) as the global carrier collaboration platform. The
The exception to this is road carrier operations in the US and Canada, which continue to use TMS4S for all GBUs except composites.
BN4L Freight Collaboration — In-Scope Functionalities
...
As-Is Landscape
- Transwide serves as the Carrier Collaboration tool, but only for Road Transport in EU Only
- No direct integration between Project44 and Transwide
- BluJay (External TMS) and CASS (Audit & Invoicing) with US & Canada coverage for all modesUse of multiple middleware for integrationRoad mode
- Integration with Transwide and P44 via WebMethods and SAP PI respectively
New Landscape
| draw.io Diagram | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Key Points
- BN4L will serve as the global carrier collaboration tool across all modes of transport worldwide, fully replacing Transwide
- Project44 (Europe) replaced by BN4L with Global Coverage for all Modes
BluJay upgraded to TMS4S with limited scope for Road in US & Canada
BN4L to cover Carrier Collaboration for Ocean & Air in the USA and Canada, and cover all modes globally which is not currently not integrated with any collaboration tool
Middleware harmonization from four middlewares to One middleware (CPI)
Direct Integration between BN4L and P44- P44) will integrate directly with BN4L. No direct connection between P44 and S4 HANA (P44 is only applicable for FCL Ocean Port to Port
Scenario) - TMS4S will replace BluJay and will be used for Road mode only in US & Canada for all SPP and P&C GBUs — Composites are excluded from TMS4S scope
- BN4L integration with S/4HANA :
- For Outbound from S4HANA - direct connections between S/4HANA and BN4L .
- For Inbound to S4HANA - SAP Integration Suite (API Management Component) will be used for routing.
| Info | ||
|---|---|---|
| ||
| In Syway, middleware used in interfaces with other tools - i.e. TMS4S, CASS, Ovinto, Selfy and Simba - will be consolidated to SAP Integration Suite. |
Technical Integration Diagram
| draw.io Diagram | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
BN4L Integration Interfaces
The table below describes all integration interfaces for BN4L in scope, organized by functional area. Each interface includes the corresponding message type, a description of its function, and whether it is a Provider API (inbound to BN4L) or Consumer API (outbound from BN4L).
...
Services Requiring Custom Implementation in S/4HANA
As per Syensqo requirement . the appointment dates has to be updated back to the freight order /freight booking . This will be updated back to the Outbound Delivery Order in EWM for the warehouse activities .
| Functional Area: Dock Appointment Scheduling | |||
|---|---|---|---|
Provider or Consumer | Interface | Message Type | Description |
|
|
|
|
|
|
|
|
|
|
|
|
Provider in S4HANA | Dock Appointment Scheduling | ZGenericAppointment_In | This is a custom interface to be created with the structure same as GenericAppointment_Out to get appointment details from BN4L to S4HANA to update the freight documents |
SAP BN4L GTT Provider Services - REST
...