Setting Up PeopleSoft Project Costing Control Data

This chapter provides overviews of project ChartFields, general control data, project-related control data, activity-related control data, and transaction-related control data and discusses how to:

• Set up project ChartFields.

• Set up general control data.

• Set up project-related information.

• Set up activity-related information.

• Set up transaction-related information.

Understanding Project ChartFields

ChartFields store the chart of accounts and provide the basic structure to segregate and categorize transactional and budget data.

See Defining and Using ChartFields.

The PeopleSoft system provides these six project ChartFields:

• Project Business Unit (BUSINESS_UNIT_PC)

• Project (PROJECT_ID)

• Activity (ACTIVITY_ID)

• (Optional) Source Type (RESOURCE_TYPE)

• (Optional) Category (RESOURCE_CATEGORY)

• (Optional) Subcategory (RESOURCE_SUB_CAT)

Use the Standard ChartField Configuration page (STANDARD_CF_TMPLT) to modify these project ChartField attributes:

• Field display order.

  You can change the placement of the group of project ChartFields when they appear in a grid with all other general ledger ChartFields. All project ChartFields move together in a block when you change the order of the Project ChartField.

• Status (active or inactive).

  • The Project ChartField must remain active if you use PeopleSoft Expenses, Resource Management, or Project Costing.

  • Source Type, Category, and Subcategory ChartFields must remain active if you specify on the Project Costing Options page that these are required fields for the project business unit.

  • The Source Type ChartField must remain active if you specify on the Project Costing Definition page that Category field values are related to the Source Type.

  • The Category ChartField must remain active if you specify on the Project Costing Definition page that Subcategory field values are related to the Category.

• Default field label.

• Field display length.

The Project Business Unit, Activity, Source Type, Category, and Subcategory ChartFields do not appear for selection in the IntraUnit Related ChartField drop-down list on the Standard ChartField Configuration page.

Note. The Analysis Type field (ANALYSIS_TYPE) is not a project ChartField; therefore, it does not appear in the Standard ChartField Configuration page. However, the Journal Lines page (JOURNAL_LN_FS) includes the Analysis Type field with the project ChartFields in the Journal Line Data grid. If you reorder the project ChartFields on the Standard ChartField Configuration page, the Analysis Type field retains its position between the Activity and Source Type ChartFields on the Journal Lines page.

Source Types

Project Costing uses transactions to track, analyze, and report on actual and planned project costs. You assign source types to individual transactions to identify the transaction's purpose.

Source types can be as general or as specific as needed. For example, you can use a Labor source type to track total project labor costs, or use overtime labor and standard labor source types to track overtime and standard labor separately.

These source types are necessary for Project Costing source groups, reports, and processes to function properly; if not implemented, these source types must still be configured:

Categories and Subcategories

Categories and subcategories further define source types. You can combine categories and subcategories in source groups for reporting and analysis. Although defining categories and subcategories is optional, using them provides greater flexibility and granularity for tracking and analyzing costs.

For example, you can divide a labor source type into different categories of labor, such as architect labor, carpenter labor, and plumber labor, and use subcategories for regular hours and overtime hours. By using these categories and subcategories, you can track items such as total labor costs for a project, total overtime hours, architect overtime hours, and carpenter standard hours.

Relating Source Types, Categories, and Subcategories

Source types, categories, and subcategories provide flexibility for defining transactions. You can define relationships between these fields to control data-entry options for specific fields, which reduces the possibility of error.

The relationships can be one-to-one or one-to-many. If you relate source types to specific categories, and assign a source type to a transaction, you can assign a category only if it is related to the source type. For example, a transaction with a labor source type can only be entered in a category that is related to labor by its definition. The same is true for relationships between categories and subcategories.

To enable relationships between source types, categories, and subcategories, select Related as the Category Edit Option and SubCategory Edit Option on the Project Costing Definition page (BUS_UNIT_TBL_PC).

See Creating Project Business Units.

Defining relationships between source types, categories, and subcategories is optional. If you do not establish relationships, the system does not limit the categories and subcategories that are available for selection.

Understanding General Control Data

By using control data, you can group Project Costing elements to facilitate system processing, increase system performance, and aid in analyzing and reporting project data. This section provides an overview of three kinds of general control data:

• Asset profiles

• Transaction codes

• Transaction types

Asset Profiles

Asset profiles are templates that contain standard depreciation criteria for an asset type and its corresponding asset books. Profiles help reduce data entry and ensure consistency and accuracy when you add assets. You can use profile data as default values, and you can override any field that is in the asset profile when you enter assets into the system. You set up asset profiles in PeopleSoft Asset Management if you use that application. If you don't use PeopleSoft Asset Management, you must set up asset profiles in Project Costing before you can summarize transactions by profile or by asset.

