Creating Purchase Order Change Orders

This chapter provides an overview of the Purchase Order Change Order business process and discusses how to:

• Set up purchase order change templates.

• Identify purchase order change order fields.

• Review processing rules for the Change Purchase Order process (PO_POCHNG).

• Generate purchase order change orders online.

• Load change orders received using electronic data exchanges (EDXs) or supplier-facing online acknowledgements (PeopleSoft eSupplier Connection).

• Use the Purchase Order and Purchase Order Change Order Acknowledgement enterprise integration point (EIP).

• Use the Purchase Order Close Short Workbench.

• Review and approve change order requests.

• Create change orders from approved change requests.

• Purge change request tables.

• View purchase order change history.

Understanding the Purchase Order Change Order Business Process

When you update a purchase order that has been dispatched, you create or append a change order. With PeopleSoft Purchasing, you can create change orders online using the purchase order pages, or you can load and process change requests using the Change Load Application Engine process (PO_CHNGLOAD) and Change Purchase Order Application Engine process.

The Change Load process loads data from the PO_HDR_EC, PO_LINE_EC, and PO_LINE_SHIP_EC tables. These tables store vendor acknowledgements that arrived in the system using EDX or supplier-facing online acknowledgements. These acknowledgements may contain information that requires you to change the purchase orders.

Based on the Change Map template, the Change Load process compares staged source record fields and field values (PO_HDR_EC, PO_LINE_EC, PO_LINE_SHIP_EC) with target system record fields and field values (PO_HDR, PO_LINE, PO_LINE_SHIP). If a difference exists, the Change Load process creates change requests (CHNG_RSQT, CHNG_RQST_DTL).

Based on the purchase order change template, the Change Purchase Order process creates the necessary change orders from these change request tables. The Change Purchase Order process takes the change order information and creates change history records (PO_CHNG_HDR, PO_CHNG_LINE, PO_CHNG_SHIP) and updates target system records with the changes.

When you request a change to a purchase order that has been sourced from a PeopleSoft eProcurement or Services Procurement requisition, the system places the request in the PeopleSoft Purchasing CHNG_RQST and CHNG_RQST_DTL tables. Using the Change Purchase Order process, the system processes the change requests and updates the purchase order. For purchase orders that have already been dispatched, a change order could be created and dispatched to the vendor.

Note. Backorders entered through the supplier-facing online acknowledgements are also processed through the Change Load and Change Purchase Order processes.

Note. The Purchase Order Change Order business process updates most changed values on the purchase order, regardless of whether the fields exist on the purchase order change template. The purchase order change template determines fields that are tracked and recorded in change order history records, and does not determine the fields that can actually be changed on the purchase order. If you are using the vendor rebate functionality, changing the Rebate ID field on the purchase order will not create a change order.

Note. Batch changes to nondispatched purchase orders are stored in the change request tables. These requests are used by the Change Purchase Order process to update original purchase orders. However, these changes, as well as changes made directly to nondispatched purchase orders, are not stored in the change order tables and the change order batch number on the purchase order header is not incremented by 1.

Change requests can come from a variety of sources. If the change request is from a phone call, the best way to make the change is through the online purchase order pages. If the request is from another source, you can make the change online or run a batch process.

Note. If the installation includes PeopleSoft eSupplier Connection, the suppliers can enter their own purchase order acknowledgement (POA) changes directly into the PeopleSoft system. Upon buyer acceptance (online or automatic according to the business unit options flag), the Change Load process requests these online POAs in a similar way as EDX transactions.

Functions that generate change order requests that can be handled by batch processes include:

• EDX purchase order acknowledgments.

• Source requisitions to an existing purchase order.

• PeopleSoft eSupplier Connection online purchase order acknowledgements with a status of Buyer Accepted.

• PeopleSoft Order Management direct-shipped order changes.

• PeopleSoft Manufacturing subcontract changes.

• PeopleSoft Supply Planning planned order changes.

• Par location replenishment.

• Close Short Application Engine process (PO_CLSSHORT).

• PeopleSoft eProcurement change requests and change orders.

Change requests received using EDX or eSupplier Connection online acknowledgements are loaded into the Change Request table by the Change Load process. The other functions write directly to the Change Request table.

