Integrating With Other Applications

This chapter provides an overview of PeopleSoft Planning and Budgeting integrations and data import, lists prerequisites, and discusses how to:

Integrate with PeopleSoft General Ledger.
Use data from PeopleSoft Asset Management.
Use PeopleSoft Commitment Control.
Integrate with third-party financial applications.
Integrate with PeopleSoft HRMS.
Integrate with third-party human resource applications.
Integrate with EnterpriseOne.

Understanding PeopleSoft Planning and Budgeting Integrations

PeopleSoft Planning and Budgeting can integrate with a number of PeopleSoft Financial Management applications, PeopleSoft HRMS applications, other PeopleSoft EPM products, EnterpriseOne products, and third party applications. We deliver integration with PeopleSoft Financial Management applications, PeopleSoft HRMS, and EnterpriseOne. As a prerequisite when integrating with a PeopleSoft database, you should verify that your environment is up-do-date.

PeopleSoft Planning and Budgeting integrates with:

PeopleSoft General Ledger.
PeopleSoft Asset Management.
PeopleSoft Project Costing.
PeopleSoft Commitment Control.
PeopleSoft HRMS.
Other PeopleSoft Enterprise Performance Management applications.
Third-party applications.
PeopleSoft EnterpriseOne.

These integrations involve importing data from the transaction systems into the PeopleSoft EPM database for use by PeopleSoft Planning and Budgeting. In many cases, you can also export this data back to the transaction databases once the planning and budgeting process is complete.

Understanding Data Import Using ETL

In PeopleSoft Planning and Budgeting, use the delivered Ascential DataStage ETL (extract, transform, and load) tool to import data from the PeopleSoft Financial Management and HRMS databases. The ETL process establishes a matching table structure between the PeopleSoft Enterprise Performance Management (EPM) database and other PeopleSoft product line databases. PeopleSoft delivers the ETL jobs (maps) that you need in order to load budgeting-specific data into the Operational Warehouse Staging (OWS) tables and Operational Warehouse Enriched (OWE) tables within the PeopleSoft EPM database.

In summary, you are using ETL jobs to copy data from the source database into the EPM OWS tables, and then to move data from OWS to the OWE tables, where Planning and Budgeting uses the data.

Note. To transfer trees into PeopleSoft Enterprise Performance Management Warehouse, use the PeopleTools TreeMover utility.

Consider reviewing the delivered ETL jobs and maps that you use to load data for PeopleSoft Planning and Budgeting (by product), and the source, OWS, and OWE tables that you require, which are listed in Appendix A of this PeopleBook.

Prerequisites

Before integrating the PeopleSoft Financial Management data and the PeopleSoft HRMS data, verify your Financial Management and HRMS application environments are up-to-date with any objects related to Planning and Budgeting integration. Updates can be found on PeopleSoft Customer Connection under Updates and Fixes.

Search on Customer Connection under Updates and Fixes, and apply to your PeopleSoft source system any updates that relate to integration with EPM Planning & Budgeting.

To review a table of delivered updates, additional posted documentation, or Red Papers, visit Customer Connection, Support, Documentation, Documentation Updates on PeopleSoft Customer Connection.

See Also

PeopleSoft Enterprise Performance Management Installation Guide

Integrating with PeopleSoft General Ledger

In this section we provide an overview of integration with PeopleSoft General Ledger and exporting data from PeopleSoft Planning and Budgeting, and discuss how to:

Using data from PeopleSoft General Ledger for Planning and Budgeting.
Report itemization and notes data from the planning model.
Export general ledger budget data from the planning model.
Move budget data back to PeopleSoft General Ledger.
Import data into PeopleSoft General Ledger.

Using Data from PeopleSoft General Ledger

In PeopleSoft Planning and Budgeting, you can use data from the following ledgers in PeopleSoft General Ledger to seed a budget or to use as a reference during the planning and budgeting process:

General ledger — Actuals (PS_LEDGER)
Standard budget ledger (PS_LEDGER_BUDG)
Project budget ledger (PS_LEDGER_PROJ)
Control budget ledger (PS_LEDGER_KK)

Before importing data from PeopleSoft General Ledger using the delivered ETL tool, identify the ledger data that you want to import.

Once imported into the PeopleSoft Enterprise Performance Management Warehouse, the data is the input source during the planning model stage process.

Data staging recognizes these sources identified within the planning model by the Planning and Budgeting scenario group which contains a collection of scenarios available for use. These scenarios are associated with the line item activity type, and they are also used on the Data Source page in the model to define a source/seed and comparison for the line item activity-scenario in the planning model.

After you complete a budget, you can export the budget data from PeopleSoft Planning and Budgeting to the PeopleSoft EPM database or directly into a staging table in order to move it into the PeopleSoft Financial Management database using ETL.

Note. If you are using PeopleSoft Commitment Control data, PeopleSoft Planning and Budgeting does not validate a child budget to verify that it does not exceed the parent budget. To validate this data and identify errors, use the journal posting process in the PeopleSoft Financial Management database.

Reporting Itemization and Notes Data from the Planning Model

When end users work with line item activities, they may be entering public or private notes that apply to line item details, or they may use the itemization method (ITM) to provide underlying details to a line item amount. This information does not get exported back to PeopleSoft Financial Management. The notes and itemization data is stored in the EPM database, which is accessible via custom reporting. These line item notes and itemization data are stored in PS_BP_LI_NOTES and PS_BP_LI_ITEMIZE, respectively.

Note. The notes and itemization data is not used as an input source for staging line item activities.

Exporting General Ledger Budget Data from the Planning Model

After you complete the budget, you can export the data from the planning model into a stage table for transference to PeopleSoft Financial Management, or the source budget ledger table in PeopleSoft EPM database. To export the financial line item budget data from the planning model, run the Export to General Ledger process (BP_EXP).

Export to General Ledger Budgeting Data Process (BP_EXP)

The Export to General Ledger process (BP_EXP) is a PeopleSoft Application Engine process that extracts line item data from the planning model into the PeopleSoft EPM database tables such as the PS_BP_LEDGER_BDEXP or the budget F00 ledger used by Planning and Budgeting. Based on the request parameters that you define, the system exports planning model data located in the master version of the line item activity-scenario at the time of the export.

If you elect to export to PeopleSoft Planning and Budgeting, the following results in the PeopleSoft EPM database:

Planning model data is extracted from the master version in the planning model and placed in the corresponding budget F00 ledger used by PeopleSoft Planning and Budgeting.
Depending on the budgeting type defined by the scenario group associated with the planning model, PeopleSoft Planning and Budgeting updates the relevant budget ledger F00 table located in the PeopleSoft EPM database—PS_BP_LED_BUDG_F00 (standard budget ledger), PS_BP_LED_KK_F00 (control budget ledger), or PS_BP_LED_PROJ_F00 (project budget ledger).

If you elect to export to PeopleSoft General Ledger, the planning model data is extracted from the master version in the planning model and placed into the PS_BP_LEDGER_BDEXP staging table in the EPM database, in preparation for transference to the PeopleSoft Financial Management database.

Note. The export process does not directly move data to the PeopleSoft Financial Management database. After data is placed in the staging table, you need to use the ETL tool to transfer the data to the financial database.

During the export process, the system logic includes the following:

The system rounds amount values to the nearest decimal level based on the currency code defined in the Currency Code table. The rounding equates the total line amount to the sum of the line period detail amounts. Any decimal rounding difference found is moved to the last budget period line.
If you select the Flip Sign setting defined for account types on the Account Type Options page in Planning and Budgeting, the system reverses the sign associated with data for the account type so that it is consistent with the ledger.

Note. It is unnecessary to run a process to export notes and itemizations created using PeopleSoft Planning and Budgeting because the system automatically stores the data in the PeopleSoft Enterprise Performance Management Warehouse.

Page Used to Export Financial Data from the Planning Model

Page Name	Object Name	Navigation	Usage
Export to General Ledger	BP_EXPORT	Planning and Budgeting, Data Integration, General Ledger Integration, Export to General Ledger	Export budget ledger data from a planning model to Planning and Budgeting ledger or staging table in the PeopleSoft EPM database.

Exporting Financial Data from the Planning Model