You must set up at least one asset profile before any assets can be added to the system. Set up asset profiles to match most, if not all, of the major asset categories you track on the books. Asset profiles can range from standard categories, such as land or furniture and fixtures, to more detailed categories, such as computers, phones, and fax machines.

Each asset profile has a unique profile ID that the system uses to group profiles by type. For example, you can define automobile profiles as autos, autos-luxury, and autos-leased.

See Also

Managing Assets

Transaction Codes

You can use transaction codes to deal with exceptions and specific cases without creating a transaction type for each case. Add transaction codes to resource transactions as an additional key, and define accounting rules for transactions containing those transaction codes. The accounting rules for those resource transactions can then use the same transaction types but specify different accounts. For example, transaction codes can identify costs specifically for month-end or year-end processing.

Using transaction codes is optional.

Transaction Types

Accounting rules determine how project transactions are translated into entries that are sent to the general ledger. Transaction types define generic transactions that are used to define an accounting rule.

Transaction rows that belong to the transaction type are assigned to a general ledger account based on an accounting rule. By defining transaction types in a separate table, you save time and reduce errors when you define accounting rules.

Standard transactions involve moving money from one account to another within the same general ledger business unit. Intercompany transactions involve moving money from an account in one general ledger business unit to an account in another general ledger business unit. Additional transaction rows are required for intercompany transactions.

Understanding Project-Related Control Data

Project-related control data consists of required and optional information that you use primarily to create new projects. This section provides overviews of:

• Integration templates

• Project types

• Project and processing statuses

• Project type status paths

• Phase types

• Project events

Integration Templates

Project Costing uses integration templates to share projects across multiple business units in PeopleSoft Asset Management, Purchasing, and General Ledger. For example, if you create an integration template that points to multiple general ledger business units, you can share a project across those specific business units. Integration templates also establish business units that are assigned to transactions by default.

You must assign an integration template to each new project. For example, if a company has an aerospace division and a utilities division, aerospace projects may use one general ledger business unit and utilities projects may use another general ledger business unit. Therefore, you will set up two integration templates—one to define the business unit integration for aerospace projects and one to define the business unit integration for utilities projects.

Each project integration template contains a specific set of general ledger business units. Integration templates provide the flexibility to define the integration between project business units and general ledger business units that best fit the organization's needs. You can set up the project and general ledger integration so that:

• One project business unit can post to many general ledger business units.

• Many project business units can post to a single general ledger business unit.

• Each project business unit can post to a different general ledger business unit.

The system also uses integration templates to control access to general ledger business units. You can post transactions for a project only to a general ledger business unit that is specified in the integration template that is assigned to the project. The same control applies to purchasing business units. You can create requisitions in PeopleSoft Purchasing for a project only if the purchasing business unit is defined on the integration template for the project.

Project Types

The system uses project types to categorize projects for reporting and analysis. Additionally, you can assign a default rate set or rate plan to a project type for specific business units. When you create a new project and specify the project type, the system automatically attaches the default rate set or rate plan that is associated with the project type and business unit combination.

Using project types is optional.

See Also

Assigning and Tracking Rates

Project and Processing Statuses

Project Costing uses two statuses to convey where a project is in its life cycle—project status and processing status:

• Status field (PROJECT_STATUS)

  This required, user-defined field identifies the conditions that you want to track for projects and activities. The status also defines project events, such as conditional changes that require approval.

  You can define status types or use the system-delivered status types.

• Processing Status field (PROCESSING_STATUS)

  This system-defined field is used by the system to restrict incoming transactions. For example, you can charge cost transactions from feeder systems to projects with an active processing status but not to projects with a pending processing status.

  Valid processing status values are Pending, Active, Inactive, and Template. You map the user-defined status types to any system-defined processing status except the Template processing status. When you update a project status, the system automatically updates the processing status based on this mapping. You cannot change the processing status of a project directly.

You can map these system-defined processing status types to project status types:

• Active

• Pending

• Inactive

This table lists the status types that Project Costing delivers as sample data and their mappings to processing status types:

Every project status must map to a processing status. You can modify project status types and the delivered mappings, but you must not delete or modify the delivered processing statuses.

Status Effective Dates

The status of a project is effective-dated. When you assign a new project status and effective date, the Project - Processing Status Link Application Engine program (PC_STAT_LINK) assigns the corresponding processing status based on the effective-dated mapping that you defined for the project status type.

