PeopleSoft Purchasing 9.1 PeopleBook

Using the Requisition Loader

This chapter provides an overview of the Purchasing Requisition Loader Application Engine process (PO_REQLOAD) and discusses how to:

Load requisitions.
Use the Purchase Order Requisition enterprise integration point (EIP).
Correct Purchasing Requisition Loader process errors.
Update direct shipment information.
Purge requisition load requests.

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 vendor 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.

See Contract Pricing for Requisitions and Purchase Orders.

Purging Requisition Load Requests

Commitment Control Budget Processor Process in PeopleSoft Purchasing

Using Requisition Loader Defaults and Overrides

Defining Purchasing Requisition Loader System Sources

This section discusses Purchasing Requisition Loader process system sources. The process looks to these various sources to see if any transactions are available for requisition creation.

Inventory System Source

When running the Purchasing Requisition Loader process, you can have it query the PeopleSoft Inventory system source (REPLEN_RQST_INV table) for inventory items that require replenishment. To have the process query this table, select a system source field value of BIN (inventory batch) on the Requisition Loader page.

The Purchasing Requisition Loader process retrieves PeopleSoft Inventory requisitions in Ready status. While the Purchasing Requisition Loader process is processing the inventory requisition, the inventory requisition is in a process status. Once the Purchasing Requisition Loader process successfully creates a requisition for the inventory requisition, the inventory requisition is in Processed status. If the item ID is not a valid PeopleSoft Purchasing item, the inventory requisition schedule status is set to Error.

The Purchasing Requisition Loader process requires a default account code, which you set up on the Requisition Loader Defaults - Req Loader Defaults page. The value that you define populates the account code on the requisition's distribution lines. This is typically defined with an accrued liability account rather than the expense or inventory account when the Purchasing Requisition Loader process loads replenishment requisitions from PeopleSoft Inventory. Because these replenishment requests will be putaway into inventory, the Inventory Accounting Line generation process determines the appropriate inventory account for the putaway transaction, and the offset accounting information originates from the Requisition's General Ledger ChartFields. In addition, the DISTRIB_TYPE field can be populated from the replenishment request, carried through PeopleSoft Purchasing, and passed back to PeopleSoft Inventory with the receiving transactions. The information is then passed to PeopleSoft Cost Management, which creates the appropriate PeopleSoft General Ledger transactions. The offset account information, which is in the PeopleSoft General Ledger ChartFields on the purchase order, is populated by PeopleSoft Payables and used on the voucher transactions to offset the actual AP Liability when the voucher is posted.

Order Management System Source

When running the Purchasing Requisition Loader process, you can have it query the PeopleSoft Order Management system source (ORD_SCHEDULE table) for order line items that require direct shipment from the vendor to the customer. To have the process query this table, select a system source field value of BOM (order management batch) on the Requisition Loader page.

The Purchasing Requisition Loader process retrieves direct shipment purchase requests that meet the following criteria:

Field	Field Value
TRFT_SRC_TYPE IN_FULFIlL_STATE TRFT_DISPOSITION or TRFT_SRC_TYPE IN_FULFIlL_STATE TRFT_DISPOSITION	3 (New Requisition) 10 (Pending) 2 (Direct Receipt) or 3 (New Requisition) 10, 70 (Pending, Depleted) 1 (Direct Ship)
ORD_SCHEDULE.ORD_SCH_STATUS	O (open)
ORD_SCHEDULE.PO_DISTRIB_STATUS	1 (active)
ORD_SCHEDULE.PO_HOLD_FLAG	N (no)

If the special handling check box (SPEC_HANDLE_CODE) is selected on the order schedule, the Purchasing Requisition Loader process uses the shipping method code (SHIP_TYPE_ID) and carrier ID (CARRIER_ID) on the order schedule for the requisition schedule. The same shipping method and carrier ID information is used on the purchase order. If the purchase request is for a configured product, the Purchasing Requisition Loader process also retrieves the configuration code (CONFIG_CODE) and template ID (TEMPLATE_ID). Each requisition line generated carries the ship to customer ID (SHIP_TO_CUST_ID) from the PeopleSoft Order Management sales order.

