Report iView
Example | Use | Look
Example

Figure 1: A report iView displaying a table.
Use
A report iView displays a report, typically as a table, or report
results; these may also be a table or a chart (see Chart
iView).
Look
The table should comprise the main part of the iView.
Order of Screen Elements
- A filter of shuffler can be placed above the
table, if data can be selected from several sets or if the amount of
data has to be reduced.
- Then follows the table.
- Place pushbuttons related to the table below the table and
left align them.
- If there exists an alternative chart view, a button below
the table allows to toggle between table view and chart view.
- Place pushbuttons related
to the whole iView in the lower left corner. If space is at a premium
these buttons may reside in the same row as table-related buttons
(see Buttons for details).
- If there exists a related Web application (IAC), a button
in this group should allow the users to call the application.
- If there is an emphasized button, it is the leftmost button
of the respective button group (table-related or iView-related). There
must not be more than one emphasized button!
Initial Size and Appearance
Empty tables are not displayed in iViews. In addition, no space is reserved
for the table or for a sentence, such as "No entries found".
Exception: There is one exception to this rule: Tables where users
can immediately enter data should appear in the intended size and with
empty lines.
Automatically Generated Tables
Tables that are generated automatically by the portal framework may have
a different look and behavior than the table view and the portal data
viewer.
top
Source: SAP
iView Guidelines
|