When you create a new project manually in Project Costing, if the project start date equals or precedes the current date, the system assigns the project status effective date based on the project start date. If the project start date is in the future, the system assigns the project status effective date based on the current date.

You cannot change the project start date to an earlier date if there is no valid project status assigned to the project based on the effective date. In this situation, adjust the project status effective date before you change the project start date.

You can modify the project status on the Project Definitions - General Information page until you save a new project. After that, you must enter a new effective-dated row on the Project Definitions - Status page to change the project status.

Default Project Statuses for Integration with Other Applications

Use the Project Status Defaults page to specify default project statuses for each system-defined processing status for projects that are programmatically created by these applications:

• PeopleSoft Resource Management.

• PeopleSoft Contracts.

• PeopleSoft Grants.

• PeopleSoft Proposal Management.

• PeopleSoft Project Portfolio Management (for projects that are created by project requests in a costing or declined status).

• PeopleSoft Program Management (for projects that are created by project requests in a costing or declined status).

Also use the Project Status Defaults page to specify both default project and processing statuses for projects that are programmatically created by project requests in an approved status in PeopleSoft Project Portfolio Management or PeopleSoft Program Management. Otherwise, the project request approval process fails.

As an example of using default project statuses for integration with other applications, assume that you create a project to model costs for a proposal in PeopleSoft Proposal Management. The system assigns the pending processing status, and assigns the default project status that is set up for pending projects that are created by project requests in PeopleSoft Proposal Management.

To change the project status for a project that is created by PeopleSoft Resource Management, Grants, Proposal Management, Project Portfolio Management, or Program Management, you select a project status that is mapped to a processing status on the Project Status Defaults page.

Process Flow

This diagram shows the process flow to set up project and processing statuses and to update a project status:

Setting up project and processing statuses

After you update the project status, the system:

1. Determines if the corresponding processing status is a valid change based on the previous processing status.

   The processing status:

   • Can change from Active to Active.

   • Can change from Active to Inactive.

   • Can change from Inactive to Inactive.

   • Can change from Inactive to Active.

   • Can change from Pending to Pending.

   • Can change from Pending to Active.

   • Can change from Pending to Inactive.

   • Can not change from Active to Pending.

   • Can not change from Inactive to Pending.

2. Determines if the project status effective date is current or future-dated.

   An Application Engine process monitors project status effective dates and updates the processing status as necessary.

3. Determines if a processing status change is valid.

   If the change is not valid, an error message appears.

4. Determines if a project type status map exists for the project type.

   If a project type status map exists, the system determines if the project status change is valid based on the project type status path for that project type.

5. Determines if a project event is defined for this project status change.

   If a project event is defined, the system triggers approval workflow.

6. Updates project status and processing status.

Project Type Status Paths

Project type status paths combine project types and project status types to control the status progression through the life cycle of a project and activity. You can define custom project status paths for each project type and business unit combination.

For example, assume that you set up a project type status path for the project type of R&D (research and development) to manage the project life cycle. The status progression for this project type is:

1. Proposed

2. Budgeted

3. Active or Closed

4. Closed

In this example, users can change an R&D project from a proposed status only to a budgeted status. In other words, you cannot approve a project until it has been budgeted. You can change an R&D project from a budgeted status to an active status if the budget is approved, or to a closed status if the budget is not approved. When the R&D project is complete, you can change the status from active to closed. This project type status path restricts users from changing a closed project to any other status. In this way, you prevent users from reopening projects that were previously closed.

Select the Use Status Path check box on the Project Types page to use a project type status path for a specific project type. Use the Project Type Status Path page to define status paths.

After the system determines if a project status and the corresponding processing status are valid changes, the system determines if the project type status path is valid.

Note. You must coordinate the default project status for new projects with the project type status path rules that you enable for project types. For example, if the default project status for new projects is Proposed, the project type status path must include a valid path for projects in a Proposed status. You define the default project status for new projects on the Project Status Defaults page.

Phase Types

When you enter dates in a project schedule, the phase of the project that those dates represent can be useful information. For example, for a phase type of Clean Up, you can enter a begin cleanup date and an end cleanup date in the project schedule to track the time that is spent specifically on the Clean Up phase. Using phase types is optional.

Project Events

Project events are changes in the status of a project or an activity. For example, you can define a change in project status from Proposed to Approved as a project event that requires approval. A project event can be a change in project status between two consecutive status types, such as Proposed and Approved, or two nonconsecutive status types, such as Proposed and Closed. You must define project status types before you define project events. Using project events is optional.

Understanding Activity-Related Control Data

Activity-related control data consists of required and optional information that you use primarily to create new activities. This section provides overviews of:

