I just found this workaround for the CS currency rounding issue.
Found it on the FRx forum at microsoft.public.com. By default, FRx adds the currency format to the 1st row of every report. SP10 has not been allowing the rows with CS to round properly.
The commenter was wondering why some of her reports rounded on the 1st row and some did not. I have wondered the same thing! I haven’t tested this yet but wanted to get it out. Here you go:
“I discovered one difference that apparently changes how the 1st row currency symbol and the whole dollar rounding from the catalog affects the report. If the 1st line of the row is blank or has a DES format code, the 1st row of data rounds correctly with the currency symbol. If the 1st line of the row contains data it gives the decimal places and needs the workaround and will show $0 even if “Display blanks for zero amounts” is checked.
So I just added a blank NP line in the row and my first line now includes the $ and rounds to the whole dollar. Don’t know why that works but I’m thankful it does!”
I’m thankful that the commenter shared her discovery!
If you want to know more about the currency rounding issue, please see my post at FRx SP10: The Good, The Bad, and the Ugly.
Today’s post is a very quick overview of the setup of FRx’s currency translation module.
This is an extra-cost add-on module used to, uh, translate foreign currencies.
[click to continue…]
This post is another that comes from Jeff Cutting, a lead developer of FRx.
It was originally posted as an answer to a question about FRx Security, Solomon and SP10 (in my SP10 post), but there is plenty of non-Solomon specific information. I thought it valuable enough to have its own post! Thank you Jeff. —Jan
I’m going to give an overall explanation of FRx security to help anyone that might be interested (for any GL), and then I will drill into the specifics for Solomon. [click to continue…]
Earlier this week, I wrote about how to divide headcount by the period number.
This post can be found at How To Divide Headcount by the Period Number. In the realm of “there’s more than one way to get downtown”, today I’ll revisit using the period number in calculations. Today’s method uses a link to Excel to pull in the period number.
This writeup is provided compliments of Jeff Cutting, a lead developer of FRx and its successor, Management Reporter. THANK YOU, Jeff! [click to continue…]
This is an alternate way to do a Percent of Sales report.
This post is also compliments of Rick Tenorio, moderator of the newsgroup at microsoft.public.frx. Normally in departmental reporting, a P&L calculates percentage of sales by using the sales for that department. For instance, the Welding department calculates percent of sales by using Welding revenue. In this report, however, Rick’s client wanted every department to calculate percent of total sales.
This is a “% of Sales” report. Per Rick, “This report was requested by a client who wanted a report that would show the % of Sales amount exactly the same for each branch of the tree. (So no rollup for the balance.) I did not have this written up in detail, so I included the FRD file and the TDB file. (The tdb file is from FRx 6.7 sp10.)”
[click to continue…]
Anybody need FRx to calculate an average?
Today’s post is compliments of Rick Tenorio. Rick is the moderator at the newsgroup at microsoft.public.frx, and he has collected a number of helpful and practical documents on using FRx. This initial post covers how to divide a headcount statistic by the period number in order to arrive at an average headcount.
Note that you can also use this technique to calculate average sales per period (use YTD revenue divided by the period number). I know a number of my clients do this in order to get an initial sense of whether their MTD revenue looks right. [click to continue…]
