Transcript Options for P2P Integration with R11.03 Projects

Chart of Account Conversion
May 21, 2009
Presented by Matt Adelman
1
INTRODUCTION
Matt Adelman

•
•
2
Independent Consultant
Oracle Financial and Projects implementation
and upgrade experience
Why change a Chart of Accounts?
3

Move to a single global chart of accounts or a
single global instance

Acquisition of another company

Running out of segment values

Reporting requirements have changed

Values are out of range

You want to track the business differently
Options for Chart of Account Change
4
1.
Oracle recommends a complete re-installation OR
hire Oracle Consulting Services to complete the
modifications
2.
Hire other consulting firms to complete the
modifications
3.
Flexfield accounting software
www.flexfieldexpress.com
COA Conversion Goal



5
Client requested to adopt international parent
company’s chart of account after parent
company installed Oracle globally
Client originally installed Oracle Apps in
1999
Limited future/growth built-in to current COA
COA Conversion

Current COA consisted of the following GL
Segments, six in total:
–
–
–
–
–
–
6
Company (2)
Account (5)
Department (4)
Product Family (3)
Product Detail (4)
Product Subdetail (3)
COA Conversion

Parent company COA consisted of the following GL
Segments, eleven in total:
–
–
–
–
–
–
–
–
7
–
Company (6)
Account (6)
Cost Center (6)
Profit Center (4)
Product Application (3)
Product Family (5)
Project (8)
Intercompany (6)
Future1 (8), Future2 (3), Future3 (3)
COA Conversion


8
Project task force created to review all
options for a chart of account conversion
Ultimately, decided the most cost effective
and efficient was to purchase Flexfield
software and complete project
COA Conversion



9
Majority of work was planned with internal
resources
One financial consultant was hired
Cost of Flexfield software was approx
$15,000
COA Conversion

Background
–
–
–
10
Client installed ‘vanilla’ Oracle with just a few
exceptions
Project plan called for a six month implementation
from beginning to end
Planned for mid-month conversion and not on
quarter or year end, due to audit and financial
reporting
COA Conversion



11
Flexfield provided step by step installation
and user instructions (varies depending on
how each company has installed and uses
Oracle Apps)
Project team mapped old GL segments to
new GL segments
Installed software and tested conversion
twice before user acceptance and regression
tests
COA Conversion
Example of pre-steps to be completed prior to conversion
using software:

–
–
–
–
–
12
Create FFIELD schema table space as required in user guide
Create new Chart of Accounts
– Create new Accounting Key Flexfield
– Setup segment structure
– Create value sets – assign to segments in KFF
– Define Flexfield qualifiers
Install Flexfield Express software
Clear ALL interface tables
Turn off concurrent manager, lockout users
COA Conversion
Example of post-steps to be completed
after conversion:

–
–
–
–
–
–
–
–
13
–
Create FSGs
Reconcile to pre conversion #’s
Create cross validation rules
Create security rules
Create Aliases
Parent/Child values
Report Sets
Verify all setup options where GL string exist
Modify ADI templates for Journal Entries
COA Conversion

Conclusion – Project was a Success!
–
–
14
Client was very pleased with the outcome
Zero Issues since cut-over (February 2009)
Project Learnings

Overall, my client was vanilla and did not demand much effort
outside of a couple part-time IT resources, but I was the only
fulltime resource on the project. Users were involved in many
of the early efforts and testing, but on a limited basis. The
following activities took the most time and effort by our project
team as part of the chart of account conversion:
–
–
–
15
Segment Mapping – do not allow too many hands in this effort as
everyone wants to see data in multiple ways to get the information
they need. This effort was by far the most difficult and took the
longest of any
FSG Creation and Reconciliation
Identification of custom objects, reports
COA Project Benefits






16
All line drill down/back capability works after conversion from
module to module (No loss of history of any kind)
Less costly and more efficient than reinstall of Oracle
Applications
Very minimal user impact outside of learning new segment
mapping values
Can complete multiple COA conversions as needed with
software purchase
Excellent customer service from Flexfield staff as issues arose
Protects your original investment in your company’s Oracle
Application
COA Project Questions




17
Process?
Issues?
Lessons Learned?
Others?
THANK YOU!
Contact
Matt Adelman
[email protected]
18