• Quality types

• Standard activities

Quality Types

Quality types identify the criteria on which you can rate activities for quality. For example, you can rate projects for quality based on accuracy, on-time performance, safety, or usability. Set up quality types that you can use to group and analyze activities with quality ratings that are based on the same criteria. Using quality types is optional.

Standard Activities

You can limit the number and types of activities that users can assign to projects, which facilitates reporting and analysis. Standard activities are predefined, keyed by setID, and based on project type. You can require users to select from a list of standard activities when they assign activities to projects.

To use standard activity functionality:

• Define standard activities on the Standard Activities page.

  1. Select the Projects option for each activity that you want to use in Project Costing.

  2. Assign a specific project type to each activity that you want to use in Project Costing.

• Create a project and on the Project Definitions - General Information page assign a project type that is associated with the standard activities that you want to add to the project.

• On the Project Costing Definition page for the project, select the Standard Activities option to enable the standard activity functionality.

Using standard activities is optional.

See Also

Defining Projects

Understanding Transaction-Related Control Data

Transaction-related control data consists of required and optional information that you use primarily to create transactions. This section provides overviews of:

• Analysis types

• Analysis groups

• Transaction identifiers

Analysis Types

With the exception of programs (summary projects), each project is composed of, at the most basic level, transactions. Transaction rows in the Project Transaction table (PROJ_RESOURCE) contain the quantity and amounts associated with each transaction and all of the identifying information that accompanied those costs. Analysis types are assigned to individual transactions to identify different types of transactions, such as estimated costs, budgeted amounts, actual costs, and billed costs. For example, you can create an analysis type for the calculation of total budgeted amounts of the project compared to total actual costs, to see if the project is over or under budget at any time during the project.

A single transaction can result in multiple transaction rows as it moves through the system. For example, assume that a project has 1,000 USD budgeted for project labor. The actual cost of labor is 1,500 USD, and the amount of billing for the labor is 1,700 USD. The result is three transaction rows that record the same labor transaction as it moves from stage to stage through the project, as shown in this table:

Many of the following analysis types are necessary for Project Costing analysis groups, reports, and processes to function properly. If you choose not to implement these analysis types, you still must configure these features. You can create additional analysis types for processing and analysis purposes.

Project Costing delivers cost sharing analysis types that are used exclusively by PeopleSoft Grants. If a transaction line for a PeopleSoft Grants project meets the criteria of cost sharing that is defined at the Grants business unit level, the system assigns the cost sharing analysis type to the transaction.

Analysis Groups

You use analysis groups to:

• Analyze projects

• Map analysis types

• Enhance system performance

Many analysis groups are necessary for Project Costing project analysis functions and mass changes to execute properly. If you choose not to use the analysis groups that are delivered with Project Costing, you still have to configure the analysis groups or create new ones to use with these functions. This table describes the analysis groups:

Using Analysis Groups to Analyze Project Costs

You use analysis groups to define relationships among analysis types to analyze project costs using Project Costing pages, queries, or reports.

Creating an analysis group to analyze projects follows this process:

1. Group the analysis types to include in the project analysis.

2. Apply the appropriate multiplier to each analysis type to create a relationship.

A multiplier determines how amounts and quantities for a specific analysis type are factored into the analysis. The multiplier is applied to total quantities and amounts in all transactions identified by a specific analysis type. For example, to add amounts to the analysis, enter 1. To subtract costs from the analysis, enter −1. To add half of the amounts to the analysis, enter 0.5.

The easiest way to create analysis groups for analyzing projects is to start with an equation. An equation makes it easier to determine what multiplier to assign to an analysis type. For instance, to create an analysis group to determine whether or not a project is over budget, you might start with this equation: Budgets − Actuals = Budget-to-Cost Variance.

You assign a multiplier of −1 to the Actual Cost analysis type and a multiplier of 1 to the Total Cost Budget analysis type. When using this analysis group for online analysis or reporting, all actual costs from the analyzed project are subtracted from budgeted costs. If the result is a negative number, the project is over budget. To set up the analysis group so that a positive number means that the project is over budget, reverse the multipliers so that budgeted amounts are subtracted from actual costs.

You can apply multipliers to quantities for each analysis type included in an analysis group. When you create analysis groups to analyze project costs, multipliers will probably be the same for both the amount and the quantity.

Using Analysis Groups to Map Analysis Types

New projects or activities can be created from copies of existing projects and activities. You can specify an analysis group to map analysis types from the existing project or activity to the new project or activity. For example, when you create a new project from an existing project, you can create an analysis group that maps actual (ACT) transactions from the existing project to the newly created project as budget (BUD) transactions. By using analysis groups, you can also manipulate mapped amounts. For example, you can enter a multiplier of 2 to double the budgeted quantities and amounts in the new project.