You can review EDX change requests or change requests from other functions in the system on the Approve Change Requests page. You approve the requests that you want processed by the Change Purchase Order process.

As part of processing purchase order changes from PeopleSoft eProcurement, the system also provides a message back to requesters if their changes cannot be updated for the purchase order. The message provides details at a specific line or schedule level and also indicates why the change could not be applied. The system uses the PO_CMMSGSEND batch program to process the messages.

During message processing if an error is detected during the PO Edit process and the source of the transaction is eProcurement (EPO), the system:

1. Updates purchase order change request transactions with error information.

2. Updates the PeopleSoft eProcurement change request (PV_CHNG_RST_DTL.PROCESS_FLG = E) with error information.

3. The PO Edit process will then:

   1. Issue a message to the requester using the PO_CMMSGSEND batch program.

      The message includes the requisition ID, line, and schedule, purchase order ID, line, and schedule, message description, and buyer name.

   2. Call the Requisition Update function to update the open quantity when the source of the change is a PeopleSoft eProcurement requisition and the change was an increase to quantity.

      This makes the open quantity available for future sourcing.

   3. When the source of the change is a PeopleSoft eProcurement requisition and the change was either a quantity decrease or increase to an amount only line or increase to a line that is distributed by amount, the process:

      - Backs out the requisition change by calling the Requisition Update function.

      - Budget checks the requisition and purchase order when commitment control is in use.

Note. When purchase order change requests do not have errors, the system calls the Common PO Change process (PO_CMCHNG) to update the purchase order transactions.

Error messages for change requests are available under the Error Messages tab on the Change Requests page. To access the page, select Purchasing, Purchase Orders, Manager Change Orders, Approve Change Requests, and click the Show Detail Entry link on the Change Requests page.

This diagram illustrates the Change Order process flow:

Purchase order change order process flow

Note. Also, the system supports change requests to the ATTN_TO (Attention To) field in the PO_LINE_DISTRIB table. This is the only PO_LINE_DISTRIB table field for which change requests are processed.

When you use online pages or when you run the Change Purchase Order process to update previously dispatched purchase orders, two events take place:

• The actual purchase order is updated.

  You make the change to the online purchase order manually or the Change Purchase Order process updates the purchase order when the change is not done manually.

• The change order tracking tables are updated with the change to the purchase order.

  When you change the purchase order online, the system automatically updates the change order tracking tables. When the change is not done online, the Change Purchase Order process inserts the change into the change order tracking tables.

When processing change orders in batch processing, the system uses the default reason code and reason comment value. This step is in the PO_CHNGLOAD process to set the change reason code to the value of the change source when the transactions being loaded are from the change sources listed in the Purchase Order Change Order Fields table. Change source descriptions are listed in the Reason Description Default Value column in this table:

Common Elements Used in This Chapter

Defining Change Order and Sequence Numbers

A change order number identifies the batch of changes that you submit to the vendor for a purchase order after its initial dispatch. The first time that you update a dispatched purchase order, the system displays Change Order 1 next to the purchase order number in the purchase order header. Each time you update the purchase order after dispatching a batch of changes to the vendor, the change order number is increased by one.

A change sequence number tracks the sequence of changes made within each purchase order at the header, line, and schedule levels. After the initial dispatch of a purchase order, a change sequence number is assigned to each change. These sequence numbers don't appear on the purchase order, but appear in the purchase order history.

Example

Here is an example of batch changes:

1. You dispatch a purchase order containing three lines.

2. You create a change on line 1.

   The header change order batch number is set to 1; the change sequence number for the first line is also 1.

   Note. A historical row is created to store original values for line 1. The header change order batch number is 0 and and change sequence number for the first line is 0.

3. After you dispatch the first batch of changes (change order batch number 1), you change lines 1 and 3.

   • The change order batch number is 2, because you are making changes after dispatching change order number 1.

   • Because this is the second time that you have changed line 1, its change sequence is 2.

   • Because you have changed line 3 for the first time, its change sequence is 1.

     Note. The system creates a historical row to store original values for line 3. The header change order batch number is 0 and the change sequence number for the first line is 0.

This diagram illustrates how the PO_CHNG_LINE table helps track the batch and sequence changes discussed in the example:

Purchase order change order batch and sequence tracking in PO_CHNG_LINE

Similar changes are stored in PO_CHNG_HDR, PO_CHNG_SHIP, and PO_CHNG_ADDR tables when changes are made to header, schedule, and one time address fields that are eligible for change order tracking.

See Also

Reviewing and Approving Change Order Requests

Creating Change Templates

Loading Change Orders Received Using EDXs or Supplier-Facing Online Acknowledgements (PeopleSoft eSupplier Connection)

Setting Up Purchase Order Change Templates

Use the purchase order change template to define which fields, if modified on a previously dispatched purchase order, will trigger a change order. When you configure the change template, you define the fields that you want to track at the various change order levels.

When triggering a change order online, the purchase order considers all fields defined on the purchase order change template.

The Change Purchase Order process looks at a subset of the fields on the change template. The fields that are considered by the Change Purchase Order process are discussed in the overview of the purchase order change order business process.

Note. The Purchase Order Change Order business process updates changed values on the purchase order, regardless of whether the fields exist on the purchase order change template. The purchase order change template helps to determine fields that are tracked and recorded in change order history tables, and does not determine the fields that can actually be changed on the purchase order.

See Also

Understanding the Purchase Order Change Order Business Process

Creating Change Templates

Enterprise PeopleTools PeopleBook: PeopleSoft Application Designer Developer's Guide

Identifying Purchase Order Change Order Fields

This table lists all of the fields as delivered by the system that are eligible for change order tracking that can be processed by the Change Purchase Order process. You can modify this list by updating the purchase order change template.

See Also

Creating Change Templates

Reviewing Processing Rules for the Change Purchase Order Process

In addition to ensuring that the changed fields are valid change order fields, the Change Purchase Order process follows these rules when generating change orders.

Status-Related Rules

These are the status-related rules for the Change Purchase Order process:

• Purchase orders in initial, pending, cancel, or canceled status are not eligible for change requests.

• You can request only that the purchase order status be changed to X (canceled).

  You cannot request that the purchase order status change to approved, completed, or dispatched. However, the process may change it to approved, pending approval, or open.

• The only change allowed against a schedule that is associated with a work order is Cancel.

• A change request cannot activate or close a line or schedule.

• The affected purchase order is set to In Process (PO_HDR.IN_PROCESS_FLG = Y), so no online activity can take place while the background change process is running.

• Purchase order status is set according to the rules that are defined on the PO Changes page.

  The system uses the PO_APPROVAL table primarily for workflow approvals.

  • APPROVAL_STATUS on the PO_APPROVAL table is set to A if PO_STATUS is A.

  • APPROVAL_STATUS on the PO_APPROVAL table is set to I if PO_STATUS is O or PA.

Validation Rules

These are the validation rules for the Change Purchase Order process:

• The change request process assumes that a valid date is passed to it.

• Fields are edited against the prompt or translate values that are specified in the record layout.

  Where a percentage edit table is specified in the record layout, the field is edited against the entire table.

• Validation against the Vendor and Item tables, to ensure that the UOM and ship to location are valid for that vendor or item, does not occur.

Cancellation Rules

These are the cancellation rules for the Change Purchase Order process:

• If you cancel a purchase order, all lines and schedules are canceled, with change records created for each line and schedule.

  If you cancel a purchase order line, all schedules are canceled, and the system creates change records for each schedule.

• If you try to create a change order to cancel a line or a schedule that has already been partially or fully received, the system rejects the transaction.

• The only active schedule for a line cannot be canceled.

• The only active line for a purchase order cannot be canceled.

Price Change Rules

These are the price change rules for the Change Purchase Order process:

• You cannot change a price to 0 unless the zero price indicator is set to Y.

• If you change the price, the system does not perform a price calculation.

• If you change the item ID, UOM, due date, purchase order quantity, or ship to location, the system recalculates the price and, if necessary, the currency is converted.

• The system only reprices changed schedules.

  For example, if pricing is done at the line-quantity level and a schedule-quantity change affects the price break, only that schedule receives the new price. The system does not force change requests for other schedules on the line.

Quantity Change Rules

These are the quality change rules for the Change Purchase Order process:

• The change order quantity becomes the updated quantity on the purchase order.

  The change order quantity is not the quantity by which the prior quantity is increased or decreased.

• If a unit of measure changes with the change request, the system adjusts the quantity appropriately.

Distribution and Schedule Adjustment Rules

These are the distribution and schedule adjustment rules for the Change Purchase Order process:

• If the schedule quantity or amount changes, the distributions are updated by prorating the revised schedule quantity or amount across all distributions, using the distribution percent.

  This is true regardless of whether the distributions have been received.

• If a distribution quantity or merchandise amount is updated, the distributions are rebalanced to ensure that they add up to the schedules.

Conversion Rate Rules

These are the conversion rate change rules for the Change Purchase Order process:

When you create a purchase order, the system updates this field if the conversion rate changes under these conditions:

• UOM or item ID changes.

• PeopleSoft Inventory is not installed and a change is made to the purchase order price or quantity.

• PeopleSoft Inventory is installed and you change the purchase order price or quantity, and the run control option Use Current UOM Conv Rate indicates that you are to use the new conversion rate.

Contract-Related Rules

If a contract is specified on the purchase order and a quantity changes, the system updates the contract release amounts and quantities. If a vendor minimum or maximum is not met or a currency conversion fails when pricing, the system issues an error message.

Tax-Related Rules

These are the tax-related rules for the Change Purchase Order process:

• The system updates the value-added tax (VAT) amounts and sales and use tax amounts as appropriate.

• If you change the ship to ID, it doesn't cause a change to the sales and use tax base ID.

BackOrder Rules

If a backorder is created for the purchase order through the supplier-facing acknowledgement component, the Change Purchase Order process automatically inserts the backorder schedule onto the purchase order and assigns the original schedule number to the BCKORD_ORG_SCHED field.

Also, for backorders created through the supplier portal, the system populates PO_LINE_SHIP_EC.BCKORD_ORG_SCHED with the original backorder schedule number.

See Also

Creating Change Orders from Approved Change Requests

Understanding the UOM Conversion Hierarchy

Generating Purchase Order Change Orders Online

To create a change order online, use the same pages that you use to update a purchase order, except that you'll be updating a dispatched purchase order. Fields that are eligible for change order tracking according to the purchase order change template are not available for entry on a dispatched purchase order. If you want to edit these fields, perform these actions:

• To make a header-level change, access the Maintain Purchase Order - Purchase Order page and click the Change Order button next to the PO Status field.

  The fields that trigger change order generation become available for entry.

• To make a line level change, select the Statuses tab on the Lines grid of the Maintain Purchase Order - Purchase Order page and click the Create Line Change button.

  Alternatively, access the Details for Line page and click the Chng Line button. The fields that trigger line-level change order generation become available for entry.

• To make a schedule-level change, click the Create Schedule Change button on the Statuses tab from the Maintain Purchase Order - Schedules page.

  To access this page, click the Schedule button from the Details tab of the Lines grid on the Maintain Purchase Order - Purchase Order page. The fields that trigger change order generation become available for entry.

• Adding a line automatically creates a change order for the line and new schedules are added.

• If you change the quantity on a purchase order line, and only one schedule exists, the system automatically creates a change order for the schedule.

  You do not have to click the Create Line Change button to make changes to the purchase order line quantity. The line quantity serves as a work field on the purchase order, so changes to its value are not tracked as changes. However, the system creates a schedule-level change order.

After you create a change order online, dispatch it as you would a regular purchase order.

When creating change orders using the online purchase order pages, if you attempt to cancel a line or a schedule that has been received (even partially), the system adjusts the quantity of the line or schedule and creates a change order.

For example, if the line quantity is 5, and two lines or schedules have been received, the line quantity becomes the received quantity, or 2 in this example. When the system transmits the change order to the vendor, the vendor sees that the quantity on the cancellation equals the quantity that he has already shipped, and he can cancel the remainder.

Note. When a purchase order has an authored contract document associated with it, certain changes made to the purchase order could affect the authored document. You should contact the contract specialist or the buyer in case they need to update the document.

See Also

Creating Purchase Order Headers

Creating Purchase Order Lines

Creating Purchase Order Schedules

