This appendix contains these topics:
The field, Current Period, in the Override Default Information is blank and the Financial Reporting Date has not been updated to the correct period.
Verify the correct balance by viewing the account online in the Account Balance by month program (P09213).
Verify the account balance is in sync with the detail transactions by running the Repost Account Ledger program (P099105) in report mode.
Verify there aren't any additional accounts in the F0902 balance file by running the Account Balance to Transaction Report (P09705).
To locate the transactions that are included in an account balance, activate the Balance Auditor feature in FASTR.
Verify that cell calculations are not set up which may be overriding an amount on the report.
Verify the FASTR setup is correct for the information you are trying to obtain.
If you are getting inception-to-date amounts for your P & L accounts, check the column amount code. Instead of using IC (for inception-to-date), use YC (for year-to-date balances) or AB (for account balances). Inception-to-date amounts are stored for profit and loss accounts, but most online programs (such as Account Ledger Inquiry P09200) are hard-coded not to include them.
If you are getting incorrect results due to balances of accounts with subsidiaries being rolled into balances of accounts without subsidiaries, you are probably sequencing separately on object and subsidiary. The program will include all subsidiaries in the object account, then print them again for each subsidiary. By changing the sequencing in your General Specifications to make the object and subsidiary the same sequence, the account will print once.
If you would like the system to print business unit category code descriptions, rather than the alternate descriptions that can be set up for FASTR, change the FASTR Category Code processing option from a value of A to blank:
Go to menu G8331
Choose the program, Category Code-ProcOption Only, and press F18 to access the processing option. If you press Enter, nothing will happen.
Change the processing option from A to blank and press Enter to exit.
If your FASTR report is not printing specific data, the most common reason is a mismatch of values entered in rows and columns, or entered between your columns and General Specifications. Often, the problem is with the Fiscal Year (FY) and Ledger Type (LT) fields.
The fiscal year field in the row report always defaults in a value of asterisk (*) unless the Row Code is T or C (Text or Calculations). The only time this field does not have a value is when you manually override the value in the field. When the program is run, the * directs the system to locate the fiscal year from the Column Specifications.
If the Fiscal Year field in the Column Specifications is blank, the system determines the fiscal year from the Current Period entered in the Override Default Information.
If the Current Period in the Override Default Information is blank, the system locates the Fiscal Year from the Financial Reporting Date. If Company is defined as the first sequence in the General Specifications, the fiscal year is determined by the financial reporting date (menu G10, Set Financial Report Date, P001019) for each company defined. If Company is not the first sequence in the General Specifications, the system retrieves the fiscal year from the Financial Reporting Date for company 00000.
You can define your fiscal year in specific rows. For example, one row might be defined for FY 99 and another row for FY 00. This will print a result as long as you define the Fiscal Year in your Column Specifications as *. If the fiscal year in the column is defined as 99 and rows are defined for fiscal year 00, the report will not print a result, because F0902 records do not exist that meet both criteria: FY = 99 and FY = 00.
If you have a fiscal year defined in your row, but leave the FY field in the column blank, the report will print a result as long as the fiscal year defined in the row is the same as the one established in the Set Financial Report Date program (P001019). For example, if the fiscal year on the row is 99 and the Financial Reporting date is for fiscal year 00, the report will not have a value. Records do not exist that meet both criteria: FY = 99 and FY = 00.
If you leave the FY year in the row blank, the system defaults to whatever fiscal year is in the column. If the fiscal year in the column is blank, the system determines the fiscal year from the Current Period entered in the Override Default Information.
If the Current Period in the Override Default Information is blank, the system locates the fiscal year from the Financial Reporting Date.
If you enter a row for any row type other than T or C, the ledger type defaults in as *. If you leave the field blank in the Column Specifications, the value of AA defaults into the field.
The only time you can have a mismatch of ledger types is when you specify the value in the row, but have a different value in the column. For example, if you enter BA as the ledger type for the row, but the column is defined as AA, you will get no data because of the mismatch of the ledger types.
General Specifications determine which F0902 records will be considered for the report. The information entered in the columns and rows determine which of those records will print on the report.
If you do not define values for the Fiscal Year or Ledger Type in your General Specifications, records for all fiscal years and all ledger types are considered. If you specify a different fiscal year in your General Specifications than you do in your column or row specifications, you will receive no data on your report.
For example, if you specify fiscal year 00 in your General Specifications, but enter fiscal year 99 in either a column or row, the report will not print a value.
You can use Wildcards in conjunction with both ledger types and fiscal year values. A ledger type entered as *A tells the system to consider all records for ledger types that end in A. Thus, you could get a balance of AA, HA, PA, BA ledger types for the account specified. If you set up fiscal year as 9* all records for fiscal years 90 through 99 for the account specified will be added together to return a result.
If you would like the account description printed, include the subsidiary as a sequence in the General Specifications.
To print the account number as well as the account description, enter a value of Y in the field, Print Descriptions with Keys, located in the Override Default Information.
If subsidiary information is not printing on the report, then check your Row Specifications to see if the object account has a trailing period. A trailing period indicates that subsidiary information should be suppressed. Remove the period to print subsidiary information on the report.
Subledgers must be defined with 8 characters. For example, if the subledger value entered into the FASTR row specification was 1001, the report would not print anything for that row, because the value should be entered as 00001001 (8 characters, zero filled). If the 8 characters are not filled, then the subledger information will not print.
There are several ways to produce a consolidated report for several companies. The key is to choose a field that is common to all records for all companies to be consolidated and sequence on that value. Possible solutions are:
Sequence on a category code that is not being used. Since the value blank is the same for that category code for all companies, sequencing on the category code will produce a consolidated report.
Add the same value to a category code (for all business units for all companies) and sequence on that value.
If the information desired is for the same fiscal year, you can also sequence on that field.
| Topic | Description |
|---|---|
| Data selection values | There is no way to add more fields to the data selection. Other options would be to use category codes, or to use "Not Equal to" rather than "Equal to". You can also set up multiple FASTR versions, and then download them to your PC, and combining them into a single Excel report. You also may want to consider a broad range in the General Specifications, and then use the Column and Row Specifications to narrow down the data that you receive. When working with column or row specifications, you may also use multiple hidden specifications, and combine them for a printing total. |
| Sequence | For row reports only, a page break may be suppressed by entering an S in the PageBk (Y/N) field in the General Specs on the last (highest) |