Importing Transactions into PeopleSoft Project Costing

Various PeopleSoft Application Engine processes that are specific to feeder system applications send cost transactions to PeopleSoft Project Costing.

Project Costing summarization templates can be used to summarize transaction rows that are imported into the Project Transaction table. For additional information about summarizing feeder transactions, see Understanding Feeder and Pricing Summarization

Select each page from the Project Costing, Cost Collection menu option.

Page Name

Definition Name

Usage

Time and Labor

PC_TL_TO_PC

Run the Time and Labor to Project Costing Application Engine process (PC_TL_TO_PC) to pull data from PeopleSoft Time and Labor into PeopleSoft Project Costing.

The billing distribution status of the transaction rows that are imported by using the Time and Labor to Project Costing process is based on the billable indicator in the PeopleSoft Time and Labor system. These transaction rows are sent to the Pricing process with cost and revenue distribution statuses of N.

Expenses

PC_EX_TO_PC

Run the Expenses to Project Costing Application Engine process (PC_EX_TO_PC) to pull approved expenses from PeopleSoft Expenses into PeopleSoft Project Costing.

In PeopleSoft Expenses, if you specify a billing action of Nonbillable or Internal on a detail time or expense row, the Expenses to Project Costing process creates a transaction row in the Project Transaction table with a billing distribution status of U (unbillable). The system assigns an analysis type to the transaction based on the analysis type that is specified in the Expenses field (for expense rows) or Mobile Time / Expense field (for time rows) on the Installation Options - Project Costing Integration page. When you price the unbillable row, if the target analysis type on the rate set belongs to the PSWKS analysis group, the system deletes the target row and does not post it to the Project Transaction table.

Payables

PC_AP_TO_PC

Run the Run the Payables to Project Costing Application Engine process (PC_AP_TO_PC) to pull approved vouchers from PeopleSoft Payables into PeopleSoft Project Costing.

Inventory

PC_IN_TO_PC

Run the Inventory to Project Costing Application Engine process (PC_IN_TO_PC) to pull fulfilled demand from PeopleSoft Inventory into PeopleSoft Project Costing.

Order Management

PC_OM_TO_PC

Run the Order Management to Project Costing Application Engine process (PC_OM_TO_PC) to pull project data from open sales orders into PeopleSoft Project Costing.

Purchasing

PC_PO_TO_PC

Run the Purchasing to Project Costing Application Engine process (PC_PO_TO_PC) to pull purchase order transactions into PeopleSoft Project Costing.

Services Procurement

PC_SP_TO_PC

Run the Services Procurement to Project Costing Application Engine process (PC_SP_TO_PC) to pull timesheets, expense transactions, and progress log information into PeopleSoft Project Costing.

Maintenance Management Tools Usage

PC_WM_TO_PC

Run the Maintenance Management Tools Usage Application Engine process (PC_WM_TO_PC) to pull work order tools usage transactions into PeopleSoft Project Costing.

Excluding Transactions from Integrations into Project Costing

PC_EXC_EXCEPTION

Identify the types of transactions to exclude from integrations into Project Costing.

The Cost Collection process integrates project transactions from many different applications in PeopleSoft Financials and PeopleSoft Time and Labor. Transactions with a Project's Business Unit, Project, and Activity are included in the cost collection process. Based on your use of project costing some project transactions may not need to be integrated into Project Costing. The Integration Exclusions page provides configurable criteria for excluding transactions from the PeopleSoft Expenses, General Ledger, and Accounts Payable cost collection processes reducing the volume of unnecessary transactions in the project costing (PROJ_RESOURCE) table.

Setup Integration Exclusions Tile

Use the Setup Integration Exclusions (EP_PC_EXC_CRITERIA_GBL) tile to view Integration Exclusions page.

Navigation:

Select the Setup Integration Exclusions tile from the Project Management Homepage.

This example illustrates the fields and controls on the Setup Integration Exclusions tile.

 Setup Integration Exclusions tile

Integration Exclusions Page

Use the Integration Exclusions (PC_EXC_EXCEPTION) page to identify the types of transactions to exclude from the cost collection processes with Expenses, General Ledger, and Payables.

Navigation:

Setup Financials/Supply Chain > Product Related > Project Costing > Setup Integration Exclusions.

You may also use the Setup Integration Exclusions tile provided on the Project Management Homepage.

This example illustrates the fields and controls on the Integration Exclusions page.

 Integration Exclusions page

Field or Control

Description

Integration Source

'Select the integration source to which the exclusions apply. Choices are Accounts Payable, Expenses and General Ledger.

Sequence

An integration source can have multiple configurations by adding another sequence.

Example: Sequence 1 can be used for criteria from one set of tables and Sequence 2 can be used for criteria for another set of tables.

Sequence helps the administrator organize criteria into manageable groupings. Each sequence is processed independently.

Effective Date

Provide the effective date for the exception criteria.

Effective Status

Select the exception criteria status. All sequences with an Active Status are evaluated when the integration process is run.

Description

Provide the description for the exception criteria.

Date Basis

Date basis is used with Effective Date. Select if the Accounting Date or Transaction Date should be used at run time to determine the effective dated configuration to evaluate.

A transaction is evaluated against only one effective dated configuration per sequence.

Record Name

Select a Record to which the criteria should be applied.

Field Name

Select the Field to which the criteria should be applied.

Operator

Select from the list of available operators.

Value

Enter the value for an excluded transaction.

Prompts are available in the value column for some fields. If prompt values do not exist, then enter values directly into the value field. When using the ‘In’ operator, the excluded values should be separated with a comma.

Example: Enter A,B,C to exclude transactions with an A, B, or C. You should not enter quotes around each value.

For certain fields, SetID will appear in the prompt for Values. The SetID displayed is mapped to the Project Costing Business Unit selected when the configuration is created.

When the PC_GL_TO_PC process is run, the GL_ACCOUNT_TBL will use the General Ledger Business Unit on the transaction to identify the setID on the GL_ACCOUNT_TBL.

Select Save and Add the exception criteria to the integration source.

Note: Each row of criteria is evaluated independently. If a transaction meets the criteria for any row of criteria in any sequence, it will be excluded from the integration into project costing.

Note: Once a transaction is identified as Excluded in the source application, it will not be reevaluated. Meaning, changes to the Exclusion Criteria are applied prospectively.