Setting Up Project Business Units

This chapter provides an overview of the PeopleSoft Project Costing operational structure and discusses how to:

Create project business units.
Define project options.
Set up other project business unit options.

Note. This chapter contains only part of what you need to know to define the operational structure. Other relevant information is located in the PeopleSoft Enterprise Application Fundamentals 9.0 PeopleBook.

Understanding the PeopleSoft Project Costing Operational Structure

A business unit in Project Costing is defined as an operational subset of the organization. Defining business units in this way enables you to plan projects and gather business data around the way that you work, without the constraints of the enterprise's standard accounting procedures for financial posting and reporting. Thus, you can organize information to best facilitate project management, analysis, reporting, and accounting.

To decide how to map the operational business structure in Project Costing, you need to examine how the business functions operationally, or how the work gets done.

After mapping the business structure and determining which tablesets to use, you can create business units. Consider these factors when you determine how many business units to create:

Each project tree is associated with a single project business unit.

If you want to group projects in one tree for summary reporting, all of the projects should be in the same project business unit. You can do consolidated reporting with many business units, but it is easier to use a tree.

Because trees are used for allocations, reporting, analysis, and security, it is important to consider the potential impact of maintaining multiple trees.
A single project business unit can post to as many general ledger (GL) business units as necessary, because you specify an integration template for each project.

Using Project Trees

Processing Allocations

Understanding Open Period Control

Open period control is used for transactions that are imported into Project Costing from interfacing applications, for transaction adjustments, and for transactions that you add through the Add Transactions functionality in Project Costing. If you use open period control in Project Costing and the accounting date on transactions that you import from other applications falls outside of the open periods that you define for Project Costing, the system modifies the accounting date on the Project Transaction table row so that it falls within the defined periods.

For open period accounting, when you enter a transaction in Project Costing through integration from other applications, the inbound Application Engine process triggers the Accounting Date Validation Application Engine process (PC_DATE) to validate the accounting date. The process of entering transactions online in Project Costing also uses the Accounting Date Validation process to validate accounting dates. The Accounting Date Validation process determines if the accounting period is open or closed by looking up the calendar ID defined at the business unit level, and resets the accounting date, if necessary.

You create calendars at the setID level by using the menu navigation Setup Financials/Supply Chain, Common Definitions, Calendars/Schedules.

See Defining Accounting Calendars.

Both the Process Project Accounting (PSA_ACCTGGL) and the Send to Asset Management (PC_AM) Application Engine processes do not validate open periods.

Open Period Control Example

Assume that you enable open period control and select Projects as the open period source. When you use the PeopleSoft Payables feeder system to send transactions to Project Costing, the Payables to Project Costing Application Engine process (PC_AP_TO_PC) triggers the Accounting Date Validation process to validate the transactions against the Project Costing open period and reset the accounting date. This example contains two transaction rows. For both rows, the Payables to Project Costing process sends a Payables accounting date that is outside of the open period. The Accounting Date Validation process validates and updates the accounting date as shown in the column titled Project Transaction Table Accounting Date:

Project Costing Open Period	Payables Open Period	Payables Accounting Date	Project Transaction Table Accounting Date	Explanation
January 2006 to February 2006	January 2001 to December 2007	December 15, 2005	January 2, 2006	Payables accounting date is earlier than the first Project Costing open period date. The system resets the accounting date to the first work day of the first open period.
January 2006 to February 2006	January 2001 to December 2007	March 16, 2006	February 28, 2006	Payables accounting date is later than the last Project Costing open period date. The system resets the accounting date to the last work day of the last open period.

Creating Project Business Units

To create project business units, use the Project Costing Business Unit Definition component (PC_BU_DEFN).

This section lists a prerequisite and discusses how to define project business units.

Prerequisite

You must establish at least one GL business unit.

Page Used to Create Project Business Units

Page Name	Object Name	Navigation	Usage
Project Costing Definition	BUS_UNIT_TBL_PC	Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Definition, Project Costing Definition	Create, define, and modify project business units.

Defining Project Business Units

Access the Project Costing Definition page.

Note. Create business unit IDs that are exactly five characters long. Depending on the operating system, performance degradation can occur if business unit IDs have fewer than five characters.

Default SetID

Enter the default setID from the available values to associate with this business unit. To establish a new setID, enter the same name as the business unit ID that you are creating.

The default setID is used to set up tableset sharing by determining the setID that is assigned to each record group for the new business unit. The setID that is assigned to a record group determines which tableset is used to determine valid values for that specific business unit. You can modify the default setID for the record group on the TableSet Control - Record Group page.

This field is available in add mode. However, if you create a new project business unit with the same name as an existing business unit in PeopleSoft General Ledger or PeopleSoft Receivables, the Description field is automatically populated, and the Default SetID field does not appear.

Note. Until you create the business unit, you cannot attach the calendar and GL business unit to the new business unit.

SetIDs are defined on the TableSet Control page in PeopleTools.

See Enterprise PeopleTools 8.48 PeopleBook: System and Server Administration.

Create FS BU (create Financials business unit)

Click to create the business unit. This button appears only in Add mode.

Rate Type

Currency Code

