Defining Reports

To ensure that the design meets user information requirements, you must view data as users view it. Users typically view data through spreadsheets, printed reports, or reports published on the Web. Oracle and its partners offer many tools for producing reporting systems for users.

Several tools can help you display and format data quickly, and test whether the database design meets user needs. For example, those who are familiar with spreadsheets can use Smart View.

During the design phase, check the following:

• Grouping and sequencing of data. Do the intersections enabled by the design provide the data that users need?

• Levels of totals. What consolidation levels are required by, for example, a Smart View user who drills down and up through the hierarchy of the outline design?

• Attribute reporting. Does the database design facilitate an analysis that is based on the characteristics or attributes of specific dimensions or members? For example, do you need to compare sales by specific combinations of size and packaging, such as comparing the sales of 16‑ounce bottled colas with the sales of 32‑ounce bottled colas?

Be sure to use the appropriate tool to create and test predesigned use reports against test data. The reports that you design should provide information that meets your original objectives. The reports should be easy to use, providing the right combinations of data, and the right amount of data. Because reports with too many columns and rows are difficult to use, you may need to create several reports instead of one all‑inclusive report, or pivot a dimension to the point of view of the report so that each user can choose a different member from that dimension without viewing all members.