Access the Export to General Ledger page.

PeopleSoft Budgeting

Select as the export destination to export data to the Planning and Budgeting ledger table in the PeopleSoft EPM database. If you select this check box, the Replace all Ledger Data check box displays.

PeopleSoft General Ledger

Select as the export destination to export data to staging table in the PeopleSoft EPM database, in preparation for transference to the financial database.

Note. If you select this check box, the Replace all Ledger Data check box is hidden; however, the Replace all Ledger Data check box is still available on the Import Budgeting Data page located in the PeopleSoft Financial Management database.

Business Unit, Planning Model ID, Scenario and Activity

Enter values to define the model, scenario and line item activity that you want to export.

Export Line Item Zero Amounts

Select this check box to export line item rows that contain zero amount values.

Clear this check box to drop any rows containing zero amount during the export process to the ledger or staging table.

Replace all Ledger Data

Select this check box to delete all ledger data associated with business unit, ledger, scenario, and fiscal year, and replace it with the data that you are defining for the export process. In other words, it lets you specify the ledger data that you want updated in the appropriate ledger table.

Clear this check box to update only the ledger table rows associated with the scenario and those planning centers that have been updated since the last export process.

This check box only displays if you select PeopleSoft Budgeting as the Export Destination.

Override GL Scenario

Select this check box to export plan or budget data to the destination budget ledger table (*_F00 tables) using the scenario that you define on this page. Overriding the scenario lets you export planning and budgeting data to a different scenario (such as for reporting purposes).

Clear this check box to export data using the GL scenario originally associated with the proposed plan or budget, as part of the planning and budgeting scenario definition.

This check box only displays if you select PeopleSoft Budgeting as the Export Destination.

Note. If, under Export Destination, you selected both the PeopleSoft Budgeting and PeopleSoft General Ledger check boxes, the Override GL Scenario only applies to the data exported to Planning and Budgeting; data exported to the General Ledger does not have this check box on the Import Budgeting Data page. The GL scenario field is populated with the original value defined by the Planning and Budgeting scenario definition.

Moving Budget Data Back to PeopleSoft General Ledger

Use the ETL tool to move the budget data back to the General Ledger. The ETL job moves data from the PS_BP_LEDGER_BDEXP staging table in EPM Warehouse to the same table name in PeopleSoft General Ledger.

The criteria for running ETL back to General Ledger is destructive and based on business unit and Planning and Budgeting scenario.

Note. The staging table's Ledger Name field (BP_LEDGER_NAME) is equivalent to the Planning and Budgeting scenario field (BP_SCENARIO).

Importing Data into PeopleSoft General Ledger

If you exported data from the planning model into the staging table in the PeopleSoft EPM database, ran the ETL job to transfer data to the PeopleSoft Financial Management database, you will now import this data back into the appropriate budget ledger table in PeopleSoft General Ledger by running the Import Budgeting Data (BPLEDGUPDATE) application engine process in the financial management database.

Note. The Planning and Budgeting 'Scenario' from the PeopleSoft EPM database is the counterpart for 'Ledger Name' on the run control in Financial Management.

To run the Import Budgeting Data process in the PeopleSoft financial management database, select the Ledger Name (Planning and Budgeting scenario) that you want to update.

To replace all ledger data associated with the selected business unit and ledger with the data in PS_BP_LEDGER_BDEXP, select the Replace All Ledger Data check box. If this check box is clear, the system only updates the budget ledger table rows that have been updated since the last import process.

Process Results

The Import Budgeting Data (BPLEDGUPDATE) application engine process moves a copy of the financial budget data from the ledger staging table (PS_BP_LEDGER_BDEXP) to the appropriate budget ledger (PS_LEDGER_BUDG, PS_LEDGER_BUDG_KK, or PS_LEDGER_PROJ) in the PeopleSoft Financial Management database based on the budgeting type.

Note. When using control budget types the import process inserts data into the PS_LEDGER_BUDG_KK table. Then you must run the PeopleSoft General Ledger Allocation process to create, edit, and post journal entries to PS_LEDGER_KK.

See your PeopleSoft Enterprise Commitment Control PeopleBook for more information about how to use the allocation and commitment control processes.

Using Data From PeopleSoft Asset Management

Using existing in-service asset and depreciation information from your source database is optional. This section lists prerequisites and discusses how to:

Set up asset data sources.
Stage asset data.

Prerequisites

In addition to the prerequisites listed at the beginning of this chapter, you can activate the PeopleSoft Application Messaging Enterprise Integration Point (EIP), process asset depreciation calculations, and use asset catalog items in PeopleSoft Asset Management by running the following processes:

To synchronize capital acquisition plan (CAP) data between PeopleSoft Asset Management and PeopleSoft Planning and Budgeting, activate the PeopleSoft Application Messaging Enterprise Integration Point (EIP) for BUDGET_CAP_SYNC using PeopleSoft Application Designer.

Note. Using transformation program is an optional step in the EIP setup. Since PeopleSoft Planning and Budgeting does not support transformations, Version 1 should be set as a default in both PeopleSoft EPM and Financial Management databases. The purpose is to subscribe and publish CAP information, when required, between the two databases since no asset or depreciation detail data is exported back to PeopleSoft Asset Management.

If you decide to use the CAP information in PeopleSoft Planning and Budgeting, the CAP Status values (Approval 1, Approval 2, Approval 3, Closed, Entered, On Hold, Open) have no affect when used in an asset activity during budgeting.
Run the Depreciation Calculation process (AMDPCALC) to populate the PS_DEPRECIATION record with annual depreciation amounts. This process moves stored depreciation amounts from department to department or category to category depending on the transaction that you are performing and the dimensions that you specify.
Run the Asset Period Allocation Setup process (AMCALLOC) in the PeopleSoft Financial Management database to populate the PS_DEPR_ALLOC_TBL with calendar information used to divide annual depreciation amounts into period amounts.

Only run the Asset Period Allocation Setup process once after you create a new calendar or modify an existing calendar. When you perform subsequent runs of the Depreciation Calculation process, you do not need to run the Period Allocation process again.
You can also import into the PeopleSoft Planning and Budgeting Asset Catalog asset profiles that you create using PeopleSoft Asset Management. Run the Load Asset Catalog (AEBDASSTITEM) application engine process to populate the asset catalog record (PS_BD_ASSET_ITEMS) with data from the profile tables (PS_PROFILE_DET_TBL and PS_PROFILE_TBL) in PeopleSoft Asset Management.
Run the Budgets Interface (AMBD1000) SQR process to load in-service assets and their associated depreciation from PeopleSoft Asset Management into the assets (PS_BD_ASSET) and depreciation (PS_BD_ASSET_DEPR) records for mapping to PeopleSoft Planning and Budgeting in EPM database.

Note. Asset depreciation calculations that you run in your financial database for import into PeopleSoft Planning and Budgeting should use the same number of periods as that defined for your proposed asset budget.

The asset activity in PeopleSoft Planning and Budgeting cannot support the distribution of amounts across multiple dimensions (ChartFields) for a single asset ID. This applies for all in-service asset data from other data sources and newly added assets by preparers during the planning and budgeting process.

Asset information from any data source should have the same business unit as those used by your planning model.

After you have finished preparing the in-service asset and depreciation data for use by PeopleSoft Planning and Budgeting, complete the following steps:

Load the asset-related data into the PeopleSoft Enterprise Performance Management Warehouse using the delivered ETL tool.
In Planning and Budgeting, define asset and account defaults to be used by the asset activities in a planning model on the Asset Budgeting Defaults, Asset Accounts and Depreciation Accounts pages. To access these pages, navigate from Planning and Budgeting menu to —Planning and Budgeting Setup, Asset Budgeting Defaults, Asset Budgeting Defaults.
If you loaded the asset catalog table from PeopleSoft Asset Management, use the Asset Catalog maintenance page in Planning and Budgeting to update any required asset budget defaults, or create new catalog items. To access this page navigate from Planning and Budgeting menu to — Planning and Budgeting Setup, Asset Budgeting Defaults, Asset Catalog.
Finally, when creating an asset activity in a planning model that will use the in-service asset and depreciation data, be sure to use a dimension for planning center which corresponds to that available in the source data loaded from asset management database.