Enter the base currency for this business unit. This field serves two purposes. First, for all new projects created for this business unit, this currency code becomes the default currency code for the newly created project. You can override this default value during project creation. Second, this value is the base currency for the business unit. For all transactions that are stored in the Project Transaction table (PROJ_RESOURCE), the system stores two amounts. The Project Transaction table stores the source transaction amount (the foreign amount) and then converts this amount to the base currency identified at the project business unit level.

A project's currency code can differ from the project business unit's base currency.

Currency codes are defined on the Currency Code page.

See Maintaining Currency Tables.

Incoming Transaction Rate Type

Select the rate type on which multicurrency processing is based. Available options are:

Projects BU: Use the project business unit's conversion method as defined in the Rate Type field on this page.

Source: Use the conversion method that is used by the feeder application from which the incoming transaction originates.

Valid options are based on either the project business unit or the source transaction with the default value set at the project business unit. If you select the Source option, all multicurrency conversions will use the rate type that is passed with the source transaction. If you select Projects BU, all multicurrency conversions will be performed based on the rate type chosen at the project business unit level.

Rate Type

Enter the default rate type to use for currency conversions that occur for this business unit. Rate types are defined on the Market Rate Type page located at Setup Financials/Supply Chain, Common Definitions, Market Rates, Market Rate Type.

See Defining Market Rates.

Unit of Measure

Use this group box to define default values that are used for analysis and PeopleSoft Program Management scheduling. The system uses these fields to convert all units of measure into hours or days.

Hours Unit of Measure

Enter the unit of measure that represents hours for the organization. Units of measure are defined on the Units of Measure page. The default value is MHR (Work Hour).

See Defining Additional Common Information.

Days Unit of Measure

Enter the unit of measure that represents days for the organization. The default value is MDY (Person Day).

Dynamic Edit Tables

Category Edit Option

Specify whether category prompt lists display all values that are in the system, or a subset based on dependencies that are established among source types, categories, and subcategories. Available options are:

Independnt (independent): All categories that are in the system are available for selection. Project Costing uses the Project Resource Category record (PROJ_CATG_TBL) to populate prompt lists.

Override: Categories that are available for selection are restricted by established criteria. Project Costing uses the selected category edit table to populate prompt lists.

Related: Categories that are available for selection are restricted by predefined relationships with source types. Project Costing uses the Project Type Category record (PROJ_TYPE_CATVW) to populate prompt lists.

You can select the Related option only if the Source Type ChartField is selected on the Standard ChartField Configuration page. If you select Related and Source Type ChartField is inactive, an error message appears when you save the page, indicating that you cannot specify a Category Edit Option of Related because the Source Type ChartField is inactive.

Available category edit options are based on the translate values in the Category Edit Options field (CAT_EDIT_OPTION) properties. The default value is Independnt.

SubCategory Edit Options

Specify whether subcategory prompt lists display all values that are in the system, or a subset based on dependencies that are established among source types, categories, and subcategories. Values are:

Independnt (independent): All subcategories that are in the system are available for selection. Project Costing uses the Project Resource SubCategory record (PROJ_SUBCAT_TBL) to populate prompt lists.

Override: Subcategories that are available for selection are restricted by established criteria. Project Costing uses the selected subcategory edit table to populate prompt lists.

Related: Subcategories that are available for selection are restricted by predefined relationships with resource category types. Project Costing uses the Project Category SubCategory record (PROJ_CAT_SUB_VW) to populate prompt lists.

You can select the Related option only if the Category ChartField is selected on the Standard ChartField Configuration page. If you select Related and the Category ChartField is inactive, an error message appears when you save the page, indicating that you cannot specify a SubCategory Edit Option of Related because the Category ChartField is inactive.

Available values are based on the translate values in the SubCategory Edit Options field (SUB_EDIT_OPTION) properties. The default value is Independnt.

Accounting Periods

Calendar ID

After you create the business unit, select the calendar that is used for such things as open period accounting and allocations from the Project Transaction table.

See Defining the Allocation Pool.

Update Open Periods

Click to access the Open Period Update page in a new browser window in PeopleSoft General Ledger to modify project source transaction settings for open period validation.

You must create the business unit before you can access the Open Period Update page.

Close the new browser window to return to the Project Costing Definition page.

General Ledger Business Unit

If open period control is enabled on the Installation Options - Project Costing page, enter the GL business unit for the selected calendar ID that the system uses to validate accounting dates. You must select a calendar ID before you select a general ledger business unit.

If open period is enabled and the open period source is Projects, when you select the calendar ID and associated GL business unit, the system creates a row in the Open Periods by Products table (FIN_OPEN_PERIOD) and Business Unit Mapping table (FIN_BU_MAPPING). This enables you to update the project calendar for open period control.

See Defining and Updating Open Periods and Adjustment Periods.

See Also

Processing Multiple Currencies

Understanding General Control Data

Processing Allocations

Defining and Updating Open Periods and Adjustment Periods

Defining Project Options

To define project options for business units, use the Project Costing Options component (PC_BUS_UNIT_OPT). Use the Project Costing Business Unit Options component interface (PROJECT_BU_OPTIONS) to load data into the tables for this component.

This section discusses how to:

