Using Sales Order Change (860) and Sales Order Change Notice (865)

This topic provides an overview of Sales Order Change and Sales Order Change Notice and discusses how to modify order change records.

Page Name

Definition Name

Usage

Order Change Maintenance Page

OMEC_ORDCHG_FLD

Modify the list of records that can be changed in Sales Order Change.

For EDI/XML orders, changes can occur as they do for orders that are entered online. Customers may want to change carriers, increase an order quantity, and so on after they have sent the inbound Sales Order (850). Sales Order Change (860) and Sales Order Change Notice (865) enable you to accept, process, and send acknowledgements to the customers for changes that are made to inbound sales orders. You can also use this process to send an acknowledgement to a customer if you changed an EDI order online.

When the acknowledgement is sent, information for the entire order is sent and requested field changes are confirmed as accepted or rejected.

Sales Order Change Notice (865) includes these statuses:

Term

Definition

AC1 (accept with no exceptions)

All of the requested changes are made.

AC2 (accept with exceptions)

The changes are accepted, but not all the changes are applied to the order, either because the requested field is not eligible for change, or the requested field cannot be changed due to the order's status in the fulfillment process.

RJ1 (reject)

The original inbound sales order does not exist in the system.

RJ2 (reject)

The request is rejected because the original inbound sales order is closed, canceled, or actually a quote.

Use the Order Change Maintenance page (OMEC_ORDCHG_FLD) to modify the list of records that can be changed in Sales Order Change.

Navigation:

Order Management > Electronic Commerce > Identify Order Changes

Field or Control

Description

Inventory Edit

If this check box is selected, the filed change must be validated against PeopleSoft Inventory.

Work Field

Used by PeopleCode to determine whether the change can still be made in PeopleSoft Inventory. The Electronic Commerce process (OM_EC) returns a value of Yes if the field can be changed, and a value of No if the field cannot be changed. For example, if the change request is to change the carrier, the program checks PeopleSoft Inventory to verify that the change can still be made. If the order line is already shipped, Electronic Commerce returns a value of No.

Field or Control

Description

Propagation Rule

Shows whether the change requests are made to the line, schedule, or both. For example, if the line has only one schedule, a change request to change the carrier on the order line is propagated down to the schedule. If more than one schedule exists, then the change is not propagated.

Alternate Field

Enter if the field name is different at the corresponding level.

Invoice Edit

If this check box is selected, the field change is validated at the schedule level if the schedule is invoiced.

Configured Kit Edit

If PRODKIT_EDIT is selected in the database, then the field can be changed.

Note: The system already defined the fields that can be changed in the sales order change. If you want to modify the list of records, use the Order Change Maintenance page. You also need to add the new fields on the SALES_ORDER_CHANGE_LOAD message to permit the change.