Note: This info is applicable to OTM 6.X version.
This product is designed such a way that it can be easily customized by IT Consultants for various client specific business needs. IT Technical consultants would need basic Oracle SQL and XML knowledge for customizing the product and Functional consultants might need logistics domain knowledge to configure(setup) the product based on the documentation and use cases provided by Oracle.
This product is originally developed by a company with name "Global Logistics Technologies, Inc" (also known as G-log). It was acquired by Oracle around 2015 and was renamed as OTM - Oracle Transportation Management.
OTM has in-built integration with Oracle E-Business Suite of applications like Oracle Shipping(WSH). OTM can integrate with any external system by posting and receiving XML files based on GlogXML.xsd (product defined schema/data structure). Note that this is not an application/module within the Oracle E-Business Suite. This requires a separate installation - both application and database. Please see the next topic "OTM Architecuture" for these details.
At a high level, few of the capabilities of OTM are mentioned here:
- Receive Purchase Orders(Order Base) from source ERP systems/legacy systems
- Create Order Releases(bookings) from the Purchase Orders for partial quantity or complete quantity with manual or automated release instructions
- Plan/consolidate Order Releases with common source and destination locations or into multi-stop shipments based on standard Bulk Plan algorithm that is configurable for client specific requirements. Bulk Plan involves identifying Itinerary(route), least cost Service Provider or Carrier (based on pre-uploaded rates), optimize loading of items into containers(equipments), calculating shipment in-transit times based on setups, etc.
- OTM can dynamically fetch LTL rates from third party applications like 'SMC Rateware' and also distances between zip codes using third party applications like 'MILEMAKER', 'PCMILER', etc
- Send Tender Offer requests to Service Providers identified during planning. Note that if Carrier cannot accept XML tender files, we need to use Middleware tools like Web Methods/Oracle BPEL process etc to translate OTM outbound XML files to carrier readable formats like EDI files.
- Receive Tender Offer response and update the shipment
- Receive Shipment Tracking updates from Service Providers and update the shipment
- Receive/process invoices from Service Providers, match the invoice costs with planned costs for invoice approvals, create vouchers for approved invoices, allocate the costs against customer orders, etc.
Nice Post
ReplyDeleteNIce Post small correction Orcale Accuired G-log in November 2005
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteAnother Capability of OTM is missed -
ReplyDeleteDock Scheduling and Yard Management - though it's used by Warehouses / DCs only but its another feature of OTM
Thank you Punit. I will update it soon.
DeleteAwesome blog for beginers...
ReplyDeleteCan we change the following statement
ReplyDelete"OTM is integrated with EBS like WSH." to
"OTM can be integrate with any application to manage inbound and outbound transactions."
Here, we are referring to only out of the box integrations. Please refer to next pages where we detailed OTM inbound/outbound integration capabilities with any other external systems. Thank you for visiting this page and suggesting. We appreciate it !
DeleteDone. Thank you.
DeleteThanks to the site creator very useful for the Beginers.
ReplyDeleteAwesome
ReplyDeleteI have looked up to many sites to learn OTM! But this one stands out from rest - very crisp, reliable and great learning for the beiginner
ReplyDeleteExcellent explanation of how BPEL interacts with OTM
ReplyDelete