Basic OTM Configurations - 06 - Tender process

Note: This post is continuation to topic: Basic OTM Configurations - 01 and these configurations are specific to business scenario mentioned in that post. Link below to that post for quick reference:

Basic OTM Configurations - 01 - Domain, Items, Locations, and Equipment

https://www.oracle-otm.com/2020/08/basic-otm-configurations-01-domain.html

Tender Process

When shipments are created, note that status on these shipments is SECURE RESOURCES_NOT STARTED.

At this point, we need to notify carrier about the shipment information like pickup time and location. This can be done using:

  

Shipment > Actions > Shipment Management > Tender > Secure Resources

 

Notice that Shipment SECURE_RESOURCE status changes to 'TENDERED' 

OTM sends out tender XML to external system or email notification to carrier based on configuration at the service provider level.

Carrier should respond to the tender either via EDI or manually login into OTM app with 'Service Provider' role and accept or reject the tender.

Tender Accept/Reject Process

Assume that carriers have access to OTM application in that case they can login as:

SERVPROV.DOMAIN-SCAC format as default USER ID

CHANGEME as default password

In this scenario, we login as SGTM and PNDP carriers and accept/reject these tenders:

You can see the outstanding tenders for the carrier:

 

You can select this record and Actions > Accept/Decline. Let’s decline this PNDP carrier tender.

Accept the tender for SGTM carrier:

Now go back to TCRP.ADMIN and review the shipments.

First leg shipment PNDP carrier rejected, so OTM automatically tendered to next available carrier SGTM with $30 rate we defined.

Now we login as SERVPROV.TCRP-SGTM to see this new tender for first leg.

Accept this tender. Now we can see both the shipments are show tender as accepted.