While the Purchasing Requisition Loader process is processing the direct shipment purchase requests, the direct ship from vendor schedule is in In Process status. Once the Purchasing Requisition Loader process successfully creates a requisition for the purchase request, the direct ship from vendor schedule status changes to Processed. If the item ID is not a valid purchasing item, the Purchasing Requisition Loader process changes the schedule status to Error. The Purchasing Requisition Loader process updates the PeopleSoft Order Management sales order with the requisition information. View the requisition in PeopleSoft Order Management on the Shipment Schedules page.

Note. Direct ship from vendor orders are not eligible for receiving in PeopleSoft Purchasing because they are normally sent directly to a customer site and received there.

Product Configurator System Source

When running the Purchasing Requisition Loader process, you can have it query the PeopleSoft Product Configurator system source (CP_OPT_HDR table) for configured line items that need to be sourced through PeopleSoft Purchasing. To have the process query this table, select a system source field value of BCP (product configurator batch) on the Requisition Loader page.

The Purchasing Requisition Loader process retrieves PeopleSoft Product Configurator orders in Open status. The Consolidate with other Reqs and Inventory Source Flag check boxes for the PeopleSoft Product Configurator system source and Loader business unit must be clear for this process to work as designed. The Purchasing Requisition Loader process sets these PeopleSoft Product Configurator defaults to No. Alternatively, you can set these defaults on the Requisition Loader Defaults - Overrides and Options page for the PeopleSoft Product Configurator system source and Loader business unit.

While the Purchasing Requisition Loader process is processing the configured item purchase requests, the configured order status is In Process. Once the Purchasing Requisition Loader process successfully creates a requisition for the configured item purchase request, the configured order schedule is in Processed status.

The Purchasing Requisition Loader process generates requisition lines for each component line item and updates the configured order with the requisition information.

Project Costing System Source

When running the Purchasing Requisition Loader process, you can have it query the PeopleSoft Project Costing system source (PROJ_RESOURCE table) for PeopleSoft Project Costing purchase requests. To have the process query this table, select a system source field value of PPC (project costing online entry page) on the Requisition Loader page.

The Purchasing Requisition Loader process retrieves PeopleSoft Project Costing purchase requests that meet the following criteria:

Field	Field Value
DEFAULT_ANALYSIS_TYPE	REQ (required)
PO_DISTRIB_STATUS	1 (active)

While the Purchasing Requisition Loader process is processing the PeopleSoft Project Costing purchase request, the Project Costing order is in In Process status. Once the Purchasing Requisition Loader process creates requisitions from the PeopleSoft Project Costing purchase request, it adds a requisition ID to each of the requisition transactions on the PROJ_RESOURCE table. It also changes the PO_DISTRIB_STATUS of the requisition transactions on the PROJ_RESOURCE table to Processed.

Maintenance Management System Source

When running the Purchasing Requisition Loader process, you can have it query the PeopleSoft Maintenance Management system source (WM_WO_SCHED_PO table) for description only or non-inventory line items that need to be sourced through PeopleSoft Purchasing. To have the process query this table, select a system source field value of WM (Maintenance Management) on the Requisition Loader page.

The Purchasing Requisition Loader process retrieves PeopleSoft Maintenance Management requisitions in Ready to Stagestatus (WO_REQ_STATUS). While the Purchasing Requisition Loader process is processing the maintenance management requests, the maintenance management requisition status is In Process. Once the Purchasing Requisition Loader process successfully creates a requisition for the maintenance management requisition, the maintenance management requisition is in Complete status.

The Purchasing Requisition Loader process retrieves the PeopleSoft Maintenance Management procurement distribution rows if the item is non-inventoried or open description. It then copies the distribution rows to the requisition. It also copies the project business unit, project, and project activity from the work order.

Plus, the process will clear the asset information for distributions that are associated with PeopleSoft Maintenance Management work orders because requisitions associated with work orders cannot be designated for PeopleSoft Asset Management.

External System Sources

External system sources for the Purchasing Requisition Loader process include third-party systems, PeopleSoft Integrated FieldService, and PeopleSoft Purchasing. Each of these external system sources stages requisition data to the PO_REQLOAD_RQST table.

The following table lists the system source field values that designate external systems sources on the Requisition Loader page:

External System Source	System Source Field Value
PeopleSoft Purchasing	BPO
PeopleSoft CRM FieldService	BPO
Third-party data source	FRM (external form)

Updating Direct Shipment Information

Processing Enterprise Integration Points (EIPs)

Understanding Inventory Replenishment Processing

Creating and Modifying Replenishment Requests

Maintaining Order Schedule Information

