FIN: Local Configuration Guide - Project Costing

This document contains the configuration decisions made and values to be used in deployment of the Contracts Module of the Oracle’s PeopleSoft FSCM 9.2 application.  As such, all additional documentation must be in agreement with the related items described herein.  Should conflict arise with information contained in another document, the data in this document shall be considered valid and that of the other shall be deemed incorrect.

The Contracts Configuration Guide explains necessary tables needed to setup an institution in the PeopleSoft system.  The order of the configuration tables presented in this document adheres to the table setup sequence required to successfully set up all tables.

Business Unit Definition

Create a Project Costing Business Unit. Other than the GL Business Unit, the same defaults are set for all Districts.

These are general, overall settings for the specific Business Unit. These include currency settings, units of measure defaults for time, and the identification code for the monthly calendar being used and the related General Ledger Business Unit.

Business Unit Definition Page Example

Navigation: NavBar > Navigator > Set Up Financials/Supply Chain > Business Unit Related > Project Costing > Project Costing Definition

Security: ZD PC Central Config Inq
Menu: ESTABLISH_BUSINESS_UNITS
Component: PC_BU_DEFN
Page: BUS_UNIT_TBL_PC
Action: A/UD

Business Unit Options

Set the options for the Project Costing Business Unit. Same options are set for all Districts.

Again, these are settings that apply to the specific Business Unit. The Project Costing Options page sets some defaults for the module’s integration with other PeopleSoft modules, and a few items that relate specifically to Project Costing (ChartField editing, Pricing Options, Work Breakdown Structure, and Cost Collection Options). The Budget Alerts tab is identifying the method and levels to be used on a stop-light warning (Green, Yellow, Red) that appears on a Budget to Actual screen. The Asset Integration Rules set the defaults for how Project Costing data will be delivered to Asset Management (if this happens at all). The Copy Template tabs identifies what data gets copied when the Project Copy feature is used and the Delete Utility Tables tab identifies the records from which data will be deleted if a Project is deleted. Note that the setting is such that you cannot delete a Project if the Project has any transactions.

Business Unit Options Page Example

Navigation: NavBar > Navigator > Set Up Financials/Supply Chain > Business Unit Related > Project Costing > Project Costing Options

Security: ZD PC Central Config Inq
Menu: ESTABLISH_BUSINESS_UNITS
Component: PC_BUS_UNIT_OPT
Page: BUS_UNIT_OPT_PC
Action: UD

Integration Templates

Identify default purchasing, asset management, and general ledger Business Units with which this PC Business Unit will integrate.

Integration Templates identify the other module Business Units with which this Project Costing Business Unit will integrate. You’ll note that this applies to Purchasing, Asset Management, and General Ledger. The strategy in the ctcLink project has been to have a one-to-one relationship between module Business Units.

Integration Tempaltes Page Example

Navigation: NavBar > Navigator > Set Up Financials/Supply Chain > Product Related > Project Costing > Project Options > Integration Templates

Security: ZD PC Local Configuration Inq and ZZ PC Local Configuration
Menu: STRUCTURE_PROJECTS
Component: PROJ_INT_TMPL
Page: PROJ_INT_TMPL_01
Action: A/UD

Accounting Rules

Accounting Rules are used to create accounting entries to post to GL for transactions that originate in Project Costing. The only Accounting Rules that exist at this point relate to transactions created for the Billing module integration. These same rules are consistent, minus the Business Unit values, for all Business Units.

For the transactions that get created in Project Costing that you also want to post to General Ledger, you need an Accounting Rule to provide the necessary information for the system to create an accounting entry to be posted in General Ledger. This page is where the accounting rules are created. You will note that accounting rules are created by Business Unit  every Business Unit has their own list.

Rate Sets Page Example

Navigation: NavBar > Navigator > Set Up Financials/Supply Chain > Product Related > Project Costing > General Options > Accounting Rules

Security: ZD PC Local Configuration Inq and ZZ PC Local Configuration
Menu: STRUCTURE_PROJECTS
Component: PSA_ACCT_SETUP
Page: PSA_ACCT_SETUP
Action: A/UD

Rate Sets

Define rules for the creation of new transactions from existing transactions. Example illustrated is to create billable transactions from expenditure transactions. Set at the Business Unit level.

Rate Sets represent a “rule” used by the system to create a new transaction from an existing transaction. For the ctcLink project, the primary utilization of this functionality is to create a billable transaction from an expenditure transaction. The billable transactions are the transactions that are sent to the Billing module from which to create an invoice. You will note that Rate Sets are created by Business Unit. You see this same item in Customer Contracts and it is the same thing, just from a different module - you don't have to do this twice.

Rate Sets Page Example

Navigation: NavBar > Navigator > Set Up Financials/Supply Chain > Product Related > Contracts > Templates > Rate Sets

Security: ZD PC Local Configuration Inq and ZZ PC Local Configuration
Menu: STRUCTURE_CONTRACTS
Component: PC_RATE
Page: PC_RATE_DTL
Action: A/UD