As Of
Date |
Indicates the last date for which the report or
process includes data.
|
Description |
Enter up to 30 characters of text describing what
you are defining.
|
Effective
Date |
Establishes the date that 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.
|
Fiscal
Year |
Specifies the fiscal year for your scenario or process
run.
|
Job
ID |
Specifies an instance of an engine.
|
Last
Run On |
Indicates the date that you last ran the report
or process.
|
Period |
Specifies the accounting period for the object being
defined or the process being run.
|
Program
Name |
Provides the Enterprise Performance Management program
name for which you are running the report or process.
|
Run
Control ID |
Identifies specific run control settings for a process
or report.
|
SetID |
Provides the ID code for a TableSet, which is a
group of tables (records) necessary to define your company's structure
and processing options.
|
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.
|
Dimension |
A field that stores a chart of accounts, resources,
and so on, depending on the application. In PeopleSoft EPM, there
are four categories of dimensions, most of which have corresponding
OWE maintenance pages: Common, CRM, Supply Chain Mgmt, and HRMS.
Dimension values/members represent individual account numbers, department
codes, and so forth. Dimensions are also known as ChartFields in
other PeopleSoft applications.
|
Planning Center |
A planning center is typically the dimension that
drives the type of plan or budget required for the process, such as
by department or project. It will represent a unit of work and will
also drive the approval structure of the activity scenario being prepared.
|
Planning Center
Dimension |
Dimension requiring a tree that is selected for
workflow and approvals. Security will be assigned to members and
nodes on the tree. The Planning Center Dimension tree requires it
to be balanced and node oriented.
|
Activity |
An activity is a user-defined entity identifying
the type it is (line item, position, or assets) that determines the
planning components such as planning center and dimensionality necessary
for plans and budgets. There are three types of activities:
Line Item – User-defined activity
to view and change plan or budget amounts in a line item format using
methods or manually entering values. You can also make adjustments
to one or many line item rows, perform allocations, or alternatively
enter via a spreadsheet add-in interface.
Position - Used to add, modify,
or view position data details, including salary, earnings, benefits,
and employer paid tax costs associated with positions. The position
budget activity represents greater level of detail than a line item,
and therefore it is typically summarized into a line item activity
defined by activity relationships.
Asset - Used to create, modify,
or view assets and depreciation costs associated with capital acquisition
plans. The asset activity represents greater level of detail than
a line item, and therefore it is typically summarized into a line
item activity defined by activity relationships.
|
Activity Group |
An Activity Group will specify a collection of activities,
the dimension hierarchies (such as trees), members, and the activity
relationships between all activities within the group. Only one activity
group can be assigned to a planning model, but different planning
models can share the same group.
|
Budget Period |
The interval of time (such as 12 months or 4 quarters)
into which a period is divided for budgetary and reporting purposes.
The Dimension allows maximum flexibility to define operational accounting
time periods without restriction to only one calendar. When you do
not use the Budget Period dimension, one is created via the Time Hierarchy
that concatenates the Fiscal Year and Accounting Period for the planning
model's activity scenarios.
|
Time Hierarchy |
Time hierarchies are required within the Scenario
Group. They establish the relationship and period aggregation of
time within the planning model for non-historical scenarios.
|
Scenario |
A Planning and Budgeting defined scenario places
the parameters, such as time and ledger, around historical and proposed
data you will want to include within your planning model. A scenario
determines what type of scenario it is (history, top-down plan, bottom-up
budget, or forecast), the ledger to use (such as actual or budget
ledger), the range of time you are referring (such as from/to fiscal
year and accounting period), GL scenario data stored, and a rate combination
when using multi-currency within your planning models. Scenarios
can be shared across scenario groups and by planning models.
|
Scenario Group |
A collection of scenarios that can be used to build
the activity scenario combinations within a single planning model.
Only one scenario group can be assigned to a planning model, but different
planning models can share the same group.
|
Activity Scenario |
Represents the intersection of an activity and scenario
that make up a unit of work or planning center. The combination of
an activity group and scenario group within a planning model auto
generates a set of activity scenario combinations allowed in the model;
then various rules, attributes, security, and so on, are applied to
each activity scenario combination.
|
GL Scenario |
This scenario is a field located in the budget ledger
tables and represents a unique and related combination of data in
the ledger that a planning and budgeting scenario ID is tied to based
on ledger, calendar, and time.
|
Account Category |
An account category defines a level in the account
tree in which to use as a filter when working with line item entry
and reporting.
|
Planning Model
ID |
A planning model is the framework used to develop
plans and budgets. It includes the scenarios and activities required
during a budget cycle. The planning model brings together all the
parameters, scenarios, and activities that establish the beginning
and end of a budget cycle. A centralized budget office or budget coordinator
typically defines planning models, and each model contains a single
Business Unit.
|
Role |
Describes how people fit into PeopleSoft Workflow.
A role is a class of users who perform the same type of work. Your
business rules typically specify what user role needs to do an activity.
There are only 6 roles used by the Planning and Budgeting application:
Coordinator: The central budget
office coordinator for an organization. This person determines parameters
and guidelines, builds the planning model, coordinates the overall
planning and budgeting process for the organization, and does high-level
forecasting and analysis.
Analyst: The user who has responsibility
for a planning center, typically a unit, department, or division within
an organization. This user may break a plan or budget into smaller
units for distribution to lower levels and establish additional guidelines
for those smaller units to follow in the budgeting process. Analysts
also do some forecasting and modeling for their overall plans or budgets.
Reviewer: The user who has responsibility
for reviewing and approving submitted budgets or plans for a planning
center. In many cases, an Analyst and a Reviewer may be the same person.
Preparer: The user at the lowest
level of preparation for a planning center. This user provides line
item, asset, and position amounts, and justifications to higher-level
users and does not usually perform allocations or aggregated analysis.
When finished preparing a plan or budget, this user submits their
work to a higher level planning center for review and approval.
Casual Preparer: An additional
user at the lowest level of preparation for a planning center. This
user performs the same activities as the Preparer role when access
is granted. The system does not, however, enable the casual preparer
role to define their own private views for line item activities. When
finished preparing a plan or budget, this user submits their work
to a higher level planning center for review and approval.
System Administrator: The person
in charge of system security.
|
Versions |
Planning and Budgeting delivers multiple versions
for each planning center level for an activity scenario. Versions
are unique to your planning center level. These versions include:
Base Version (Version 0).
Contains the base budget or plan, or selected data
source/seed scenario. All methods and amounts reflect the base budget
(BASBUD) amounts from the data source/seed scenario for the rows,
plus/minus the incremental percentage applied. No calculations are
performed or required for the base version. It is always the same
static amounts – and will never receive any updates or require calculation.
Versions 1 through 3, 5 through
9, and A through Z.
These are unique working
versions for the planning center and level, and are the version in
which users can modify and update.
Master Version (Version 4)
When users have finished working on their planning
center activity scenario, they will submit the completed plan or budget
that is delivered to the next planning center level. The master version
is created based on the version that you submit. Alternatively, if
the user is not ready to submit, they may copy any of their other
versions into master.
|