Define project options for business units.
Define budget plan version analysis types.
Define parameters for copying projects and creating projects from templates.
Define parameters for copying activities, transactions, and analysis groups.
Define parameters for the Delete utility.

Pages Used to Define Project Options

Page Name	Object Name	Navigation	Usage
Project Costing Options	BUS_UNIT_OPT_PC	Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options, Project Costing Options	Establish project-related transaction fields that are required for importing transactions from other PeopleSoft applications. Establish the method for calculating the percent complete value for all projects and activities in the business unit.
Budget Row Versioning	PC_BUD_VER_HST_CFG	Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options, Budget Row Versioning	Enable budget row versioning for the business unit, and define the sequence of analysis types that the system uses to distinguish historical cost and revenue budget plan versions.
Copy Template Option 1	PC_CPY_TMPL_PNL1	Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options, Copy Template Option 1	Specify the project tables that the system copies into a new project from a template.
Copy Template Option 2	PC_CPY_TMPL_PNL2	Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Options, Copy Template Option 2	Specify the activity and transaction tables that the system copies into a new project from a template, and define parameters analysis groups.
Delete Utility Tables	PC_DEL_PROJ_REC_PG	Setup Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options, Delete Utility Tables	Define the parameters for deleting projects, activities, and transactions for a specified business unit.

Defining PeopleSoft Project Costing Options for Business Units

Access the Project Costing Options page.

Use the Project Costing Options page to define required criteria relating to transactions that enter Project Costing from other PeopleSoft applications.

If you modify the settings on the Project Costing Options page, the system does not modify existing project settings. The system applies the modified settings only to new projects.

Time and Labor Interface

Select the type of data to import from PeopleSoft Time and Labor into PeopleSoft Project Costing. If you select Time and Labor for Billing, also select a reconciliation method.

You select the analysis types for rows that you import from PeopleSoft Time and Labor on the Installation Options - Project Costing Integration page.

Time and Labor Actuals	Select to import payroll expenses into PeopleSoft Project Costing after the close of a payroll period.
Time and Labor Estimates	Select to import estimates into Project Costing for the open pay period.
Time and Labor Contractor	Select to import contractor time and labor for this business unit after the close of a payroll period.
Time and Labor for Billing and Reconciliation Method	Select to create separate time and labor for billing rows after the close of a payroll period as part of estimate processing. Amounts are subject to change. If you select this option, also select from the list of Reconciliation Method options to reconcile the difference between actual time and labor costs with previously entered estimated time and labor costs. Each reconciliation creates a delta row in the Project Transaction table with the same analysis type as the transaction that you are reconciling. Available options are: Both Quantity and Amount (reconcile by both quantity and amount) Do Not Reconcile Reconcile by Amount Reconcile by Quantity
Summary Level	Select the level at which the system summarizes reconciliations. This affects the number of delta rows that are created during the reconciliation process. If the reconciliation method is not Do Not Reconcile, the selection of a summary level is defaulted into the project business unit options at save time with a default value of business unit, project, and activity. At a minimum, if you enable reconciliation, delta transaction rows are grouped by employee ID, business unit, project, and activity, and they cascade down from there. For example, if you summarize by category, then the transaction rows are grouped by employee ID, business unit, project, activity, and category. This field is not available if you select Do Not Reconcile as the reconciliation method for the Time and Labor for Billing option.

Enforce Team

Determine who can charge time, expenses, or both, to a project or activity based on the team membership. Define at what level (business unit level or project level) the decision is made to enforce team restrictions, and to what extent.

If you select any option other than the Decide at Project Level option on the Project Costing Options page, the selection applies to all future projects that you create for the business unit and cannot be modified at the project level. If you select the Decide at Project Level option at the business unit level, users can specify a team security option on the Project Costing Definition page for each project.

Do Not Enforce	Select to make the team restriction decision at the business unit level for all projects that belong to the business unit. There is no restriction on charging time or expenses to projects, so the Products drop-down list box does not appear when you select this option. You cannot override this option at the project and activity team level.
Project Team Only	Select to make the team restriction decision at the business unit level for all projects that belong to the business unit, and restrict the charging of time and expenses to project team members. The Products drop-down list box appears when you select this option. You cannot override this option at the project and activity team level.
Project and Activity Team	Select to make the team restriction decision at the business unit level for all projects that belong to the business unit, and restrict the charging of time and expenses to project or activity team members based on the Enforce Team option that you select on the Activity Definitions - Definition page. The Products drop-down list box appears when you select this option. You cannot override this option at the project and activity team level.
Project Resource Pools Only	Select to enable only resources that belong to the project’s resource pools to charge time and expense against the project in the PeopleSoft Expenses application. This option is available only for the PeopleSoft Expenses application and not the PeopleSoft Time and Labor application. Therefore, if you select this option, the Expenses value appears in the Products field and is not editable. This option appears only if both PeopleSoft Program Management and PeopleSoft Resource Management are installed. Note. Project managers use the Project Resource Pool page to specify project resource pools. See Selecting Project Resource Pools.
Project Activity Resource Pool	Select to enable only resources that belong to the activity’s resource pools to charge time and expense against the activity in the PeopleSoft Expenses application. This option is available only for the PeopleSoft Expenses application and not the PeopleSoft Time and Labor application. Therefore, if you select this option, the Expenses value appears in the Products field and is not editable. You cannot select this option if the Activity Costing Level option is selected as the project charging level on the Program Management Options page. This option appears only if both PeopleSoft Program Management and PeopleSoft Resource Management are installed. Note. Project managers use the Activity Resource Pool page to specify resource pools for each of the project's activities. See Defining Business Unit Options. See Selecting Activity Resource Pools.
Decide at the Project Level	Select to defer the decision to restrict charges to the project manager for each project that belongs to the business unit. The project manager uses the Project Costing Definition page to specify the extent to which restrictions are imposed. The Products drop-down list box does not appear when you select this option.
Products	Available product options are: Exp and TL Expenses and Time and Labor): Select to allow project and activity team members to charge to the project from both PeopleSoft Expenses and PeopleSoft Time and Labor. Expenses: Select to allow project and activity team members to charge to the project only from PeopleSoft Expenses. Time&Labor: Select to allow project and activity team members to charge to the project only from PeopleSoft Time and Labor.

