You are on page 1of 21

OTM Implementation Best Practices in an EBS Environment

Lucidity Background
Founded in 2001 Headquarters in Dallas with offices in Chicago and Denver Flexible Implementation Options 110+ Full-time employees 140+ Customers Full service consulting approach
Complete Oracle portfolio provider Application Support Technology Integration

Seasoned Consultants

Experienced Practice Leaders

Oracle Certified Advantage Partner

Multi Recipient of Oracle Partner of the Year Award First Oracle Partner to go live with OTM post acquisition

Proven Partner to our Customers

OTM Product Footprint


Transportation Order Capture Transportation Planning Transportation Execution Freight Payment, Billing and Claims

Carrier and Asset Management

Cooperative Route Planning

Transportation Sourcing

Global Visibility Supply Chain Event Management Business Intelligence (Analytics & Reporting) Freight Forwarding and Brokerage

Packaged Integration
EBS OM / WMS / Inv Mgmt EBS Purchasing XML / XSL Oracle Retail EBS Financials

B P E L

Web Services Orders Shipments Events Oracle OTM

Web Services Invoices Allocations Accruals

B P E L

XML / XSL

Other Financials

Other ERP / SCM

Standardized, packaged integrations via Web Services, orchestrated by BPEL XSL

Outbound Order Process Flow

Oracle EBS Required Setups


Profile options Enabling OTM in Shipping Parameters Create/Sync Carriers Create Equipment item in Oracle Item Master Other data points in Oracle to keep in mind:
Service levels Freight terms

Profile Options

Shipping Parameters

Create/Sync Carriers

Equipment Items

Oracle Lookup Values

OTM Required Setups


External System(s)
Create External System Create Web Service Create WSDL document Assign WSDL doc to Web Service Assign Web Service to External System

Automation Agents Rate Service Payment Codes

EBS Automation Agents

Rate Service Setup


EBS Service Level = OTM Rate Service

Payment Method Codes


EBS Freight Terms Code = OTM Payment Method Code Code in OTM must match what is defined in EBS

Things to Keep in Mind


Packaged integration only supports a single OTM domain

Limitation of modes available in EBS

Delivery creation process is crucial

Single Domain Support


OTM supports multiple domains however, the standard integration will only support whatever domain is defined in this profile option.

Limited Modes Available in EBS


Although OTM supports many different modes of transportation, Oracle Shipping only supports this finite list of modes

Delivery Creation Process is Crucial


Single delivery must not exceed weight/volume constraints of equipment defined in OTM Dates that drive shipment planning are contained in fields that are typically hidden on the Shipping Transaction form Ignore for Planning field must be displayed

Other Best Practices


Load and maintain rate data via CSV files Leverage automation agents to automate business processes Create/utilize custom screen sets and menus Use Oracle UPK for training