This PeopleBook describes how to set up and use Oracle's PeopleSoft Planning and Budgeting.
This preface discusses:
Oracle's PeopleSoft products.
PeopleSoft application fundamentals.
Deferred processing.
Common elements used in this PeopleBook.
This PeopleBook refers to the following PeopleSoft products:
PeopleSoft Workforce Rewards
PeopleSoft General Ledger
PeopleSoft Asset Management
PeopleSoft Commitment Control
PeopleSoft Project Costing
PeopleSoft Human Resources
The PeopleSoft Planning and Budgeting 9.1 PeopleBook provides implementation and processing information for the Planning and Budgeting system. However, additional, essential information describing the setup and design of the system resides in companion documentation, Enterprise Performance Management Fundamentals 9.1 PeopleBook The companion documentation consists of important topics that apply to PeopleSoft applications across the Enterprise Performance Management product lines.
Several Planning and Budgeting pages may operate in deferred processing mode. Most fields on these pages are not updated or validated until you save the page or refresh it by clicking buttons, links, or tabs. Delayed processing has various implications for the field values on the page. For example, if a field contains a default value, any value that you enter before the system updates the page overrides the default. Another implication is that the system updates quantity balances or totals only when you save or otherwise refresh the page. See the guidelines for designing pages in the PeopleTools PeopleBook: PeopleSoft Application Designer.
This section lists the following common elements used in Planning and Budgeting:
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:
|
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:
|
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:
|
A companion PeopleBook called PeopleBooks and the PeopleSoft Online Library contains general information, including:
Understanding the PeopleSoft online library and related documentation.
How to send PeopleSoft documentation comments and suggestions to Oracle.
How to access hosted PeopleBooks, downloadable HTML PeopleBooks, and downloadable PDF PeopleBooks as well as documentation updates.
Understanding PeopleBook structure.
Typographical conventions and visual cues used in PeopleBooks.
ISO country codes and currency codes.
PeopleBooks that are common across multiple applications.
Common elements used in PeopleBooks.
Navigating the PeopleBooks interface and searching the PeopleSoft online library.
Displaying and printing screen shots and graphics in PeopleBooks.
How to manage the locally installed PeopleSoft online library, including web site folders.
Understanding documentation integration and how to integrate customized documentation into the library.
Application abbreviations found in application fields.
You can find PeopleBooks and the PeopleSoft Online Library in the online PeopleBooks Library for your PeopleTools release.