Note. PeopleSoft Time and Labor 9.0 does not enforce project activity team. If you select the Project and Activity Team option, and select the Exp and TL or Time&Labor product option, the system restricts PeopleSoft Time and Labor users for projects to which they can charge time. However, PeopleSoft Time and Labor users can charge time to any activity on a particular project if they have security access to the project.

Note. Prompt tables are synchronized between the Financial Management Solutions (FMS) and Human Capital Management (HCM) by using the PROJECT_FULLSYNC message in application messaging. If project team enforcement takes place at the business unit level, you must run the PROJECT_FULLSYNC process manually.

Percent Complete

You can manually enter the percent complete for a project and activities, or have the system automatically calculate this value.

Calculation Method

Select a method to calculate the percent complete value. Available options are:

Budget Amount: This option bases the calculation on budgeted and actual amounts. Use the analysis group that you specify in the Cost Budget field on the Project Costing Definition page to determine what constitutes the budgeted amount. There must be a finalized budget posted to the Project Transaction table for the calculation to return a value. The percent complete equation is:

Budget Hours: This option behaves similarly to the Budget Amount option, except that it bases the calculation on the number of hours that are budgeted to complete the activity, as in this equation:

Duration: This option is available only if you use PeopleSoft Program Management. It bases the calculation on the number of days that are allotted to complete the activity, as in this equation:

Forecast Amount: This option compares the actual amount against the estimate at completion (EAC). The EAC is actual amount plus the estimate to completion (ETC). Use the analysis group that you specify in the Forecast field on the Project Costing Definition page to determine what constitutes the EAC amount. ETC transactions must be loaded to the Project Transaction table for the calculation to return a value. The equation for this option is:

Forecast Hours: This option behaves similarly to the Forecast Amount option, except that it compares hours instead of amounts. The equation is:

Manual: This option bases the calculation on manual entry of percent complete. If you select this option, only the None and Straight-Line summary methods are available for selection in the Summary Method field.

If you select the Budget Amount or Forecast Amount option, the percent complete calculation includes only transactions with the same unit of measure (UOM) as specified in the Hours Unit of Measure field on the Project Costing Definition page for the business unit, or that have a conversion rate defined for the project business unit hours UOM on the Unit of Measure page.

If you use PeopleSoft Program Management and select a project charging level of Activity Costing Level on the Program Management Options page, the Percent Complete Application Engine process (PC_PERCENT) evaluates only activities in the project charging level that have transactions associated with them. The system ignores planning activities. This affects the percent calculation if you select Budget Amount, Budget Hours, Forecast Amount, or Forecast Hours as the calculation method.

See Finalizing Budgets.

See Defining Projects.

See Entering Units of Measure.

See Understanding Project Charging Levels.

Summary Method

Select a method that the system uses to roll up activity completion percentages to the project. Available methods are:

None: The system does not summarize the percent complete value.
Straight-Line: Adds the individual activity percent complete values for the project, and divides that amount by the total number of activities.
Weighted: Adds the actual amounts, duration, or units for all activities, and divides that amount by the total budgeted value for the project.

Retain History

Select the frequency in which the system retains the percent complete data. Available options are:

Daily: The system retains the results of the final run of the Percent Complete process each day in the Project Percent Complete (PC_PROJ_PERCENT) and Activity Percent Complete (PC_ACT_PERCENT) history tables. For example, if the Percent Complete process runs five times a day, the system retains the values from the fifth run of the day in the history tables with an effective date of that day.

Monthly: The system retains the results of the final run of the Percent Complete process each month in the history tables with an effective date of the first day of the month. The calendar is specified in the Monthly Calendar field in the Reporting Roll Up Calendars group box on the Installation Options - Project Costing page.

Quarterly: The system retains the results of the final run of the Percent Complete process each quarter in the history tables. The calendar is specified in the Quarterly Calendar field in the Reporting Roll Up Calendars group box on the Installation Options - Project Costing page.

Weekly: The system retains the results of the final run of the Percent Complete process each week in the history tables. This is the default value. The calendar is specified in the Weekly Calendar field in the Reporting Roll Up Calendars group box on the Installation Options - Project Costing page.