For example, if department is the only dimension associated with the asset ID, you will need to use this as your planning center for the asset activity, since there is no delivered process to map the department ID to a different dimension.

See Also

PeopleSoft Asset Management PeopleBook, “Processing Depreciation”

Setting Up Asset Budgeting

Setting Up Asset Data Sources

In preparation for staging asset data, you must define the data sources for asset activity scenario in the planning model. Navigate to Planning and Budgeting, Planning and Budgeting Setup, Setup Model, Planning Models, Activity Scenario, then click the Data Source link for an asset activity scenario.

On this page you define:

Use Source Data

Select the check box in order for the staging process to pick up any in-service asset and depreciation data for inclusion in the asset activity. If you are not using source data from an asset management database, you do not need to select the check box.

Asset Book Name

Enter the asset book information for this business unit model and activity.

Only a single asset book is supported for the asset activity scenario.

Default Depreciation Account

Enter the depreciation account for assets that do not have matching depreciation rows. The valid depreciation accounts are taken from those defined using the Depreciation Accounts page.

See Defining Data Sources for Asset Activities.

Note. The imported, in-service asset data in the PeopleSoft Planning and Budgeting interface tables is the source data during the model staging process.

You cannot edit in-service assets that you import from PeopleSoft Asset Management in PeopleSoft Planning and Budgeting.

Staging Asset Data

The data staging process for an asset activity moves data as follows:

From	To
PS_BD_ASSET	PS_BP_ASSET
PS_BD_ASSET_DEPR	PS_BP_ASSET_DEPR

Note. The asset catalog table does not require staging. When selecting an asset catalog item for a new asset, the asset catalog defaults are retrieved from the PS_BP_ASSET_ITEMS table.

The staging process assigns an account for a depreciation row for in-service assets when missing an account value for depreciation. The system populates the depreciation account according to the following hierarchy:

If the field is blank, the system uses the BP_DEPR_ACCOUNT from PS_BP_ASSET.
If the field is blank and the catalog item can be found, the system uses the BP_DEPR_ACCOUNT from the asset catalog for the profile ID assigned to the asset.
The system uses the depreciation account that you specify on the Data Source page.

Other rules applied to in-service asset data when running the staging process include:

Only in-service assets that have a related depreciation impact are supported and processed during data staging.
When the dimension member for planning center is missing from the source data, the asset and depreciation rows are dropped and not processed.
Only in-service assets that have a depreciation impact to the proposed budget year are processed. This means the assets must have a budget impact in the time-frame defined by the bottom-up scenario to be staged for an asset activity.
Any single asset ID shared by more than one planning center (or any other dimension) is not supported, and therefore will not be processed.

Using Data from PeopleSoft Project Costing

This section lists prerequisites and discusses how to:

Process project costing data.
Export and import project budgets.

Prerequisites

In addition to the prerequisites listed at the beginning of this chapter, you can use your PeopleSoft Project Costing budget data as a source for Planning and Budgeting. Before you can load the data into the PeopleSoft Enterprise Performance Management Warehouse using the delivered ETL tool, run the application engine process (PC_PC_BD_B) in PeopleSoft Project Costing database from the Send to Budgeting page, to move data from the PS_PROJ_RESOURCE table to PS_LEDGER_PROJ.

Once the data is moved to the project budget ledger, run the ETL jobs to move the data from the financial database source to the PS_LEDGER_PROJ (OWS) table and then the PS_BP_LED_PROJ_F00 (OWE) table in the EPM database.

Processing Project Costing Data

When processing data from PeopleSoft Project Costing, consider the following:

Due to index size constraints on some database platforms, the number of index fields (such as PS_LEDGER_PROJ) may be limited. Consequently, LEDGER_PROJ and PS_BP_LED_PROJ_F00 is delivered with the following fields marked as non-key: CHARTFIELD1, CHARTFIELD2, CHARTFIELD3, AFFILIATE_INTRA1, AFFILIATE_INTRA2, DIMENSION1, DIMENSION2, and DIMENSION3. The LEDGER_PROJ table is the staging table for PS_BP_LED_PROJ_F00. The LEDGER_PROJ table does not contain the fields of DIMENSION1, DIMENSION2, and DIMENSION3.

Consider evaluating your key requirements based on your data and reset these keys as appropriate to insure that indexes are correctly built.

Note. When you change key requirements, this will apply to the entire PeopleSoft EPM database.

See Activating Inactive Dimensions.
Once you have enabled the required keys, access the Dimension Configuration page in Planning and Budgeting to set the status as 'Active' for the dimensions you plan to use with your project budgets.
When implementing PeopleSoft Planning and Budgeting using project budget types, implement with a one-to-one relationship between your warehouse business unit and your project's business unit. Because of the related logic around the project's business unit and the project, do not consolidate the project's business units or IDs.
To define the planning center for your line item project budget, you can use any available dimension in PeopleSoft Planning and Budgeting. When you use the project dimension (ChartField) as the planning center, the same rules apply for defining trees where you must use a node-oriented tree.
On the Budgeting Installation Options page, select your project costing interface as PeopleSoft 8.4/8.8. When you define this as your interface, the project dimension will use the information about the project ID on the project integration template assigned to the project. This information about which project integration template is used is needed to determine to which general ledger business unit the project ID will be mapped. Planning models created in Planning and Budgeting are defined by a general ledger business unit, and not the project business unit.

See Identifying Data Integration Sources.
When adding a new project in the PeopleSoft EPM Warehouse using the project maintenance page, the integration template value is required only if using project budget types. Use the Ascential DataStage ETL tool to copy the project integration template table (PC_INT_TMPL_TBL) into PeopleSoft Planning and Budgeting.
When integrating with PeopleSoft Project Costing, there is no online validation between the project and activity ID. To optionally accommodate this requirement, consider using combination edits.
When using the online analysis for line item activities, there are no descriptions or validations to filter—only the activity IDs associated and allowed with a project.
For the Activity ID table, use the PS_PROJ_ACTIVITY table for PeopleSoft Planning and Budgeting. When moving data back to PeopleSoft Project Costing, the Activity ID is required with the Project ID.

Note. When integrating with PeopleSoft Project Costing, you should not use the PS_FS_ACTIVITY_TBL table.

Note. When using the project budget ledger (PS_BP_LED_PROJ_F00) as the integration source for Planning and Budgeting, you can only use line item activity type in the planning model. Asset and position activities are not available when using budgeting type of project budget ledger, as defined on the Scenario Group page that is associated with the planning model.

See Also

PeopleSoft Enterprise Project Costing 8.8, "Budgeting Project Costs and Planning Revenue," Integrating Budget Data with PeopleSoft Budgeting and Overview of the PeopleSoft Budgeting Integration Process.

Exporting and Importing Project Budgets

After you complete the planning and budgeting process for a project budget, you can export the project data back to PeopleSoft Financial Management database. To send the data back into the PeopleSoft Project Costing application, you perform the following:

Access the Export to General Ledger page and run the process with an Export Destination of PeopleSoft General Ledger for the defined planning model, activity, and scenario.
Use the ETL tool to move the project budget data back to the Financial Management database. The ETL job moves data from the PS_BP_LEDGER_BDEXP staging table in EPM database to the same table name in PeopleSoft General Ledger.
In PeopleSoft General Ledger, run the Import Budgeting Data (BPLEDGUPDATE) application engine process to transfer project budget data from the staging table to the project ledger (LEDGER_PROJ).
Finally, to load the project budget data into the PeopleSoft Project Costing table (PS_PROJ_RESOURCE) in the Financial Management database, access and run the Retrieve from Budgeting page in Project Costing and run the application engine (PC_BD_TO_PC) to move data from PS_LEDGER_PROJ to the PS_PROJ_RESOURCE table.

See Exporting General Ledger Budget Data from the Planning Model.

See Importing Data into PeopleSoft General Ledger.

Using PeopleSoft Commitment Control

