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.

Tip #4: Compacting your FRX specset database:

Frx stores all its report data in a database; external to Solomon. On a periodic basis, say bi monthly, you should compact your spec set database. This task is very simple, but often overlooked by end users. To compact your frx database you choose from the main menu File, then the menu choice : Compact FRX database, then current spec set database. This screen shot describes the location of these menu choices :

After successfully compacting the database, you will get a simple message like:

Tip #5: Your report worked previously but now it is giving you bad data.

If you have say one column on a report which is giving you bad data, while all other colunmns of the report are properly presenting data, I recommend you review the logic of the problem column in the column definition. If this column definition looks okay, I have seen the problem of the bad data being reported become correct by deleting and re entering the column from the column building block. If this solution works, make sure you save your frx data.

Tip #6: Saving your report FRX definitions

FRX is a third party software, which is typically used to create all of Solomon financial reports. The logic for the FRX reports is not included with the Ms sql data for Solomon. Therefore it is critical that you back up this data to a safe spot whenever you update or change your financial reports. The location of your data may vary depending on which version of FRX you are using. Therefore these instructions may need to be modified for your particular company; and how FRX was installed. Typically, the FRX programs and your FRX database are stored where ever the Solomon modules files are stored. In a multi user environment, these files are stored typically on the Solomon server in a sub directory below Solomon IV called FX, FV, FD or FP. The multiple subdirectories result from the various versions of FRX, which you may be using. Using only one of these four sub folders has any data or programs in it. This is likely to the also where your frx report definitions are also stored. Check with your VAR if you are not clear how FRX was installed. After locating the desired folder, just make sure this folder and all of its sub folders are backed up. (Typically the data is stored in the sysdata folder). I recommend you keep a copy of these report frx folders on both your server and your main local workstation for your power FRX user.

Tip #7: Always turn on Recalc of GL indexes:

I have found that the simple trick of always turning on the flag to recalculate FRX gl indexes greatly improves the accuracy of the reports. This flag is found in the catalog are under the field called: report date. Clicking on the black down arrow next to the report date, will bring up this subform:

Click the small box near the center of this screen which says: Rebuild FRX GL indexes. Always have this box checked prior to running any reports.

I hope these tips are useful. You have a great tool with FRX. Use it.