|
|
a |
|
BAIRS Core Reports
a
Core reports are recommended for monthly
use by departments. You can click on any report name below to go to
the description of that report. Additionally, we recommend that departments
run all three of the recommended summary reports the first time and then
decide which one (or two) to use on a monthly basis. For more information
on this aspect of BAIRS, you can also enroll in one or both of two forums
on Reporting Tools: one on Resource Management and one on Verification procedures.
Both are available in ICE
(on-line enrollment). For a description of all the reports in BAIRS,
see the BAIRS Report List.
Recommended reports fall
into these three categories:
Monthly
summary reports to manage departmental resources:
(We recommend you choose
one and use it consistently.)
- GL_Sum_by_Account_L4_BUDSUM
This report includes the
BUDSUM or rollup accounts, thus distinguishing balances by Academic Salaries,
Staff Salaries, Computer Equipment, Domestic Travel, etc. within combinations
of org-fund-project-flex-prog.
- GL_Sum_by_Account
This report provides more
detailed account information than GL_Sum_by_Account_L4_BUDSUM but less
of the full chartstring. The report summarizes balances by BFS
account (i.e. lab supplies vs. general supplies) with subtotals by the
BUDSUM or rollup accounts. But the report summarizes these balances
by only one or two chartfields rather than the five used in the Actuals
to Tempbudg report. So, you can get total expenses by account
for each fund, each org, each org-fund, each project, each flexfield,
or for all parameters. That last option means it's a summary by
account of ALL the data you requested in your parameters.
Note: We recommend that you use
a summary report to manage your resources and use detail reports, such as
the Detail_Standard or Detail_Expanded reports or the Encumbrance and Pre-Encumbrance
reports, to investigate anomalies you see on your summary reports.
Monthly
reports to verify/reconcile external activity:
- GL_Detail_Transaction_Verification
Designed to help departments
verify or "reconcile" the transactions affecting their orgs which orginated
OUTSIDE of their processing unit. Departments are strongly
encouraged to use this report for a monthly review of transactions (rather
than the Standard or Expanded Detail) as the majority of transactions
in the department have already been prepared, reviewed and in some cases
approved by departmental staff. This report includes only those
transactions which did not go through this process.
Please note that you can specify different levels of the organizational tree for use in determining a transaction's status as one that should be verified (should appear on the report). The default value is to show transactions which originate outside the L4 Department, but it can be changed if you work in a subunit of a department and want all transactions which originate outside of your L5 or L6 unit to be considered "exceptions" for verification.
- Payroll
Exception Report
Departments are strongly encouraged
to run this report on a monthly basis to identify Payroll transactions
which have not posted properly. Departments should not attempt the
corrections themselves, but rather contact Payroll (payhelp@uclink) and
provide the correct chartstring information to them.
Monthly
reports for "customers":
Last updated:
11/15/04
|