Using Analysis Groups to Enhance System Performance

On some PeopleSoft Project Costing pages, analysis groups limit the number of resource transactions that appear on a page at one time. For example, when there are tens of thousands of transactions per project in the system, performance is greatly reduced if you try to access all of those transactions every time that you open a page. By using analysis groups, you can limit the number of transactions that appear on a page to transactions of specified analysis types.

To do this, create an analysis group that identifies a group of analysis types. When an analysis group is entered as part of the selection criteria, only the resource transactions that contain the analysis types specified in that analysis group are available for use on the page.

See Also

Creating and Defining Projects

Source Groups

The source groups in the following list are necessary for certain award analyses and processes delivered with PeopleSoft Grants to function properly. If you choose not to use the source types that are delivered with PeopleSoft Grants, you still have to configure these source groups or create new ones to be used with these features:

• ITEMS (Inventory Items)

• LABOR (Total Labor)

• MATER (Total Material)

The high-level steps to establish source groups are:

1. Define source types.

2. Define resource categories.

3. Define resource subcategories.

4. Combine multiple source types for award analysis and billing.

5. Add descriptions to resource groups.

Transaction Identifiers

Tiered pricing enables you to adjust the rate applied to cost transactions during the Pricing Application Engine process (PC_PRICING) based on quantities that accumulate against a contract line. This type of pricing applies to rate-based, contract-line processing only. Implementing tiered pricing requires that you create transaction identifiers, which are similar in concept to using analysis groups. Transaction identifiers provide users with the flexibility to identify and group project ChartField values and eliminate the need to identify the ChartField values each time they define tiered pricing for a new contract line.

Transaction limits, another feature that is available if you use PeopleSoft Contracts, also requires the use of transaction identifiers. Transaction identifiers enable you to apply specific limits to transactions with Project Costing ChartField values that match the contents of the transaction identifier for a specific contract line.

Note. You must use PeopleSoft Contracts to implement the Tiered Pricing and Transaction Limits features.

See Defining Transaction Identifiers.

Setting Up Project ChartFields

To set up project ChartFields, use these components:

• Source Types (PROJ_RES_TYPE)

• Categories (PROJ_CATG_DEFN)

• Subcategories (PROJ_SUBCAT_DEFN)

• Relate Source Type/Category (PROJ_TYPE_CAT)

• Relate Category/Subcategory (PROJ_CAT_SUB)

Use these component interfaces to load data into the tables for this component:

• PC_RES_TYPE_INTFC

• PC_CATG_DEFN_INTFC

• PC_SUBCAT_DEFN_INTFC

This section discusses how to:

• Relate source types to categories.

• Relate categories to subcategories.

Pages Used to Set Up Project ChartFields

Relating Source Types to Categories

Access the Relate Source Type/Category page (Set Up Financials/Supply Chain, Product Related, Project Costing, Transaction Options, Relate Source Type/Category, Relate Source Type/Category).

Category	Enter a category to associate with the displayed source type. Available values are based on the Project Type Category Prompt table (PROJ_TYPE_CAT). Add more rows to add additional categories.
Relationship	Enter a description of the relationship for each type and category combination.

Relating Categories to Subcategories

Access the Relate Category/Subcategory page (Set Up Financials/Supply Chain, Product Related, Project Costing, Transaction Options, Relate Category/Subcategory, Relate Category/Subcategory).

Subcategory	Enter a subcategory to associate with the displayed category. Available values are based on the Project Subcategory Prompt table (PROJ_CAT_SUB). Add more rows to add additional subcategories.
Relationship	Enter a description for the new category and subcategory relationship.

Setting Up General Control Data

To set up general control data, use these components:

• Asset Profile (PROFILE_PC).

• Budget Items (PC_BUD_ITEMS).

• Interest Types (INTEREST_TYPE).

• Transaction Codes (PROJ_TRANS_CODE)

• Transaction Types (PC_TRANS_TYPE)

This section discusses how to:

• Define asset profiles.

• Define budget items.

• Define interest types.

• Define transaction types.

Pages Used to Set Up General Control Data

Defining Asset Profiles

Access the Asset Profile page (Set Up Financials/Supply Chain, Product Related, Project Costing, General Options, Asset Profile, Asset Profile).

Note. Project Costing can create capitalized rows and distribute them without integrating with PeopleSoft Asset Management. You can still use the PeopleSoft Asset Management interface tables (INTFC_FIN and INTFC_PHY_A); however, a custom process is required to extract data from these tables.

