Understanding the Purchasing Requisition Loader Application Engine Process (PO_REQLOAD)
The Purchasing Requisition Loader process collects purchase requests from PeopleSoft Inventory, PeopleSoft Order Management, PeopleSoft Project Costing, PeopleSoft Product Configurator, PeopleSoft Maintenance Management and from PeopleSoft Purchasing or external systems. The process loads the requests into PeopleSoft Purchasing, where requisitions can be created for them.
These different sources of requisition data are called system sources. The PO Batch (purchase order batch) and External Source are always valid system sources for the Purchasing Requisition Loader process. Valid system sources for other PeopleSoft applications appear if you have those applications installed.
The Purchasing Requisition Loader process identifies each loaded purchase request by its requesting business unit. It uses default requester, item, and supplier information to generate requisition lines for sourcing purchase orders or generating inventory demand transactions. Before running the Purchasing Requisition Loader process, you must establish this requisition default information on the Requisition Loader Defaults - Req Loader Defaults (requisition loader defaults - requisition loader defaults) page. Use this page to set up default values for each business unit, system source, and loader business unit combination for which you want to process purchase requests. These default values populate appropriate empty requisition fields when the process runs.
You can use the Requisition Loader Defaults - Overrides and Options page to set override options for the Purchasing Requisition Loader process. The values and status that you define on this page replace the applicable existing requisition field values when the process runs.
The Purchasing Requisition Loader process initially validates the requesting business unit ID and identifies SetID-related information. If the process does not encounter any errors, it changes the purchase request status to being processed. The Purchasing Requisition Loader process generates a requisition for the valid request rows and assigns it the next sequential requisition ID for the PeopleSoft Purchasing business unit.
This process will also populate the procurement card information on the requisition if default procurement card information is defined for the requester. If during this process the system determines that the procurement card has expired, it will go ahead and create the requisition without the procurement card information. In this situation the process does not issue any messages. Finally, the process then sets the status of the valid request rows to Processed. If the Purchasing Requisition Loader process encounters an error in processing the purchase request rows, it stops processing and leaves the purchase requests unchanged.
PeopleSoft Integrated FieldService, PeopleSoft Purchasing, and external system purchase requests are stored on the PO_REQLOAD_RQST table. You should purge the PO_REQLOAD_RQST table periodically by using the Purge Reqload Requests process (PO_RLRQPRG).
You can also default contract information into the requisition loader by using Default Contract on Req check box on the Purchasing Business Unit Options page. This makes the contract available to automatically default onto requisition and purchase order transactions.
The system searches for and ensures that the correct contract is selected for use with the requisition. Any pricing changes for the requisition are called by the AE_PO_CMPRICE process to handle the pricing related to the defaulted contract. For example, if a contract is defaulted into the requisition loader, it will have its related contract price in the requisition item. The system also verifies that the Auto Default check box is selected on the Contract page.
Note:
Depending on the PeopleSoft Framework Approval setting for the requisition, the update might be required to go through approval workflow.