FAQ

1. What is the trigger for sending the message "Consumer API for Freight Tendering" via API?

Whenever LBN receives an RFQ from Shipper SAP TM system and if APIs are configured, we will send it out immediately. Shippers can configure the point at which they would trigger.

2. Does every Carrier/Forwarder must have an account on LBN to receive offers from the Shipper?

Yes. Shipper identify the carrier based on the LBNID issued

3. Can a shipper have multiple LBN IDs - say if a shipper has multiple SAP TMS systems associated with him, does such a shipper also have multiple SAP LBN IDs?

 In most cases shipper will have one LBN ID. However, if shippers want to segregrate their business based on Legal entity, geography, etc. they might setup multiple LBNID. IN such cases, we should consider them as a separate entity. 

4. For creationDateTimeUTC, timezone will be only UTC or will we have to apply an offset?

Only UTC. No offset

5. Would SAP be sending trackID ?

No. Carrier / Partner can generate a trackID and send to LBN. In subsequent update or delete calls, the trackID will be sent by LBN

6. While calling LBN OrderEvents endpoints, should the locationType be passed ?

LocationType field is optional. If an event has to be reported based on the a planned stop, only the stopId is sufficient. If the event has to be reported for a unplanned stop, locationType is optional. This will provide customers additional information.

7. What is SAP LBN IP range used for outbound calls?

IP range 155.56.128.0/17, port 443 (SSL) must be whitelisted for communication with SAP LBN