Asset Level Defaults

Taggable

Defining Budget Items

Access the Budget Items page (Set Up Financials/Supply Chain, Product Related, Project Costing, General Options, Budget Items, Budget Items).

Budget Items - General

The system uses a percent symbol (%) as a wildcard on the Budget Items page. This symbol indicates that the fields with populated values are used in the budget details when that budget item is selected, and the fields that contain wildcards are blank in the budget details.

Note. To create a new budget item, at a minimum you must enter the Budget Item, Effective Date, Effective Status, Description, and a value other than the percent symbol in at least one other field, excluding the Resource Class and Project Role fields. For example, if you enter the required fields, and a resource class and project role, you must still enter a value other than the percent symbol for any other field.

Project Information and General Ledger Information

Enter default values for the fields in the Project Information tab to define project transaction level groupings, and in the General Ledger Information tab to break down the budget amounts to the ChartField level. ChartField values that you enter here are used to establish default values for budget rows entered in the Budget Detail table (PC_BUD_DETAIL). These ChartField values are also used to identify and group transactions when reviewing costs or revenue charges against a budget.

The primary general ledger business on the integration template of the associated project appears as the default value on detail budget rows.

Defining Interest Types

Access the Interest Types page (Set Up Financials/Supply Chain, Product Related, Project Costing, General Options, Interest Types, Interest Types).

Use this page to set up interest types, which identify the type of interest that the system calculates for projects.

Interest types are required only if you want to calculate more than one type of interest for a period.

See Calculating Interest.

Defining Transaction Types

Access the Transaction Types page (Set Up Financials/Supply Chain, Product Related, Project Costing, General Options, Transaction Types, Transaction Types).

Create as many transaction rows as necessary for each transaction type. A single transaction type may contain transaction rows for both standard transactions and intercompany transactions.

The Distribution Type group box functionality is used in earlier releases of Project Costing.

Setting Up Project-Related Information

To set up project-related information, use these components:

• Integration Templates (PROJ_INT_TMPL).

• Project Type (PROJ_TYPE).

• Status Types (PROJ_STATUS_DEFN).

• Project Type Status Path (PC_PRJSTATCTL_PNLG).

• Project-Processing Status (PC_STATUS_DEFAULT).

• Project Role Definition (PROJ_ROLE).

• Phase Types (PROJ_PHASE_TYPE).

• Events (PROJECT_EVENTS).

This section discusses how to:

• Define integration templates.

• Define project types.

• Define status types.

• Define project type status paths.

• Define project status default values.

• Define project roles.

• Define project events.

Pages Used to Set Up Project-Related Information

Defining Templates for Integration with Other Applications

Access the Integration Templates - General Integration page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Integration Templates, Integration Templates, General Integration).

Enter purchasing and asset business units for transactions that are created by projects that are associated with the integration template. Available values are based on the Integration Template table (PC_INT_TMPL).

Note. Users can overwrite the purchasing business unit on rows that are created in Project Costing with a REQ (Requisition) analysis type. However, when you run the Requisition Loader Application Engine process (PO_REQLOAD), the process converts the purchasing business unit to the one that is defined on the integration template.

Access the Integration Templates - General Ledger Integration page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Integration Templates, Integration Templates, General Ledger Integration).

For each project integration template, enter general ledger business units for all transactions that integrate with a project and all accounting transactions that are created by the project. Available values are based on the Integration Template General Ledger table (PC_INT_TMPL_GL).

Defining Project Types

Access the Project Types page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Project Types, Project Types).

Use this page to set up project types that are used to group projects into clusters. Project types enable you to easily analyze all projects of a certain type. For example, you can assign construction projects, maintenance projects, and capital projects as project types.

Rates by Unit

Defining Status Types

Access the Status Types page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Status Types, Status Types).

Effective Date	Enter the date when the status change goes into effect. Status types are effective dated, so multiple statuses can be defined and applied sequentially to a project or activity over time.
Status	Select the status of the effective-dated row. Available values are: Active: This is the default value. Inactive: Select to deactivate the status control options that are associated with the effective date.
Processing Status	Select the processing status to map to this status type. Available values are Active, Inactive, and Pending. When you update a project status type, the system automatically updates the processing status based on this mapping.

Status Control

Use this group box to associate a project control action with an analysis type for a particular status type. To control transactions by using status control on a project or activity, the Enable Status Control option must be activated on the Installation Options - Project Costing Integration page, the project or activity must contain the specified status type, and the incoming transactions must contain the specified analysis type.

Defining Project Type Status Paths