Note. If the percent complete calculation method is Manual, the system retains the percent complete value that you enter on the Project Definitions - General Information, Activity Definitions - General Information, and Project Activities pages in the history tables based on the selected retain history option.

Commitment Control Reversals

To set up reversal amounts for project commitments, select a Commitment Control ledger group, requisition source type, and purchase order source type. The Purchasing Adjustment Application Engine process (PC_POADJUST) uses the Ledger Group field, and Requisition Source Type or Purchase Order Source Type fields, in addition to the purchase order or requisition numbers from the Project Transaction table, to identify rows in the Commitment Control Liquidation table (KK_LIQUIDATION). The process copies the corresponding rows to the Project Transaction table.

Integration Default Role Values

Default Project Role	Specify the default project role for the system to use when copying project and activity team members from third-party applications to Project Costing.
Project Manager Role	Enter the default project manager role that is assigned to project managers that are added from PeopleSoft Grants or PeopleSoft Proposal Management, or through a project request. The default project manager role that you define on this page becomes the role that the system assigns to the project manager on the project team.

ChartField Editing

Select the Edit Combinations check box to enable ChartField combination editing when integrating with PeopleSoft General Ledger.

Pricing Options

Select options in this group box that the Pricing Application Engine process (PC_PRICING) uses when it is triggered by incoming Application Engine processes or through the Add Transactions functionality in Project Costing. Examples of incoming Application Engine processes are the Payables to Project Costing process (PC_AP_TO_PC) and the Time and Labor to Project Costing process (PC_TL_TO_PC). In this case, the Pricing process uses the pricing options that you select on this page for the business unit of each transaction row that it processes. The Pricing process triggers the Limits Application Engine process (CA_LIMIT), which processes the same type of transaction rows (revenue, billing, or both).

Cost

Select to use this option as a default pricing option for the business unit on the Pricing run control page. You can override this pricing option when you run the process.

Billing

Select to use the billing option as a default pricing option for the business unit on the Pricing run control page. You can override this option on the run control page.

Revenue

Select to use the revenue option as a default pricing option for the business unit on the Pricing run control page, and as a default processing option on the Limits run control page in PeopleSoft Contracts if you run the Limits process manually. You can override this option on the run control pages.

The Revenue pricing option enables the Pricing process and Limits process to run exclusively for revenue contract rows. This option is available if you use the Government Contracting feature that is available with PeopleSoft Contracts, and you select the Separate Billing and Revenue option in the Installation Options - Contracts page.

See Understanding PeopleSoft Project Costing and Government Contracting Integration.

Waived Facilities and Administrative Calculation

Select either Institution Minus Funded or Sponsor Minus Funded to tell the system how you want to calculate waived and cost-shared facilities and administration amounts. The system uses this option only if you choose to calculate waived or cost shared amounts in the Facilities Admin Options page in PeopleSoft Grants.

This group box appears only if you install PeopleSoft Grants.

See Establishing F&A and Direct-Cost Cost-Sharing Options.

Budget Item Defaults

Select the revenue budget item that the Distribute Costs to Budgets Application Engine process (PGM_SPREAD) uses as the default budget item when it creates revenue budget rows. The default value is REVEST.

The revenue budget item that you enter on this page appears in the Bill tab in the Resources by Activity page.

Note. To create cost budget rows, the Distribute Costs to Budgets process uses budget items that you specify for each resource row in the Cost tab of the Resources by Activity page.

Input Control

Specify the fields that are required when you enter transactions for this business unit in PeopleSoft cost feeder applications and directly in Project Costing through the Add Transactions page. Values are Required or Optional.

Note. A project business unit, project, and activity are always required when you enter transactions directly in Project Costing.

If you select Required for Category or SubCategory input control for any business unit, you cannot inactivate those ChartFields on the Standard ChartField Configuration page.

See Also

Editing ChartField Combinations

Defining PeopleSoft Grants Options

Enterprise PeopleTools 8.48 PeopleBook: PeopleSoft Integration Broker

Defining Budget Plan Version Analysis Types

Access the Budget Row Versioning page.

Note. Before you can define the analysis types and sequences to use to create budget plan versions, you must set up analysis types in the Analysis Types component (PROJ_ANALYSIS_TYPE) to use to distinguish budget rows for particular budget plan versions.

See Defining Analysis Types.

PeopleSoft delivers a series of analysis types and groups that you can use to distinguish historical cost and revenue budget versions.

See Budget Plan Versions.

The system uses two different analysis type sequences to distinguish budget plan versions—one sequence for cost budget plan versions and one for revenue budget plan versions.

Enable Budget Row Versioning

Select to activate budget row versioning for the business unit. When this option is active, historical versions of finalized cost and revenue budget plans are stored in the Project Transaction table for analysis or reporting.

You cannot enable budget row versioning if Commitment Control is enabled for Project Costing on the Installation Options - Products page.

See Defining Options for Installed PeopleSoft Applications.

Cost Budget Analysis Type Sequence and Revenue Budget Analysis Type Sequence

Enter a series of analysis types to represent historical cost and revenue budget versions. You can use the analysis types that are delivered with the system for this purpose, or create your own sequences. Enter as many analysis types as needed for each sequence.