Creating Direct Production and Requisition Orders

Defining Purchase Item Rules

Integrating Requisitions and Purchase Orders with PeopleSoft Project Costing

Using Requisition Loader Defaults and Overrides

Loading Requisitions

This section discusses how to run the Purchasing Requisition Loader process.

Page Used to Load Requisitions

Page Name	Definition Name	Navigation	Usage
Requisition Loader	RUN_POC1210	Purchasing, Requisitions, Load Requisitions, Requisition Loader	Set parameters for running the Purchasing Requisition Loader process.

Running the Purchasing Requisition Loader Process

Access the Requisition Loader page (Purchasing, Requisitions, Load Requisitions, Requisition Loader).

System Source	Indicates the version of the Purchasing Requisition Loader process that you want to run for the selected requisition loader business unit. Depending on the system source that you define here, the process queries various tables and loads qualifying purchase requests to create requisitions. PeopleSoft Purchasing batch and the external system sources are always valid values. Other valid system sources vary depending on the applications installed. Values include: BCP (configurator product batch). BIN (inventory batch). BOM (order management batch). BPO (purchase order batch). POU (point of use). PPC (project costing online entry page). WM (maintenance management)
Run Type	Select whether to run the process for all business units, one business unit, one purchase request, or a range of business units. The Auto Load Indicator check box on the Requisition Loader Defaults - Req Loader Defaults page must be selected for business units and their requests to be eligible for processing in conjunction with the All Business Units and Range of Business Units run types. Run types are: All Business Units: Select to run the process for all business units. One Business Unit: Select to run the process for one business unit. If you select this value, enter a value in the Requesting Loader Bus Unit (requesting loader business unit) field. One Request: Select to run the process for a particular requisition request ID or replenish ID. When you select this value, the Requisition Request ID field becomes available for entry. If you select this value for the BIN system source, the Replenish ID field becomes available for entry and you must enter a value. Range of Business Units: Select to run the process for a range of business units. If you select this value, enter a From and To Requesting Loader Bus Unit.
Requesting Loader Bus Unit (requesting loader business unit)	Select the originating business unit for the requests that you want to load. Values include only those business units that are valid for the selected system source. The valid business units for each system source are defined on the Requisition Loader Defaults - Req Loader Defaults page.
Requisition Request ID	Identifies a group of purchase request rows on the PO_REQLOAD_RQST table. Create this ID by specifying any number as the requisition request ID. If you select a run type of One Request, you must enter either a requisition request ID or a replenish ID. The Requisition Request ID field is not used for inventory batch requests, or for the BIN system source.
Replenish ID (replenishment ID)	Identifies the inventory replenishment to be loaded to a requisition and is used when the system source is inventory batch, or BIN. If you select a run type of One Request, you must enter a replenishment ID. If you do not enter a replenishment ID when running the process for the BIN system source, all replenishment IDs for the Inventory Requisition Loader business unit selected are loaded to the requisition.
Auto Assign Req ID (automatic assign requisition ID)	Select to specify the automatic numbering options for the requisitions that are created by the Purchasing Requisition Loader process. If a requisition ID is already assigned to the purchase request on the PO_REQLOAD_RQST table, the existing requisition ID is used. Values are: When not specified: If no requisition ID is assigned on the table or on the page, the Purchasing Requisition Loader process determines the requisition ID. When not specified use: If no requisition ID is assigned, the requisition ID that you specify in the adjacent field is assigned and the line numbers are calculated.
Create Mult Reqs (create multiple requisitions)	Select this check box to create a separate requisition ID for each replenishment ID (PeopleSoft Inventory), loader requisition ID (external), resource ID (PeopleSoft Project Costing), and order number (PeopleSoft Order Management). If you select this check box, the maximum load lines number is ignored, and the Auto Assign Req ID and Auto Line Numbering fields are unavailable for entry. Unless you select the Create Mult Reqs (create multiple requisitions) check box, the Purchasing Requisition Loader process creates one requisition that includes all the purchase request data until the maximum load lines number is met. Set the maximum load lines number at installation on the Installation Options - Purchasing page. Note. If the rows for the Purchasing Requisition Loader process have stockless items and standard items (items you stock) and you do not select the Create Mult Reqs check box, the system will still create separate requisitions one for the stockless items and one for the standard items.
Auto Line Numbering	Select automatic line numbering options for the requisitions that are created by the Purchasing Requisition Loader process. Values are: Auto Assign: Select to have the system assign a number to each requisition line automatically. Any requisition line numbers that you entered previously are overridden. When not specified: Select to have the system assign requisition line numbers only when a line number is not specified.
Copy Item Spec (copy item specifications)	Select this check box to copy the item specifications to the requisition. This check box is available when the system source is inventory batch, or BIN.
Get Preferred Vendor	Select a vendor for the requisitions that the Purchasing Requisition Loader process creates. Values are: Always Override: Select to have the system override the vendor that is selected on the requisition and substitute it with the preferred vendor. None: Disables this field. A preferred vendor is not selected. If the vendor ID field on a requisition is blank, the system does not populate that field. However, if you have already provided a vendor ID, the system preserves the selection. When not specified: Select to have the system select the preferred vendor only on requisitions that do not have a vendor specified.