Dispatching and Printing Purchase Orders

Creating Change Templates

Loading Change Orders Received Using EDXs or Supplier-Facing Online Acknowledgements (PeopleSoft eSupplier Connection)

This section discusses how to run the Change Load process.

The Change Load process loads changes to purchase orders received using EDX or online acknowledgements into the Change Request table. You can review and approve these change requests on the Change Ord Rqsts page.

See Also

Identifying Purchase Order Change Order Fields

Reviewing and Approving Change Order Requests

Page Used to Load Change Orders Received Using EDXs or Supplier-Facing Online Acknowledgements (PeopleSoft eSupplier Connection)

Running the Change Load Process

Access the Change Load page (Purchasing, Purchase Orders, Manage Change Orders, Load Change Requests, Change Load).

See Also

Creating Change Map Templates

Using the Purchase Order and Purchase Order Change Order Acknowledgement EIP

This section provides an overview of the Purchase Order and Purchase Order Change Order Acknowledgement EIP and discusses how to use the Purchase Order and Purchase Order Change Order Acknowledgement EIP.

Understanding the Purchase Order and Purchase Order Change Order Acknowledgement EIP

The Purchase Order Acknowledgement and Purchase Order Change Order Acknowledgement EIP processes service operations that contain purchase order acknowledgements and change order acknowledgements from vendors.

This asynchronous batch subscribe EIP also supports flat-file processing for electronic data interchange (EDI) transactions X.12 855 and 860.

Run the Change Load process (PO_CHNGLOAD) to move the data from staging tables to application tables.

Pages Used to Use the Purchase Order and Purchase Order Change Order Acknowledgement EIP

Using the Purchase Order and Purchase Order Change Order Acknowledgement EIP

Oracle 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 and Purchase Order Change Order Acknowledgement EIP, you must:

1. Set up the service operation within PeopleSoft Integration Broker and Enterprise Components:

   Use the information in the following table and refer to the setup instructions in the PeopleSoft Enterprise 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_ORDER_ACKNOWLEDGEMENT	Inbound Asynchronous	PurchaseOderAcknowledgement	No	third-party system EDI transactions X.12 855 and 860.

2. Run the Change Load process (PO_CHNGLOAD) to move the data from staging tables to application tables.

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

Understanding Electronic Data Interchange

Enterprise PeopleTools PeopleBook: Integration Broker

Using the Purchase Order Close Short Workbench

This section provides an overview of the Close Short job and discusses how to:

• Search for purchase orders to close short.

• Use the PO Close Short Workbench.

• Define Close Short job request options.

Understanding the Close Short Job

The Close Short job enables you to close short both stockless and nonstockless line items on a purchase order. When you run the Close Short job, the system runs both the PO_CLSSHORT AE process and the PO_POCHNG AE process and updates the purchase orders to reflect the close short processing. This is different than when you run the Close Short process by itself from the PO receiving menu, which creates the batch purchase orders change requests only and requires that you run the Process Change Orders program afterward.

Note. You can also initiate the Close Short process at the time of receipt. The Close Short AE process (PO_CLSSHORT) is called by the PO_RECVPUSH process when the receipt header Run Close Short check box is selected and at least one of the receipt lines has the Close Short field checked.

When you run the Close Short process from the Run Control page, the system processes all purchase orders for the selected business unit.

Note. The PO_RECVPUSH process can initiate the PO_CLSSHORT process, but the PO_CLSSHORT process cannot initiate the PO_RECVPUSH process.

During the Close Short process, the system:

• Checks the receipt line Close Short setting (RECV_LN_SHIP.CLOSE_SHORT_FLG) for a value of selected instead of checking the purchase order line stockless setting as it does in the SQR process.

• Creates purchase order change order transactions to set the purchase order schedule quantity that is equal to the total receipt quantity for the purchase order schedule when the Close Short check box is selected on the corresponding receipt line.

• Checks for purchase orders that have had some receiving activity and if a purchase order line is not referenced on any receipt and the Close Short field is selected on the purchase order line, a purchase order line cancel transaction is created.

• Creates a purchase order cancel transaction when purchase orders have had some receiving activity and a purchase order line is not referenced on any receipt, and the Close Short check box is selected on the purchase order line.

