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 topic, you can use your Project Costing budget data as a source for Planning and Budgeting. Before you can load the data into the EPM Warehouses using the delivered ETL tool, run the application engine process (PC_PC_BD_B) in the Project Costing database from the Send to Budgeting page to move data from the PS_PROJ_RESOURCE table to PS_LEDGER_PROJ.
After 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 Project Costing, consider the following guidelines:
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 are 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 DIMENSION1, DIMENSION2, and DIMENSION3 fields.
Consider evaluating your key requirements based on your data and reset these keys as appropriate to ensure that indexes are built correctly.
Note: Changing key requirements will affect the entire EPM database.
After you enable the required keys, access the Dimension Configuration page in Planning and Budgeting to set the status as Active for the dimensions that you plan to use with your project budgets.
When implementing Planning and Budgeting using project budget types, implement with a one-to-one relationship between your warehouse business unit and your project business unit.
Because of the logic related to the project business unit and the project, do not consolidate the project business units or IDs.
To define the planning center for your line item project budget, you can use any available dimension in Planning and Budgeting.
When you use the project dimension (ChartField) as the planning center, the same rules apply for defining trees when you must use a node-oriented tree.
On the Budgeting Installation Options page, select your project costing interface as PeopleSoft when your source is PeopleSoft Project Costing.
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. The information about which project integration template is used is needed to determine which general ledger business unit the project ID will be mapped to. Planning models created in Planning and Budgeting are defined by a general ledger business unit, and not the project business unit.
When adding a new project in the EPM Warehouses using the project maintenance page, the integration template value is required only if you are using project budget types.
Use the ETL tool to copy the project integration template table (PC_INT_TMPL_TBL) into Planning and Budgeting.
When integrating with Project Costing, no online validation exists between the project and activity ID.
To optionally accommodate this requirement, consider using combination edits in conjunction with the enforce budget flag enabled for the activity scenario in the planning model.
When using the online analysis for line item activities, no descriptions or validations exist to filter—only the activity IDs associated and allowed with a project.
For the Activity ID table, use the PS_PROJ_ACTIVITY table for Planning and Budgeting.
When moving data back to Project Costing, the Activity ID is required with the Project ID.
Note: When integrating with 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 use only line item activity type in the planning model. Asset and position activities are not available when you are using budgeting type of project budget ledger, as defined on the Scenario Group page that is associated with the planning model.
See the product documentation for PeopleSoft FSCM: Project Costing
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:
Access the Export to General Ledger page and run the process with an Export Destination of PeopleSoft General Ledger for the defined planning model and scenario.
Use the ETL tool to move the project budget data back to the Financial Management database.
The ETL jobs move data from the PS_BP_LEDGER_BDEXP staging table in the EPM database to the table with the same name in PeopleSoft General Ledger, and from PS_BP_LEDG_DTL_VW in EPM to PS_BP_LEDG_DTL_EXP in 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 Understanding Exporting General Ledger Budget Data from the Planning Model.