Agility by Design - eprentise Blog

The Master Row Set: Managing Financial Statements

PDFPrintE-mail

Building a master row set for your Financial Statement Generator (FSG) reports will save time, provide agility and consistency, and allow the business users the ability to quickly create new reports "on-the-fly". In this article, we focus on how you can get the most out of reporting by employing a master row set in FSG. You’ll learn the secrets to keeping FSGs to a minimum and generating a variety of reports faster by focusing on the built-in reporting features of EBS. A master row set eliminates the requirement of rewriting each report in order to get the particular information you need at a certain time, allowing you to reduce the time spent creating custom reports from days to under an hour.

Read more: The Master Row Set: Managing Financial Statements

 

How to Generate FSG Reports - Part II

PDFPrintE-mail

In the second tip of the Financial Statement Generator (FSG) report series, we continue to explain how FSG reports can be created that are reusable and easy to maintain. The FSG's are powerful tools that can be used to produce a variety of traditional reports such as balance sheets, profit and loss statements, income statements, expense analyses and gross margin reports.

Standards

Develop master report components that can be combined and reused for generating different reports. Use meaningful names that describe the contents of the component by the row set name. These do not print on the report.

  1. All names must be unique. For example, do not have a row set named "Balance Sheet" and a report named "Balance Sheet".
  2. Do not use names such as "Test Row Set" or Test 1.
  3. Row Set Names identify which rows are included in the row set. For instance, a row set name might include "Summary of Revenue and Expense Accounts". The Row Set Name should be followed by an "R" to distinguish it from the report name.
  4. Column Set Names indicate the type of report such as "Company Consolidation", "Rolling Monthly", or "Budget/Variance Comparison".
  5. Content Set Names should identify the sort criteria, such as "Cost Centers 100-500" or "Company 01".
  6. Row Order Names should state which row order display characteristics will be used, such as "Cost Center and Account Values" or "Account Descriptions".
  7. Report Names should be similar to the row set name ("Balance Sheet," or "Expense Analysis"). Report Set Names should reflect when the group of reports are usually run, such as "Month-end Closing", "Yearly Audit", etc.
  8. Row and Column Names do not print on the report. They are used primarily for identifying the row or column when doing calculations. Therefore, the row name should be descriptive of the type of row (assets header, cash title, A/R detail, shares outstanding hidden, equity calculation, expenses total) or the type of column (Q1, Company 02, YTD, total, etc.)
   

How To Generate FSG Reports - Part I

PDFPrintE-mail

Learn to create Financial Statement Generator (FSG) reports that are reusable and easy to maintain. The FSG's are powerful tools that can be used to produce a variety of traditional reports such as balance sheets, profit and loss statements, income statements, expense analyses and gross margin reports.

There are many time-saving ways to construct and test the reports. Once the "standard" reports are developed, more sophisticated reports can be generated.

Overview

Each report is made up of several components. Each component is featured on a screen and has many fields that allow for a great deal of flexibility. Each screen allows the user to input display characteristics, state override segments, input offsets, and add levels of detail. In order to successfully create uniform, reusable reports, it must be determined where and how the different features of the FSG will be used.

Financial Statement

Here is the breakdown of a financial statement:

  • Rows – Detail of the report (row headings, accounts or flexfield assignments, calculations, totals)
  • Columns – Different periods, companies or consolidations. Usually, pre-defined column sets work with minor modifications.
  • Report – A single combination of a row set and column set with an optional content set and an optional row order.
  • Content Sets (optional) – Grouping of the same row sets and column sets sorted by a flexfield segment.
  • Row Order (optional) – Display and sorting characteristics of rows in a report. Used primarily to insert the segment value (like account number) or to utilize the description of the segment value.
  • Display Set (optional) – Used to block out ranges of rows or column sets simultaneously.
  • Report Set – A group of reports that are run together. 

Read more: How To Generate FSG Reports - Part I

   

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

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?

Show solution...

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."