You must enter analysis types in the order that you want them to be assigned by the system to historical budget versions. When budget row versioning is enabled, the first time that you finalize a project budget for the business unit, the system assigns the first analysis type in the cost or revenue budget sequence on this page to a copy of the budget plan rows. Each subsequent time that you finalize the budget for this project, the system updates a copy of the new finalized budget rows with the next available analysis type from the sequence. The budget version is assigned on a project-by-project basis.

You cannot enter an analysis type that is associated with an analysis group that you specify for Cost Budget, Revenue Budget, Actual Cost, or Actual Revenue, in the Analysis Group Defaults group box on the Installation Options - Project Costing page.

Add

Click to append analysis types to the sequence.

After you enter analysis types and save the page, you can append analysis types to the sequence, but you cannot change an existing analysis type or change the sequence order.

You are not required to create an analysis type sequence in ascending alphanumeric order. The system maintains a separate sequence number for each analysis type on this page. Each time that you add an analysis type, the system increments the Sequence Number field (SEQ_NBR) for the budget type (cost or revenue). The Sequence Number field is not visible on the user interface. The system uses the field to determine the next available budget version analysis type when you finalize a project budget plan.

See Also

Maintaining Budget Plan Versions

Defining Parameters for Copying Projects and Creating Projects from Templates

Access the Copy Template Option 1 page.

This page is used to configure both the Project Copy and Project Templating features. Use this page to specify the tables that contain field values that the system copies into a new project that you create from a template.

For Project Copy, you can select the Allow Project Copy, Allow Activity Copy, and Allow Transaction Copy check boxes to enable this feature at project business unit level. Then you indicate at the project business unit level which records are eligible for copying field values from one project to another.

The Project Templating feature does not use the Allow Project Copy, Allow Activity Copy, or Allow Transaction Copy check boxes to determine if you can create a project from a template. The system makes that determination based on security for project creation. The eligible records that the system uses to create projects and field values from templates are based on the selected records in the Template column.

Allow Project Copy	Select to include project definitions in a project that you copy from an existing project. The system copies the field values from the tables that are listed in the Project Records grid from the existing project to the new project.
Allow Activity Copy	Select to include activity definitions in a new project that you create from an existing project. The system copies the field values from the tables that are listed in the Activity Records grid on the Copy Template 2 page from the existing project to the new project.
Allow Transactions Copy	Select to include transactions in a new project that you create from an existing project. The system copies the transactions from the tables that are listed in the Transaction Records grid on the Copy Template 2 page from the existing project to the new project. You cannot copy transactions from one project to another if you use Commitment Control or Projects Budgeting. Therefore, the Allow Transactions Copy check box is not available for selection if Commitment Control is enabled for Project Costing on the Installation Options - Products page.
Update Project Tree	Select to insert the new project into a project tree.
PC Business Unit (project business unit)	Enter a business unit to use with Copy Record/Temporary Tables function.
Copy Record/Temporary Tables	Click to copy record settings of the business unit that is selected in the PC Business Unit field to this template. Note. Project Costing delivers standard and temporary Project Records in Business Unit US003, which you can use as a guideline for all Project Records that can be used in the Project Copy and Project Templating features.
Allow Copying	Select the check box corresponding to the project-level records from which you want to copy field values for an existing project into a new project. Note. You must also select the Allow Project Copy option for the system to copy the selected records and their field values.
Template	When you select the Allow Copying check box for a row, the system automatically selects the Template check box if the record is eligible to be copied to create projects from templates. This check box is not editable. This column does not restrict data that is saved in the database tables for a project template.

This table lists the records and temporary records that are available for performing the project copy and project templating process:

Project Record (Table)	Temporary Record (Table)	Used for Project Copy, Project Templating, or Both
PC_AM_RULE_PRJ	PC_CPY_PJAM_TAO	Both
PC_BUD_ALERT	PC_CPY_BDAL_TAO	Both
PC_BUD_PLAN	PC_CPY_BUP_TAO	Both
PC_PIC_ADD_TBL	PC_CPY_PICA_TAO	Copy
PC_PIC_STUS_TBL	PC_CPY_PICS_TAO	Copy
PC_PROJHEALTH	PC_CPY_HLTH_TAO	Both
PC_SR_DATES	PC_CPY_SRDT_TAO	Copy
PC_SR_FRQS	PC_CPY_SRFQ_TAO	Copy
PGM_ACTION_PLAN	PC_CPY_RKAP_TAO	Copy
PGM_PRL_QL_ATTR	PC_CPY_ATTR_TAO	Both
PGM_PRL_QL_ATVL	PC_CPY_ATVL_TAO	Both
PGM_PRL_QL_COMP	PC_CPY_COMP_TAO	Both
PGM_PRL_QL_DEG	PC_CPY_DEG_TAO	Both
PGM_PRL_QL_LIC	PC_CPY_LIC_TAO	Both
PGM_PRL_QL_LNG	PC_CPY_LNG_TAO	Both
PGM_PRL_QL_MEM	PC_CPY_MEM_TAO	Both
PGM_PRL_QL_NOTE	PC_CPY_NOTE_TAO	Both
PGM_PROJ_RISK	PC_CPY_RISK_TAO	Copy
PGM_RISK_NOTES	PC_CPY_RKNT_TAO	Copy
PGM_RISK_TRIGGR	PC_CPY_RKTG_TAO	Copy
PROJ_APPROVAL	PC_CPY_PJAP_TAO	Both
PROJ_DOCUMENT	PC_CPY_PDOC_TAO	Copy
PROJ_EV_APPROVE	PC_CPY_EVAP_TAO	Both
PROJ_JUSTIFY	PC_CPY_PJUS_TAO	Both
PROJ_LOCATION	PC_CPY_PLOC_TAO	Both
PROJ_TEAM_SCHED	PC_CPY_TMSC_TAO	Both
PROJECT	PC_CPY_PROJ_TAO	Both
PROJECT_DESCR	PC_CPY_DESC_TAO	Both
PROJECT_MGR	PC_CPY_MGR_TAO	Both
PROJECT_SCHED	PC_CPY_PSCH_TAO	Both
PROJECT_STATUS	PC_CPY_PSTA_TAO	Both
PROJECT_TEAM	PC_CPY_TEAM_TAO	Both
PSA_ORGPRJ_DEFN	PC_CPY_PORG_TAO	Copy

