integrating ebs and otm - process flows and avoiding pitfalls.pdf
TRANSCRIPT
MavenWire
Integrating EBS and OTM:Understanding the Process Flows and Avoiding Pitfalls
OTM SIGUser Conference ‘07
July 2007
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Agenda
High Level Overview of the EBS/OTM IntegrationTechnical Requirements and InstallationData Flows
Entity Mapping / TerminologyProcesses FlowsShared Data
Lessons LearnedQ and A / Discussion
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Objectives
Present an overview of Oracle’s pre-packaged EBS/OTM integrationShare the lessons learned while implementing with early-adopter clientsShow how to best leverage the integration flows while avoiding pitfalls and duplicate workAnswer your questions and have an open, interactive discussion
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Technical Requirements
E-Business Suite11i.10
Oracle Transportation Management5.5 CU2 (CU3 recommended)
Oracle Application Server10gR2
BPEL Process Manager10.1.2.0.2
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Technical Requirements (cont)
EBS Patches3480000 55160074712852 55924405086184 56028505234512 56040465309217 56108235470818 57057605560931 57169625532582 5711923
OTM Patches5730027
BPEL Patches48690105638122
(Current as of February 2007)
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Data Flows - Terminology
EBS Delivery = OTM Order ReleaseEBS Trip = OTM Planned ShipmentEBS Service Levels = OTM Transport Modes
EBS Org ~ OTM Domain EBS Concurrent Process ~ OTM Automation Agent
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Lessons Learned – Planning & Communication
Planning is Critical!Set Realistic Expectations
OTM is new to Oracle FamilyFirst release of EBS / OTM integration
Two Apps = Two TeamsImplementers must CooperatePower Users will use both Apps
Gap Analysis is Critical!Does it fit your business process?Customizations may be required
Have Well-Defined (Strict) Process FlowsApps do not limit what the user can do
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
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 syncTime ZonesUnits of MeasureItem Masters / Carrier EquipmentService Levels / Modes of TransportCarriers *
Rate Offering configuration in OTMRefnum and Servprov Qualifiers for A/P
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Lessons Learned – Process Flow Issues
Changes to Ship DateNeeds to be done in EBS **
Changes to Warehouse / Ship-FromNeeds to be done in EBS
Changes to CarrierNeeds to be done in EBS
Ship-Confirm in EBS – No Turning BackIn OTM, not locked, even after POD
WMSChanges Order Lines – new Delivery
MavenWireIntegrating EBS and OTM: Process Flows and Pitfalls
Lessons Learned – Pitfalls
Team CommunicationData SynchronizationLack of Documentation
Installation / ConfigurationBest Practices
Process FlowsCan cause double-booking
Error HandlingEBS => BPEL => OTM and backTime spent debugging issuesError / Failure Notification
Finding Qualified HelpProduct ExpertsSupport