Transportation Management

Get Involved. Join the Conversation.

Comments

  • LAKSHMIDEEPAK GADDIPATI

    Hi,

     

    We did pilot in TI and we didn't encounter this issue. TI authentication happens using OTM roles. Is this happening for every user?

  • amiresi sathish

    Seems something wrong with accessing XML info to DB, I just tried same XML in my instance it worked for me.

    </RIQQuery>
                   <RemoteQueryStatus>
                      <RemoteQueryStatusCode>ERROR</RemoteQueryStatusCode>
                      <RemoteQueryStatusSubject>RateActionSession Exception</RemoteQueryStatusSubject>
                      <RemoteQueryStatusMessage>ERROR PROCESSING RATE INQUIRY</RemoteQueryStatusMessage>
                      <StackTrace>[002804] No Valid Rates Found
     

  • Ashok Revuri

    yes, i did :)

  • amiresi sathish
    • posted via email reply September 4, 2019
    • Permalink
     
    
    Not faced this error,  hope you had replace the user name and password in the transmission header
    
  • Ashok Revuri

    Thanks Satish.

    While i try to upload this xml in OTM. i am getting below error. Have you encountered this before?

    glog_error id="[001391]">
        <log_timestamp>2019-09-04 10:22:24.690</log_timestamp>
        <process>
            <machine/>
            <gid>350464</gid>
            <start>2019-09-04 10:22:24.641</start>
        </process>
        <causes>
            <cause>
                <error>java.lang.IllegalStateException: java.lang.IllegalArgumentException: null java.sql.Connection</error>
            </cause>
        </causes>
        <stack_trace>[001391] java.lang.IllegalStateException: java.lang.IllegalArgumentException: null java.sql.Connection
     
    java.lang.IllegalStateException: java.lang.IllegalArgumentException: null java.sql.Connection
    at glog.integration.transmission.TransmissionDBReader.open(TransmissionDBReader.java:57)

     

  • amiresi sathish
    • posted via email reply September 4, 2019
    • Permalink
     
    
    Please find the sample rate inquiry XML
    
    <Transmission>
    
        <TransmissionHeader>
    
            <TransmissionType>QUERY</TransmissionType>
    
            <TransactionCount>1</TransactionCount>
    
            <UserName>PPGTM.SATHISH</UserName>
    
            <Password>******</Password>
    
            <AckSpec>
    
                <ComMethodGid>
    
                    <Gid>
    
                        <Xid>HTTPPOST</Xid>
    
                    </Gid>
    
                </ComMethodGid>
    
                <AckOption>YES</AckOption>
    
            </AckSpec>
    
        </TransmissionHeader>
    
        <TransmissionBody>
    
            <GLogXMLElement>
    
                <RemoteQuery>
    
                    <RIQQuery>
    
                        <SourceAddress>
    
                            <MileageAddress>
    
                                <LocationGid>
    
                                    <Gid>
    
                                        <DomainName>PUBLIC</DomainName>
    
                                        <Xid>NYC</Xid>
    
                                    </Gid>
    
                                </LocationGid>
    
                            </MileageAddress>
    
                        </SourceAddress>
    
                        <DestAddress>
    
                            <MileageAddress>
    
                                <LocationGid>
    
                                    <Gid>
    
                                        <DomainName>PUBLIC</DomainName>
    
                                        <Xid>BDL</Xid>
    
                                    </Gid>
    
                                </LocationGid>
    
                            </MileageAddress>
    
                        </DestAddress>
    
                        <RateOfferingGid>
    
                            <Gid>
    
                                <DomainName>PPGTM</DomainName>
    
                                <Xid>DEFAULT_LTL</Xid>
    
                            </Gid>
    
                        </RateOfferingGid>
    
                        <RateGeoGid>
    
                            <Gid>
    
                                <DomainName>PPGTM</DomainName>
    
                                <Xid>DEFAULT_LTL_US</Xid>
    
                            </Gid>
    
                        </RateGeoGid>
    
                        <RateServiceGid>
    
                            <Gid>
    
                                <DomainName>PPGTM</DomainName>
    
                                <Xid>DISTANCE_DURATION</Xid>
    
                            </Gid>
    
                        </RateServiceGid>
    
                        <TransportModeGid>
    
                            <Gid>
    
                                <Xid>LTL</Xid>
    
                            </Gid>
    
                        </TransportModeGid>
    
                        <UseRIQRoute>N</UseRIQRoute>
    
                        <ShipUnit>
    
                            <ShipUnitGid>
    
                                <Gid>
    
                                    <DomainName>PUBLIC</DomainName>
    
                                    <Xid>123456</Xid>
    
                                </Gid>
    
                            </ShipUnitGid>
    
                            <ShipUnitSpecGid>
    
                                <Gid>
    
                                    <DomainName>PUBLIC</DomainName>
    
                                    <Xid>DEFAULT</Xid>
    
                                </Gid>
    
                            </ShipUnitSpecGid>
    
                            <WeightVolume>
    
                                <Weight>
    
                                    <WeightValue>100.0</WeightValue>
    
                                    <WeightUOMGid>
    
                                        <Gid>
    
                                            <Xid>LB</Xid>
    
                                        </Gid>
    
                                    </WeightUOMGid>
    
                                </Weight>
    
                                <Volume>
    
                                    <VolumeValue>0.5000</VolumeValue>
    
                                    <VolumeUOMGid>
    
                                        <Gid>
    
                                            <Xid>CUFT</Xid>
    
                                        </Gid>
    
                                    </VolumeUOMGid>
    
                                </Volume>
    
                            </WeightVolume>
    
                        </ShipUnit>
    
                    </RIQQuery>
    
                </RemoteQuery>
    
            </GLogXMLElement>
    
        </TransmissionBody>
    
    </Transmission>
    
  • Karl Baker

    The 19B/C feature Consider Service Provider Capacity Across Days provides you with the ability to configure OTM to consider using capacity limit capacities that are available on different days.  You can encourage or discourage the use of capacity on different days for both cost based decisions as well as priority based decisions.

    The full description from the What's New document for 19B is below...

    CONSIDER SERVICE PROVIDER CAPACITY ACROSS DAYS

    This feature provides you with the ability to configure a policy that will allow OTM to consider using capacity limit capacities that are available on different days.  With this feature, you have configuration capabilities that will allow you to encourage or discourage the use of capacity on different days – for both cost based decisions as well as priority based decisions.

    Shippers who would like to take advantage of lower cost carriers with limited capacity and still manage the priority of the shipments (High, Medium, Low) now have a place to configure a policy on how to configure the delay to shipping based on priority and how long of a delay is allowed.

    New Parameters

    • SPA MAX DAYS TO CONSIDER
      • This parameter determines how many extra possible start days OTM will consider for each shipment that is subject to capacity limits. 
    • SPA TIME CHANGE POLICY
      • This parameter allows you to configure your policy for changing a shipment's start date in order to take advantage of (future) capacity.
        •  For example, given a service provider with the least expensive rate on a lane and a capacity of one truck per day. Assuming that today's capacity has already been used, and there is another shipment that could be assigned to the least cost service provider if the service provider had capacity - does it make sense to change the start date of today's shipment to tomorrow - assuming that the change is feasible - to use tomorrow's capacity - or does "delaying" the start time by a day add an unacceptable service time failure risk by eliminating the available slack time in the shipment timing?  
      • The available SPA TIME CHANGE POLICY options are:
        • 3. Encourage Time Change.
        • 2. Discourage Time Change For High & Medium Priority Shipments'
        • 1. Discourage Time Change For High Priority Shipments'
        • 0. Discourage Time Change

    STEPS TO ENABLE

    Assuming that you are already planning with capacity limits - to extend capacity limits to consider using capacity availability on different days you will want to configure the following parameters which can be found in the Service Provider Assignment group:

    • SPA MAX DAYS TO CONSIDER
      • This parameter determines how many extra possible start days OTM will consider for each shipment, subject to capacity limits. When using this parameter, it is best to set this no larger than needed, as it can have a performance impact. For example, if two extra days is sufficient to find the right resources, then there is no reason to set it higher than 2.
      • The default is "0" (zero). See the Service Provider Assignment and Resource Management topic, Service Provider Assignment Time Window Functionality section, for more details.
    • SPA TIME CHANGE POLICY
      • This parameter provides priority level control about whether OTM should discourage delaying the shipment start date in order to take advantage of a cheap but capacity-limited service provider. For example, there is a cheap carrier that has only one truck per day. Should I delay my shipment departure to tomorrow to get the cheap truck, or should I let it ship today on an expensive truck?  The options are:
        • '0. Discourage Time Change',
        • '1. Discourage Time Change For High Priority Shipments',
        • '2. Discourage Time Change For High & Medium Priority Shipments',
        • '3. Encourage Time Change'.

     

    TIPS AND CONSIDERATIONS

    SPA MAX DAYS TO CONSIDER -  When using this parameter, it is best to set this no larger than needed, as it can have a performance impact. For example, if two extra days is sufficient to find the right resources, then there is no reason to set it higher than 2.

     

  • Karl Baker
    • OTM does not have the Int Saved Query ability on every element. Int Saved Query is used for finding gids. Currently Int Saved Query is available only on the Parent Invoice element and is meant to find the parent invoice. 

    Why do you need this replacement?

    • Consolidated Invoice approvals
      1. "After parent invoice approvals, voucher is generated but the cost of voucher is zero (I assume by this time child invoices are not completely processed hence the cost is zero), if approve after few mins then voucher is generated with correct amounts."   Can you please provide a scenario for this.  The voucher should be created with total net amount due of the consolidate invoice. Not sure why it is being shown as zero.
      2. How to validate each invoice cost line with related shipment cost line?
        1. As of now there is hard reference between the shipment costs and invoice lines.
        2. When OTM checks for line level tolerance, the assumption was that each of the shipment costs and invoice line would be unique for the combination of Cost Type, Accessorial Code, Payment Method and General Ledger code.
        3. If the costs and invoice line are provided in this manner then each of shipment cost can be matched to invoice line.
        4. But for this combination (Cost Type, Accessorial Code, Payment Method and General Ledger code) if there are multiple costs or multiple lines, OTM does not have any effective way of matching the costs and lines. The logic tries to sort each of the groups costs and lines by cost and starts matching each with the other and checks for tolerance.
        5. Once the tolerance checks are done, when creating the voucher, we just create the voucher with the invoice line items as voucher invoice line items and the sum of each of voucher invoice line items as the total amount of voucher.

     

  • Karl Baker

    Suggestion - based on your use case - could you try adding a PRE action check (v post) based on the invoice status that gets triggered before approving an invoice? 

  • Karl Baker

    As noted in your SR - the workaround while this issue is being investigated is to include all the referenced xsd files and use a physical wsdl file in lieu of the URL based WSDL.

  • Karl Baker

    From a product documentation perspective we do not generate or maintain a set of BPMs for OTM and GTM - we do, however, generate and maintain a large (and expanding) set of How To/Configuration Topics in Help which provide the standard configuration for setting up OTM and GTM to solve common business use cases and scenarios.

    OTM How To/Configuration Topics

    • Setting up OTM
    • Bulk Plan Performance and Tuning
    • Business Number Generator
    • Order Management
    • Promote to Production (P2P) Process
    • Messages
    • Configuring the User Interface
    • Tips and Troubleshooting
    • About Client Session Management
    • About Grouping Location Resources
    • About Oracle Transportation Mobile
    • About OTM Sending Hazmat Information to External Distance Engines
    • About Sending Equipment Dimensions to External Distance Engines
    • About Service Providers Accessing Workbench
    • Adding and Applying US HOS Rules
    • Allocation of Costs and Assigning General Ledger Codes
    • Configuring a Fuel Surcharge
    • Configuring an External Web Service Engine
    • Configuring and Processing a Credit Check
    • Configuring European VAT
    • Configuring and Using Rate Preferences
    • Configuring OTM to Integrate with Kewill Flagship Parcel Rates
    • Configuring Shipment Groups
    • Configuring Tiered Rating
    • Configuring VAT Components
    • Creating Agents for Report Sets
    • Creating an Automation Agent
    • Creating a Calendar
    • Creating a Multistop Order
    • Creating Canadian Postal Codes
    • Creating Rates for Zones
    • Creating Saved Queries
    • Generating Shipping Forms
    • How to Assign General Ledger Codes
    • How To Configure Conditional ing
    • How to Configure Cross-Docks and Pools
    • How To Configure Dispatch Level Tendering
    • How to Configure Shipment Depot Stops
    • How To Create a Rule 11 Shipment
    • How To Receive Migration Project Export Packages via Email and FTP
    • How To Set Up and Execute Cooperative Routing Aggregation
    • How To Set Up Milestone Templates and Monitors
    • How To Set Up Notifications for Additional Contacts for Tender Events
    • How To Set Up SMS Text Messaging
    • How To Enable the Use of Parameterized Saved Queries
    • How To Use an XML Template
    • How to Settle an Invoice
    • How to Set Up an SMC Rate
    • Index Based Accessorial
    • Logistics Network Modeling Overview
    • Purge Actions
    • Settling a Bill
    • Setting Up Interfaces for Integration
    • Sending Messages to the Message Center
    • Spot Bid Tenders Configuration
    • Using Advanced Layouts
    • Using Maps
    • TI How To/Configuration Topics
      • Using Transportation Intelligence for an End User
      • How to Define a Default Dashboard in Transportation Intelligence
      • How to Provide Access 

    Flow Topics

    • Conditional Booking Process Flow
    • Demurrage Flow
    • Network Routing Flow
    • Order Movement Build Shipment Process
    • Order Release Equipment
    • Order Release Flow
    • Rate Maintenance Process Flow

    GTM How To/Configuration Topics

    • Restricted Party Screening
    • Landed Cost Simulator
    • Implementation of EAR Control Process in GTM
    • License Screening
    • Duty and Tax Calculation on Trade Transaction or Declaration
    • Landed Cost Estimation on Trade Transaction or Declaration
    • AES Export Declaration Filing Process
    • Trade Content Download
    • Oracle Transportation Management-Global Trade Management Integration
    • Trade Compliance Management
    • How to Use Sanctioned Territory Screening in GTM
    • Configuring and Processing Declarations
    • Product Classification Process
    • Supplier Solicitation
  • LAKSHMIDEEPAK GADDIPATI

    Hi,

    Thanks for your reply. I believe this is applicable only for Adjustment costs but not for direct approvals. Scenario which i was asking is when user trying to approve a already approved invoice. Note, customer wants to see the details cost section so adding a action check on approval was not the solution. 

  • Karl Baker

    Materials look great. thanks... 

  • Karl Baker

    Without delving into the details - I believe the 19B feature below will provide you with a possible solution to the challenge being described.  This feature was delivered in 19B and will be available for you when you upgrade from 19A to 19C.

    INVOICE ADJUSTMENT COST BEHAVIOR ENHANCEMENT

    This feature provides you with a new property that allows you to control how OTM processes invoice adjustments.  Using the new property glog.invoice.adjustments.createNewInvoiceForAdjustments you can now support the following scenarios.

    With glog.invoice.adjustments.createNewInvoiceForAdjustments=true (default): 

    • Given an adjustment to an Approved Invoice the adjustment amount will be captured in a new invoice.
    • Given an adjustment to an Unapproved Invoice the adjustment amount will be added to the existing invoice as a invoice line. 

    With glog.invoice.adjustments.createNewInvoiceForAdjustments=false: 

    • Given an adjustment to an Approved Invoice the adjustment amount will be added to the existing invoice as a new invoice line. 

    STEPS TO ENABLE

    You don't need to do anything to enable this feature.

     

    TIPS AND CONSIDERATIONS

     

    The property default for glog.invoice.adjustments.createNewInvoiceForAdjustments=true (default): 

    • Given an adjustment to an Approved Invoice the adjustment amount will be captured in a new invoice.
    • Given an adjustment to an Unapproved Invoice the adjustment amount will be added to the existing invoice as a invoice line.

     

  • LAKSHMIDEEPAK GADDIPATI

    3-20691520941