- SAP Managed Tags:
New features and assets for SAP Business Network for Logistics have been released! With this blog, I would like to share the highlights with you. The blog is intended for shippers and solution owners, carriers, and data providers as well as sales and presales colleagues who already have a detailed understanding of SAP Business Network for Logistics.
Amongst others, there are updates in SAP Business Network Freight Collaboration on the invoice rejection scenario. So we will dive into the following question:
But let's s go through them one by one.
Cross SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace
Subscribe to release updates on SAP Help Portal
We have enabled the option for you to subscribe to the ‘What’s New’ sections for feature updates that we publish on SAP Help Portal. The release updates on Help Portal are usually published a couple of days prior to this blog series and contain a full list of newly released features. However the list does not including screenshots and additional explanations like this blog does.
If you want to receive the updates from SAP Help Portal, navigate to the ‘What’s New in SAP Business Network for Logistics' and select ‘Subscribe’.
New integration package available – SAP S/4HANA Integration with SAP Business Network for Logistics
Customers who connect to SAP Business Network for Logistics and have their own SAP Cloud Integration tenant can now use the standard integration package, 'SAP S/4HANA Integration with SAP Business Network for Logistics'.
To find this integration package, log on to your SAP Cloud Integration tenant, navigate to ‘Discover’, and search for 'SAP S/4HANA Integration with SAP Business Network for Logistics'. In the Documents tab, you can find detailed documentation on how to establish the connectivity.
You can also access the integration package in SAP Business Accelerator Hub under the following link:
A new property has been added to the Provider API for Order Events
In the Provider API for Order Events (GTT) and Provider API for Order Events (FC), the new property ‘reportedBy’ was added to the event object to specify the source of the event.
Code List Documentation
New value in Event Reason Code Descriptions code list
The Event Reason Code Descriptions code list was enhanced with the following value: INVALID_CARRIER.
The new event reason code ‘invalid carrier’ is supported in the Consumer API for Order Tracking (FC), Provider API for Order Events (FC), Consumer API for Order Tracking (GTT), and Provider API for Order Events (GTT).
SAP Business Network Freight Collaboration
Enhanced design and layout of email notifications
After changes to some notifications in 2402, now the design and layout of the following email notifications has been changed:
- Freight booking rejection notification
- Freight booking update notification
- Freight order rejection notification
- Freight order update notification
- Freight request for quotation awarded notification
- Freight request for quotation cancellation notification
- New freight request for quotation notification
- Freight quotation rejection notification
- Invoice processing failed notification
- Invoice not yet submitted notification
- Invoice processed notification for Carrier
- Invoice not yet submitted notification
- Invoice processed notification for Shipper
- Invoice ready for submission notification
- Dispute resolved by shipper notification
- Dispute resolved by carrier notification
- Dispute updated by shipper notification
- Dispute updated by carrier notification
- Request for approval notification
All emails related to dock appointment scheduling
Street prefix and suffix can now be captured and displayed across SAP Business Network Freight Collaboration apps and API
Addresses such as '5th Avenue North' can now be managed and displayed properly. In the following applications and APIs, street prefix, street suffix, additional street prefix, and additional street suffix have been added to the business partner addresses:
- Freight Requests for Quotation
- Freight Quotations
- Freight Orders for Confirmation
- Confirm Freight Bookings (Ocean)
- Confirm Freight Bookings (Air)
- Freight Orders for Reporting
- Consumer API for Freight Subcontracting
- Consumer API for Freight Tendering
- Consumer API for Freight Booking
- Provider API for Freight Booking
Settlement: New API available for carriers to cancel invoices
After the release of ‘cancel invoice with credit memo’ in the 2402 release, now the ‘Provider API for Invoice Cancellation’ is also available.
Settlement: Updates to rejection scenario
We have simplified handing of invoices that raise a dispute due to missing attachments.
When the ordering party rejects a charge item i.e. raises a dispute due to a missing attachment, carriers should now add the attachment along with a note for the disputed charge item. Since the rate amount remained unchanged, the dispute is resolved automatically, and the invoice directly goes to status ‘submitted’ for further processing by the ordering party.
SAP Business Network Global Track and Trace
Sample code for template apps has been deprecated
The template apps for version 2 have been deprecated as of March 16th, 2024. Changes include:
- The sample codes in GTT repository on Github.com are out of maintenance.
The link to sample codes of template apps is removed from the Model Overview page of the Manage Models app.
We recommend you use Fulfillment Tracking apps for your tracking services.
If you want to extend the fulfillment tracking apps, e.g. add custom fields, you may utilize the sample code for fulfillment tracking apps. You may also build custom applications from scratch v...
All Fulfillment Tracking apps: Stage-level observation may be deactivated
Let's take a deeper look into what stage-level observation is:
When a tracked process observes another tracked process at stage level, the event correlation follows the following rules:
- For actual events that can match a planned event in the observing tracked process, they can be correlated to the observing tracked process from the observed tracked process.
- For actual events that cannot match a planned event in the observing tracked process, only those of the observed stages can be correlated to the observing tracked process from the observed tracked process.
The correlation stops once the arrival event on the last stop of the observed stages is reported for the observed tracked process.
The correlated events from the observed tracked process can be displayed in the timeline or events table of the observing tracked process.
Example:
Events reported on tracking unit level BEFORE planned departure event or AFTER planned destination arrival event of the freight unit, were NOT propagated to the observing freight unit.
Now, solution owners can switch OFF the stage level observation, so all actual events on tracking unit level will be propagated to the observing tracked process (freight unit).
Stage-level observation applies to the following observation scenarios:
- Outbound Delivery observes Shipment
- Inbound Delivery observes Shipment
- Freight Unit observes Shipment
- Freight Unit observes Tracking Unit
Shipment observes Tracking Unit
You can find more details on stage-level observation here.
User Assistance – Logistic Service Providers, Carriers and Data Providers
A new set of videos on carrier integration via API has been published and can be accessed here. With the next update cycle, we also plan to bring these onto SAP Help Portal SAP Business Network Logistics Provider, basic membership, which is our central entry point for logistic service providers.
--------------------
The above summarizes the key innovations for 2403 We hope you enjoy the new capabilities. Thanks for reading the blog post and stay tuned!
A full overview of the 2403 release can be found in the following link.
To learn more about SAP Business Network for Logistics visit SAP - Business Network for Logistics.
For further questions and feedback related to the blog, please check the Q&A area and feel free to post your questions in the link with the tag SAP Business Network for Logistics.
| User | Count |
|---|---|
| 5 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