The system can also call the Close Short process from the Receipt Push process that is submitted when you save the receipt. This occur only if the RUN_CLOSE_SHORT check box is selected on the receipt header. To process the purchase orders, the system:

1. Processes purchase orders only that are referenced on the current receipt.

2. Creates purchase order change order transactions to set the purchase order schedule quantity equal to the total receipt quantity, if any, when the purchase order schedule is referenced on one of the current receipt's lines and the Close Short field is selected on the corresponding receipt line.

3. Does no further processing.

   Generally, all other purchase order lines that are not referenced on the current receipt are automatically processed the next time the Close Short process is triggered from the Run Control page for the relevant purchase order business unit.

Note. The system uses the PO Change batch process to apply the quantity change and cancel transactions for the purchase order.

Pages Used with the Purchase Order Close Short Workbench

Searching for Purchase Orders to Close Short

Access the PO Close Short Workbench - Purchase Orders page (Purchasing, Manage Change Orders, PO Close Short Workbench).

You can define a single purchase order or a list of purchase orders that are eligible for closing short. Enter the search parameters and click the Search button to retrieve the purchase orders. The system issues an error message if you perform the search without entering search parameters. You can search for eligible purchase orders based on a variety of search criteria, such as activity dates, vendor ID and item IDs, and buyers.

The number of returned rows from the search depends on the value in the Close Short Max Rows field on the Installation Options page. If search results exceed that field value, the system displays an error message. You will have to change or add search criteria to narrow the results. If the Close Short Max Rows field value is zero, the system does not set a limit and displays the rows 6 or 100 at a time and enables you to navigate from group to group.

When you click the Search button, the system displays the results in the PO Close Short Worklist grid. Search results are appended to any existing rows in the worklist. The system also saves both the search results and search criteria.

Using the PO Close Short Workbench

Access the PO Close Short Workbench - Purchase Orders page (Purchasing, Purchase Orders, Manage Change Orders, PO Close Short Workbench).

The Close Short Workbench provides a way to review purchase orders and determine whether outstanding purchase order lines should be set to close short. Using PO Close Short Workbench, you can run both the PO_CLSSHORT AE process and the PO_POCHNG AE process so that the purchase order is updated to reflect the Close Short processing.

The workbench page is divided into two sections. The top portion enables you to define search criteria for locating the purchase order schedules. The lower portion is a grid of the returned rows from the search. Each returned row contains a combination of purchase order header, line, and schedule information for your review and analysis.

Search Criteria

Click the Expand button for Search Criteria section to view the search criteria used to search for purchase orders that are eligible to be closed short. You can for example search for orders based on a specific purchase order or a range of orders, vendor IDs, due date, or contract ID.

Details

Use the Details tab to view line and schedule information for selected purchase orders.

More Details

Use the More Details tab to view additional purchase order details.

Defining Close Short Process Request Options

Access the Process Request Options page (click the Submit Close Short Processing button on the PO Close Short Workbench - Purchase Orders page).

You must either have specific authority or belong to the permission list to run this job. After you enter the required information, click the OK button. The system submits the Close Short Job to the process scheduler. The Close Short Job consists of the PO Close Short process and the PO Change Order process.

Reviewing and Approving Change Order Requests

This section provides an overview of the change request tables and discusses how to:

• Select change order requests to review and approve.

• Review and approve change order requests.

• Review and approve change request details.

Understanding the Change Request Tables

The change request tables are used for background processing. To load data into these tables, use one of these business processes:

• EDX change order acknowledgments loaded by the Change Load process.

• Source requisitions to an existing purchase order.

• PeopleSoft Order Management direct-shipped order changes.

• PeopleSoft Manufacturing subcontract changes.

• PeopleSoft Supply Planning planned order changes.

• Par location replenishment

• Close Short process.

• PeopleSoft eProcurement change requests and change orders.

• PeopleSoft eSupplier Connection online POA changes loaded by the Change Load process.

The Change Request is divided into two tables:

• Change Request.

  The key fields on the Change Request table are Process Instance, Business Unit, Purchase Order ID, Change Source, and Date/Time.

