Loading Interface Table Data into PeopleSoft Project Costing
This topic discusses how to:
Load project and activity data.
Load transaction data.
Pages Used to Load Interface Table Data into PeopleSoft Project Costing
|
Page Name |
Definition Name |
Navigation |
Usage |
|---|---|---|---|
|
Load Projects and Activities |
PC_INTF_GEN |
|
Run the Load Projects and Activities process to load project and activity data into PeopleSoft Project Costing tables. |
|
Load Transactions |
PC_INTFEDIT |
|
Run Load Third-Party Transactions to load transaction data into the Project Transaction table. |
Load Projects and Activities Page
Use the Load Projects and Activities page (PC_INTF_GEN) to run the Load Projects and Activities process to load project and activity data into PeopleSoft Project Costing tables.
Image: Load Projects and Activities page
This example illustrates the fields and controls on the Load Projects and Activities page. You can find definitions for the fields and controls later on this page.

After you stage data from third-party systems to its respective interface tables, you run the various PeopleSoft Application Engine processes to bring the data into PeopleSoft Project Costing tables.
If you use PeopleSoft Program Management, the Load Third-Party Transactions process loads only transactions for activities at the project costing level that is specified on the Program Management Options page. If the Application Engine processes a row that is not a valid costing activity, an error occurs and the transaction remains in the Transactions Interface table. You can view the error on the Review Transactions Details page.
Loading Data from Primavera P6
If the data is coming from Primavera P6, this process is automatically called from the Project Synchronization process (PGM_SYNC_PRJ). When the process is called from Project Synchronization, this process reads data in the project, activity, and resource third-party staging tables and:
Creates new and updates existing project, activity, and resource data in PeopleSoft Project Costing tables.
Updates cross-reference, audit, and synchronization log tables.
If the data is not coming from Primavera P6, this process loads third-party project, activity, and resource data.
Load Transactions Page
Use the Load Transactions page (PC_INTFEDIT) to run Load Third-Party Transactions to load transaction data into the Project Transaction table.
Image: Load Transactions page
This example illustrates the fields and controls on the Load Transactions page. You can find definitions for the fields and controls later on this page.

The Load Third-Party Transactions process validates third-party application transaction data in the Transactions Interface table. If the Projects Budgeting feature is not enabled, then the system loads the data into the Project Transaction table.
If the Projects Budgeting feature is enabled, the process sends budget rows to the Project Budget Detail table (PC_BUD_DETAIL), the Project Budget Plan table (PC_BUD_PLAN), and the Project Transaction table if the interface ID for the row is between 1200000 and 1299999 or between 16000000 and 16999999 and the analysis type is in the cost budget or revenue budget analysis group that is defined on the Project Costing Definition page.
Note: PeopleSoft feeder systems assign an interface ID within the range of 16000000 and 16999999 to rows that are eligible to be posted to the Project Transaction table. For example, transactions that come into PeopleSoft Project Costing from the Commitment Control to Project Costing Application Engine process (PC_KK_TO_PC) have an interface ID that is within this range.
The Load Third-Party Transactions process calls the Multicurrency Conversion Application Engine process (PC_MULTI_CURRENCY) that converts source transaction amounts that come into the Transactions Interface table with a different currency code than the project business unit currency code, if you set up the appropriate exchange rates.
Error Processing
Each row in the Transactions Interface table can hold only one message number and offending field name. If a row has multiple errors, only the last error is stored in the Message Number (MESSAGE_NBR) and Field Name (FIELDNAME) fields.
You can view and correct the error on the Review Transaction Details page. When you correct the error and run the program again, the system writes only the second error to the Message Number and Field Name fields. Repeat the process to correct the remaining errors.