PeopleSoft Commitment Control is an optional feature of the PeopleSoft Financials, Enterprise Services Automation, and Supply Chain Management product lines that lets you actively control expenditures against predefined, authorized budgets. In PeopleSoft Planning and Budgeting, you can develop budget data for a control budget type while leveraging the rules from Commitment Control definitions that are set up in the PeopleSoft Financial Management database. This lets you validate budget data according to rules that you are also using in PeopleSoft General Ledger. After you complete the development of a control budget, export the budget data to the Commitment Control ledger in PeopleSoft General Ledger.

Note. PeopleSoft Planning and Budgeting supports PeopleSoft Commitment Control if you are integrating with PeopleSoft 8.4 and 8.8 General Ledger.

This section describes how to:

Set up and Use PeopleSoft Commitment Control.
Use control budget rules.
Use control budget options.
Use the ruleset ChartField.
Use keys and translations.
Use the control ChartField.
Use excluded account types.
Export control budget data.

See the Commitment Control documentation delivered as part of your PeopleSoft Financials PeopleBooks library.

Setting Up and Using PeopleSoft Commitment Control

Complete the following steps to set up and use the PeopleSoft Commitment Control rules and features in PeopleSoft Planning and Budgeting:

Use the delivered ETL tool to import ledger data from PS_LEDGER_KK into the Operational Warehouse Staging (OWS) and Operational Warehouse Enriched (OWE) tables in the PeopleSoft EPM database. Use the delivered ETL tool also to load other related information, such as control budget rules, into the warehouse.

Note. The ETL process loads the data from the Financial Management database into the OWS tables. Once loaded to the OWS (PS_LEDGER_KK), run a second ETL job to load the data from the OWS tables into the OWE table (PS_BP_LED_KK_F00), for use by Planning and Budgeting.
Use the Scenario and Scenario Group pages in Planning and Budgeting to set up budget parameters that are for a Commitment Control budget type.
1. For a historical planning scenario, select History as the Scenario Type on the Scenario page that can be used as a seed/source for base budget and historical comparison scenarios. For a historical scenario type that uses a control budget ledger ID, you will need to select a Trans Type (transaction type).
  
  PeopleSoft Planning and Budgeting uses the transaction type on the Scenario page to filter the data rows from the source commitment control ledger tables. Available transaction type options include original and final budget data. During the staging process, only those data rows associated with the selected transaction type are populated in the staging tables as you prepare for the model staging process.
  
  Note. The transaction type only applies to ledgers associated with the Commitment Control budget ledger when integrated with PeopleSoft Financial Management General Ledger.
  
  The calendar selected for each ledger in a scenario for which you want the system to enforce commitment control definitions determines the ruleset definitions used in PeopleSoft Planning and Budgeting. Planning and Budgeting supports a single calendar per defined scenario. Rulesets that do not use the selected calendar are not used in Planning and Budgeting. The rulesets and their related calendars only apply to PeopleSoft General Ledger.
2. For the proposed planning type (a non-history Scenario Type), select the From and To budget period that represents the date range of your budgeting cycle, on the Scenario page.
3. On the Scenario Group page select Controlled Budget Ledger as the Budgeting Type.
Use the Activity and Activity Group pages in Planning and Budgeting to set up dimensions (ChartFields), trees, and members that are to be used in the Commitment Control budget type. The SetIDs used for dimensions should be the same as those used by your commitment control rules from PeopleSoft General Ledger.

Note. It is not necessary to use the same trees used by your commitment control rules, but the dimension summarization defined for the activity scenario in the planning model should be consistent with the rules.
Define a planning model. Using the Planning Model page, select the scenario group that you defined with the controlled budget ledger as the budgeting type.
Using the Activity Scenario Line Item Defaults page, select the Enforce Budget check box next to each line item activity scenario for which you want the system to enforce the control budget rules.

Note. The Enforce Budget check box is only available for line item activity types, because ledger ID is a required field when recognizing the control budget rules for validation.
When running the data staging process for the line item activity, the process will validate all ChartField (dimension) combinations against the control budget definitions you mapped over from PeopleSoft General Ledger. Any rows that do not pass the validation against the control budget ruleset will still be staged but marked in error when they are inserted into the proposed control budget.

Once the budgeting process begins, a preparer who submits a line item budget to the next planning center level must correct any rows marked in error or delete them before submission, by accessing the Dimension Error Corrections or Dimension Errors page.

Note. When the row marked in error is from a child activity (such as that in an asset or position type), you will need to make the dimension corrections in the child activity.

See Also

Defining Scenarios

Using Control Budget Rules

When developing data for a controlled budget ledger for PeopleSoft General Ledger, PeopleSoft Planning and Budgeting uses rulesets to determine:

Valid ChartField values for each dimension.
Valid combinations of ChartFields and ChartField values.
Valid rulesets for calendars used for a ledger.
Account types and values not excluded by the ruleset.

In the PeopleSoft Financial Management database using the Budget Definitions component, set up commitment control definitions—including the control ChartField, key ChartFields, and translation rules—for each commitment control ledger group. From this source, PeopleSoft Planning and Budgeting uses the relevant records to enforce the control budget definitions. The following table lists the specific records that Planning and Budgeting uses and the data entry point within PeopleSoft Financial Management:

Record for FDM	Data Entry Page
PS_KK_BUDGET_TYPE	Control Budget Options
PS_KK_SUBTYPE	Ruleset ChartField
PS_KK_FILTER	Ruleset ChartField
PS_KK_KEY_CF	Keys and Translations
PS_KK_CF_VALUE	Control ChartField
PS_KK_EX_ACCT_TYPE	Excluded Account Types
PS_KK_EX_ACCT_VAL	Excluded Account Types

Using Control Budget Options

For the PeopleSoft Financial Management database, the following field in the Control Budget Rules page applies for control budget types created in PeopleSoft Planning and Budgeting:

Enable Statistical Budgeting

If selected, you can enter statistical budgets using the statistical code dimension in the line-item activity. To make statistical codes available during budgeting, define the dimension details for statistics. You enable the use of the statistical code dimension on the Activity page, while the members are included in the Activity Group.

Using the Ruleset ChartField

When creating control budgets in PeopleSoft Planning and Budgeting, the following rules from the RuleSet ChartField page in General Ledger apply:

The ruleset ChartField and the associated ruleset definition, or group of ruleset definitions for a ledger group, are defined. A ruleset ChartField can have multiple ruleset definitions; however, they must be mutually exclusive and cannot overlap. Rulesets can also be defined using different tree levels.
When you select the tree used for the planning center ChartField (dimension) definition, PeopleSoft Planning and Budgeting requires that all planning centers requiring a detailed budget are on the same level of the tree. In addition, a detail tree used for the planning center definition cannot have missing levels. The control budget definitions in PeopleSoft General Ledger must use a tree with the detail budget level on the same level as that used in Planning and Budgeting for the planning center tree. To meet this requirement, you may need to modify a new tree in Planning and Budgeting (such as create additional levels of approval).

Note. When using the Control Budget definitions from PeopleSoft General Ledger, you must also move into the PeopleSoft EPM database any trees used by the ChartField rulesets.

Using Keys and Translations

When creating control budgets in PeopleSoft Planning and Budgeting, the following attributes from the Keys and Translations page in General Ledger apply:

Calendar ID

Represents the level on which the ruleset is defined. Each ruleset can contain a different calendar; however, PeopleSoft Planning and Budgeting only supports a single calendar per scenario definition. You can define more than one proposed scenario within a scenario group that is associated with a planning model.

Note. You can specify multiple scenarios in the scenario group definition with each scenario using a different calendar.

The calendar that you select for the scenario as part of the control budget scenario group definition determines the rulesets that will be used for the line item activity associated with the scenario. Only those rulesets that use a calendar ID can be used to validate a scenario in Planning and Budgeting, since calendar is a required field for the scenario definition.

If you selected the Enforce Budget check box on the Line Item Default page in the planning model, the system will refer to the PS_KK_KEY_CF record to determine some of the validation rules for the control budget.

See Understanding the Combination Data Validation Process.

When running validations for control budgets in Planning and Budgeting, the following field applies from the Keys and Translation page in Financial Management:

ChartField

The ChartFields listed in the Keys and Translations grid are required ChartFields during budget preparation. If any of these listed ChartFields (dimensions) are blank, the system generates an error message when performing validations.

