The presentation will include an overview of how the two systems integrate at a high level. We will then delve deeper and describe and diagram the flows between EBS and OTM, for the following processes: Sales Orders, Purchasing, Payables, Rates and Ship Methods. With that complete, we will discuss lessons learned from the projects, including the relative maturity of this integration offering, data mapping issues (particularly around units of measure and delivery dates), synchronization of shared data (including locations, carriers and service levels) and understanding several key terminology differences between the two products. Finally, we will end with a Q and A session, so that attendees can get answers to related questions or delve deeper into particular segments for greater detail. Presented by Chris Plough at MavenWire.

1. Integrating EBS and OTM:
Understanding the Process
Flows and Avoiding Pitfalls
OTM SIG
User Conference ‘07
July 2007 MavenWire

2. Agenda
High Level Overview of the EBS/OTM
Integration
Technical Requirements and Installation
Data Flows
Entity Mapping / Terminology
Processes Flows
Shared Data
Lessons Learned
Q and A / Discussion
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

3. Objectives
Present an overview of Oracle’s pre-packaged
EBS/OTM integration
Share the lessons learned while implementing
with early-adopter clients
Show how to best leverage the integration
flows while avoiding pitfalls and duplicate
work
Answer your questions and have an open,
interactive discussion
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

4. High Level Overview – EBS / BPEL / OTM
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

5. Technical Requirements
E-Business Suite
11i.10
Oracle Transportation Management
5.5 CU2 (CU3 recommended)
Oracle Application Server
10gR2
BPEL Process Manager
10.1.2.0.2
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

6. Technical Requirements (cont)
EBS Patches
3480000 5516007
4712852 5592440
5086184 5602850
5234512 5604046
5309217 5610823
5470818 5705760
5560931 5716962
5532582 5711923
OTM Patches
5730027
BPEL Patches
4869010
5638122
(Current as of February 2007)
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

7. Data Flows - Terminology
EBS Delivery = OTM Order Release
EBS Trip = OTM Planned Shipment
EBS Service Levels = OTM Transport Modes
EBS Org ~ OTM Domain
EBS Concurrent Process ~ OTM Automation
Agent
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

8. Data Flows – Rate and Route Estimation
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

9. Data Flows – Sales Orders to Shipments
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

10. Data Flows – Freight Invoices to A/P
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

11. Data Flows – Inbound POs
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

12. Lessons Learned – Planning & Communication
Planning is Critical!
Set Realistic Expectations
OTM is new to Oracle Family
First release of EBS / OTM integration
Two Apps = Two Teams
Implementers must Cooperate
Power Users will use both Apps
Gap Analysis is Critical!
Does it fit your business process?
Customizations may be required
Have Well-Defined (Strict) Process Flows
Apps do not limit what the user can do
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

13. Lessons Learned – Data Sync Issues
EBS is the data master!
Data Mapping based on EBS assigned IDs
Naming Conventions (car-*, loc-*, etc)
Environment Migration
Data Entities that require manual sync
Time Zones
Units of Measure
Item Masters / Carrier Equipment
Service Levels / Modes of Transport
Carriers *
Rate Offering configuration in OTM
Refnum and Servprov Qualifiers for A/P
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

14. Lessons Learned – Process Flow Issues
Changes to Ship Date
Needs to be done in EBS **
Changes to Warehouse / Ship-From
Needs to be done in EBS
Changes to Carrier
Needs to be done in EBS
Ship-Confirm in EBS – No Turning Back
In OTM, not locked, even after POD
WMS
Changes Order Lines – new Delivery
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

15. Lessons Learned – Pitfalls
Team Communication
Data Synchronization
Lack of Documentation
Installation / Configuration
Best Practices
Process Flows
Can cause double-booking
Error Handling
EBS => BPEL => OTM and back
Time spent debugging issues
Error / Failure Notification
Finding Qualified Help
Product Experts
Support
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

16. Q & A and Discussion
Questions?
Integrating EBS and OTM: Process Flows and Pitfalls MavenWire

17. Thank You!
MavenWire