Set Up Generic Variables
Print
Modified on: Tue, 21 Jun, 2022 at 10:11 AM
What This Process Does
- This setup screen controls the functionality as well as visibility of several processes within Financial Management.
Best Practice
- After changing any of the generic setup variables, the user must run updates for the Financial Management module in System Administration.
Generic Setup Variables
- Finance → Financial Management → Setup → Financial Management Setup → Setup Variables → Generic
- Each tab can be viewed and have changes made.
- Use the tables below as a guide. Each table will give a brief description of each field and box.
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Installation Date | — | — | ♦ | Display only; the date the financial management programs were installed |
| Compile Date | — | — | ♦ | Display only; the date the financial management programs were compiled |
Attributes Tab
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Current Fiscal Year | — | — | ♦ | This is the current fiscal year default; it can be changed on this screen or by choosing the Set/Change Fiscal Year from the task bar |
| Display Post Activity | ♦ | — | — | This GSV will display the option to Post Activity on the task bar for all modules that interface with Financial Management rather than just on the Financial Management task bar; this is used in conjunction with the Display Post Activity from the user's security profile |
| Display EZ Adds | ♦ | — | — | This allows a simplified version of the receipts data entry screen to be accessible; only the expenditure and revenue account type is entered |
| Skip Over Budget Warnings | ♦ | — | — | If an entry is made to an account that is over the budgeted amount, a warning will display during data entry; this setup variable will prevent the warning from displaying; it does not affect save errors as these are based on the user's security profile (budget override); it is used adding vouchers as well as journal entries |
| Budget Amendments Journal ID | — | — | ♦ | When entering budget amendments into financial management, a specific budget ID must be established for amendments so the system will store the amendment amounts and flag the account as amended |
| Monthly Hard Close | ♦ | — | — | This option makes it possible to close a given month so that no additional activity can be posted to it; if this is chosen, each month would be flagged as closed as well; from the Task bar: Financial Years/Current Month → Monthly Status tab; select the month you want to close and click the save button; any month may be unflagged so that additional entries may be posted if necessary |
| Default J/E to Cash instead of Transfer Controls | ♦ | — | — | This controls the default balance sheet code when entering expenditure (credit) and revenue (debit) type journal entries |
| Use Simplified/Combination procedures | — | ♦ | — | This option allows the receipt verification, distribution, and bank reconciliation update processes to be done in one step instead of individual steps on the receipts tab of the task bar |
| Display Legacy Information (Conversions) | ♦ | — | — | When account codes are converted to OpenRDA, this allows you to display the legacy code on the account maintain screens when you query the account masters on the task bar; should only be used if the converted account codes are different |
| In the detail query, set the Fiscal Period using the Affect Date | — | ♦ | — | When using the query buttons at the bottom of the Account Balance Inquiry screen, the fiscal period will default based on the affect date if this setup variable is flagged; when the affect date is changed, the fiscal period will default to agree with the affect date period; this is only applicable when using SW Bundle 25 (Affect Date) |
Receipts Tab
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Use clearing fund for receipts | ♦ | — | — | When the organization has multiple bank accounts, allows all deposits to be made to one bank account with automatic updating of Due To/Due From accounts |
| Use Add Bank | ♦ | — | — | System uses Add Bank Deposits instead of the standard |
| Deposits in lieu of Update Bank Rec Report | ♦ | — | — | Update Bank Reconciliation report |
| Force Deposit Date | ♦ | — | — | Forces Deposit Date to be a required field |
| Default Receipt Date | — | — | ♦ | The receipt date will default to the system date if flagged |
| Default Deposit ID | — | — | ♦ | Nothing, System Date, Deposit Date, Deposit Date/Login |
| Use Actual Receipts - Receipt Type | ♦ | — | — | This must be flagged in order to print receipts; they can be sorted by control/deposit ID or transaction number |
| Print Actual Receipts on Laser Printer | ♦ | — | — | If receipts are printed on a laser printer, this boolean should be flagged so the pages will form feed |
Reports Tab
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Use Landscape Orientation on Order Reports | ♦ | — | — | Certain reports print landscape instead of portrait so that more information can display; must be landscape orientation |
| Print Comments on Post Activity Reports | ♦ | — | — | Print comments from the Distribution report on the Post Activity Report |
Import / Export Tab
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Account Submenu | ♦ | — | — | Select to Display Import/Export Submenu |
| Journal Entry Submenu | ♦ | — | — | Select to Display Import/Export Submenu |
| Receipt Submenu | ♦ | — | — | Select to Display Import/Export Submenu |
| Setup Submenu | ♦ | — | — | Select to Display Import/Export Submenu |
| Use Munis Interface for Invoice Processing | ♦ | — | — | A voucher interface report that produces a file (munis.txt) |
Errors Tab
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Add Journal Entry Implementation Error | — | ♦ | — | Module-wide Journal Entry Errors can be added here |
| Add Receipts Implementation Error | — | ♦ | — | Module-wide Receipt Errors can be added here |
Warnings Tab
| FIELDS | Opt. | Rec. | Req. | Description |
|---|
| Add Journal Entry Implementation Warning | — | ♦ | — | Module-wide Journal Entry Warnings can be added here |
| Add Receipts Implementation Warning | — | ♦ | — | Module-wide Receipt Warnings can be added here |
| Opt. = Optional Rec. = Recommended Req. = ReqSuired |
Did you find it helpful?
Yes
No
Send feedback Sorry we couldn't be helpful. Help us improve this article with your feedback.