Access the Project Type Status Path page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Project Type Status Path, Project Type Status Path).

Project Status	Enter the status for the path that you are defining. Available values are based on the Project Status table (PROJ_STATUS_TBL).
Email Notify for Status Change	Select to email project members when the project status changes.
Business Process Name, Activity Name, and Event Name	Select the business process, activity, and event to associate with the project type status path.
Project Status To	Select the statuses to which the current status can change. Add rows to add more statuses.

Defining Project Status Default Values

Access the Project Status Defaults page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Project Status Defaults, Project Status Defaults).

Status	Enter the status of the project status defaults. Values are Active and Inactive. The default value is Active.
Processing Status - Active, Processing Status - Inactive, and Processing Status - Pending	Enter the default statuses to map to the Active, Inactive, and Pending processing statuses that the system assigns to autogenerated projects from PeopleSoft Resource Management, Contracts, Grants, and Proposal Management. PeopleSoft Project Portfolio Management and PeopleSoft Program Management use these default statuses only for projects that are created from project requests that are in a Costing or Declined status. If you use PeopleSoft Project Costing without PeopleSoft Program Management, the system uses the project status that you enter for the Active processing status as the default value for new projects that you create in Project Costing. If you use PeopleSoft Program Management, the system uses the project status that you enter for the Pending processing status as the default value for new projects that you create in PeopleSoft Project Costing.
Processing Status	Enter the default processing status that the system assigns to autogenerated projects that are created from approved project requests in PeopleSoft Project Portfolio Management and PeopleSoft Program Management.
Default Project Status	Enter the default project status to map to the processing status for projects that are created from approved project requests in PeopleSoft Project Portfolio Management and PeopleSoft Program Management.

Defining Project Roles

Access the Project Role page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Project Roles, Project Role).

Project roles are defined by two profiles—the security profile and the qualification profile.

Note. You must install PeopleSoft Program Management to integrate with PeopleSoft Resource Management for staffing.

Defining Project Events

Access the Events page (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Events, Events).

You must define project status types before you define project events.

Use the Project Definitions - Approval page to define approval sequences for project events.

Setting Up Activity-Related Information

To set up activity-related information, use these components:

• Activity Types (PROJ_ACTIVITY_TYPE).

• Activity Type Status Path (PC_ACTSTATCTL_PNLG).

• Quality Types (PROJ_QUALITY_DEFN).

• Define Standard Activities (FS_ACTIVITY_TBL).

Use the PC_STD_ACT_INTFC component interface to load data into the tables for the FS_ACTIVITY_TBL component.

This section discusses how to:

• Define activity types.

• Define activity type status paths.

• Define standard activities.

Pages Used to Set Up Activity-Related Information

Defining Activity Types

Access the Activity Types page (Set Up Financials/Supply Chain, Product Related, Project Costing, Activity Options, Activity Types, Activity Types).

Activity type labels identify and group activities to facilitate analysis and reporting on similar activities across projects.

See Also

PeopleSoft Project Costing Reports: A to Z

Understanding Integration of PeopleSoft Project Costing with Microsoft Project

Defining Activity Type Status Paths

Access the Activity Type Status Path page (Set Up Financials/Supply Chain, Product Related, Project Costing, Activity Options, Activity Type Status Path, Activity Type Status Path).

You must define status types before you define activity type status paths. Activities use the same status type data that you define at the project level.

The procedure to define activity type status paths is the same as the procedure to define status paths for projects.

See Project Type Status Paths.

Defining Standard Activities

Access the Standard Activities page (Set Up Financials/Supply Chain, Common Definitions, Activities, Define Activities, Standard Activities).

Use this page to predefine activities that users can assign to projects.

Standard activities are keyed by setID and based on project type. To enable standard activity functionality, select the Standard Activities check box on the Project Costing Definition page for a project. Using standard activities is optional.

See Also

Defining Projects

Adding Activities to Projects

Setting Up Transaction-Related Information

To set up transaction-related information, use these components:

• Analysis Types (PROJ_ANALYSIS_TYPE)

• Analysis Groups (ANALYSIS_GRP_DEFN)

• Resource Groups (PROJ_RES_GRP_DEFN)

• Transaction Identifiers (PC_TRANS_IDENTIFY)

This section discusses how to:

• Define analysis types.

• Define analysis groups.

• Define source groups.

• Define transaction identifiers.

Pages Used to Set Up Transaction-Related Information

Defining Analysis Types

Access the Analysis Types page (Set Up Financials/Supply Chain, Product Related, Project Costing, Transaction Options, Analysis Types, Analysis Types).

