SAP BusinessObjects Report Design Usability Checklist – Comerit Labs

/ Item /
Fonts
Commonly available fonts like Times or Arial is used.
The text is legible (fonts no smaller than 8pt).
The header and footer are in the same font.
The body of the report is in one font.
Header
*The title describes the scope of the data (for example, organization wide, team specific, Entry/Exp level) and any conditions in the report (for example, term, fiscal year, department ID).
The title states the time period covered (for example, term, date range, as of date) for date related information.
The title indicates how the data is grouped or arranged.
The last execution date is in the upper right, labeled "Last Refreshed:”
Any dates that are included are clearly labeled (for example, Last Execution Date, Last Load Date, Last Date Printed). Avoid using Current Date. This prints the system date but is not tied to the refresh or run of the query in any way!
When appropriate, the user response (=UserResponse or =ReportFilter) is echoed in the report title or report body.
Report Body
The report block is left justified.
There is a minimum of 0.5" margin on all sides.
The columns of data are arranged in logical order (English speakers read left to right).
*The data has been purged from the report.
Columns of numbers are right justified.
If a legend or annotation is used, it is understandable and in an appropriate font.
For data that spans multiple pages, section breaks are set to keep data and titles together when possible.
Footer
*The document name (=Document Name) is in the lower left corner.
The page number is formatted as "page # of #pages" and is in the center of the footer.
The page number is in 10pt font or less.
The report revision date is in the lower right, labeled “Rpt Rev,” with the date formatted as month/year (for example, Rpt Rev 12/02).
Readability & Accuracy
*When prompts are used, they model how the data should be entered. For example, “Enter the term (e.g. 1760)”
*Any values saved within prompts are appropriate. Notes: Do not save confidential values as defaults in prompts. Standards for values to save in prompts have not been developed.
The report is readable overall (for example, shading prints appropriately).
The title, header, footer, and any labels have been checked for spelling errors.
*The report name conforms to BusinessObjects report naming standards. See SAP-BOBJ Development standards and Guidelines v1.0.docx for those standards.
Query Design
*The data is drawn from the appropriate source, for example, the data comes from the folder(s) that provide accurate results and optimum performance.
*The query qualifies on codes, not descriptions.
*The query results are correct and have been checked against an appropriate source.
*Performance is acceptable.
/ Item /
Reports with Multiple Data Providers
*The appropriate dimension objects have been merged.
*Detail objects are associated with the appropriate dimension objects.
Text Box
*If the user needs to select an effective date or effective term option other than the default or Current Row when running the report, the report contains a text box informing the user of the necessary option.
*If there is a text box, it contains only information that users need to know in order to run the report and get correct results.
The text is short and similar to text boxes in other reports.
For example, most text boxes begin, “In order to obtain the correct results for this report,” and consist of a paragraph containing no more than two sentences followed by a second paragraph stating, “To get to the report, please click on the ‘Report1’ tab below.”
*The text does not include the words “Note” or “Important Note.”
*The text is left justified, Border is set to None (no lines around box), the text does not include carriage returns, and “Wrap text” is turned on.
*The tab that contains the text box is labeled “Note” in mixed case.
*The Note tab is the first tab in the report and the report is saved with the Note tab on top.
Other Considerations
The report is saved so that it opens in results view, not structure view.
Overall Report Design
*The report has been reviewed by the appropriate CPU(s) or Central Office(s).
Reports that Use Data from Multiple Universes
*If the report uses data from multiple universes, it is named according to the following standard:
Begin with CMB (for Combined), then a descriptive name of the report, then the short names of the universes involved in alphabetical order. For example: HDS CORP IT Employees [HR01, PY01, SA03, SA04].rep
*The report contains a text box with the following content:
“This report includes data from multiple universes (LIST THE UNIVERSES HERE). In order to run the report, you must have access to all of these universes.”
If the report uses data from secured tables in any of the universes, the text box informs the user of this.
*If the report uses data from multiple data areas (that is, more than one of FI, CO, AR, AP, GL etc.), all relevant data areas have signed off on the report as being well written and accurate.

*Required item.

About the BusinessObjects Report Design Usability Checklist

Background

All reports have their own distinct data needs. However, there are guiding principles that can be applied to the design and layout of that data to make it easier for users to analyze and interpret. This checklist is designed to assist those who create reports by ensuring that these principles are applied consistently to BusinessObjects reports while allowing report writers flexibility as necessary to achieve the needs of a particular report.

Use the checklist when creating or modifying any report that is or will be in the HD Smith-Maintained folder in BusinessObjects.

How to Use the Report Design Usability Checklist

·  Make sure that the report meets all the checklist items that are indicated with a star (*).

·  Use the items that aren’t indicated with a star as guidelines or suggestions: follow them if it is appropriate and ignore any that don’t make sense for your report. For example, one item on the checklist states that fonts are no smaller than 8 point, but this item is not required so a smaller font can be used if necessary in order to include all the data.