Also, you cannot budget (or enter budget data) on a ChartField that is not included in the Keys and Translations grid.

Tree Name and Level Name

Defines the valid values—all those located on the specified tree level and above—for the ChartField based on the tree and tree level.

Single Calendar for Ledger for PeopleSoft Financial Management

The calendar defined for the scenario (within the scenario group definition) determines the rulesets used for validation associated with that scenario. Only those rulesets that use the same calendar as that defined for the scenario are valid.

For example, suppose you define a scenario group with the following:

Scenario Group: 2006 Controlled Budget

Scenario: 2006 Dept Control Budget, where Calendar is MN (month)

2006 Dept Control budget has three rulesets associated with it as follows:

Ruleset	Ruleset ChartField	Calendar ID	Default Ruleset
Group1	50000 – 56000	MN	Y
Group2	60000 – 69999	MN	N
Group3	70000 – 79999	QT	N

PeopleSoft Planning and Budgeting considers as valid only those rulesets with a monthly calendar (MN). The ruleset Group3 is excluded from the control definition, and ChartField values of 70000 – 79999 are considered invalid. Optionally, you could define a second scenario that uses the quarterly (QT) calendar if planning and budgeting is required for Group3.

Using the Control ChartField

In PeopleSoft General Ledger, the Control ChartField page lets you specify tolerance exceptions entered on the Control Budget Options page.

If the budget data entered does not fall within the Range From and Range To, it is considered invalid. PeopleSoft Planning and Budgeting does not use any other options on this page such as the tolerance limits.

To use all the control ChartField values, select the All Control Values check box.

Using the Excluded Account Types

In PeopleSoft General Ledger, the Excluded Account Types page lets you specify account types and account values that you want to be excluded from the budget.

The budget data entered in Planning and Budgeting should not include Account Type and Account values that are a part of the excluded rule, and would be considered invalid when used.

Exporting Control Budget Data

After you complete the planning and budgeting process, you can export the control budget data to PeopleSoft General Ledger. This is done by running the Export to General Ledger process, selecting the PeopleSoft General Ledger option to populate the staging table. From there, use the ETL tool to transfer the staged data to the corresponding staging table of the same name in PeopleSoft General Ledger.

Once the data is exported to the General Ledger database, access this database and run the BPLEDGUPDATE process from the Import Budgeting Data page in the PeopleSoft General Ledger application to update the PS_LEDGER_BUDG_KK table located in the PeopleSoft General Ledger application.

Note. In PeopleSoft General Ledger, use the Allocation process (GL_ALLOC in PeopleSoft General Ledger 8.4 and FS_ALLC in PeopleSoft General Ledger 8.8) to create budget journals and allocate the budget data in PS_LEDGER_BUDG_KK to the Commitment Control budget header and line tables (PS_KK_BUDGET_HDR and PS_KK_BUDGET_LN) and the Commitment Control ledger (PS_LEDGER_KK). You can also run the Commitment Control Posting process to edit and post the budget journals to PS_LEDGER_KK if you do not do so as part of the Allocation process. The PeopleSoft Financial Management release you are on will determine the name of the allocation process.

See your PeopleSoft Enterprise Commitment Control PeopleBook for more information on using allocations and integration with Planning and Budgeting.

See Exporting General Ledger Budget Data from the Planning Model.

Integrating With Third-Party Financial Applications

If you are using financial data from non-PeopleSoft applications, populate the Operational Warehouse Staging (OWS) and the Operational Warehouse Enriched (OWE) tables in the PeopleSoft EPM database, and then implement the other steps described in this chapter for integrating with PeopleSoft Financial Management applications.

Note. Be sure to store general ledger data for Planning and Budgeting in the PeopleSoft EPM database in the following OWE tables: PS_LEDGER_F00, PS_BP_LED_BUDG_F00, PS_BP_LED_KK_F00, and PS_BP_LED_PROJ_F00.

If you require your general ledger source data to be stored in the OWS tables, use the following tables: PS_LEDGER, PS_LEDGER_BUDG, PS_LEDGER_KK, and PS_LEDGER_PROJ.

Integrating with PeopleSoft HRMS

This section provides an overview of preparing HRMS job and position data for import to Planning and Budgeting, data source setup, and stage processing, lists prerequisites, and discusses how to:

Map HR business units to planning centers.
Map HR departments to planning centers.
Include benefit plan types.
Include earning codes.
Correct dimension errors.
Update position data imported and staged from PeopleSoft HRMS.
Export position data from the planning model.
Move position data back to HRMS.
Import position data into PeopleSoft HRMS.

Preparing PeopleSoft HRMS Job and Position Data for Import

You can use existing position and human resource setup data from PeopleSoft HRMS for position budgeting. Prepare the position and job data within the PeopleSoft HRMS database before importing the data into PeopleSoft Planning and Budgeting.

Note. As indicated in this chapter's prerequisites, you should verify your PeopleSoft HRMS environment is up-to-date with any objects related to the Planning and Budgeting integration.

Understanding Data Source Setup

Before you begin setting up your planning model and running data stage for a position activity, define your position budgeting defaults in PeopleSoft Planning and Budgeting.

The location of the source data that was mapped from your PeopleSoft HRMS system by the ETL tool is stored in the following PeopleSoft Planning and Budgeting tables:

PS_BP_JOB_F00
PS_BP_POSITION_D00
PS_BP_COMP_F00

In preparation for staging job and position data, you must define the data source in the planning model. Navigate to Planning and Budgeting, Planning and Budgeting Setup, Setup Model, Planning Models, Activity Scenario and click the Data Source link (associated with a position activity) on the Activity Scenario page.

On this page you define these options:

Use Source Data	Select when you integrate employee job and position data from your human resource system, and you wish to include during data staging. The flag enabled indicates there is data located in the source human resource tables and stage will retrieve any corresponding data. You do not need to select the check box when you do not bring data from your human resource system for integration.
Position Source Scenario	Select a scenario ID in which you have job and position data stored. If you are integrating with PeopleSoft HRMS, you should leave the field blank since the field does not exist in the source system and contains no value.
Select Spreads	Click to access the Spread Definition page and define spreads.
Include Tax Calculation	Select to perform employer paid tax calculations while loading the job and position data. The process uses the Employer Tax Group default from Positions Data Defaults page if the information is not first associated with a corresponding job code assigned on the Job Code Defaults page.
Use Defaults for Employee Data	Select to assign the same compensation defaults to populate data at the employee level. If you do not want employee data rows populated with position defaults, clear this check box. Note. If you select this check box, the system uses job code and position data defaults to populate missing employee compensation components—benefit and earning types—when there are no other rows associated with the employee for that compensation type. For example, if the employee has existing benefit data but no earnings data, the system picks up only earnings data, but no benefit data since it already exists. This check box is optional. It is particularly useful when you are not using PeopleSoft Human Resources payroll or total compensation, and you want to prepopulate default compensation components at the employee level for earnings and benefits.
Create New Positions	Select to create positions (and automatically generate position numbers) within PeopleSoft Planning and Budgeting for employees that do not have assigned positions. Clearing the check box will only locate job records that also contain a corresponding position number from your human resource system.
Exclude Temporary Employees	Select to exclude employees designated as temporary in the source job table (PS_BP_JOB_F00) when creating positions. This check box is available when you select the Create Position check box.
Include Employee Contributions	Select to include the employer-paid portion of the employee's benefit retirement contribution.

Note. PeopleSoft Planning and Budgeting does not use any existing employer-paid tax data from PeopleSoft Human Resources. All employer paid tax information is defined as tax defaults in PeopleSoft Planning and Budgeting. Alternatively, if you have existing tax data that you want to use, populate the tax-related source table (PS_BP_COMP_F00), and the system will use this data instead of the defaults during the data staging process.

See Defining Data Sources for Position Activities.

Understanding Stage Processing Details

The staging process populates the following tables in PeopleSoft Planning and Budgeting:

PS_BP_JOB_TBL
PS_BP_POSITION_TBL
PS_BP_SAL_DIS_TBL
PS_BP_BNFT_DIS_TBL
PS_BP_EARN_DIS_TBL
PS_BP_TAX_DIS_TBL

