160 likes | 644 Views
Integration of Oracle E-Business Suite with Oracle Utilities Work and Asset Management. Session: CON5590 September 29, 2014 Marriott Marquis - Golden Gate C1/C2. Agenda. Introductions About NEORSD About AST Product Definitions Project Background Integration Lessons Learned Questions.
E N D
Integration of Oracle E-Business Suite with Oracle Utilities Work and Asset Management Session: CON5590 September 29, 2014 Marriott Marquis - Golden Gate C1/C2
Agenda • Introductions • About NEORSD • About AST • Product Definitions • Project Background • Integration • Lessons Learned • Questions
Introductions • Donice Bell – Program Manager, NEORSD • Prakash Chhatwani – Senior Practice Director, AST Corporation
About NEORSD National Environment Achievement Award 2009 - 2013 Supplier Diversity 2009 Excellence in Management 2003, 2007 Middle Market Senior Management 2012, 2013
Product Definitions • Oracle EBS: Oracle E-Business Suite (R12) Upgrade • Oracle Supply Chain Management Implementation • Six (6) Modules • Oracle Fusion Middleware • SOA and BPEL • Oracle Integration Pack (JSK)
Project Background • As Is: • Oracle EBS used for FIN and HRMS only • Oracle WAM used for all SCM, Work Orders & Asset Mgt • To Be / Goal: Move Supply Chain functionality from WAM to EBS • Oracle EBS used for SCM (Procurement & Inventory) along with Financials and HRMS • Oracle WAM used for Work Orders & Asset Mgt only • Business Driver: Need for Asset Costing in WAM (increase operational efficiencies) • Material & Services purchased for work orders • Inventory Items used for work orders
Overview of Integration • Pre-Built Integration Packs (PIPs) • Set of pre-built integrations - ‘plug & play’ interface code • Offered in 2 models based on pre-established, standardized business flows • EBS to WAM model (SCM in EBS) – chosen model • WAM to EBS model (SCM in WAM) • Integration driven by SOA and BPEL • All mapping, error handling and scheduling of interface records handled using BPEL processes • All records created/interfaced using standard APIs (in both systems)
Integration Points • Purchase Requisition Integration • Purchase Order Integration • Receipts Integration • Invoice and Payments Integration • Material Request Integration • Stock Transaction Integration • Vendor Integration • Accounts Integration • Employee and Employee Wages Integration • Catalog Integration • Store Room Integration • Checkout Integration
Lessons Learned • Planning & Approach • Identify: Integration Points, Business Flows, System of Record for Key Components (Items, Suppliers, Employees, etc.) • ‘As Is’ documentation (up-to-date) • ‘Familiarization’ - Spend the time to learn the business flows delivered (as early as possible) • Not really an ‘Out of the Box’ solution • GAPs should be identified (as early as possible)
Lessons Learned • Technology Impact • Don’t underestimate time & resources based on the concept of ‘plug & play’ • Technology is advanced and can speed up the process but it doesn’t replace the need for • Timeline – ensure adequate time is provided to: • Build test environments • Identify GAPs • Test and disposition GAPs • Resources - skillset and knowledge of the technical components and products • Technical resources – SOA • Functional resources – Oracle EBS/Oracle WAM • Subject Matter Experts – Business Flows
Lessons Learned • Testing • Plan for multiple test iterations • Include unit tests, system integration tests and even performance tests • Involve business and end users early on in the testing process • Provide for time between testing iterations to make decisions and updates • Test complete business flows between WAM and EBS for exception handling