Transportation Management

Get Involved. Join the Conversation.

Comments

  • Zomi Fathi

    Hi,

    Can you please give an example of what you are trying to do, is it the manual/UI initiated  upload of the xml that you want error checking on?

    thanks

     

  • Zomi Fathi

    Hi,

    there is an existing RBI that uses OR ref num values as input.  Can this be used instead of flex fields?

  • Karl Baker

    Vivek,

    Can you provide an example of this rating setup?   

  • Karl Baker

    Amiresi,

    OTM does support the generation of multiple invoices for a shipment - but the current split rule criteria can only support the following criteria:

    • Per Shipment Cost Lines
    • Per Shipment Cost Type
    • Per Shipment Cost Accessorial

    I can not think of a way to use the existing functionality to support the business division and weight allocation method you require. 

     

    Below is the Help topic that covers the current Split Rule Criteria and capabilities.

    Split Rule Criteria

     Related Topics

    This page is accessed via Financials > Power Data > General > Split Rule > Split Rule Criteria field.

    Before an invoice or bill is created, OTM verifies if there is a split rule defined for that process. Using the split rule, OTM generates single or multiple invoices/bills which are based on the split rule criteria. The split rule criteria can be any of the following:

    • Per Shipment Cost Lines
    • Per Shipment Cost Type
    • Per Shipment Cost Accessorial

    Example

    Let's look at an example where a shipment is defined with cost as shown in the below table:

    S.No

    Cost Type

    Shipment Cost

    Accessorial Code

    Special Service Code

    1

    Base

    US$ 5000

     

     

    2

    Accessorial

    US$ 500

    UNLOADING

    UNLOADING

    3

    Accessorial

    US$ 300

    PACKING

    PACKING

    4

    Accessorial

    US$ 400

    LOADING

    LOADING

    5

    Accessorial

    US$ 700

     

     

    6

    Accessorial

    US$ 100

     

     

    7

    Accessorial

    US$ 200

    HANDLING

     

     

    OTM uses the split invoice criteria to split the invoices.

    Per Shipment Cost Lines

    If you select 'Per Shipment Cost Lines,' then OTM generates one invoice for each cost line. From the above example, you see that there are seven cost lines defined in a shipment. OTM will generate seven invoices, one invoice for each cost line (one invoice is for base cost line and other six are for accessorial cost lines).

    Per Shipment Cost Type

    If you select 'Per Shipment Cost Type', then OTM splits the invoice based on the cost types defined for the shipment.

    The valid shipment cost types are:

    • Accessorial
    • Base Cost
    • Circuitry
    • Delta
    • Discount
    • Stop-off
    • Other

    Based on the above example, OTM generates one invoice for each cost type. There are seven cost lines defined for that shipment but only two distinct cost types, so OTM will create two invoices in this case (one for base cost and one for all accessorial costs).

    Per Shipment Cost Accessorial

    If you select 'Per Shipment Cost Accessorial' then OTM generates a separate invoice or bill for each distinct accessorial cost and then generates an additional invoice or bill which contains all other costs such as Base cost, Circuitry, Delta, Discount, Stop-off, and Other.

    Based on the above table, the following details explain how OTM generates invoices when you select the per accessorial cost split rule criteria:

    • One invoice for each distinct accessorial cost with accessorial code and special service code: In the above table, there are three accessorial costs with an accessorial code and a special service code. So OTM will generate three invoices for these accessorial costs.
    • One invoice for distinct accessorial cost with an accessorial code but without a special service code: In the above table, there is one accessorial cost with an accessorial code but no special service code. So OTM will generate one invoice.
    • One invoice for all accessorial costs without an accessorial code: In the above table, there are two accessorial costs without an accessorial code or special service code. So OTM will generate one invoice for both the accessorial costs.
    • One invoice for all other costs: In the above table, there is one cost other than accessorial. So OTM will generate one invoice for this base cost.

     

     

  • Karl Baker

    Very interesting - I've read several articles from large LSPs (Logistics Servicer Providers) looking to incorporate Chatbots as the starting point for many of their customer service inquiries.  Most of the use cases/flows have the Chatbot handling the high volume basic inquiries (where is my order/shipment etc) with the option to punch out to a real person/Customer Service Rep (CSR) if the inquiry is more complex/involved than what the Chatbot has been designed to support. 

    For example:

    Chat Bots – DHL is looking into using autonomous customer service representatives by using deep learning-based natural language processing (NLP) technology, such as Amazon‘s Alexa, to automate some of the easier interactions between customers and DHL’s customer service representatives.

    “Automating some of the low-level queries with chat bots can really increase the value of each interaction between customer and [human] agents by letting them focus on more high-level queries,” Gesing says. “That basically increases our throughput by a multiplier, not just a marginal increase.”

    I can see a lot of possibilities for front ending the Oracle Global Trade and Transportation system with a Chatbot. 

     

     

  • Daniel Schoerner

    We have seen a number of customers deploy both to great benefit. Scoular, GE Power, Panasonic Avionics and more have presented at various public conferences on how they use OTM+GTM for customs filing processes such as the AES filing in the United States. Much of the transportation data is critical to making a clean customs declaration and the combined platform provides robust data management with a complete picture of the information needed to manage either an inbound or outbound shipment. 

    I highly encourage you to check out attending one of the following to learn more about OTM and GTM:

    - OTM SIG held in August in Philadelphia with other conferences held globally throughout the year

    - Oracle OpenWorld in San Francisco

    - Modern Supply Chain Experience in San Jose

  • Karl Baker

    Dan,

    I found your blog/news article very interesting.  Are there any client case studies demonstrating the value proposition of Oracle's Global Trade and Transportation Platform? 

  • Karl Baker

    For your locations with the full layer requirement, go to the Location Role Profile and add or edit the Location Transport Handling Unit Capacity entry for the THU you want to ship in full layers for.  Items that you might want to configure on the Location Transport Handling Unit Capacity:

    • First - to invoke this capability you will need to select the check box on your Location's Location Transport Handling Unit Capacity entry for all the THUs where you want the Fully Layered logic to apply. The Fully Layered capability is unchecked/off by default

    • For each THU you want to enable, save the entry.

    • When done, save the Location Role Profile.

     

    • Select Finished to save the changes for your location.

    Once the feature is properly configured - OTM will build full layer pallets - the remainders - if any - will go on a new pallet/ship unit. 

  • Karl Baker

    Rate Offering Tab with Fallback Rate Service ID highlighted

  • Karl Baker

    I would suggest using the Fallback Rate Service feature.  The Fallback Rate Service feature was designed and is intended to be used to support the use case described. If you add a Fallback Rate Service to your Vessel rate offerings - when your buyers run an RIQ requests that is beyond the number of days specified in the FALLBACK RS NUM OF DAYS parameter OTM will switch to the Fallback Rate Service to provide a cost.  Clients typically use either a Simulation or a Lookup rate service as a fallback.  

    By default any Rate Offering that has an Offering Type of "Vessel" will have the FallBack Rate Service ID option visible on the attributes tab.  The Fallback Rate Service attribute can be added to other Offering Types as well. As noted - the parameter FALLBACK RS NUM OF DAYS determines how many days into the future a query needs to be before the  fallback rate offering is used. The default value for this parameter is 90 days.

     

  • Karl Baker

    1.  freight lane scenarios, what-if (ad-hoc modeling) cases pertaining to mode, lane pair, and service level

    Short answer is OTM does support modeling scenarios - and we have many clients performing what-if modeling scenarios with OTM, but the tool is primarily an operational planning and execution tool - so the setup for what-if planning scenarios requires a knowledgeable user. 

    2.  freight bill payment & audit to validate freight provider invoices

    Yes - standard functionality is provided to support freight bill payment and audit for match and pay and auto-pay scenarios.

    3.  shipment consolidations promoting lower cost/kg

    OTM's planning functionality is focused on delivering transportation cost reduction.

  • Karl Baker

    There is no way to include the pdf document information - or more correctly - include the <otm:DocContentBinary/> element representation of the pdf in the Planned Shipment XML.  The suggested method is to transmit the required documents to other systems using the Document API.  

    The Document API XML provides a binary encoded representation of the document content in the <otm:DocContentBinary/> element.  To convert the string of characters provided in the<otm:DocContentBinary/> element you will need to use an encode/decode utility to convert the binary string back into the pdf document format.  There are lots of free encode/decode utilities available to support this process.  

  • Karl Baker

    I'm not sure - OTM supports something called Step Tendering which sounds like what you are doing.  There is a good section that describes the functionality in On-Line Help.

    Description from Help.

    When step tendering, carriers are sent tenders one at a time starting with the best/lowest cost service provider. Every time Oracle Transportation Management sends a step tender, it starts a step tender timer. If the carrier responds within the regular response time, but outside of the step tender timer, they are not guaranteed the tender. Instead, after the step tender time is reached, a new step tender is sent to the next best service provider. Any service provider with pending step tenders can respond to the tender. Thus preference can be given to the best service providers, but you do not have to wait the full regular response time before sending tenders to other service providers.

  • Karl Baker

    You're in luck - the Source Location on the Ready to Ship action can default to being blank by setting the glog.webserver.rts.defaultShipFromAsBlank property to true.

  • Karl Baker

    By default OTM will rate your accessorials in alphabetical order based on the object where the requirement for the accessorial originated, i.e. shipment accessorials first, then ship unit, then location, then order base, then order base ship unit, then item and finally the global accessorials.  To explicitly control the sequencing of the accessorials in rating, you can, for each accessorial, enter the appropriate Sequencing Factor. The accessorial Sequencing Factor value - when provided - will cause OTM to consolidate all the accessorials across all the objects and then sequences the accessorials for rating using the sequencing factor.

    • So - from the example above - to calculate the Out of Route Miles charges first and then a Fuel Surcharge, and then apply the Discount; enter the sequencing factor value as 1 for the Out of Route Miles charges, 2 for Fuel Surcharge, and 3 for Discount would rate the accesorials in the correct order.