When data staging occurs for a position activity, it will define the first effective date for all employee and position records staged. This date will be the start date of your proposed budget year, as defined by the planning and budgeting scenario. When your proposed budget uses a calendar year, this will be a January 1 effective date. However, if your planning and budgeting scenario does not have a begin date of January 1 (such as a fiscal year beginning July 1), a January 1 effective date which occurs just prior to the proposed budget scenario will be created instead. Creating the first effective date as January 1 provides the necessary information when using maximum gross rules for tax calculations. For example, suppose you are preparing position data for the proposed budget year starting July 1, 2006 to June 30, 2007. In this case, the first effective date created for all employee and position data would be January 1, 2006.

The staging process performs the following:

Staging Process	Type of Distribution	Table Search Order	Funding Distribution Hierarchy
For salary distributions, the stage process selects all current and future-dated job rows from PS_BP_JOB_F00 based on the start date of the planning and budgeting scenario. Current job rows are selected for employees with a status of Active, Leave With Pay, Retired with Pay, or Terminated with Pay. For benefits distributions, the stage process selects all current and future-dated rows from the total compensation table (PS_BP_COMP_F00), based on the start date of the planning and budgeting scenario. For retirement distributions, the stage process selects all current and future-dated rows from benefit participation and retirement plan records based on the start date of the planning and budgeting scenario.	Salary, benefits, and retirement	For salary distributions: PS_JOB_EARNDST_D00 PS_BP_JOB_F00 PS_DEPT_BUDERN_D00 PS_ACCT_CD_D00 For benefits distributions: PS_BP_JOB_F00 PS_DEPT_BUDGET_DED PS_ACCT_CD_D00 For retirement distributions: PS_BP_JOB_F00 PS_DEPT_BUDGET_DED PS_ACCT_CD_D00 Tables updated: PS_BP_JOB_TBL PS_BP_SAL_DIS_TBL PS_BP_BNFT_DIS_TBL	Appointment Position Job Code Position Pool Department
For earnings distributions, the stage process selects all current and future-dated rows from the total compensation table (PS_BP_COMP_F00), based on the start date of the planning and budgeting scenario. Current rows are selected for employees with the status of Active, Leave With Pay, Retired with Pay, or Terminated with Pay.	Earnings	PS_BP_JOB_F00 PS_DEPT_BUDERN_D00 PS_ACCT_CD_D00 Tables updated: PS_BP_EARN_DIS_TBL PS_BP_JOB_TBL PS_BP_BNFT_DIS_TBL PS_BP_SAL_DIS_TBL	Appointment Position Job Code Position Pool Department
If partial or full position management is in effect, the stage process selects all current and future-dated rows from PS_BP_POSITION_D00; otherwise, the process will assign a Planning and Budgeting position number when one is not available.	Positions	PS_DEPT_BUDERN_D00 PS_ACCT_CD_D00 Tables updated: PS_BP_SAL_DIS_TBL PS_BP_POSITION_TBL	Appointment Position Job Code Position Pool Department

If your position-related data does not use or contain account code information in records such as PS_BP_JOB_F00, PS_DEPT_BUDERN_D00, and PS_DEPT_BUDGET_DED, or your organization does not use the account codes in the PeopleSoft HRMS system, you are not required to create one.

When the account code for an appointment is unavailable for salary, earnings, or benefits from your job and position data, a default account can be assigned on the Position Data Default page by business unit when setting up your position budgeting defaults in Planning and Budgeting. On the Position Data Default page, assign a default account used by your position activity when one is not found. Fill in the default account for each of the following fields on the Position Data Default page: Salary Account, Benefit Account, and Earning Account.

When you run the stage process to format and load employee and position data into the PeopleSoft Planning and Budgeting activity tables in the PeopleSoft EPM database, the system validates the dimension (ChartField) distributions imported from PeopleSoft HRMS to ensure that the dimension members associated with each position exist within PeopleSoft Planning and Budgeting. After staging the position activity data for the planning model, you can correct any rows you wish to include in the activity before releasing to your end users.

Note. The stage process automatically creates and assigns a position number to an employee when the existing human resources data does not have a position number. System-generated and existing position numbers are used in position budgeting and can coexist within the PeopleSoft Planning and Budgeting application. For position or job sharing to be supported, use a position number such as the position feature in the PeopleSoft HRMS application. Otherwise, when the format process generates the position number, a single employee ID that has multiple effective dated rows is grouped into a single position number.

See Also

Understanding Position Budgeting Setup

Prerequisites

In addition to the prerequisites listed at the beginning of this chapter, complete the following steps to prepare position and job data in PeopleSoft HRMS:

Run the optional Copy Job Data process (BPJBCOPY) to move a copy of the existing data in the PS_JOB, PS_COMPENSATION, and PS_JOB_EARNS_DIST tables to PS_BP_JOB, PS_BP_COMPENSATION, and PS_BP_JOB_ERN_DIST tables. PeopleSoft Planning and Budgeting uses copies of these tables instead of HRMS tables to ensure that any changes to the data occur in the Planning and Budgeting tables and do not impact any current HRMS job data when running the step increment process.
Run the optional Load Step Increment (BPCMP107) process for budgets to generate any future-dated job data to the PS_BP_JOB and PS_BP_JOB_ERN_DIST tables.
Run the optional Total Compensation process to extract deductions (HR_TCBENEF) and additional pay (HR_TCPYERN) to calculate benefits and earnings compensation that generates estimated annualized benefit and earning costs and adds job data rows to the TC_EE_DETAIL table in HRMS.

Use the delivered ETL tool to copy data into the Operational Warehouse Staging (OWS) tables, and the additional map to populate the Operational Warehouse Enriched (OWE) tables for Planning and Budgeting.

Note. Steps 1–3 listed above are all optional. If you do not require or use the PeopleSoft HRMS processes mentioned in Steps 2 and 3 — Step Increment process for salary projections or Total Compensation to determine annual earning or benefit data — you can alternatively use the ETL jobs that map the PS_JOB record to the PS_BP_JOB_F00 record for Planning and Budgeting.

There are various prerequisite options to leverage PeopleSoft HRMS salary, earnings, and benefit data, and they are as follows:

Salary Data		Benefit and Earnings Data
Salary Only	Salary with Step Increment	Uses Total Compensation	Use Defaults
Run ETL jobs that maps PS_JOB to PS_BP_JOB_F00.	Run the Copy Job Data process. Run the Load Step Increment process. Run ETL jobs that maps PS_BP_JOB to PS_BP_JOB_F00.	Run Total Compensation process for additional pays and deductions to calculate annual amounts. Run ETL jobs that maps PS_TC_EE_DETAIL to PS_BP_COMP_F00.	This is defined in Planning and Budgeting. Defaults are defined at the job code level on the Job Code Defaults page and/or the business unit level on the Position Data Default page.

After you have finished preparing the human resource data for use by PeopleSoft Planning and Budgeting and have run the ETL jobs, you perform the following steps in preparation for running the data staging process:

Define your position budgeting defaults—including salary, benefits, earnings compensation, employer paid taxes, distributions, and job codes—in PeopleSoft Planning and Budgeting.
Assign these position budgeting defaults to the Position Data Default and the Job Code Defaults pages.
Define a planning model to include a position activity, and defined the Data Source defaults.
Map your HR business units to your Planning and Budgeting business unit.
Map your HR departments to the Planning and Budgeting planning center that corresponds to your position activity in the model.
Select the benefit plan types and the earnings codes to be retrieved from the human resource data during stage process.

The following steps apply before releasing the position activity to preparer, but after you have run the data staging process for a position activity scenario:

Access and correct dimension member errors.
Update the staged employee and position activity data before releasing the scenario to end users.

Pages Used to Prepare and Export Job and Position Data