Defining Purchasing Installation Options

Defining Requisition Loader Defaults

Using the Purchase Order Requisition EIP

This section provides an overview of the Purchase Order Requisition EIP and discusses how to process the Purchase Order Requisition EIP.

Understanding the Purchase Order Requisition EIP

The Purchase Order Requisition EIP processes requisition data using an asynchronous service operation from PeopleSoft CRM or external surgical resource software application.

This data is loaded to the PO_REQLOAD_RQST and PO_REQLOAD_CMT staging tables.

Run the Purchasing Requisition Loader process to create requisitions from the staged data.

Pages Used to Use the Purchase Order Requisition EIP

Page Name	Definition Name	Navigation	Usage
Requisition Loader	RUN_POC1210	Purchasing, Requisitions, Load Requisitions, Requisition Loader	Set parameters for running the Purchasing Requisition Loader process.
Data Collection Setup	BCT_SETUP_FS	SCM Integrations, Setup, Data Collection, Data Collection Setup	Set the option to keep transaction log history for electronic data collection transactions and to set the default file suffix.
Data Def Maint (data definition maintenance)	EO_EIP_CTL_MAINT	SCM Integrations, Transaction Error Handling, Maintain Data Definitions, Data Def Maint	View data detail or correct errors for subscribe messages that contain data rather than transactions

Using the Purchase Order Requisition EIP

PeopleSoft delivers the service operations in PeopleSoft Integration Broker with a default status of Inactive. You must activate each service operation before attempting to send or receive data from a third-party source or another PeopleSoft system, such as CRM.

Before you can use the Purchase Order Requisition EIP, you must:

Setup the service operation within PeopleSoft Integration Broker and Enterprise Components:

Use the information in the table below and refer to the setup instructions in the PeopleSoft Supply Chain Management Integration 9.1 PeopleBook, "Implementing Integrations" chapter, Setting Up Service Operations section.

Service Operation	Direction and Type	Handlers	Chunking Available?	Integrates With
PURCHASE_REQUISITION_LOAD	Inbound Asynchronous	PurchaseRequisitionLoad	No	third-party system Surgical Resource Software application
PURCHASE_REQUISITION_LOAD_CRM	Inbound Asynchronous	PurchaseRequisitionLoad	No	PeopleSoft CRM

Service Operation

Direction and Type

Handlers

Chunking Available?

Integrates With

PURCHASE_REQUISITION_LOAD

Inbound

Asynchronous

PurchaseRequisitionLoad

third-party system

Surgical Resource Software application

PURCHASE_REQUISITION_LOAD_CRM

Inbound

Asynchronous

PurchaseRequisitionLoad

PeopleSoft CRM

Run the Purchasing Requisition Loader process to create requisitions from the staged data.
Use the Data Def Maint page to view service operation data and correct error messages that are picked up in the processing of the service operation.

See Also

Setting Up Service Operations

Understanding PeopleSoft Supply Chain Management Enterprise Integration Points

PeopleTools PeopleBook: Integration Broker

Correcting Purchasing Requisition Loader Process Errors

This section provides an overview of the Purchasing Requisition Loader error processing and discusses how to:

Review and correct Purchasing Requisition Loader process data errors.
View and enter requisition comments.
Enter or edit override address information.

Understanding the Purchasing Requisition Loader Error Processing

During processing, the Purchasing Requisition Loader process, like other processes, writes messages to the PeopleSoft Application Engine trace log. If an error occurs that terminates the Purchasing Requisition Loader process before it creates the new requisition, you must review the log, correct the error that is indicated on the Requisition Loader Request page, and restart or rerun the Purchasing Requisition Loader process.