Defining Parameters for Copying Activities, Transactions, and Analysis Groups

Access the Copy Template Option 2 page.

Allow Copying

Select the check box corresponding to the activity-level records from which you want to copy field values for an existing project into a new project. The system copies the selected records and their field values only if you select the Allow Activity Copy option on the Copy Template 1 page.

Template

When you select the Allow Copying check box for a row, the system automatically selects the Template check box if the record is eligible to be copied to create projects from templates. This check box is not editable.

Analysis Group

Enter the analysis group that the system uses for mapping analysis types from the template project or activity to the new project or activity.

When you copy transaction rows from one project to another, the analysis group indicates which transaction rows to copy. The system copies only those rows with an analysis type that is in the selected analysis group. The Template Copy analysis group (COPY) selects actual cost rows (with an analysis type of ACT) and maps them to total cost budget rows (with an analysis type of BUD). Thus, the system selects ACT rows from the template project and copies them to the new project as BUD rows. PeopleSoft delivers the COPY analysis group as system data; however, you can use any analysis group.

See Defining Analysis Groups.

Activity Records

This table lists the activity record and temporary records that are necessary for performing the copy process:

Activity Record (Table)	Temporary Record (Table)	Used for Project Copy, Project Templating, or Both
PC_AM_RULE_ACT	PC_CPY_ACAM_TAO	Both
PC_BUD_ACTIVITY	PC_CPY_BDAC_TAO	Copy
PC_BUD_ALERT	PC_CPY_BDAL_TAO	Both
PC_BUD_DETAIL	PC_CPY_BDTL_TAO	Both
PC_BUD_ITEM	PC_CPY_BDIT_TAO	Both
PC_DELIVERABLES	PC_CPY_DELV_TAO	Both
PC_PRICE_R_PLAN	PC_CPY_PRCP_TAO	Both
PC_PRICE_RATES	PC_CPY_ARAT_TAO	Both
PGM_ACT_DEP	PGM_CPY_ATD_TAO	Both
PROJ_ACT_DESCR	PC_CPY_ADES_TAO	Copy
PROJ_ACT_LOC	PC_CPY_ALOC_TAO	Both
PROJ_ACT_STATUS	PC_CPY_ASTA_TAO	Both
PROJ_ACT_TEAM	PC_CPY_ACTM_TAO	Both
PROJ_ACTIVITY	PC_CPY_ACTY_TAO	Both
PROJ_QUALITY	PC_CPY_QUAL_TAO	Both
PSA_ORGPRJ_ACT	PC_CPY_OGAC_TAO	Copy

Transaction Records

Transaction Record (Table) and Temporary Record (Table)

The only transaction record that is necessary for performing the copy process is PROJ_RESOURCE. The corresponding temporary record is PROJ_RES_TMP.

The system copies the selected records and field values only if you select the Allow Transactions Copy option on the Copy Template 1 page.

Defining Parameters for the Delete Utility

The Project Delete utility provides an effective means of removing projects, activities, and transactions from the database. Before you can use the utility, you must set up utility tables for each business unit that is on the Delete Utility Tables page, which is accessible to managers or power users who have permission to implement the Project Delete utility.

Access the Delete Utility Tables page.

Use this page to set up the system to allow the deletion of:

All or selected transactions based on the project, activity, and analysis group.
All or selected activities based on the project.
A project and all associated project data.
A project node from a specified project tree.

The Project Delete utility does not purge project-related data from feeder systems or modules that interface with Project Costing.

Warning! Give thoughtful consideration to the process of setting up the Project Delete utility. Project deletions are permanent and irreversible.