Page Name	Object Name	Navigation	Usage
Map HR Business Units	BP_HR_TO_BU_MAP	Planning and Budgeting, Data Integration, Human Resource Information, Map HR Units and Departments, HR Business Units tab	Define HR business units to map to business unit in planning model that uses position activity. Used during the staging process.
Map HR Departments to Planning Centers	BP_HR_SECURITY	Planning and Budgeting, Data Integration, Human Resource Information, Map HR Units and Departments, HR Departments tab	Define HR departments to map to the planning centers in a business unit model. Used during the staging process.
Earning Codes	BP_VALID_EARNCODES	Planning and Budgeting, Data Integration, Human Resource Information, Earning Codes and Plan Types, Earning Codes tab	Define the earning codes that will be extracted during stage process from the source compensation data for budgeting purposes.
Benefit Plan Types	BP_VALID_PLANTYPES	Planning and Budgeting, Data Integration, Human Resource Information, Earning Codes and Plan Types, Benefit Plan Types tab	Define the plan types that will be extracted during stage process from the source compensation data for budgeting purposes.
Dimension Error Corrections	BP_INTRFC_FIND	Planning and Budgeting, Data Integration, Human Resource Information, Dimension Error Corrections	Correct dimension member errors resulting from the position data staging process.
Dimension Errors	BP_INTRFC_FIND2	Click the Position link on the Dimension Error Corrections page.	Correct Dimension errors in compensation distributions.
Edit Employee Data	BP_SAL_STG_ADJ	Planning and Budgeting, Data Integration, Human Resource Information, Edit Employee Data	Adjust or update employee position data before releasing a position activity-scenario in a planning model.
Export to HR	BP_EXPORT	Planning and Budgeting, Data Integration, Human Resource Information, Export to HR	Transfer position budget data from planning model tables to the warehouse, in preparation for moving it to a human resource application or using as a data source for a new position activity scenario.

Mapping Human Resource Business Units to Planning Model

Access the Map HR Business Units page.

Select one or many HR Business Units that map to a single business unit in Planning and Budgeting. The HR business units listed on this page apply to any planning model associated with the business unit displayed in the header of the Map HR Business Units page. Any employee and position data from HR associated with the HR business unit data can be retrieved during the data staging process for a planning model.

Mapping HR Departments to Planning Centers

Access the Map HR Departments to Planning Centers page.

Planning Center Dimension

Select the dimension (ChartField) that is defined as the planning center in any planning model associated with a specific business unit.

Note. You may only define one dimension per business unit that is used as a planning center for position activities. For example, if you define Department as your planning center for Business Unit A, any position activities associated with planning models that are for Business Unit A should use Department as the planning center when there is human resource data available.

Auto Fill

When your HRMS departments and planning centers have a one-to-one relationship (when Department is also your planning center), click Auto Fill to auto-populate all planning center values. Even when your PeopleSoft HRMS department and planning center are the same, this setup is still required.

Show Blank Rows

Click to display only the rows that do not contain a planning center. Any data associated with an HR department that is not mapped to a corresponding planning center cannot be mapped during the stage process.

HR Department and Department(or other Dimension)

Select a planning center (for example, Department) value for each department from PeopleSoft HRMS.

The HR Department identifies the department associated with positions located in the source tables. The planning center description depends on the planning center definition. The stage process uses Map HR Department to Planning Center to map positions to planning centers. After you stage a position activity in a planning model and associate it with a planning center, you cannot change its relationship to the HR Department.

Note. You can also think of this relationship as establishing ownership of position data from HR. Only one planning center has visibility to a single position number.

See Also

Understanding Position Budgeting Setup

Including Earning Codes during Stage

Access the Earning Codes page.

Check the earning codes for an effective date for human resource data that are to be processed by data staging, or click Select All to check all earning codes listed. Your earning codes would have been copied from your HR system by using the ETL tool. The earning codes you select here only apply to the staging of the existing compensation data from the HR system, and does not restrict their use during data entry by end users.

Including Benefit Plan Types during Stage

Access the Benefit Plan Types page.

Check the benefit plan types for an effective date for human resource data that are to be processed by the staging process, or click Select All to check all benefit plan types listed in the system. The plan types you select here only apply to the staging of the existing compensation data, and does not restrict their use during data entry by end users.

Correcting Dimension Errors

Access the Dimension Error Corrections page.

Dimension Filters

To select an invalid dimension (ChartField) member, click the dimension's (for example, Department) prompt table button. After selecting an invalid dimension member, click Find to display the positions that contain that invalid dimension and member based on your search criteria. The system displays only invalid dimensions found within the Dimension Filter section.

Position

Click the position number link to access the Dimension Errors page where you can correct the dimension errors.

Note. If there are many rows of data that require dimension corrections, consider correcting the source position data or changing your defaults before running the data staging process. Otherwise, you must access the Dimension Error Correction page to correct invalid dimensions and members for each position row.

Correcting Human Resource Dimension Errors

Access the Dimension Errors page.

Salary Distribution,Benefits Distribution,Earnings/Allowance Distribution,andTax Distribution

The system displays only invalid data. When a position's data appears in the Job Details grid, the information contains some incorrect dimension member information. For the dimension member in error for any salary, benefit, earning, or tax data, correct the data if you want it to be included within the position activity associated with a planning model.

After you correct and save the data entered on this page, the data is inserted into the staged tables that were populated during the data stage a process.

Note. Since the changes you make are directly inserted into the staged tables, you do not need to run any additional processes.

You are only allowed to perform these changes before a position activity scenario is released to end users. Once the activity-scenario status leaves the 'staged' state, you can no longer perform this operation, and any position data that contained errors is not included within your position budgeting activity.

Updating Position Data Imported and Staged from PeopleSoft HRMS

Access the Edit Employee Data page.

Search and Filter Options

Activity

Select the activity for a planning model and scenario for which you are editing data.

Adjustment Type

Select Salary, Earnings, or Benefits to indicate the type of adjustment that you want to make.

The Salary Adjustment, Earning Adjustment, or Benefit Adjustment grid displays at the bottom of the page depending on the selected Adjustment Type.

When selecting and adjustment type of Earnings, you need to define an earnings code to adjust.

When selecting and adjustment type of Benefits, you need to define an plan type to adjust.

Job Code, Union Code, Position From, and Position To

Use these fields to specify additional search parameters to narrow the number of retrieved rows. When you click Find, values for positions that meet your criteria display in the grid.

Default Option

Percentage or Amount	Enter the value of the adjustment as a percentage or fixed amount. Use a minus sign to indicate a decrease. The system applies the value to the Before Adjustment value for selected rows in the Adjustment grid.
Select All orClear All	Click to select the check boxes associated with each row displayed in the adjustment grid. When you click Adjust Selected, the system adjusts each selected row. The system toggles between Select All and Clear All.
Refresh	Click to update the adjustment amounts in the Adjustment Total for Selected Entries box. This does not apply the changes, it just shows you what the net change will be. The Adjust Selected button applies the changes.
Adjust Selected	Click to apply the defined default adjustment value to all selected rows.

Salary Adjustment, Earning Adjustment, or Benefit Adjustment

Select	Use to specify the rows that you want to adjust.
Percent and Manual Amt (manual amount)	Enter values to apply adjustments to individual rows and override the default percentage defined in the Default Option group box.

Adjustments made to salary rows are incremental updates to the existing row whereas adjustments made to earnings and benefit type rows replace the existing amount.

Adjustments to employee job and position rows are made against the existing effective date. You cannot create new effective dates using this page.

Note. There is no adjustment option for employer paid taxes.

Exporting Position Data from the Planning Model

Access the Export to HR page.

Business Unit, Planning Model ID, Scenario, and Activity

Specify the parameters for the planning model containing the job and position budget data that you want to export.

Export All Positions

Select to export all job and position costs saved in the planning model, including positions defined as Exclude from Budget Calc on the Position Data page. If you clear this check box, the system does not export positions specified as excluded from budget calculations.

Override Position Scenario and Scenario

Select this check box to export the employee job and position budget data to the destination tables using the new scenario that you define on this page. Overriding the scenario lets you export planning and budgeting position data to a different scenario (such as for reporting purposes), or reuse by a new position activity-scenario.

Clear this check box to export data using the original GL scenario associated with the proposed plan or budget, as part of the planning and budgeting Scenario definition.

The Export to HR process (BP_EXP) exports position planning data from the master version in the planning model into the following tables located in the PeopleSoft EPM environment as its export destination:

PS_BP_JOB_F00
PS_BP_POSITION_D00
PS_BP_COMP_F00

