Understanding Integration with PeopleSoft Purchasing

PeopleSoft Project Costing integrates requisitions, purchase orders, or both. PeopleSoft Project Costing also provides a process to adjust purchase requisitions and purchase orders.

This topic discusses:

  • Integrating requisitions from PeopleSoft Project Costing to PeopleSoft Purchasing.

  • Integrating requisitions from PeopleSoft Purchasing to PeopleSoft Project Costing.

  • Integrating purchase orders from PeopleSoft Purchasing to PeopleSoft Project Costing.

These actions occur to create requisition transactions in PeopleSoft Project Costing:

  • The Purchasing Requisition Loader process uses the Project Transaction table (PROJ_RESOURCE) to determine which transactions have an analysis type of REQ and a PO Distribution Status field (PO_DISTRIB_STATUS) value of 1.

    The process copies those transactions into PeopleSoft Purchasing, creates requisitions, and adds a requisition ID to each requisition transaction on the Project Transaction table.

    Note: The Purchasing Requisition Loader process can group multiple transactions into a single requisition by item ID, project ID, activity ID, source type, and so on.

  • The PO distribution status of the requisition transactions on the Project Transaction table changes to 4 (processed) to indicate that the transactions have been processed by PeopleSoft Purchasing.

These actions occur to integrate requisitions originating in PeopleSoft Purchasing into PeopleSoft Project Costing:

  1. After you create requisitions in PeopleSoft Purchasing they are posted to the Requisition Distribution table (REQ_LN_DISTRIB).

    If a requisition originated in PeopleSoft Project Costing, it is replaced when the requisition is approved in PeopleSoft Purchasing.

  2. The Purchasing to Project Costing Application Engine process (PC_PO_TO_PC) uses the Requisition Distribution table to determine which requisitions have a value of N (not distributed) for the PC (Project Costing) Distribution Status field (PC_DISTRIB_STATUS).

    This indicates that the requisition did not originate in PeopleSoft Project Costing, and has not been picked up by Project Costing.

  3. The Purchasing to Project Costing process pulls these requisition lines into PeopleSoft Project Costing.

    Requisitions appear as transactions with the analysis type that is specified in the Requisitions field (AN_TYPE_PO_REQ) on the Installation Options - Project Costing Integration page. The Requisitions field default value is REQ.

    If you use PeopleSoft Maintenance Management, the process also imports the work order business unit, work order ID, task ID, work order resource type, and work order resource line into the Project Transaction table.

  4. The PC Distribution Status field value on the Requisition Distribution table changes to D (distributed) for each transaction that is copied into PeopleSoft Project Costing.

You can integrate purchase orders that originate in PeopleSoft Purchasing into PeopleSoft Project Costing. The Purchasing to Project Costing process identifies the distribution lines in the PO Line Accounting Entries table (PO_LINE_DISTRIB) that are eligible for integration to Project Costing. Rows in the PO Line Accounting Entries table are eligible for integration if they:

  • Contain values for the required project-related ChartFields.

  • Have a PC Distribution Status status of N (not distributed).

The Purchasing to Project Costing process updates the PC distribution status to D (distributed) and copies the transactions to PeopleSoft Project Costing. If you use PeopleSoft Maintenance Management, the process also imports the work order business unit, work order ID, task ID, work order resource type, and work order resource line into the Project Transaction table.

Purchase orders appear as transactions with the analysis type that is specified in the Purchase Orders field (AN_TYPE_PO_PO) on the Installation Options - Project Costing Integration page. The Purchase Orders field default value is COM.