Comments

  • 1-15 of 15
  • LAKSHMIDEEPAK GADDIPATI

    Hi,

    Are you looking to add HST and GST on invoice costs ? If Yes, please Province Code Profiles,Vat Code,Vat Configuration. 

  • LAKSHMIDEEPAK GADDIPATI

    This is fixed in weekly patch 20190928

  • LAKSHMIDEEPAK GADDIPATI

    Please check this request and see if it's feasible to make temp control,hazardous flags truly optional in appointment rulesets. Ability to control resource selection will be key use case among many customers . 

  • LAKSHMIDEEPAK GADDIPATI

    This is indeed a bug. If you are planning to upgrade for 19c make sure you check this out.

  • LAKSHMIDEEPAK GADDIPATI

    Hi ,

    OTM Chooses equipment first based on Items and their commodities. Dry and Ref specially depend on temperature control of items on delivery. Once list of equipment groups identified then a suitable rate will be searched. Usually rate offerings are tied to a specific equipment group. Based on temp group of items a suitable rate will be automatically selected. 

  • LAKSHMIDEEPAK GADDIPATI

    If you really want to override , update the shipment with appropriate rate record and rate offering information of Dry Truck and recalculate. If you want to record this as exception, make it a cost fixed shipment and adjust the costs accordingly.

  • LAKSHMIDEEPAK GADDIPATI

    Hi,

    Did you measure how much time it's taking to process order updates , ideally it should be near to the polling frequency? Did you use a filter in poller and what type of poller you are using ? Please refer Oracle doc id 2544304.1 it helped us in configuring our set up in cloud.

    Thanks,

    Deepak

     

  • LAKSHMIDEEPAK GADDIPATI

    To update,

    Because of limitations of Appointment rule flexibility, we ended up using other alternatives to constrain doors.

  • 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?

  • 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. 

  • LAKSHMIDEEPAK GADDIPATI

    3-20691520941

  • LAKSHMIDEEPAK GADDIPATI

    Only reason code selection will be a customization and i am not sure there are any avenues to implement that in SaaS. 

  • LAKSHMIDEEPAK GADDIPATI

    Please check Action Reasons. You should be able to action reasons to prompt reason codes for certain actions.

  • LAKSHMIDEEPAK GADDIPATI

    Hi,

    We moved a onprem (but oracle hosted) solution to SaaS version last month. We moved from 6.3.7 to 6.4.2 below are key observations,

    Prep work,

    1. you need to remove all custom techniques (JavaScript/Modified Servlets)  in OTM. Redesign processes which used custom procedures. 
    2. If you have any custom data extractions plugged into current database using jdbc or any other database connectivity ,best time to redesign them.
    3. No more stand alone pcmiler supported, need to get a webservice based pcmiler license.
    4. One user typically will have one email so you really can't create multiple user ids for users any more.Same applies to carriers. This can be a process change as well as technical change if any business cases need to access more than 1 domain. 
    5.  6.3 versions have columns named as XX, ideally they should have been removed as part of prior migration activities . Making sure you don't have XX columns in 6.3 database before going for migration

    Data migration:

    1. Based on retention requirement and data volume you want to carry over to cloud this can be challenging.
    2. Identify how you are going to move data
      1. Use DIPC (If your solution hosted in oracle) 
      2. Use custom data replication tools (if you have full access to current db )
      3. Use manual uploads (Not accurate, need validations,need solid methods to handle deleted data)
      4. Use custom scripting  (We written python scripts using csvutil and dbxml techniques to pull and push data between on prem and cloud
    3. Separate data between Config,Master,Transaction categories 
    4. If you use manual uploads watch out for,
      1. Linefeed data in remarks and other free text fields. 
      2. Quote or apos in identifiers and description.
      3. Take care of leading zeroes. 
      4. Take care of rounding the digits
    5. If you use dbxml it will not carry over insert date,insert user ,update date and update user.DBXML has serious size limitations. 
    6. If you use csvs also many tables has triggers which will prevent to carry over foot print columns.Triggers can be tough to deal with, for example capacity usage has a trigger which will not allow few shipment level table data as capacity is already met but we are doing a migration and it doesn't matter to the trigger.
    7. If you are doing manual uploads you will need to spread the data migration in batches and you need to build solid technique to replicate data deletions. Especially batches towards the end of the cycle will be challenging.

    Integrations: 

    1.  Fortunately not many changes noticed. Only key change is all integration users need to be switched from interactive roles to a new role called INTEGRATION 
    2. Dataqueue setup is turned on by default, don't use it if you already have integration systems which does work for you
    3. No major xsd changes noticed.
    4. However, you will not be able to see entire xml in transmisison manager. Only transmission body or transaction body shown based on choice. 

    Agents:

    1. Most of the 6.3 agents will work as-is in 6.4.2. 
    2. In very rare cases we noticed direct sqls showed few issues ,mainly because of data migration issues.
    3. Use migration project to export and import agents,saved queries,saved conditions,complex expressions,menus,screen sets
    4. If you are using same events across domains check them twice. Review agents which are set up to run as objects.
    5. Make a note that, application default time is going to change from x to UTC. so if you have any jobs or sqls which were based on that understanding needs to be changed.

    Reporting:

    1. No more lexical parameters
    2. BI publisher separated
    3. If you have lot of reports which are parameter driven, this will take good enough time to rewrite them. 
    4. SQL timeouts,no more long running reports
    5. For simple reports it's now easier to create reports
    6. Point all current reports in otm to new report paths

    External Data feeders:

    1. If you have any external application which is reading/writing data from/to otm database redesign it. Same options as data migrations without the manual option. We opted for dbxml based approach built on aws solution.

    Data migration and prep work can be worked out in parallel streams ,redesigning all custom fixes and replacing with available otm components will give confidence on overall approach

    Overall, data migration is going to be tough battle.

     

    LakshmiDeepak Gaddipati

     

  • LAKSHMIDEEPAK GADDIPATI

    Hi,

    I am not sure what ERP you are using. But any ERP should have GL,COST/PROFIT center . So assigning GL/other attributes at order level and sending a allocation base and let ERP assign the cost to respective GL and COST/PROFIT centers.

     

    Thanks,

    Deepak