Project Business Unit	To copy the settings of the Analysis Groups, Project Records, and Activity Records group boxes from another project business unit to the business unit that is listed at the top of the page, enter the business unit that is to be copied and click Copy Settings.
Delete Project Tree Node	Select to delete the corresponding project node from the business unit's project tree structure when the project is deleted.
Delete Project Security List	Select to delete the corresponding rows from the Project Security table (SEC_PROJLST_CLS). When you delete a project, the system also removes project team members from the Project Security table who are associated with the project.
Allow Delete with Transactions	Select to delete projects and activities even if transaction rows exist. When you attempt to delete a project or activity, a warning appears indicating that transaction rows are present and are deleted along with the project or activity. Clear the Allow Delete with Transactions option to restrict users from deleting a project or activity if a transaction row is present.
Analysis Group	Enter the type of transactions, by analysis group, that you can delete at the transaction level. At this level, project and activity tables remain unchanged.
Project Records	Enter the project records from which data is purged when you delete a project and its activities at the project level. To prevent data fragmentation, include these records in the Project Records group box: GM_PRJ_DEPT GM_PRJ_DEPT_PCT GM_PROJ_RES GM_PROJ_RES_DT PC_AM_ASSET PC_AM_ASSET_SUM PC_AM_RULE_PRJ PC_BUD_PLAN PC_BUD_PLAN_LNG PC_BUD_PLN_HIST PC_BUDPLHST_LNG PC_CHC_INFO PC_GNT_PROJ PC_IM_ATTCH_LNG PC_IM_ATTCH_TBL PC_IM_HIST_LNG PC_IM_HIST_TBL PC_IM_ISSUE_LNG PC_IM_ISSUE_TBL PC_IM_NOTE_LNG PC_IM_NOTE_TBL PC_IM_RSLTN_LNG PC_IM_RSLTN_TBL PC_PIC_ADD_LNG PC_PIC_ADD_TBL PC_PIC_NOTE_LNG PC_PIC_NOTE_TBL PC_PIC_STUS_TBL PC_PROJHEALTH PC_SR_DATES PC_SR_FRQS PC_TEAM_IP_SCHD PC_TEAM_IPSC_LG PC_TEAM_SC_LANG PGM_ACTION_PLAN PGM_BUDANALFACT PGM_BUD_AUDIT PGM_BUD_AUDT_LG PGM_BUD_DETAIL PGM_BUD_DOC PGM_BUD_DOC_LG PGM_BUD_PERIOD PGM_BUD_PLAN PGM_BUD_PLAN_LG PGM_CHC_BUD_LG PGM_CHC_HDR_LG PGM_CHC_PRD_LG PGM_CHC_REQ_BUD PGM_CHC_REQ_HDR PGM_CHC_REQ_PRD PGM_CHC_REQ_RES PGM_CHC_RES_LG PGM_PRJ_RISK_LG PGM_PROJ_RISK PGM_RISK_ATTACH PGM_RISK_ATT_LG PGM_RISK_NOTES PGM_RSK_NOTE_LG PGM_RISK_TRIGGR PGM_RSK_TRIG_LG PROJECT PROJECT_DESCR PROJECT_LANG PROJECT_MGR PROJECT_SCHED PROJECT_STATUS PROJECT_TEAM PROJ_APPROVAL PROJ_DOCUMENT PROJ_EV_APPROVE PROJ_FUNDING PROJ_JUSTIFY PROJ_LOCATION PROJ_TEAM_LANG PROJ_TEAM_SCHED PSA_ORGPRJ_DEFN You can copy project record settings from the sample database that PeopleSoft delivers.
Activity Records	Enter the activity records from which rows are purged when you delete data at the activity level. To prevent data fragmentation, include these records in the Activity Records group box: GM_PRJ_ACT_FA GM_PRJ_ACT_FA1 GM_PRJ_ACT_FA2 GM_PRJ_ACT_FA3 PC_AM_PROJ_DEFN PC_AM_RULE_ACT PC_BUD_ACTIVITY PC_BUD_ALERT PC_BUD_ALRT_LNG PC_BUD_DETAIL PC_BUD_DTL_HIST PC_BUD_ITEM PC_BUD_SUMMARY PC_PRICE_R_PLAN PC_DELIVERABLES PC_DELIVER_LANG PC_DELV_DOC PC_DELV_DOC_LNG PC_PRICE_RATES PC_RES_FUND PC_SR_SUM_DTL PC_SR_SUMDTL_AF PGM_ACT_DEP PGM_CHC_ACT_LG PGM_CHC_ARL_LG PGM_CHC_REQ_ACT PGM_CHC_REQ_ARL PGM_CHC_REQ_ETC PROJ_ACTIVITY PROJ_ACTIVTY_LG PROJ_ACT_DESCR PROJ_ACT_LOC PROJ_ACT_STATUS PROJ_ACT_TEAM PROJ_QUALITY PSA_ORGPRJ_ACT Activity record settings can be copied from the sample database that PeopleSoft delivers.

Setting Up Other Project Business Unit Options

Additional pages in the Project Costing Options component (PC_BUS_UNIT_OPT) are discussed in business process sections of this PeopleBook. This table lists the additional component pages and provides a link to the discussion:

Project Options Component Page	Location of Page Discussion
Microsoft Project	See Defining Integration Criteria.
Budget Alerts	See Defining Budget Alert Thresholds.
Asset Integration Rules	See Defining Asset Integration Rules for Express Capitalization. See Defining Asset Integration Rules for Manual Capitalization.
Interest Calculation	See Defining Interest Calculations.