Integrating Requisitions from PeopleSoft Purchasing to PeopleSoft Project Costing

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.