Working With Layouts
In general, how you create a layout depends on the layout type. However, some basic tasks are common to all layout types. This section discusses how to:
Use nPlosion (matrix layouts only).
Set a TimeSpan.
Specify setIDs and business units.
Enter effective dates.
Data selection is the heart of the PS/nVision layout. The database values retrieved for a matrix-based report are the results of intersecting criteria defined in the matrix layout. These criteria tell PS/nVision exactly which database values to retrieve and where to put them. The values retrieved from a tabular layout are not row and column intersections but the results of a query. Each instance is a list file representing either a partial or complete answer set for that query.
You can specify data selection criteria at the level of the entire spreadsheet, a row or column, or an individual cell. Generally, you specify criteria at the highest level applicable. So, if you have criteria that apply to the entire worksheet, you specify them at the worksheet level; if you have criteria that are unique to a single cell, you apply them to that cell only.
If there is a conflict between row and column criteria, the row overrides the column criteria. Cell criteria override all other criteria, followed by row, column, and finally worksheet criteria at the lowest level of the hierarchy.
Note: nVision should not use trees with a mixture of dynamic details and range details. The results returned from the reports using such trees could be inaccurate.
nPlosion is a feature that you can specify within your field criteria. If field criteria uses a tree node value, nPlosion automatically adds rows or columns that contain the sublevels (while subtotaling) as well as detail values found under the tree nodes that you specify. This creates a group of rows or columns that can be summarized—showing just the tree node value—or expanded to show the detail values and the summarized value.
You can also use nPlosion to show detailed TimeSpan information.
A TimeSpan limits query or ledger results to those from a particular period of time. Although you can use TimeSpan in a query-based matrix layout, it is more commonly used in ledger-based matrix layouts.
PS/nVision uses the setID you specify when creating a matrix layout to determine available choices when you define layout criteria. If the Use Business Unit in nVision option is clear, you can omit the setID. If you enter one, it must be valid. To set the Use Business Unit in nVision option on or off, select
Note: The Use Business Unit in nVision option is selected by default because essentially all PeopleSoft applications now use business units.
When you define a matrix layout, you must always enter an effective date. Like the setID, this controls which values are available for you to select when defining criteria. For some criteria, you can override the global effective date. Generally, it’s a good idea to use an effective date as late as any control (tree, department, and so on) you might want to use in the layout. The effective date used for prompting while designing a layout is not used when running the report; instead, the as of date for trees and other controls is specified in the report request when running a report.