• Change Request Detail.

  This is a child to the Change Request table and contains additional key fields such as Line Number, Schedule Number, and Field name that are to be changed.

See Also

Replenishing Par Locations

Understanding PeopleSoft Supply Chain Management Enterprise Integration Points

Updating Direct Shipment Information

Changing Requisitions and Using Change Requests

Pages Used to Review and Approve Change Order Requests

Selecting Change Order Requests to Review and Approve

Access the Selection Criteria page (Purchasing, Purchase Orders, Manage Change Orders, Approve Change Requests).

Reviewing and Approving Change Requests

Access the Approve Change Requests page (click the OK button on the Selection Criteria page).

You can use this page and the Change Request page to manage approvals for change requests. Values you select on this page

Change Header

Select the Change Header tab.

Change Reason

Select the Change Reason tab.

See Also

Creating Change Orders from Approved Change Requests

Defining Change Order and Sequence Numbers

Viewing and Approving Change Request Details

Access the Change Requests page (click the Show Detail Entry link on the Change Ord Rqsts page).

This page displays all change requests for a purchase order with the same source and change time.

Change Values

Select the Change Values tab.

You can also use this tab to approve or deny the approval of all or individual change requests.

Requisition Details

Select the Requisition Details tab.

When the purchase order is associated to a requisition, this tab provides the requisition ID, line, schedule, and requester. Click the Requester link to access the Change Order Requester Detail page. This page provides information about the purchase order requester.

Error Messages

Select the Error Messages tab.

Deny Reason(s)

Select the Deny Reason(s) tab.

When the page initially appears, and contains requests that require deny reasons, the cursor is positioned on the Reason Code field for the first row that needs a deny reason. The Copy Previous Reason check box is selected as the default value for all rows after the first row that were set to Denied as part of the Deny All processing.

If the change header is set to a Denied status, the system also sets all lines for the header with a change process status of Initialize, Error, or Recycle to the Denied status.

For each detail row with an approval status of Denied and when the source is EPO, the system sends a notification to the requester of the corresponding requisition. To set up the notification:

• Establish the notification (EOEN Interface) instance.

• Set the EOEN business unit properties.

• Create the EOEN context record (CHNG_EWN_CTX).

  This record contains the requisition ID, line, and schedule, the purchase order ID, line, and schedule, buyer name, requester ID, and message description.

• Create the email or worklist entries for the notification.

• Set up a URL for the message.

• Insert a row into the REQ_CHNG_REASON table for each unique deny reason and reason description combination.

• Update the REASON_SEQ field on the PV_CHNG_RST_DTL record that is associated with the purchase order change detail (CHNG_RQST_DTL) to map to the new REQ_CHNG_REASON that contains the deny reason.

Creating Change Orders from Approved Change Requests

This section discusses how to run the Change Purchase Order process.

The Change Purchase Order process creates change orders from approved change requests in the Change Request tables.

Page Used to Create Change Orders from Approved Change Requests

Running the Change Purchase Order Process

Access the Change Purchase Orders page (Purchasing, Purchase Orders, Manage Change Orders, Process Change Orders).

Chg Request Selection Criteria

PO Update Options

Purging Change Request Tables

This section provides an overview of the Purge Change Request process (PO_POCHGPRG) and discusses how to run the PO_POCHGPRG process.

Understanding the Purge Change Request Process

The Purge Change Request process (PO_POCHGPRG) enables you to purge completed and error rows from these Change Request tables:

• PS_CHNG_RQST_DTL

• PS_CHNG_RQST

• PS_CHNG_RQST_MSGLG

Page Used to Purge Change Request Tables

Running the PO_POCHGPRG Process

Access the Purge Change Requests page (Purchasing, Purchase Orders, Manage Change Orders, Purge Change Requests).

Viewing Purchase Order Change History

The PeopleSoft Purchasing system maintains a history of changes made to purchase orders. There are two ways to view purchase order changes to tracked fields that are identified in the purchase order change template. You can first view history by change order batch using the Review Change History menu. The second way is to view all tracked changes for a purchase order using the Review Change Order menu. The PO Change Order process updates purchase orders, but does not track change orders, if the purchase order has never been dispatched.

This section lists the pages that you use to view purchase order change history.

Pages Used to View Change Order History