EMEA/APAC  Quarterly  Webinar    

10  June  2015  07:00  GMT  

OTM  6.3  Upgrade  Experiences    

OTM SIG Board vacancies •  The OTM SIG Board needs you! •  Two client seats available now •  Benefits

–  Increase you network to other OTM clients –  Select topics for webinars –  Shape the annual OTM Conferences

Contact boardadmin@otmsig.com

Oracle Customer Satisfaction Survey •  Your feedback is one of the primary methods Oracle uses to

measure performance against your expectations

Surf to otmsig.com/oraclesurvey

Call  for  Ac@on  

US •  9-12 August 2015, Philadelphia, US •  Celebration of 10 years OTM •  Agenda to be published soon •  Early registration discount ends 17 June •  All information on otmconference.com

APAC •  10-11 December 2015, Singapore (subject to change) •  We need your input on otmsig.com/singapore

Europe •  3-5 February 2016, Copenhagen area •  Save the date!

OTM  Conferences  

OTM  6.3  Upgrade  Experiences    

APAC  Client  and  Technology  Partner  combined  presenta@on  for  OTMSIG  

 Presented  by  and  Marcus  Lim  and  Brian  Steemson  

4  

Background  -­‐  Steel  Transport  Industry  -­‐    Road,  Rail,  Ship  -­‐  Started  with  MLO  v5.0  as  a  na@onal  TMS  -­‐  Plan  pieces  using  Order  Movement  -­‐  Use  mul@ple  types  of  Shipment  setup  (Bulk  Plan,  SAW,  

Appointment)  -­‐  Integrate  7  different  system  transport  data  in  1  place  

5  

Exis@ng  Data  -­‐  5000+  loca@ons,  calendars  -­‐  322  i@neraries  -­‐  249  equipment  types  -­‐  85  Rate  Service,  140  Rate  Offerings,  3870  rate  records  -­‐  87  service  providers  -­‐  107  commodity  types  -­‐  700+  invoices  generated  daily,  consolidated  weekly  -­‐  1804  saved  queries  (mostly  sql)  

OTM  6.3  Upgrade  Experience    •  Business  Drivers  •  Func@onal  assessments  and  improvements  •  Install  Process  •  Technical  Changes  •  Issues  •  Roadmap  

7  

Business  Drivers  •  Leverage  on  soaware  “smarts”  to  improve  efficiency  •  Centralised  planning  model  •  Stay  current  and  take  advantage  of  func@onal  improvements  •  Introduce  OTM  Mobile  to  carriers  using  OTM  login  •  Beeer  control  of  planning  results  via  addi@onal  configura@on  

segngs  and  parameters  •  Allow  users  to  change  configura@on  /  modify  queries  •  Improve  traceability  of  shipments  •  Automated  Bulk  Plan,  Repor@ng  •  Improve  soaware  response  @me  and  reliability  

8  

OTM  Solu@on  for  Business  Drivers  •  Automa@on  Improvement  via  priority  level  automated  

shipment  crea@on  Mobile  Func@onality  –  Func@onal  Assessment,  Rollout  to  Carriers  

•  Improvements  to  UI  –  Advanced  Layouts  •  Change  to  Tracking  Events  –  Func@onal  Assessment,  Mandatory  

Changes  •  Flex  Fields    •  Other  changes,  inline  edi@ng,  sor@ng  by  refnum  •  Future  improvements  to  planning  eg.  priority,  beeer  3d  

planning,  changes  to  planning  parameters  to  improve  automa@on  etc.  

9  

Upgrade  Technical  Overview  •  Environment  Overview  •  Approach  •  Install  Process  •  App  Server  Install  •  DB  Migra@on  •  Customiza@ons  •  Issues  •  Func@onality  •  Road  Map  •  More  Info  

10  

Environment  Overview  •  Dedicated  Linux  Servers,  2  web  servers  (1  user,  1  integra@on),  

1  app  and  1  db  server  •  Customiza@on/Configura@on  

–  1  custom  db  schema  with  40  custom  tables  –  25  custom  db  packages,  190  stored  procedures  –  11  Custom  BI  publisher  reports  (using  embedded  BI  Publisher)  –  13  external  systems,  10  custom  stylesheets  –  Over  200  Automa@on  Agents  

