SAP Knowledge Base Article - Preview

3842477 - Why Freight Messages Failed to Reach Carriers in SAP BN4L?

Symptom

I observed that Freight Subcontracting (TransportationOrderRequest) messages were received by SAP Business Network for Logistics but failed to reach specific carrier tenants, showing ESCALATED status with HTTP 500 errors (/v1/route and occasionally /v1/federate) starting from 01-Oct-2026.


Read more...

Environment

  • SAP Business Network for Logistics
  • Freight Request for Quotation

Product

SAP Business Network for Logistics 2.0 ; SAP Logistics Business Network 1.1

Keywords

freight subcontracting, transportationorderrequest, bn4l, http 500, internal server error, escalated, manage integration logs, v1/route, v1/federate, carrier tenant, wrong tenant, routing, tenant mismatch, reprocess, freight order , KBA , SBN-LBN-FC-RFQ , Freight Request for Quotation , SBN-LBN-FC , Freight Collaboration , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.