| SetID |
Provides the ID code for a tableset. A tableset
is a group of tables (records) necessary to define your company's
structure and processing options.
|
| Effective
Date |
Establishes the date on which the row in the table
becomes effective. It determines when you can view and change the
information. Pages and batch processes that use the information use
the current row.
|
| Status |
Indicates whether a row in a table is active or
inactive. You cannot select inactive rows on pages or use them for
running batch processes.
|
| Description |
Allows free-form text of up to 30 characters that
describes what you are defining.
|
| Run
Control ID |
Identifies specific run control settings for a process
or report.
|
| Program
Name |
Provides the PeopleSoft Enterprise Performance Management
program name for which you are running the report or process.
|
| When |
Specifies the frequency with which you want to run
a process. You can select Once, Always, or Don't.
|
| Last
Run On |
Indicates the date on which the report or process
was last run.
|
| As Of
Date |
Indicates the last date for which the report or
process includes data.
|
| Scenario
ID |
Provides an identifier for a specific scenario.
|
| Model
ID |
Provides an identifier for a model. A model uniquely
identifies the types of data that you want to include in a scenario.
For example, you might want to review revenue by region—a broad scope.
If you use Oracle's PeopleSoft Activity-Based Management, you might
want to review only those activities that relate to a certain product
line for certain types of resources—a narrow scope.
|
| Fiscal
Year |
Specifies the fiscal year for your scenario or process
run.
|
| Period and Accounting Period |
Specifies the accounting period for the object or
process.
|
| Job
ID |
Specifies an instance of an engine.
|