If the item ID on a purchase request is not a valid PeopleSoft Purchasing item, the purchase request line status is set to Error. To correct this error, go to the system source.

See Also

PeopleTools PeopleBook: PeopleSoft Application Engine

Pages Used to Correct Purchasing Requisition Loader Process Errors

Page Name	Definition Name	Navigation	Usage
Requisition Loader Request	PO_REQLOAD_RQST	Purchasing, Requisitions, Stage For Loading, Requisition Loader Request	Review and correct Purchasing Requisition Loader process data for the external form and purchasing batch system sources. For other system sources, errors are set as statuses on source records. Access the source document directly to correct data.
Description	PO_REQLOAD_DESCR	Click the Description link on the Requisition Loader Request page.	Enter and view descriptions for a specific item. The item description link comprises the first 30 characters of the item's description in the Transaction Item Description text box on the Description page.
Asset Information	REQ_LOAD_ASSET	Click the Asset Information link on the Requisition Loader Request page.	Enter asset information for an eligible item.
Comments	REQ_LOAD_CMT1	Click the Comments link on the Requisition Loader Request page.	View and enter comments for specific requisitions.
Category Search	CAT_SEARCH_SEC	Click the Category Search link on the Requisition Loader Request page.	Search for and select an appropriate category ID for the item when entering an improvised item. The search for the category ID is done using a category hierarchy tree.
Override Address	REQ_LOAD_OVADDR	Click the Override Address link on the Requisition Loader Request page.	Enter or edit override address information that is carried over with the requisition from the PO_REQLOAD_RQST table.
View Category Hierarchy	CAT_PARENTAGE_SEC	Click the View Hierarchy link on the Requisition Loader Request page.	View information about where a category resides in the entire catalog tree hierarchy.

Reviewing and Correcting Purchasing Requisition Loader Process Data Errors

Access the Requisition Loader Request page (Purchasing, Requisitions, Stage For Loading, Requisition Loader Request).

Requisition Tab

Status	Displays the current status of the purchase request transaction. After you make any necessary corrections on this page, change the status from Error to Active, then save the page. When you change the status to Active, the purchase request transaction becomes available to be picked up by the Purchasing Requisition Loader process.
Item ID	Displays the ID number for the requisitioned item. If the purchase request has an incorrect item ID, you must correct the item ID to save the page. If the purchase request does not have an item ID, enter a requisition quantity, unit of measure, price, and category in order to save the page.

Price Tab

Select the Price tab.

Ship To Customer	Displays the ship to customer ID that is assigned to the requisition line. For system sources of BPO, a value in this field indicates that the order should be shipped directly to a customer.
IN Unit (PeopleSoft Inventory business unit)	Displays the PeopleSoft Inventory business unit that is assigned to the requisition line.
Revision	Displays the manufacturer's product revision number of the requested item. If the ship to is a PeopleSoft Inventory business unit, and the item is under revision control in that business unit, the revision defaults to that effective on the due date.
Req Qty (requisition quantity)	Displays the requisition quantity. If no requisition quantity appears, you must enter a value here.
Calc Price (calculate price)	Select this check box if you want the requisition price to be recalculated for the purchase order by the PO Calculations process (PO_POCALC).

Chartfields Tab

Select the Chartfields tab.

All the fields on this tab are optional and are used only if they are supplied by the system source from which the information is being loaded.

Currency	The value in this field appears by default from the Requester Setup page (REQUESTOR_TBL) if the business unit enables multicurrency requisitions. If the business unit does not allow multicurrency requisitions, the currency field value is populated from the business unit. You cannot override this value on this page. This currency is referred to as the requisition transaction currency. If there is no currency set up in the requester table, it appears by default from the business unit.
Location	Enter the internal item delivery location for this requisition line. The value in this field is the internal destination of the requested items.
GL Unit (PeopleSoft General Ledger business unit)	Displays the PeopleSoft General Ledger business unit that is charged for the requisitioned items. The PeopleSoft General Ledger business unit appears by default from the requisition business unit.
Entry Event	Correct any errors resulting from invalid entry event codes that are loaded from external sources. Any value that is selected here is overridden if there is an entry event code selected on the Requisition Loader Defaults - Overrides and Options page.
Ult Use Code (ultimate use code)	Select the ultimate use code. In some situations, the ultimate use of an item alters the sales and use taxes that a business unit must pay. The system calculates the sales and use tax based on the tax authority and the ultimate use codes that are established on the Ultimate Use Code page.
Entered By	Displays the user ID of the person who entered the requisition.

