Breadcrumbs
Home / Blog / Chart of Accounts Structure / Into the Future (And Back Again)Written by Helene Abrams Sunday, March 16 2008
Designing an accounting flexfield is one of the most difficult processes in an Oracle implementation. A “good” chart of accounts has the following criteria:
- The segments support important aspects of the business.
- You are able to report on critical business components with standard reports without resorting to spreadsheets.
- There is enough room to expand within each segment.
- FSGs and other reports are easy to create.
- Summary accounts and rollup groups fall naturally within ranges.
- Information in the chart of accounts is not repeated from other modules.
- There is only one type of information in each segment.
Answering the 4 questions “Who?”, “What?”, “Where”, “Why”, and possibly “How” helps identify segments that will give your accounting flexfield the ability to classify each transaction. When transactions are classified, then it is easy to report on the relevant aspects of that transaction, to group that transaction with other similar types of transactions, and to differentiate the parameters of the transaction. “Who” can be represented by a legal entity and intercompany segments and a cost center, a department or business unit segment. An Activity segment can answer the “What” question. “Where” is represented by a Location or Region segment. “Why” is answered by the natural account segment (e.g. a lease expense, revenue from sales). “How” is often used in government or fund accounting to identify the fund from which the money is coming.
If your segments are designed to answer the who, what, where, why, and how questions, and within each segment you have designed different levels of roll-up groups, then you will easily be able to analyze the transactions in different ways and in as much detail as you want without using spreadsheets. The most detail is in the lowest level of rollup groups. If you want to analyze the big picture, report on the parent values. When designing the values be sure to allow enough room to grow within each rollup group. I usually suggest incrementing by at least 5 within each group, and by 10 if the group is likely to be a high growth area. For example, if you have a location segment, allow enough room to add ten additional values between each of your lowest levels. Your location hierarchy might look like this:
10000 US11000 Midwest
11100 Detroit Metropolitan Area
11110 Ann Arbor
11120 Canton
11130 Plymouth
20000 Canada
When you are creating reports, you can report on the parent values (Detroit Metropolitan Area, Midwest, or the entire US) to track the right information for your analytical needs. When creating rules cross validation and security rules and FSG reports, you can include a whole range of values in your rule or create a master report for the entire range and then exclude specific values if needed. Many of our customers have reduced thousands of cross-validation rules to under 50 rules by re-ranging their values.When designing your segments, you should have information in one place. If you are implementing Oracle Projects modules, there is no need to have a project segment in your accounting flexfield. You will get all the information that you need from reports in the Projects modules. If you are implementing Receivables, then there is no need for a customer segment. If your cost center has the same type of information as a business unit segment, there is no need to implement both. Thinking about the category of information and putting only one type of information in one place reduces the maintenance of keeping information accurate in two places, and it reduces the possibility of introducing errors into your accounting. Introducing a “Future” or “TBD” segment increases the probability that multiple types of information will be held in a single segment. For some, the future segment might mean a sub-account or local account, while for others, that same future segment might represent a particular tax code.
When you first implemented your e-Business Suite, you may not have thought about all of these things in the design of your accounting flexfield. The good news is that now, with FlexField® software, you can redesign your chart to meet your current business needs, and allow for growth to meet your future needs.
So, where do I start? Learn more about FlexField software.
| < Prev | Next > |
|---|
Related Articles
- Putting Numbers in Boxes: Spring Cleaning for Charts of Accounts - Part I
- Basic Accounting for IT - Part I
- Details and Setup of Other Flexfields in Oracle E-Business Suite
- If IFRS...Then, Part 2: 5 Best Practices in Designing a Chart of Accounts in Oracle E-Business Suite
- Basic Accounting for IT - Part II
Enter your email address to sign up for our Newsletter
May Puzzle
David is often referred to as Rainman due to his peculiar ability to effortlessly figure out a certain date's day of the week. He recently displayed this talent when I asked him if there was a conflict with the upcoming Fuzzy Dice Conference and our weekly court-ordered community service. He asked the date of the convention. It was April 20th, 2012.
"Oh, that’s a Friday," he said, effortlessly. "And your sentences have you committed for the next few dozen Wednesdays so you'll be able to go." And of course he was right.
One day a few weeks ago I asked out loud in the office about the date June 5th. And of all people, my brother Tommy piped up and said "Oh, that's a Tuesday."
"That's right," said David.
Well how about Otcober 3rd?
"That's a Wednesday," said Tommy. Then I asked about Christmas Day 2012.
"Oh, that's a Tuesday." David nodded in agreement.
Do we now have two rainmen? Or had Tommy figured something out?
Solution
Here's what was going on. Tommy was using something called anchor dates. And these dates apply to each and every year. April 4th, or 4/4 we’ll call it from now on, June 6th or 6/6, 8/8, 10/10, 12/12, are all the same day of the week, each and every year.
So too are 5/9 and 9/5, May 9th and September 5th. So too are 7/11 and 11/7, and all the above dates are the same day of the week, as is the last day in February, Leap Year or not. And they’re all the same day as January 4th, it would otherwise be January 3rd, but this was a leap year, and that’s changes the anchor day from January 3rd to January 4th.
Tommy also knew that New Year's Day was a Sunday. He was sobered up by then. And he knew it was a Sunday because Christmas was a Sunday in 2011, so New Year's Day is a Sunday, so the Anchor Day for 2012, January 4th, has to be a Wednesday!
So if that's a Wednesday, then 4/4, 6/6, 8/8, 10/10, 12/12, 5/9, 9/5, 7/11, 11/7, and February 29th are all the same day of the week, and they're all Wednesdays. So when I ask for example, about October 3rd, he knew October 10th was a Wednesday, 10/10. So 10/3 must also be a Wednesday. 12/12 is a Wednesday in 2012, so it’s 12/26, which is two weeks later. So 12/25, or Christmas Day, must be a Tuesday.
Success Tips for Oracle Project Management
- Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
- Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
- If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
- Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
- Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
- Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
- Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
- Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
- Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
- Include governance, risk, and compliance management as part of the project plan.
- Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.
The Analyst Corner
John Van Decker, Research VP of Gartner, states:
"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."
Popular Articles
- Organization Setup in R12
- If IFRS...Then, Part 2: 5 Best Practices in Designing a Chart of Accounts in Oracle E-Business Suite
- 11i to R12 Decision: Upgrade or Reimplement?
- Designing a Global Chart of Accounts and Taking Advantage of Oracle® E-Business Suite Release 12
- Moving from GAAP to IFRS with Oracle EBS





