Topics Map > University of Chicago > IT Services > Business Systems
Business Objects - Reporting Best Practices
This article gives a number of items to remember when querying financial (FAS) data using IRF Business Objects.
For Reports in General
- When saving your document(s), always use Save As, it gives you the opportunity to change the name of the document and preserve the original.
- Before modifying a report tab, make a copy of it; right-click on the report tab and select Duplicate Report.
- Use meaningful names for documents, reports, tables, variables, data providers, etc. This makes everything easier to understand both for you and other report users.
- Make sure to use measures that match the lowest level of data so that measures are duplicated on each row of resulting data and aggregate improperly. Data levels with measurements by subject area;
- For Financials - Account, Sub-Account and Transaction
- For Payroll - Person and Job
- For HR - Person, Job and funding account
- For GEMS - Expense Report, Transaction, Level 3 data/allocations/attendees/IRF Ledger transactions
For Financial (FAS) Reporting
- Don't combine SL and GL data in the same data provider. They are different types of data and when you refresh your data it will run for a long time/ timeout and/or return incorrect results.
- Always have at least two of three of the condition types listed below in your query, there is a limit to the amount of data you can pull into your document and it will run faster if you place boundaries on the data you request:
- Organization (Exec, Dept, Sub-Dept or Sub Sub-Dept)
- Date (Calendar or Fiscal Year/Month) - You almost always want some kind of Date condition!
- SL or GL Account(s) and/or Sub Accounts
- Totaling transaction amounts may not tie to Account or sub account summaries, you will need a good understanding of transaction entry codes to know what codes should be excluded. If you are using the Transaction Tracking (TT) universe there is a condition under SL Transactions | Entry Cd called Cash Receipts/Disb & Transfers that will exclude all transaction amounts that shouldn't be totaled.
- Use Detail Amt measures for account and sub account summaries, Unless you are pulling to much data, then and only then use teh Total Amt measures.
For Payroll Reporting
- When using Person data only, don't include any calendar objects. The Person data is not historical and will be repeated for each date selected.
- Always use calendar and organizational conditions in your data provider, there is a limit to the amount of data you can pull into your document; it will run faster if you place boundaries on the data you request.