•  Main  Func@onal  Addi@ons  –  Automated  Planning  (scheduled  auto  releasing,  planning,  tendering  and  repor@ng)  –  Automa@c  shipment  crea@ng  for  Freight  Forwarding  –  Automa@c  shipment  merging  by  rego  and  load  id  –  3d  Load  Configura@on  for  load  coils  into  containers  –  Custom  OM  screen  with  calculator  for  planning  single  loads  –  Server  based  scripts  repor@ng,  background  processing,  monitoring  applica@on  

performance  and  logs  for  errors  

11  

Approach  •  Review  release  notes,  TOIs  and  other  doco.  for  changes  

–  Impact  on  workflow  or  process  –  Opportuni@es  

•  Run  a  PoC  to  assess  func@onality  •  OTM  upgrade  is  a  re-­‐install,  no  longer  an  upgrade  •  Parallel  6.2  and  6.3  install  on  Development  •  Messaging  sent  in  parallel  to  both  instances  •  UaT  on  the  6.3  Instance  •  Pre-­‐install  and  test  of  6.3  on  Produc@on  directed  do  dev  db  •  Final  produc@on  cutover  just  a  db  migra@on  

12  

Install  Process  

DEVAPP

DEVWEB

OTM Dev DB ServerDEVDB

OTM 6.2.8 DB MLOD

OTM 6.3.4 DB MLO63

OTM Web 6.2.8Http://

devweb:1337

OTM Web 6.3.4Http://devweb

OTM App 6.2.8devapp:7001

OTM App 6..3.4Devapp:7010

OTM 6.2 Database Cloned and upgraded to OTM 6.3 on existing Dev DB Server

OTM App and Web Servers 6.2 and 6.3 both

running existing hardware, running on different ports

13  

DB  Migra@on  •  Migra@on  scrips  run  to  migrate  the  db  from  OTM  6.2.8  to  6.3.6  •  Migra@on  updates  every  record  in  some  tables  (eg.  order  release)  in  OTM,  

which  changes  the  update  date  used  in  purge  queries  •  Need  to  run  a  process  to  store  dates  prior  to  the  migra@on.  •  The  leg  table  needed  to  be  cleared  to  reduce  migra@on  run  @me  •  Steps  

–  Clear  down  leg  table  –  Saved  order  release  and  order  movement  update  dates  prior  to  migra@on  –  Run  the  pre  migra@on  script  –  Run  the  dbpatch_60.sh  script  and  review  logs  –  Run  the  dbpatch_63.sh  script  and  review  logs  –  Disable  insert/update  triggers  on  order  release  and  order  movement  –  Restore  Update  Dates  –  Re-­‐enable  triggers  –  Update  permissions  on  non  OTM  users  

14  

Customiza@ons  •  Oracle  provide  a  script  which  can  be  modified  to  copy  custom  

components  eg.  stylesheets,  branding  •  Need  to  migrate  other  customiza@ons  

–  Configure  log  file  loca@ons  –  Re-­‐install  custom  OM  screen  –  Custom  bean  counts  no  longer  need  to  be  configured  –  Mobile  site  change  to  prevent  the  e-­‐loca@on  alert  change  in  /app/otm/otmweb636/

glog/gc3webapp/WEB-­‐INF/ml/jsp/mobile/trackingevent/servProvMEventGetInfo.jspx  –  Tracking  events  –  enable  LEGACY  SHIPMENT  TRACKING,  had  to  change  to  run  as  ADMIN  

role  to  prevent  issues  for  carriers.  –  Some  agent  and  procedure  changes  to  handle  constraints  on  the  

shipment_s_equipment_join  tables.  –  Various  addi@onal  ACLs  

15  

Customiza@ons  –  Order  Movement  

•  Using  Ship  With  Group  in  OM  to  automate  bulk  planning  

•  Javascript  pop-­‐up  calculator  

•  Dual  Pane  •  Unplanned  –  Pieces  available  for  planning  •  Planned  –  Shipment  specific  details  •  Order  Base  –  Addi@onal  pieces  (future  week)  if  required  

Customiza@ons  –  Advance  Layout  

•  Flex  Field  used  in  buy  shipment  screen  •  Use  User  Defined  Aeribute1  •  Stop  returned  more  than  one  result  in  a  single  sub-­‐row  query  

error  when  displaying  in  the  buy  shipment  screen  

Customiza@ons  –  Flex  Fields  

Issues  •  IE11  compa@bility.    All  compa@bility  must  be  disabled.    Outstanding  issue  