See Also

Using Entry Events

Running the PO Calculations Process

Defining Ultimate Use Codes

Understanding PeopleSoft ChartFields

Establishing Requesters and Defaults

Using Requisition Loader Defaults and Overrides

Viewing and Entering Requisition Comments

Access the Comments page (click the Comments link on the Requisition Loader Request page).

Comment Type	Select a comment type. Types are: Header: Comments are designated as requisition header comments and are accessible from the Maintain Requisitions - Requisitions page. Line: Comments are designated as requisition line comments and are accessible from the Maintain Requisitions - Requisitions page.
Allow Modify Comments	Select this check box to enable other users to modify these comments.
Send to Vendor	Select this check box to send these comments to vendors.
Shown at Receipt	Select this check box to have these comments appear on the receipt documents.
Shown at Voucher	Select this check box to have these comments appear on the voucher.

See Also

Creating Requisition Header Information

Entering or Editing Override Address Information

Access the Override Address page (click the Override Address link on the Requisition Loader Request page).

The address information that you enter on this page should not necessarily be the customer address, if a ship to customer ID is supplied. The override address information could be almost any other address, from an alternate customer address to a mailbox stop where a service technician can pick up a part that is needed to perform a repair.

Updating Direct Shipment Information

This section provides an overview of the Direct Shipments Update Application Engine process (PO_REQDROP) and discusses how to run the Direct Shipments Update process.

Understanding the Direct Shipments Update Application Engine Process (PO_REQDROP)

The Direct Shipments Update process retrieves modified PeopleSoft Order Management sales order schedules and updates the requisitions in PeopleSoft Purchasing.

This process looks for purchase requests on the ORD_SCHEDULE table that have a direct ship status (PO_DISTRIB_STATUS) value of Modified. When you modify certain aspects of direct ship from vendor sales order lines or shipment schedules in PeopleSoft Order Management, the system sets the direct ship status to Modified.

Changes made to the following fields set the direct ship status to Modified:

Field	Field Name	PeopleSoft Order Management Page
Product ID	PRODUCT_ID	Order Lines
Order Quantity	QTY_ORDERED	Order Lines
Requested Shipment Date	REQ_SHIP_DTTM	Shipment Schedules
Requested Shipment Time	REQ_SHIP_DTTM	Shipment Schedules
Requested Arrival Date	REQ_ARRIVAL_DTTM	Shipment Schedules
Requested Arrival Time	REQ_ARRIVAL_DTTM	Shipment Schedules

If the special handling check box (SPEC_HANDLE_CODE) is selected on the order schedule, changes that are made to the values in the following fields also set the direct ship status to Modified:

Field	Field Name	PeopleSoft Order Management Page
Carrier ID	CARRIER_ID	Shipment Schedules
Shipping Via	SHIP_TYPE_ID	Shipment Schedules

If you cancel the PeopleSoft Order Management direct ship from vendor sales order schedule, the system sets the direct ship status to Modified. After the Direct Shipments Update process runs, if the direct ship from vendor sales order schedule is changed, the direct ship status (PO_DISTRIB_STATUS) is set to Processed. If the direct ship from vendor sales order schedule is canceled, the system sets the requisition distribution status to Canceled. If the requisition is sourced to a purchase order, an entry is created for the Change Purchase Order process. When the change order is processed and if the purchase order is already dispatched, corresponding purchase order lines are canceled. If the purchase order is not yet dispatched you'll receive a message suggesting that you delete the corresponding purchase order lines.

If the requisition has already been sourced to one or more purchase orders, each changed field that is defined in the change order template generates a change order in PeopleSoft Purchasing. If the changed field is not identified in the change order template, PeopleSoft Purchasing does not create a change order. There is a new change order every time that you dispatch the purchase order.

Page Used to Update Direct Shipment Information

Page Name	Definition Name	Navigation	Usage
Update Direct Ship	RUN_REQ_DRPSHP_CHG	Purchasing, Requisitions, Update Direct Shipments, Update Direct Ship	Run the Direct Shipments Update process.

Running the Direct Shipments Update Process

Access the Update Direct Ship page (Purchasing, Requisitions, Update Direct Shipments, Update Direct Ship).

