hiThis chapter provides overviews of PeopleSoft trees and the ACE (Analytic Calculation Engine) interface and discusses how to:
Identify data integration sources.
Configure dimensions for Planning and Budgeting.
Activate inactive dimensions.
Set up file transfer protocols.
Set up single sign-on.
When using PeopleTools trees for setup around planning centers and dimensions, there are specific tree requirements for Planning and Budgeting.
For the planning center dimension tree, all planning centers that require a detail plan or budget must reside on the same level of the tree, and there cannot be missing levels. Missing levels occur when some sections of the tree skip levels while other sections do not.
For all other dimension trees, when using members from the detail level of the tree for plans and budgets, it is not necessary they reside on the same level of the tree. But when using a non-detail level for dimension summarization, you may only pick one level and therefore the rollup values you wish to use should reside on the same level of the tree.
All trees used in Planning and Budgeting for dimensions or planning center trees, must be node-oriented trees. Standard detail trees cannot be used by Planning and Budgeting. The level you pick as the planning center must be a node value, and not a detail level.
Using trees is only required for the planning center dimension. They are optional for defining other dimensions, or when using the account category as a filter for working on and reporting against plans and budgets.
Note. A node-oriented tree is one where all the members in the tree reside in the dimension table for all detail and node values. A standard detail tree uses the PS_TREE_NODE_TBL table for nodes, which is not used by Planning and Budgeting.
See Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager.
The PeopleTools ACE (Analytic Calculation Engine) is used in conjunction with Planning and Budgeting line item activities. The ACE tool is not used in conjunction with asset and position activity types; they are built using PeopleCode.
The PeopleTools ACE is a delivered set of tools, and only requires analytic servers to be turned on as part of application server configuration.
See Enterprise PeopleTools PeopleBook: PeopleSoft Analytic Calculation Engine.
To identify the source of your general ledger, human resource, and asset data, use the BP_INSTALLATION.GBL component.
Page Name |
Object Name |
Navigation |
Usage |
BP_INSTALLATION |
System Administration, Maintain System Options, Installation Options |
Specify the existing general ledger, human resource, asset management, and project applications used for data integration. |
Access the Budgeting Installation Options page.
General Ledger Interface, HRMS Interface, Asset Management InterfaceandProject Interface |
Select the source of the data interface: PeopleSoft 8.3: Indicates integration with the PeopleSoft 8.3 products. (HRMS only). PeopleSoft 8.4/8.8: Indicates integration with the PeopleSoft 8.4 and 8.8 FDM products. (Asset Management, Project Management and General Ledger). PeopleSoft 8.8: Indicates integration with the PeopleSoft 8.8 products. (HRMS only). PeopleSoft 8.9: Indicates integration with the PeopleSoft 8.9 products. (HRMS only). Third Party Vendor: Indicates integration with non-PeopleSoft applications. |
Sequence Number Generation |
Select for a DB2 installation if your database is configured to use the COUNTER() function to generate sequence numbers. This function is part of the member udf.c in the sqllib/samples/c directory. Follow the instructions in the README member to set up this function. Warning! If you select this check box and your database is not configured appropriately, some jobs will fail. Contact technical support for additional information. |
To configure and maintain dimensions use the BP_CF_MAINT.GBL component.
This section provides an overview of dimension selection and discusses how to configure dimensions.
The system accesses your data integration source selections from the Budgeting Installation Options page to determine which active and inactive dimensions are available for use as the planning center or as a dimension (also known as ChartFields) in the planning model. You cannot change these dimension options, only their status.
You should consider both integration sources for human resource data as well as for financial data when determining the available dimensions that you want to use for position budgeting. You may only want to use dimensions that are supported in both the financial data integration source and human resources data integration source. You defined these integration sources using the Budgeting Installation Options page under Maintain System Options.
The following table specifies with an X the dimensions that you can use as the planning center and as the dimension in a Planning and Budgeting model:
Dimension |
Planning and Budgeting |
Dimensions (ChartFields) Used by Source Systems |
||||
Dimensions Allowed as Planning Center |
Third-Party Applications (FDM and HCM) |
PeopleSoft Financial Management 8.4/8.8 |
PeopleSoft HRMS 8.3/8.8/8.9 |
PeopleSoft EnterpriseOne 8.10/8.11 |
||
Account |
X |
X |
X |
X |
||
Activity ID |
X |
X |
X |
X |
||
Affiliate |
X |
X |
X |
X |
||
Alternate Account |
X |
X |
X |
|||
Budget Reference |
X |
X |
X |
X |
||
ChartField 1 |
X |
X |
X |
X |
X |
|
ChartField 2 |
X |
X |
X |
X |
X |
|
ChartField 3 |
X |
X |
X |
X |
X |
|
Class Field |
X |
X |
X |
X |
X |
|
Currency Code |
X |
X |
X |
X |
||
Department |
X |
X |
X |
X |
X (Department ID only) |
|
Dimension 1 (Note 1) |
X |
|||||
Dimension 2 (Note 1) |
X |
|||||
Dimension 3 (Note 1) |
X |
|||||
E1 Business Unit (Note 2) |
X |
X |
X |
|||
E1 Sub Account (Note 2) |
X |
X |
||||
Fund Affiliate |
X |
X |
X |
X |
||
Fund Code |
X |
X |
X |
X |
X |
|
Operating Unit |
X |
X |
X |
X |
X |
|
Operating Unit Affiliate |
X |
X |
X |
X |
||
Product |
X |
X |
X |
X |
X |
|
Program Code |
X |
X |
X |
X |
X |
|
Project |
X |
X |
X |
X |
X |
|
Resource Analysis Type |
X |
X |
X |
X |
||
Resource Category |
X |
X |
X |
X |
||
Resource Sub Category |
X |
X |
X |
X |
||
Resource Type |
X |
X |
X |
X |
||
Statistics Code |
X |
X |
X |
X |
||
Subledger (Note 2) |
X |
X |
||||
Subledger Type (Note 2) |
X |
X |
Note. (1) Dimension 1–3 are not dimensions/ChartFields used or available in other PeopleSoft source systems. They are exclusively
used by Planning and Budgeting as a dimension that can be used and customized by an organization requiring different dimensions
than those that integrate with other systems. These Dimensions 1–3 are only intended for Line Item Activity types. They cannot
be exported back to PeopleSoft Enterprise source systems.
(2) These dimensions are delivered to integrate with PeopleSoft EnterpriseOne. Only the E1 Business Unit can be a planning
center. These are only intended for Line Item Activity types. They cannot be exported back to PeopleSoft EnterpriseOne source
systems.
Note. Budget Period, Fiscal Year, and Accounting Period do not require a dimension definition because, by default, the element of
time is part of the planning model and determined by the model's setup.
Planning and Budgeting does not support the PC Business Unit dimension.
Page Name |
Object Name |
Navigation |
Usage |
BP_CF_MAINT |
System Administration, Maintain System Options, Dimension Configuration |
Identify dimension (ChartFields) availability and define status for Planning and Budgeting. |
Access the Dimension Configuration page.
Status |
Select Active next to each dimension (ChartField) that you want to use in Planning and Budgeting or select Inactive next to each dimension (ChartField) that you do not want to use in Planning and Budgeting. |
Planning Center Dimension |
When selected, indicates the dimension can be used to define a planning center. |
Dimension/ChartField |
When selected, indicates the dimension can be used for the planning model. |
Not all dimensions in the EPM database are active by default. Depending on the subrecord, five to eight dimensions are delivered as inactive because, on database platform DB2/OS390, indexes have a limit of 255 characters. If PeopleSoft were to activate all dimensions, then some indexes would exceed that limit.
This section describes how to activate an inactive dimension. If you do not intend to use these inactive dimensions, then you can leave them inactive and ignore the remainder of this section. If you are unsure whether or not you will use a dimension, consider activating it. Not using an active dimension has minimal system impact; whereas, storing data in an inactive dimension could cause data integrity errors.
For subrecord BP_CF9B_AK_SBR, the following eight dimensions are delivered as inactive:
Dimension ID |
Dimension Description |
AFFILIATE_INTRA1 |
Fund Affiliate |
AFFILIATE_INTRA2 |
Operating Unit Affiliate |
CHARTFIELD1 |
ChartField 1 |
CHARTFIELD2 |
ChartField 2 |
CHARTFIELD3 |
ChartField 3 |
DIMENSION1 |
Dimension 1 |
DIMENSION2 |
Dimension 2 |
DIMENSION3 |
Dimension 3 |
For subrecord CF9A_PK_SBR, the following five dimensions are delivered as inactive:
Dimension ID |
Dimension Description |
AFFILIATE_INTRA1 |
Fund Affiliate |
AFFILIATE_INTRA2 |
Operating Unit Affiliate |
CHARTFIELD1 |
ChartField 1 |
CHARTFIELD2 |
ChartField 2 |
CHARTFIELD3 |
ChartField 3 |
To activate a dimension:
Launch Application Designer.
Select File, Open.
In the Open Definition dialog box, set Definition to Record and Type to Subrecord..
Enter subrecord BP_CF9B_AK_SBR, and then click Search.
To view the key field setting of the active subrecord, select View, Use Display.
Eight of the dimensions are not marked as keys.
Right-click each dimension that you want to activate, and then click Record Field Properties.
In the Record Field Properties dialog box, select Key and Search Key, and then click OK.
On database platform DB2/OS390, to keep indexes within the 255-character limit, for each dimension that you activate, be sure to deactivate any unused dimensions by clearing Key and Search Key.
Save your changes to the subrecord.
For subrecord CF9A_PK_SBR, repeat the earlier steps. Use this subrecord if you are modifying LEDGER_PROJ.
In Application Designer, select File, New to create a project.
Select Insert, Definitions Into Project, and then insert the following record IDs that contain either subrecord CF9A_PK_SBR or BP_CF9B_AK_SBR:
LEDGER_PROJ |
BP_LED_E00 |
BP_LN_PCANN_T |
BP_ALLC_AMT_T |
BP_LED_F00 |
BP_LN_PCPRD_T |
BP_ALLC_TAM_T |
BP_LED_KK_E00 |
BP_LN_PRDTL_T |
BP_ASSET_T |
BP_LED_KK_F00 |
BP_LNITMRPT_T |
BP_ASST_DPR_T |
BP_LED_KK_T |
BP_TGT_LEDB_EX |
BP_CF_LI_ERR |
BP_LED_PROJ_E00 |
BP_TGT_LEDB_T |
BP_DIM_DTL_AET |
BP_LED_PROJ_F00 |
BP_TGT_LEDC_EX |
BP_DIM_DTL_TBL |
BP_LED_PROJ_T |
BP_TGT_LEDC_T |
BP_DIMLST1_T |
BP_LED_T |
BP_TGT_LEDP_EX |
BP_LD_BDG_TT |
BP_LI_FLX_INFC |
BP_TGT_LEDP_T |
BP_LD_TT |
BP_LINE_CF_SBR |
BP_TGT_LINE |
BP_LED_BUDG_E00 |
BP_LINE_ITM_T |
BP_TGT_LINE_ERR |
BP_LED_BUDG_F00 |
BP_LINE_WRK |
BP_TGT_LINE_T |
BP_LED_BUDG_T |
BP_LN_AMUNT_T |
Save your changes.
Select Build, Project.
In the Build dialog box, select Create Indexes and Execute and build script.
Click Settings, and then select Recreate index only if modified.
Click OK.
In the Build dialog box, click Build.
Note. For database platforms DB2/OS390 and DB2/UNIX, you must recreate all views.
To set up file transfer protocols use the URL_TABLE.GBL component.
This section describes how to set up file transfer protocols for attachments and lookup tables.
Page Name |
Object Name |
Navigation |
Usage |
URL_TABLE |
Planning and Budgeting, System Administration, Maintain System Options, FTP Server |
Set up file transfer protocol (FTP) to use file attachments and lookup tables. |
Access the URL Maintenance page.
Use this page to set up server connectivity for file transfers. Use FTP when you use driver lookup tables or attach files and want to make them available to budget users. References uniform resource locators (URLs) saved here from page controls.
URL |
Enter the full uniform resource locator for the following two required URL definitions: BP_ATTACHMENT_FTP_SERVER identifies the FTP address for Planning and Budgeting documentation attachments. CSV_IMPORT_APP_SERVER_DIR identifies the directory to find and upload comma-delimited files for driver lookup tables used with methods. |
See Enterprise PeopleTools PeopleBook: Data Management, "PeopleTools Utilities," URL Maintenance
Links to the Financials Portal are available from within PeopleSoft Planning and Budgeting, but they require that Single Sign-on be set up between PeopleSoft Enterprise Performance Management and PeopleSoft Financials databases.
Follow these steps to set up single sign-on.
In the EPM database, navigate to the Portal tab of your ERP Node Definition using the path PeopleTools, Portal, Node Definitions.
Change the content of the Portal URI Text field and Content URI Text field to point to the web server of the Financials database. Make sure the machine name, psc, and psp are in lowercase.
Click Save .
In the EPM database, navigate to Structure and Content using the path PeopleTools, Portal, Structure and Content.
Click the EPM Foundation link.
Click the EPM Setuplink.
Click the Ledger Setup link.
Click the Ledgers link.
Click the Edit link next to the Ledger For A Unit (FDM) line item. The Content Ref Administration page appears.
In the Node Name field, enter the name of your ERP node.
(Optional) Set the Financials pages to open in a new window. Enter information in the Content Reference Attributes section.
Enter NAVNEWWIN in the Name field.
Enter True in the Attribute Value field.
Save and exit the page.
Access the Content Ref Administration page for ComboEdit Budget Inquiry.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the ComboEdit Budget Inquiry line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for ComboEdit Definition.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the ComboEdit Definition line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for ComboEdit Group.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the ComboEdit Group line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for ComboEdit Inquiry Selection.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the ComboEdit Inquiry Selection line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for ComboEdit Rule.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the ComboEdit Rule line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for ComboEdit Template.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the ComboEdit Template line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for Commitment Control Setup.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the Commitment Control Setup line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Access the Content Ref Administration page for Review Combo Edit Build.
From the Structure and Content page, click the Planning and Budgeting link.
Click the Activity Preparation link.
Click the Edit link next to the Review Combo Edit Build line item. The Content Ref Administration page appears.
Repeat steps 5 and 6.
Have your server administrator setup the web servers, portal configuration and security configuration for single sign-on. This step requires server setup. (See PeopleTools PeopleBooks)
Make sure the Operator ID being used in EPM is also defined in the Financials databases, with access to the components being referenced. Have your Security Administrator update Operator Security in the Financials database to ensure that you have read-only access to the following components:
See Enterprise PeopleTools PeopleBook: System and Server Administration
Menu |
Component/Object ID |
Item Label/Page Name |
ESTABLISH BUSINESS UNITS |
BUSINESS_UNIT_LED |
Ledgers for A Unit |
DESIGN_CHARTFIELDS |
COMBO_EDIT_TMPL1 |
ChartField Editing Template |
DESIGN_CHARTFIELDS |
COMBO_CF_DEFN |
Combination Definition |
DESIGN_CHARTFIELDS |
COMBO_RULE |
Combination Rule |
DESIGN_CHARTFIELDS |
COMBO_GROUP |
Combination Group |
DESIGN_CHARTFIELDS |
COMBO_SEL_INQ |
Review Combination Build |
DESIGN_CHARTFIELDS |
COMBO_INQ_SEL |
Review Combination Selector Table Data |
DESIGN_CHARTFIELDS |
COMBO_INQ_BUDG |
Review Budgets Combination Data |
MANAGE_COMMITEMENT_CONTROL |
KK_BUDGET |
Commitment Control Budget Definition |
See PeopleTools 8.4x PeopleBook, Security Administration, “Setting up Digital Certificates and Single Signon”
See For PeopleTools 8.45, Enterprise PeopleTools 8.4x PeopleBook: Internet Technology, Configuring the Portal Environment, “Defining Portal Nodes”
See For PeopleTools 8.45, Enterprise PeopleTools 8.4x PeopleBook: Internet Technology, Configuring the Portal Environment, “Implementing Single Signon Functionality”
See For PeopleTools 8.45, Enterprise PeopleTools 8.4x PeopleBook: Internet Technology, Administering Portals, “Administering Content References”