with  some  screens  eg.  xml  upload,  csv  export.  •  Legacy  rate  service  depreciated,  required  changes  to  ground  service  and  

calendars  •  Carrier  Track  and  Trace  messages  not  matching  shipments,  had  to  enable  

Legacy  Shipment  Matching  and  run  agent  as  Admin.  •  Various  issues  with  sor@ng,  screen  totals  and  expor@ng,  SR’s  raised  and  

patches  applied  •  Changes  in  UTC  package  permissions,  run  as  AUTHID,  had  to  grant  BI  User  

permissions  to  run  java  programs.  •  Various  Acl  issues  with  users  unable  to  run  certain  func@ons  or  view  data  •  Shipments  created  in  appointment  screen  missing  equipment  record  •  Use  in  finder  unchecked  query  export  returning  5000  rows,  export  

property  segng  needs  to  be  >  query  limit.  •  Agent  changes  to  work  around  issues  eg.  dimensions  not  copied  to  order  

movement.  19  

DML  Caching  -­‐   Changes  to  caching  in  6.3  -­‐   Default  mode  is  DML  (data  manipula@on  language)  -­‐   Uses  a  returning  statement  to  refresh  cache  -­‐   The  returning  statement  is  invalid  with  sub  queries  e.g    

INSERT  INTO  ob_refnum  (order_base_gid,  ob_refnum_qual_gid,  ob_refnum_value,  domain_name)  SELECT  order_base_gid,domain_name||'.DD  NUMBER','  ',domain_name  FROM  ob_order_base  o  WHERE  order_base_gid=$GID  AND  NOT  EXISTS  (SELECT  1  FROM  ob_refnum  r  WHERE  r.order_base_gid=o.order_base_gid  AND  r.ob_refnum_qual_gid=o.domain_name||'.DD  NUMBER')    

-­‐     SQL  run  against  all  agents  to  disable  caching  on  these  statements  -­‐     A  new  cache  refresh  of  Object  Tree  also  introduced  -­‐   Performance  issues  when  this  was  run  on  statements  calling  a  stored  procedure.  -­‐   Cache  refresh  disabled  on  calls  to  stored  procedures.  

20  

Tracking  Events  Recommenda8ons  •  Con@nue  to  use  legacy  matching  (will  need  to  reconfigure  in  

future  releases)  •  Configure  workflow  to  hide  duplicate  events  •  May  be  useful  to  receive  bulk  events  eg.  Train  delay  •  Record  events  against  a  coil  •  Consider  how  it  can  be  used  for  merging  to  keep  track  and  

trace  

21  

Promote  to  Produc@on  •  Provides  a  mechanism  to  copy  groups  of  objects  from  dev  to  

prod  and  vice  versa  •  Useful  to  promote  changes  eg.  For  the  upgrade  we  used  a  

migra@on  project.  •  Can  include  anything  including  shipments,  rates  etc.  •  Maybe  useful  for  tes@ng  and  copying  rates  and  other  master  

data  changes  •  Doesn’t  handle  delete  records  very  well.  

22  

Mobile  Screens  •  Use  for  smaller  carriers  to  enter  track  and  trace  •  The  submit  events  will  show  shipments  that  are  in  the  watch  

list  which  are  not  ENROUTE_COMPLETE.    This  means  a  user  must  search  for  shipments.      

•  Search  is  case  sensi@ve  •  Configure  workflow  to  pre-­‐populate  the  watch  list  for  a  user  

so  that  incomplete  shipments  would  automa@cally  appear.    

23  

Road  Map  

•  Roll  out  mobile  screens  to  country  carriers  •  Remaining  Func@onal  Ac@vi@es  

–  Review  changes  in  Load  Building    –  Review  changes  in  priority  planning  –  Improvements  from  u@lizing  flex  fields  

•  OTM  moving  to  IaaS,  VM’s  on  Bizcloud  •  Other  Opportuni@es  

–  U@lize  planning  parameter  changes  to  improve  automa@on  –  Use  of  advanced  layouts  –  Use  tracking  events  to  preserve  TnT  aaer  merging  –  ...  

 

24  

More  Informa@on  •  OTM  6.3  Release  Notes  •  OTM  6.3  TOIs    •  OTM  Func@onal  Overviews  •  OTM  Administra@on  Guides  (Install,  Migra@on,  Security  etc.)  •   See  Oracle  document  796594.1  

25  

Ques@ons  

26