Commitment Control Amount Type	Select an amount type that tells Commitment Control how to process transactions. This field is directly related to the type of transaction that is coming into Commitment Control and identifies what type of transaction to process. This field appears only if the Commitment Control feature is activated.
Source Transaction Type	Displays the source transaction type defined in the Commitment Control feature, which maps Project Costing fields to Commitment Control fields. The two source transaction types are PC_JOURNAL and PC_BUDGET. This field appears if the Commitment Control feature is activated.

See Setting Up Commitment Control Source Transaction Types.

Defining Analysis Groups

Access the Analysis Groups page (Set Up Financials/Supply Chain, Product Related, Project Costing, Transaction Options, Analysis Groups, Analysis Groups).

Perform Mapping	Select to use the analysis group for mapping analysis types from a template to a new project or activity.
Perform Multiplication	Select to manipulate transaction quantities and amounts. Enter multipliers in the Quantity Multiplier and Amount Multiplier fields.
Analysis Type	Select the analysis types to include in the analysis group.
Analysis Type Map	Select the analysis type to which the analysis type in the first column will be converted in the newly created project or activity. These fields appear only if you select the Perform Mapping option.
Quantity Multiplier and Amount Multiplier	Enter a factor that the system uses to modify incoming quantity and amount values. Enter multipliers of zero to copy quantities and amounts into new projects as zero.

Defining Source Groups

Access the Source Groups page (Set Up Financials/Supply Chain, Product Related, Project Costing, General Options, Transaction Options, Source Groups, Source Groups).

Flexible Rate	Enter a rate by which to multiply the source types in this source group to create a special project view.
Source Types	Select the source types to include in the source group.

Defining Transaction Identifiers

Access the Transaction Identifiers page (Set Up Financials/Supply Chain, Product Related, Project Costing, Transaction Options, Transaction Identifiers, Transaction Identifiers).

Enter source type, category, and subcategory rows that are valid combinations of project ChartField values. Use the wildcard value (a percent sign) in a field to indicate that any value for that field is valid in combination with the other field values in that row. Although the system prevents the creation of duplicate rows within a transaction identifier, an identical row can be part of other transaction identifiers.

See Also

Defining Tiered Pricing

Pricing Contracts

Setting Up Summarization Templates

This section discusses setting up summarization templates.

Summarization Templates are used during the feeder interface process (such as PC_EX_TO_PC), the Pricing process (PC_PRICING), and the Variance Pricing process (PC_VAR_PRICE).

For additional information about Feeder and Pricing Summarization,

See Understanding Feeder and Pricing Summarization.

For additional information about Variance Pricing,

See Understanding Variance Pricing.

Page Used to Set up Summarization Templates

Setting up Summarization Templates

Access the Summarization Template page (Set Up Financials/Supply Chain, Product Related, Project Costing, General Options, Summarization Template).

If you have selected the corresponding check box on the Project Costing Integration page, in the Summarization Options group box, then Use this page to create summarization templates. Summarization templates determine the fields and the level of summarization that the system should use when these processes run:

The Variance Pricing summarization process. The results of the Variance Pricing process are posted to the PROJ_RESOURCE table, or can be reviewed prior to posting to the PROJ_RESOURCE table.

If you leave a field off of the summarization template you are indicating that the information in that field is not necessary. Therefore, if a field is left off of the template, the field is populated with these values on the summarized transaction:

• Blank – if the field is a string field.

• Zero – if the field is a number field.

• Null – if the field is a date field.

Because leaving a field off of the summarization template results in a blank, or zero, value in the summarized transaction, you should use caution when deciding to not include the Project Costing ChartFields and General Ledger ChartFields. If you use the Project Costing ChartFields such as source type, category, and subcategory, Oracle's PeopleSoft recommends that these fields be included on summarization templates.

Pricing Summarization Templates

When creating a pricing summarization template, Oracle's PeopleSoft recommends that you include these fields, at a minimum:

• CONTRACT_NUM

• CUST_ID

• RESOURCE_TYPE

• RESOURCE_CATEGORY

• RESOURCE_SUB_CAT

• DESCR

If you are using Time and Labor integration and Pricing Summarization, but are not using Time and Labor summarization, then you should include these fields on the Pricing Summarization Template:

• EMPLID

• EMPL_RCD

• SEQ_NBR

Time and Labor Summarization Templates

When creating a Time and Labor summarization template, you must include these fields to reconcile billed estimates with new estimates and actuals. (The first two are required and will generate errors if you leave them off a template but the third field is suggested and will generate a warning to be used if you are doing any type of billing):

• EMPLID

• EMPL_RCD

• BI_DISTRIB_STATUS