Process Request Parameters

All Business Units

Select to run this process for all PeopleSoft Order Management business units. If you clear this check box, enter a single PeopleSoft Order Management business unit value in the Order Management Business Unit field.

Purging Requisition Load Requests

This section provides an overview of the Purge Requisition Load Request Application Engine process (PO_RLRQPRG) and discusses how to run the Purge Requisition Load Request process.

Understanding the Purge Requisition Load Request Application Engine Process (PO_RLRQPRG)

Use this process to purge purchase requests that accumulate on the PO_REQLOAD_RQST table. This table is used to store purchase requests that are loaded by the Purchasing Requisition Loader process.

To increase system performance, PeopleSoft recommends that you run the Purge Requisition Load Request process regularly, depending on how often you execute the Purchasing Requisition Loader process.

Page Used to Purge Requisition Load Requests

Page Name	Definition Name	Navigation	Usage
Purge Reqload Requests (purge requisition load requests)	RUN_PO_RLRQPRG	Purchasing, Requisitions, Purge Load Requests, Purge Reqload Requests	Set parameters for the Purge Requisition Load Request process and initiate the process.

Running the Purge Requisition Load Request Process

Access the Purge Reqload Requests page (Purchasing, Requisitions, Purge Load Requests, Purge Reqload Requests).

Purge Processed Rows	Select this check box to purge the purchase requests on the PO_REQLOAD_RQST table that are in Processed status.
Purge Error Rows	Select this check box to purge the purchase requests on the PO_REQLOAD_RQST table that are in Error status.
System Source	Select the system source for the requests that are to be purged.
Requesting Loader Bus Unit (requesting loader business unit)	Select a business unit. If you do not specify a business unit, all requisition loader business units are processed.
Requisition Request ID	Select a requisition request ID on which to run this process. If you enter a value here, specify a requesting loader business unit. Values include the available IDs for the selected business unit. Entering a value here further refines the selection that you make by specifying a requesting loader business unit.
Date Selection	Specify a date selection operation. This field value combines with other operation modifiers to define a date selection operation for capturing Purchasing Requisition Loader requests to purge. Values include: C (current date): Defines the date selection operation based on the current date and the operation modifier in the Operand field. M (current date minus days): Defines the date selection operation based on the current date, the operation modifier in the Operand field, and the number of days that you subtract from the current date by using the Nbr Days (number of days) field. N (no selection by date): Prevents the use of a date selection operation. P (current date plus days): Defines the date selection operation based on the current date, the operation modifier in the Operand field, and the number of days that you add to the current date by using the Nbr Days field. S (specified date): Defines the date selection operation based on a date that you specify and on the operation modifier in the Operand field. When you select this value, the Date Sel Date (date selection date) field is activated.
Operand	Enter an operand to modify the date selection operation. An operand is the modifier that is appended to an operation. In this case, the value in this field combines with the value in the Date Selection field to define the date selection operation that the system uses to collect the Purchasing Requisition Loader requests for purging. The value that you enter here can also combine with the value in the Nbr Days field to further define the date selection operation. Values include: < (less than selection date): The date selection operation captures only Purchasing Requisition Loader process requests with process dates that are less than the selection date. The process date is the date on which the Purchasing Requisition Loader process processed the request and created the requisition. <= (less than or equal to selection date): The date selection operation captures only Purchasing Requisition Loader process requests with process dates that are less than or equal to the selection date. <> (not equal to selection date): The date selection operation captures only Purchasing Requisition Loader process requests with process dates that are not equal to the selection date. = (equal to selection date): The date selection operation captures only Purchasing Requisition Loader process requests with process dates that are equal to the selection date. > (greater than selection date): The date selection operation captures only Purchasing Requisition Loader process requests with process dates that are greater than the selection date. >= (greater than or equal to selection date): The date selection operation captures only Purchasing Requisition Loader process requests with process dates that are greater than or equal to the selection date.
Nbr Days (number of days)	Enter a number of days to be used as an operation modifier. This operation modifier combines with the values in the Date Selection and Operand fields to define the date selection operation. If you select a date selection value that requires a number of days, enter the number here.
Date Sel Date (date selection date)	Enter a specific selection date other than the current date. The date that you enter here is the basis for the date selection operation that is used to collect Purchasing Requisition Loader process requests for purging. This field becomes available for entry when you select S (specified date) in the Date Selection field.