Note. The export process does not directly move data to the PeopleSoft HRMS database. After data is placed in the above tables, you will need to use the ETL tool to transfer data to the human resource database.

See Also

Adding and Copying Positions

Moving Position Data Back to HRMS

Run the ETL process to move position data back to PeopleSoft HRMS. ETL moves the data from EPM Planning and Budgeting tables to the HRMS staging tables as follows:

From PeopleSoft EPM Warehouse Tables	To PeopleSoft HRMS Staging Tables
PS_BP_JOB_F00	PS_BP_JOB_EXP
PS_BP_POSITION_D00	PS_BP_POSITION_EXP
PS_BP_COMP_F00	PS_BP_SAL_DIS_EXP PS_BP_BNFT_DIS_EXP PS_BP_EARN_DIS_EXP PS_BP_TAX_DIS_EXP

Note. The PS_BP_COMP_F00 contains all the compensation information of salary, benefits, earnings, and tax; however, there are four separate staging tables in PeopleSoft HRMS which each have their own corresponding ETL job (map).

Importing Position Data Into PeopleSoft HRMS

After you export data from the planning model and run the ETL tool to map stage data back to PeopleSoft HRMS database, you import this data into the appropriate PeopleSoft HRMS budget tables.

Once the data is staged to PeopleSoft HRMS, you populate human resource budget tables by running the Import Budgeting Data (BPIMPORTHR) application engine process in the PeopleSoft HRMS database.

The process moves copied position budget data from the staging tables to the following budget tables in PeopleSoft HRMS database:

PS_BD_DISTR_TBL
PS_BD_JOB_TBL
PS_BD_POSITION_TBL

Note. This Import Budgeting Data process does not transfer the compensation components for earning and employer paid tax data for human resource budget tables.

Note. The staging table's Ledger Name field (BP_LEDGER_NAME) in PeopleSoft HRMS is equivalent to the planning and budgeting scenario field (BP_SCENARIO) used by EPM Planning and Budgeting.

Integrating with Third-Party Human Resource Applications

If you are not using PeopleSoft applications as a data source for position and job data, you can use data from non-PeopleSoft applications by populating the Operational Warehouse Enriched (OWE) tables in the PeopleSoft EPM database (PS_BP_JOB_F00, PS_BP_POSITION_D00, and PS_BP_COMP_F00), and then completing the other integration steps described under the integrating with PeopleSoft HRMS applications section of this chapter.

If you require your human resource source data to be stored in the OWS tables, use the following tables: PS_S_BP_JOB, PS_S_POSITION_DATA, and PS_TC_EE_DETAIL.

Integrating with EnterpriseOne

Planning and Budgeting integrates with EnterpriseOne as follows:

Planning models support a standard budget ledger type. Data sourced from EnterpriseOne populates actual and standard budget ledgers for use in the planning model.

Note. There are no delivered maps to populate the control or project budget ledgers; therefore, you should not use control and project budgeting types when defining our Scenario Group.
Planning and Budgeting supports line item activity types for a standard planning model. Data sourced from EnterpriseOne is inserted into ledger tables used by the line item activities.

Note. Do not use line item validation. Disable the Enforce Budget flag for line item activity types since no combination edit rules are available from the data source.

Note. There are no delivered maps to populate human resource or asset data for the position and asset activity types.

Note. If using Asset Budgeting activity, change your accounts to use the Account Type A, because they are the only account types retrieved through the BP_ASSET_ACCT_VW view.

We do not support exporting budget data back to EnterpriseOne. You can export budget data out of the planning model into the Enterprise Performance Management Warehouse; however, there are no delivered ETL jobs to send data back to your source database. In other words, even though both check boxes are available on the run control page to export ledger data, we do not have maps to move the budget data back to PeopleSoft EnterpriseOne.

You should consider the following setup items:

Set up the Account Type options in Planning and Budgeting based on the account types from the data sourced. The account types from EnterpriseOne are B (balance sheet) and I (income statement). In PeopleSoft EPM, refine the account types to the desired Planning and Budgeting account types.

Optionally, you can change the account types for the EnterpriseOne accounts to EPM account types, navigate to EPM Foundation, Business Metadata, Business Framework, Accounts and then change the EnterpriseOne account types B or I to the relevant account types Asset (A), Expense (E), Liability (L), or Revenue (R). It is not required that you use these account types; accounts used in line item activities can remain as B and I account types from EnterpriseOne.
Rate type should be set to CRRNT.
Create a balanced, node-oriented tree containing your planning centers. This is the minimum tree requirement for using Planning and Budgeting. A planning center tree represents the rollup and approval structure for the plan and budget development process. The dimensions available as the planning center is dependent upon data sources.

PeopleSoft Budgeting	Select as the export destination to export data to the Planning and Budgeting ledger table in the PeopleSoft EPM database. If you select this check box, the Replace all Ledger Data check box displays.
PeopleSoft General Ledger	Select as the export destination to export data to staging table in the PeopleSoft EPM database, in preparation for transference to the financial database. Note. If you select this check box, the Replace all Ledger Data check box is hidden; however, the Replace all Ledger Data check box is still available on the Import Budgeting Data page located in the PeopleSoft Financial Management database.
Business Unit, Planning Model ID, Scenario and Activity	Enter values to define the model, scenario and line item activity that you want to export.
Export Line Item Zero Amounts	Select this check box to export line item rows that contain zero amount values. Clear this check box to drop any rows containing zero amount during the export process to the ledger or staging table.
Replace all Ledger Data	Select this check box to delete all ledger data associated with business unit, ledger, scenario, and fiscal year, and replace it with the data that you are defining for the export process. In other words, it lets you specify the ledger data that you want updated in the appropriate ledger table. Clear this check box to update only the ledger table rows associated with the scenario and those planning centers that have been updated since the last export process. This check box only displays if you select PeopleSoft Budgeting as the Export Destination.
Override GL Scenario	Select this check box to export plan or budget data to the destination budget ledger table (_F00 tables) using the scenario that you define on this page. Overriding the scenario lets you export planning and budgeting data to a different scenario (such as for reporting purposes). Clear this check box to export data using the GL scenario originally associated with the proposed plan or budget, as part of the planning and budgeting scenario definition. This check box only displays if you select PeopleSoft Budgeting as the Export Destination. Note.* If, under Export Destination, you selected both the PeopleSoft Budgeting and PeopleSoft General Ledger check boxes, the Override GL Scenario only applies to the data exported to Planning and Budgeting; data exported to the General Ledger does not have this check box on the Import Budgeting Data page. The GL scenario field is populated with the original value defined by the Planning and Budgeting scenario definition.

Planning Center Dimension	Select the dimension (ChartField) that is defined as the planning center in any planning model associated with a specific business unit. Note. You may only define one dimension per business unit that is used as a planning center for position activities. For example, if you define Department as your planning center for Business Unit A, any position activities associated with planning models that are for Business Unit A should use Department as the planning center when there is human resource data available.
Auto Fill	When your HRMS departments and planning centers have a one-to-one relationship (when Department is also your planning center), click Auto Fill to auto-populate all planning center values. Even when your PeopleSoft HRMS department and planning center are the same, this setup is still required.
Show Blank Rows	Click to display only the rows that do not contain a planning center. Any data associated with an HR department that is not mapped to a corresponding planning center cannot be mapped during the stage process.
HR Department and Department(or other Dimension)	Select a planning center (for example, Department) value for each department from PeopleSoft HRMS. The HR Department identifies the department associated with positions located in the source tables. The planning center description depends on the planning center definition. The stage process uses Map HR Department to Planning Center to map positions to planning centers. After you stage a position activity in a planning model and associate it with a planning center, you cannot change its relationship to the HR Department. Note. You can also think of this relationship as establishing ownership of position data from HR. Only one planning center has visibility to a single position number.

Dimension Filters	To select an invalid dimension (ChartField) member, click the dimension's (for example, Department) prompt table button. After selecting an invalid dimension member, click Find to display the positions that contain that invalid dimension and member based on your search criteria. The system displays only invalid dimensions found within the Dimension Filter section.
Position	Click the position number link to access the Dimension Errors page where you can correct the dimension errors.