Topics Map > University of Chicago > IT Services > Business Systems

Business Objects - Webi - IRF Reporting Best Practices

This article gives a number of items to remember when querying financial (FAS) data using IRF Business Objects.

This article gives a number of items to remember when querying financial (FAS) data using IRF Business Objects.

General Tips for Reports

  • Alert: 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.

  • When saving your document(s), always use Save As This 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 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.

  • Data levels with measurements by subject area:

    • Financials: Account, Sub-Account and Transaction

    • Payroll: Person and Job

    • HR: Person, Job and funding account

    • GEMS: Expense Report, Transaction, Level 3 data/allocations/attendees/IRF Ledger transactions

For Financial (FAS) Reporting

  • Alert: Do not 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, 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 Subaccounts

  • Totaling transaction amounts may not tie to account or subaccount 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 should not be totaled.

  • Use Detail Amt measures for account and subaccount summaries, You should only use the Total Amt measures if using Detail Amt results in pulling too much data.

For Payroll Reporting

  • When you are using Person data by itself, don't include any calendar objects. 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.




Keywords:Business_Objects, IRF, Financials, HR, Payroll, GEMS, BO, Query, WebI, Cheatsheet, Quicktips   Doc ID:16966
Owner:James I.Group:University of Chicago
Created:2011-02-17 19:00 CDTUpdated:2017-03-03 16:17 CDT
Sites:University of Chicago, University of Chicago - Sandbox
Feedback:  4   1