|
 |
 |
 |
 |
 |
|
|
| |
|
FRX DEBUGGING AND TIPS |
 |
|
| |
| |
| |
| I have worked with various FRX version for over 10 years. The flexibility of the re usable
building blocks of rows, columns, and trees is amazing. The speed to create a
new financial report is astonishing. But still, we run across problems periodically with this great tool. I am going to examine some of the ideas
for debugging the problem FRX tool |
|
| Tip #1: Make sure you have the latest service patches installed for your frx version. |
| You can use the customersource web pages to verify what updates have been issued. |
| |
| Tip #2: Because FRX reports are created by you, they can be wrong. You need to create sanity checks for your reports, so you don’t get blind sided by issuing incorrect reports. Your Solomon Trial balance report (01.610) is a great place to start, because this one report is the most reliable reference report in Solomon. There are natural totals on the trial balance reports for Total Assets, Total Liabilities & Equity, and Net Income |
 |
| |
| Use the Select feature of Solomon reports to create versions of your Trial balance report which can tie to your FRX department reports. Create a habit of checking your results on your FRX reports before publishing them. |
| |
| |
| Tip #3: Building some row logic into your reports so that you can check for your own FRX reports. For instance, when you create a profit and loss report for an entire company, you can build in a section at the end of your row lines which looks something like this: |
| |
 |
| In line code: #6220 we are calculating the normal net income on this income statement. Because we can create a test calculation of the same net income value in row codes: 6310 to 6400, we have the chance to create a “sanity” calculation in row code: 6430. In row codes 6310 and 6325 we calculate total revenues, and in row codes: 6340 and 6370 we calculate the total cost of goods and operating expenses. Because we are using the print control NP in column F none of these calculations print out on your reports. In row code #6430 we calculate the difference between the original net income and the new net income and we only get a printed line when the value is non zero for the result. The print control codes in column F ( ie X0 and B) suppress any printout unless a non zero value is calculated. Thus we see only this additional error page printing out with a value when we have an potential error in our reports. |
| |
| |
| In the same way we can build into creating a sanity check on a balance sheet report which does not have total assets equal (total liabilities and equities). Here is a sample of the row codes which accomplishes this test: |
| |
 |
| In row 1585 we ask that a new page be inserted. Next in row code 1600 we test that the line for the total assets (ie 709) be subtracted from the line for total liabilities & equities (1510). If the report is not in balance, then we get a print out for the difference. In column F on row code 1600 we are requesting that the print control features b0 and x0 be used to print this line only if the value is not zero. In this way, we build in a simple test which allows us to catch out of balance conditions / errors on our reports; before we publish them to others. |
| |
| |
| |
| |
| Next... |
|
|
|
|
|
|
| |
| Copyright © 2007 Systematic Solutions Incorporated. All rights reserved. |
| |
| |
|
