170 likes | 328 Views
RCG/BCG Finance Integration Draft Scope, Plan and Approach February 9, 2010. Key Assumptions. Summary Functional Scope. General Ledger Scope/Strategy. Accounts Payable. Fixed Assets. Employee Expense Management. Procurement. Key Design Considerations.
E N D
RCG/BCG Finance Integration Draft Scope, Plan and Approach February 9, 2010
Key Design Considerations • Implement RCG Operations in USA in existing Operating Unit or create second US Operating Unit for RCG (Legal entity considerations are key) • AP, AR, Quoting, Sales Order Entry, Pricing, Procurement are all managed at the operating unit level in Oracle. • To support AP processing in Canada for RCG, we will need a second Operating Unit for Canada • Method to apply MC accounting to transactions generated from legacy applications (R6000, etc) • Develop custom mapping utility to map from RCG COA to MCG COA prior to posting to Oracle GL – this is similar to the approach currently used in BCG for plants not yet on Oracle EBS. Phase 1 • License and utilize Financial Accounting Hub to create and apply accounting to transactions from external systems. Potential Phase 2 • Technical: Re-implement RCG interfaces on Oracle SOA (BPEL/BAM) • Re-engineer point to point and monthly interfaces (if any) to use Oracle SOA and process data daily or more frequently
Finance Integration - Instances Required Applications • R6000 (MRCG legacy OTC/Manuf) • JDE Legacy for MRCG • Oracle EBS (inclSabrix) & SOA Environments • Development • Test • Integrated Test (use for training also ?) • UAT (re-use Integrated Test?) • Stress Test Event (Focus is month close/reporting; and interfaces)
Security • Leverage Oracle EBS already implemented • Augment for iExpense • Augment for special international requirements
BI for Finance • GL (source from Oracle GL) • AP (source from Oracle AP) • AR (From Oracle AR for Builder Operations and R6000 for retail operations)
Adopt BT2 processes for executing project • eRoom for Deliverables • Weekly Status reporting and meeting • Develop detailed project schedule • Test Director for managing test scenarios • Change control
Decisions • Start Date – asap • Go-live Date(s) • Implement GL feed (from JDE GL) for end May ? • Shut-off JDE for GL and AP after June close; redirect all RCG legacy applications to Oracle EBS from July 1 • iExpense go-live in July • Work Location(s) • Co-location for design phase • Co-location for key testing weeks (~3) • Consultants spend more time at Middlefield than Adrian • Extended Team for Testing