Understanding Feeder and Pricing Summarization

The Feeder Transaction Summary Process

When running an integration process, such as PC_EX_TO_PC, the data is added to a new staging table PC_xx_DETAIL, where xx is the product abbreviation, such as PC_EX_DETAIL. The integration process looks for a transaction summarization template to determine the summarization rules. If a transaction summarization template is found, the integration process uses the rules to summarize the data that is inserted into the project transaction table (PROJ_RESOURCE).

A benefit of the detail table is that you can drill back to the detail when viewing transactions on the Transaction List page.

This diagram illustrates the process flow of the PeopleSoft Expenses, Time and Labor, General Ledger, and Third-Party interface processes:

This diagram illustrates that each application engine process for the corresponding feeder application, sends detailed information to the corresponding detail table. If summarization is being used (the application check box is selected in the Summarization Options section on the Installation Options – Project Costing Integrations page), then the detailed data is summarized and then added to the Project Costing transaction table (PROJ_RESOURCE).

The Pricing Summary Process

When the Pricing process (PC_PRICING) runs, the process takes transactions from the project transaction table (PROJ_RESOURCE) and identifies source rows that are eligible for pricing. The process then generates target rows and looks for a pricing summarization template. If a pricing summarization template is found, the process uses the pricing summarization rule to summarize the data, create target rows, and update the project transaction table (PROJ_RESOURCE).

This diagram illustrates the process flow of the Project Costing pricing summarization process when pricing is called separately from the feeder interface process.

This diagram illustrates the process flow of the Project Costing pricing summarization process when the Pricing process is called with an individual feeder interface process.

The Purchasing and Payables to Project Costing Process

When the Purchasing to Project Costing process (PC_PO_TO_PC) is run, the summarization application engine process is called to summarize requisitions, purchase orders, and reversals. The rows are summarized based on the Payables/Purchasing summarization template.

It is important to understand that there are differences in the way the process handles these two tasks:

• Updates:

  • When not using summarization, the PC_PO_TO_PC and the PC_POADJUST processes automatically update PROJ_RESOURCE.

    If an update comes from a requisition or a purchase order, the processes delete the existing (original) transaction from PROJ_RESOURCE and insert the new transaction.

  • When using summarization, updates are generated off of the detail row in PC_APPO_DETAIL and sent to PROJ_RESOURCE.

    The system creates a new resource ID, a negative amount, and a negative quantity from the original row, which reverses the old row. The system then adds the new transaction to summarized rows.

    The original row of the update cannot be deleted from PROJ_RESOURCE because the PROJ_RESOURCE row is the result of summarizing more than one row together.

• Resource IDs:

  • When not using summarization for Purchasing, the resource ID is assigned using SQL objects PC_COM_RESID_PO and PC_COM_RESID_REQ.

    For purchase orders, the system concatenates the Purchasing business unit, purchase order ID, line number, schedule number, distribution account type, and distribution line number.

    For requisitions, the system concatenates the Purchasing business unit, requisition ID, line number, schedule number, and distribution line number.

    Concatenated resource IDs can be found by clicking the Drill to Source button from the Transaction List page, or on the Maintain Requisitions page.

  • When using summarization for Payables and Purchasing, the system automatically generates resource IDs using auto-numbering for RESOURCE_ID.

Example of Feeder Transaction Summarization

This example shows the difference in the amount of rows that are written to the Project Transaction table when not using transaction summarization templates versus when using transaction summarization templates. The actual level of summarization and the number of transactions that are written to the Project Transaction table is determined by the applicable summarization template.

When not using transaction summarization templates, these three transactions are written to the Project Transaction table (PROJ_RESOURCE):

When using transaction summary templates for expense transactions, these transactions are written to the Expense Detail table (PC_EX_DETAIL):

When using transaction summary templates for expense transactions, these transactions are written to the Project Transaction table (PROJ_RESOURCE):