This chapter provides an overview of sales order and quotation enterprise integration points (EIPs) and discusses how to:
Run Electronic Commerce for inbound sales order and quote EIPs.
Publish outbound sales order and quote EIPs.
Use Sales Order Change and Sales Order Change Notice.
Use request price check.
PeopleSoft Order Management is delivered with many enterprise integration points (EIPs) to send and receive sales order and quote data from a third-party system or another PeopleSoft application. These EIPs are service operations within PeopleSoft Integration Broker.
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 PeopleSoft CRM. If you are using chunking for outbound service operations, the handlers must be active on the Handlers page.
Use the information in the following table and refer to the setup instructions in the PeopleSoft Supply Chain Management Integrations 9.1 PeopleBook, "Implementing Integrations," Setting Up Service Operations.
Service Operation |
Direction and Type |
Handlers |
Chunking Available? |
Integrates With |
PRODUCT_PRICELIST_SYNC |
Outbound Asynchronous |
NA |
No |
Electronic data interchange (EDI), Third-party source |
SALES_CRM_ORDER_CHANGE_LOAD |
Inbound Asynchronous |
SalesCRMOrderChangeLoad |
No |
Customer relationship management (CRM) |
SALES_CRM_ORDER_LOAD |
Inbound Asynchronous |
SalesCRMOrderLoad |
No |
CRM |
SALES_CRM_QUOTE_LOAD |
Inbound Asynchronous |
SalesCRMQuoteLoad |
No |
CRM |
SALES_ORDER_ACKNOWLEDGEMENT (855) EDI_TXN_855 |
Outbound Asynchronous |
ROUTERSENDHDLR |
Yes |
CRM, EDI (X12 standard format), Third-party source |
SALES_ORDER_CHANGE_LOAD (860) |
Inbound Asynchronous |
SalesOrderChangeLoad |
No |
EDI, Third-party source |
SALES_ORDER_CHANGE_NOTICE (865) |
Outbound Asynchronous |
ROUTERSENDHDLR |
Yes |
CRM, EDI, Third-party source |
SALES_ORDER_LOAD (850) EDI_TXN_850 |
Inbound Asynchronous |
SalesOrderLoad |
No |
EDI (X12 standard format), Third-party source |
SALES_ORDER_STATUS |
Outbound Asynchronous |
ROUTERSENDHDLR |
Yes |
CRM, EDI, Third-party source |
SALES_QUOTE_LOAD (840) EDI_TXN_840 |
Inbound Asynchronous |
SalesQuoteLoad |
No |
EDI (X12 standard format), Third-party source |
SALES_QUOTE_NOTICE (845) EDI_TXN_845 |
Outbound Asynchronous |
ROUTERSENDHDLR |
Yes |
CRM, EDI (X12 standard format), Third-party source |
These EIPs have two versions. Version 2 contains new attributes for this release.
Sales Quote Notice (845)
Sales Order Acknowledgement (855)
Sales Order Change Notice (865)
Integrating with PeopleSoft CRM and SCM Databases
If both PeopleSoft CRM and SCM are installed, use the Exclusions by Source Code page when running CRM Sales Order or CRM Sales Quote to exclude calculating freight, sales tax, price adjustments, or value-added tax (VAT) for sales orders or quotes when Order Completion (OM_BACKGRND) is run. Otherwise, Order Completion (OM_BACKGRND) will calculate them again.
See Integrating with PeopleSoft CRM.
UPC and Universal Item IDs
The Universal product code (UPC) and Universal item identifiers can be received from the various EDI transactions and are stored on the sales order, buying agreement, and RMA. A customer's ordering preference is established at the customer level on the Sold To Options page. The new options UPC and Universal Item Identifier will be available in addition to the existing System and Customer Product Identifier options.
If you use the Universal Item ID option, you can assign any valid universal item ID type to that sold to customer to be used specifically for product entry. The Electronic Commerce (OM_EC) process transforms the universal item ID that is provided on a sales order/quote inbound EDI EIP into a corresponding system product ID and unit of measure by looking for a match with IDs of the type specified on the sold to customer. If you use the UPC option, Electric Commerce (OM_EC) will transform the UPC provided on the EIP into the corresponding system product ID. The system product ID, universal item ID, and UPC will be stored on the sales order line, and the universal item ID and UPC will be available on outbound EDI EIPs such as the sales order acknowledgement, quotation notice, Advanced shipping notice (ASN), and billing invoice.
Your customers can also send user-defined fields to be stored on the sales order and sent back with the oubound EDI EIP. If any errors occur, you can correct them after running Electric Commerce using the Header (cont.) page for the custom fields.
Inbound and Outbound Process Flow Diagrams
This diagram displays the process for inbound sales orders and quote EIPs.
Inbound process flow of sales order
This diagram displays the process flow for outbound sales orders and quote EIPs.
Outbound process flow of sales order
See Also
PeopleSoft Enterprise Supply Chain Management Integration 9.1 PeopleBook
Enterprise PeopleTools PeopleBook: Integration Broker
This section provides an overview of the Electronic Commerce process and discusses how to run Electronic Commerce.
The Electronic Commerce process (OM_EC) is part of the overall inbound electronic commerce flow. It validates the fields that are on the record of items that are loaded in the staging tables to ensure that the values are correct. The process performs these steps:
Edits the data, such as customer numbers and units of measure, to ensure that they are valid.
Converts the customer's product, UPC, or universal item ID or item number to a PeopleSoft product identifier when a PeopleSoft product identifier is not provided.
Assigns PeopleSoft order numbers.
Sets system defaults and status flags.
Validates data changes to ensure that they are valid.
Loads data into the production order tables (order staging data that has errors is not loaded into the production tables until the errors are corrected).
Important! If any data that is related to a specific document (order, order change, or request for quote) is in error, the complete document remains in the staging tables until all errors are corrected.
When the data is loaded into the production order tables, you must run additional processes to complete EDI/XML orders and to make them accessible by using the standard order entry pages.
See Understanding Order Entry Required Processing.
Note. If you are integrating with PeopleSoft CRM, use the Exclusions by Source Code page to exclude calculating freight, sales tax, price adjustments, or VAT for sales orders or quotes when you run Order Completion (OM_BACKGRND). Otherwise, Order Completion calculates them.
Note. If pricing should not be calculated, set the Price Protected flag accordingly.
These staging tables are used for processing inbound transactions:
Header (ORD_HEADER_EC).
Line (ORD_LINE_EC).
Schedule (ORD_SCHEDULE_EC).
Address (ORD_ADDR_EC).
Notes (ORD_NOTES_EC).
Configuration Options Header (ORD_OPT_HDR_EC).
Configuration Options Detail (ORD_OPT_DETL_EC).
User Defined Reference (ORD_CDATA_EC).
When errors occur after the Order Management Electronic Commerce process runs, the data remains in the order staging tables. You need to correct the errors by using the error correction pages.
For each of the staging tables, two types of pages are available. The first type displays the errors; the fields with errors are the only ones that are available for data entry. These tables have multiple pages that display the errors. The pages are Order Header, Order Line, and Order Schedule. The second type lists the errors and explains their nature.
Many editing errors occur when the business unit is incorrect. This is because many of the edits depend on setID; when the business unit is invalid, the system cannot derive a setID. Even though the data (other than business unit) appears correct, an error may occur because of an invalid business unit. Correcting the business unit often resolves other edit errors.
Note. When the Order Management business unit is incorrect for any inbound data, you must be correct it on the Electronic Commerce Header Errors - Order Header page. When you correct it there, all data that is associated with that document—lines, schedules, addresses, and so on—are automatically updated with the correct business unit value. If, for example, a document has 1000 order lines associated with it, each with an incorrect business unit, the incorrect business unit is corrected once at the header level.
The Error Summary page includes all the errors for a particular EIP control ID.
Page Name |
Definition Name |
Navigation |
Usage |
Electronic Commerce |
RUN_OM_EC |
Order Management, Electronic Commerce, Process Staged Orders/RFQs |
Run Electronic Commerce. Establish process parameters for inbound requests for quotations, sales orders, and sales order changes. |
SRC_CD_EXCLUSIONS |
Order Management, Electronic Commerce, Source Code Exclusions |
If you are integrating to PeopleSoft CRM, exclude calculating freight, price adjustments, sales tax, and VAT for sales orders or quotes when you run Order Completion (OM_BACKGRND). Otherwise, Order Completion calculates them again. If the installation includes PeopleSoft Contracts, you must define exclusions for the CA (contracts order) and RCA (replacement order from contracts order returns) for quotes and sales orders. PeopleSoft Contracts calculates freight, sales tax, VAT, and price. |
|
OMEC_HDR |
|
Correct Electronic Commerce errors that appear on the document header. |
|
Header (continued) |
OMEC_HDR2 |
|
Correct Electronic Commerce errors that appear on the document header. |
Header (continued) |
OMEC_HDR3 |
|
Correct Electronic Commerce errors that appear on the document header. |
Header (continued) |
OMEC_HDR4 |
|
Correct Electronic Commerce errors that appear on the document header for the customized fields. |
OMEC_HDR_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Header |
View the list of errors and their nature at the header level. |
|
OMEC_LIN |
|
Correct Electronic Commerce errors that appear on the document line. |
|
OMEC_LIN2 |
|
Correct Electronic Commerce errors that appear on the document line. |
|
OMEC_LIN3 |
|
Correct Electronic Commerce errors that appear on the document line. |
|
OMEC_LIN_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Line |
View the list of errors and their nature at the line level. |
|
OMEC_SCH |
|
Correct Electronic Commerce errors that appear on the document schedule. |
|
OMEC_SCH2 |
|
Correct Electronic Commerce errors that appear on the document schedule. |
|
OMEC_SCH3 |
|
Correct Electronic Commerce errors that appear on the document schedule. |
|
OMEC_SCH_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Schedule |
View the list of errors and their nature at the schedule level. |
|
OMEC_ADR |
|
Correct Electronic Commerce errors that appear in the document ship-to or sold-to override address. |
|
OMEC_ADR_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Address |
View the list of errors and the nature of the violations in the order address. |
|
OMEC_NOT |
|
Correct Electronic Commerce errors that appear in the document note. |
|
OMEC_NOT_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Note |
View the list of errors and their nature for order notes. |
|
OMEC_CDATA |
|
Correct Electronic Commerce errors that appear in the user-defined reference data. |
|
OMEC_CDATA_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, User Defined |
View the list of errors and their nature that are in the user-defined reference data. |
|
OMEC_OPH |
|
Correct Electronic Commerce errors that occur in configuration options at the header level. |
|
OMEC_OPH_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Option Header |
View the list of errors and their nature for configuration information at the header level. |
|
OMEC_OPD |
|
Correct Electronic Commerce errors that occur in configuration options at the detail level. |
|
OMEC_OPD_ERR |
Order Management, Electronic Commerce, Correct Staging Errors, Option Detail |
View the list of errors and their nature for configuration information at the detail level. |
|
OM_EIP_ORDERS |
Order Management, Electronic Commerce, Correct Order/RFQ Errors |
Access the individual error pages to make corrections. |
|
RUN_OM_EC_DEL |
Order Management, Electronic Commerce, Review Staging Details, Delete Staging Tables |
Clean up the staging tables after the order has been moved to the production order tables. |
Access the Electronic Commerce page (Order Management, Electronic Commerce, Process Staged Orders/RFQs).
Delete staging records |
Select to remove the data from the staging tables. |
Business Unit |
If you enter a specific business unit for inbound processing and the inbound staging data has an invalid business unit value, that data is not processed. |
Transaction Type |
Values for inbound EDI/XML transactions are: PO: Inbound Sales Order. POCHG: Sales Order Change. RFQ: Inbound Request for Quote. |
EIP Control ID |
Select to further define the processing run. |
Source Code |
Use to limit the transactions. For example, you could process data only from PeopleSoft CRM. |
Run Order Completion |
Select to run the Order Completion process (OM_BACKGRND). |
Run Hold Checking |
Select to run the Hold Checking process (OM_HOLD). |
Run Credit Checking |
Select to run the Credit Checking process (OM_CREDIT). |
Run Populate Demand |
Select to run the Demand Population process (OM_DEMAND). |
Run Reservations |
Select to run the Reservations process (INV_FUL_RSV). |
Set up the EMP_SERVLET process for the notifications to use with URL locations prior to running the process.
See Setting Up the URL Location for Notifications.
When processing large volumes of orders through to PeopleSoft Inventory, you can stream the various batch processes together by selecting from the post process options on the run control page. All data selected as part of the process will be evaluated in subsequent processing.
The application engine processes take advantage of features including parallel processing and set base processing that use temporary tables to reduce risk by date contention and deadlocks. To take full advantage of this, set up your runs to partition data. For example, for an Order Management business unit, you can process all orders coming from a specific source.
See Enterprise PeopleTools PeopleBook: PeopleSoft Application Engine
This section lists common elements and discusses how to :
Process outbound EIPs for order acknowledgements, sales order changes, and sales quote notices.
Process outbound EIPS for product price lists.
Process outbound EIPs for order and quote status.
See Also
Business Unit |
Enter a value to limit the EIPs to publish. |
Request ID |
Appears by default from the run control ID. You can change the value. |
Description |
Describe the outbound EIPs. |
Page Name |
Definition Name |
Navigation |
Usage |
IN_RUN_PUB_MSG |
SCM Integrations, Publish Outbound Message |
Initiate the outbound message publish process for outbound PeopleSoft SCM EIPs. |
|
OM_RUN_OUTBOUND_EC |
|
Enter processing options for the Sales Order Acknowledgement, Sales Order Change Notice, and Sales Quote Notice outbound EIPs. You can select processing options for only one EIP at a time. |
|
OM_RUN_PRODPRC_OUT |
Select Product Price List on the Publish Outbound Message page to enable the Product Price List link. Click the Product Price Link on the Publish Outbound Message page. |
Select processing criteria for the price sales catalog. |
|
OM_RUN_OUTORD_STAT |
Click the Sales Order/Quote Status link on the Publish Outbound Message page. |
Enter processing options for the Sales Order/Quote Status EIP. |
Access the Order Acknowledgement Message Selection Criteria, Sales Order Change Notice, or Sales Quote Notice Message Selection Criteria page (click the Sales Order Acknowledgement link, Sales Order Change Notice link or Sales Quote Notice link on the Publish Outbound Message page).
Note. The page is the same for the order acknowledgements, order change notices, and quote notices.
Select Processing Parameters
Source Code |
Further define processing options for the EIPs. |
Outbound Messages Selected
You can select multiple EIPs to process.
Access the Product Price List Message Selection Criteria page (select Product Price List on the Publish Outbound Message page to enable the Product Price List link, and click the Product Price Link on the Publish Outbound Message page).
The following process describes how the OM_PPRC_OUT application engine determines the products and prices to include in the product price list using the retail catalog.
The OM_PPRC_OUT application engine first determines what sold-to customer contacts are set up to receive the product price list information by EDI/XML from the Contact Additional Info page.
If a customer or customer group is entered on the Product Price List Message Selection page, the program sends only product price list information to the specified contact for the customer or sold-to customers belonging to the specified pricing customer group that is set up on the Customer Group Table page. For each of these customers, the program inserts any products that are attached to the retail catalog into a temporary table. If a particular customer is not attached to any catalog, or if no catalog number is entered in the selection options that are on the Product Price List Message Selection page:
The program attempts to retrieve products from the retail catalog where the customer's pricing customer group is attached to the catalog.
If no customer group is attached to the catalog, the program attempts to retrieve products from the Price List tables.
The program looks for any records that exist on the Price List tables for the sold-to customer being processed and inserts those products into a temporary table. If a price list ID is entered as optional criteria, the program selects only products for that price list ID.
If no price list records are found for the sold-to customer being processed, the program looks at the Price List tables to determine if any price lists are attached to the sold-to customer's pricing customer group and inserts those products into a temporary table. If a price list ID is entered as optional criteria, the program selects only products for that price list ID.
Finally, if a particular customer has no catalogs or price lists, the program retrieves all active products from the PROD_ITEM table. If a product group is entered as optional criteria, the program selects only products that are for the specified product group.
When the program has a list of products for each customer, it retrieves prices for each of the products.
The system uses the lowest price on the most recent start date on or before today's date.
The program first determines whether price lists are set up for the sold-to customer and product combination that is being processed and inserts the lowest list price, start date, unit of measure, and so on, into a temporary table. Again, if a price list ID is entered as optional criteria, the program look only at prices from the specified price list ID.
If no price lists are found for the customer and product ID combination, the program then determines whether price lists are set up for the customer's pricing customer group and product that is being processed. The system inserts the lowest list price, start date, unit of measure, and so on into a temporary table. Again, if a price list ID is entered as optional criteria, the program looks only at prices from the specified price list ID.
If no price lists are found for the customer and product ID or customer group and product ID combination, the program retrieves the prices from the PROD_PRICE table and inserts them into a temporary table. If an inventory business unit is entered as optional criteria, the program loads PROD_PRICE records only for the specified inventory business unit.
Selection Type
All Customers |
Select to have the process run for all of the customers. |
Specific Customer |
If you select this option, enter the customer name. |
Specific Customer Group |
If you select this option, enter the customer group. |
Selection Options
You can select these options only if you are running the process for all customers.
None |
No further selection options are available. |
Inventory Business Unit |
If you select this option, enter the inventory unit. |
Catalog |
If you select this option, enter the catalog number. |
Price List |
If you select this option, enter the price list ID. |
Product Group |
If you select this option, enter the inventory unit. |
Access the Order/Quote Status Message Selection Criteria page (click the Sales Order/Quote Status link on the Publish Outbound Message page).
Select Processing Parameters
Access to limit the processing parameters for the order or quote status EIP.
Status |
Select any of the order statuses for the EIP. |
This section provides an overview of Sales Order Change and Sales Order Change Notice and discusses how to modify order change records.
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:
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. |
Page Name |
Definition Name |
Navigation |
Usage |
OMEC_ORDCHG_FLD |
Order Management, Electronic Commerce, Identify Order Changes |
Modify the list of records that can be changed in Sales Order Change. |
Access the Order Change Maintenance page (Order Management, Electronic Commerce, Identify Order Changes).
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. |
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.
This section provides an overview of the Request Price Check process, lists common elements, and discusses how to run Request Price Check.
The Request Price Check process enables you to validate a customer's net price, which is included in the EDI file, against the system-calculated net price.
When processing an EDI/XML order, you should run the Request Price Check process (OM_AUDIT) along with the other required background jobs. Run them in this order:
OM Electronic Commerce (OM_EC).
Order Completion (OM_BACKGRND).
Request Price Check (OMAUDIT).
Automatic Credit Check (OM_CREDIT).
Automatic Hold Check (OM_HOLD).
Populate Demand (OM_DEMAND).
Request Price Check Process Procedure
Perform these steps to use Request Price Check to validate the customer's net price that is sent by EDI against the system-calculated net price.
Run the Request Price Check process.
Use the Price Hold Release page to review the customer and system-calculated net unit price.
Change any of the prices that are on the page and accept the customer's price in lieu of the system-calculated price. If you want to accept the customer's price, change the List Price and Net Unit Price fields to match the customer's price. When you save the page, the system sets the Price Protected flag at the schedule level to Y so that Order Pricing does not recalculate the price. The order schedule is also updated with the selected price. If the price validation is performed on an order change, the order acknowledgement is not sent to the customer until the price discrepancy is reviewed and the order is released from hold. The order acknowledgement includes the adjusted net unit price.
Understanding How the System Performs Price Checking for EDI/XML Orders
The data that the customer sends in for these fields triggers the system to perform the comparison against the system-calculated prices and discounts.
CUST_PO_PRICE (the customer's price before discounts).
CUST_PO_PRC_BASE (the customer's price before discounts in the base currency).
CUST_NET_PRICE (the customer's price after discounts).
CUST_NET_PRC_BASE (the customer's net price in the base currency).
CUST_BILL_BACK_ALL (the customer's bill backs).
CUST_BBACK_ALL_BSE (the customer's bill back in the base currency).
CUST_OFF_INV_BASE (the customer's off-invoice discounts in the base currency).
CUST_OFF_INV_DISC (the customer's off invoice discounts).
The Automatic Request Price Check process selects order schedules that do not have a blank net unit price and the Price Protected flag is set to NO. It compares the customer's net unit price against the system-calculated net unit price. On the inbound purchase order, the customer's net unit price can include promotional discounts such as off-invoice or bill-back discounts.
In situations in which the customer's inbound purchase order includes promotional discounts, the off-invoice and bill-back discounts are summed in the ORD_PRICE_ADJST table to get a total discount amount on the inbound purchase order.
This example illustrates how the customer's net unit price and system-price are calculated for an inbound purchase order with the following criteria:
List Price of 100 USD for 1 case.
Off-invoice discount of 10 USD per case.
Bill-back allowance of 10 USD per case. (The bill-back adjustment is an accrued adjustment.)
The customer's net unit price is 90 USD.
The system-calculated price is 100 USD.
To validate these fields, the system calculates the price by using the pricing structure (price rules, price lists, and so on) that are set up in PeopleSoft Enterprise Pricer. The system calculates the price for each order line or schedule based on the pricing structure and then compares the calculated values against the values that are sent by way of the EDI/XML Inbound Purchase Order.
The validation is as follows, assuming that the price discrepancy hold is set up on the Order Management Business Unit Hold Processing page.
If the customer's list price does not equal the system-calculated price, the Request Price Check validation routine checks the customer's pricing and promotion fields in this order:
Net unit price
Bill-back allowances
Off-invoice discount
List price
If the customer's bill-back allowance amount is not zero, the validation routine should check whether the system calculates a bill-back adjustment for the same amount.
If the bill-back allowance does not match the customer's bill-back allowance, the validation routine places the order on hold.
If the bill-back allowance does match the system-calculated bill-back allowance, the validation routine checks the off-invoice discount.
If the off-invoice discount does not match, the validation routine places the order on hold.
If the off-invoice discount does match, the validation routine checks the list price.
If the list price does not match, the validation routine places the order on hold.
Page Name |
Definition Name |
Navigation |
Usage |
HOLD_CD |
Financials/Supply Chain, Product Related, Order Management Foundation, Hold Codes |
Establish a price discrepancy hold code. |
|
BUS_UNIT_TBL_OM2 |
|
Assign a price discrepancy hold code for the business unit |
|
RUN_OM_AUDIT |
Order Management, Quotes and Orders, Update Price, Request Price Check-EDI/XML |
Validate the customer's net price against the system-calculated net price for orders that are processed by EDI/XML. |
|
Price Hold Release: System Information, Customer Prices |
OM_PRC_HOLD |
Order Management, Quotes and Orders, Update Price, Update Price Discrepancies |
View and update the customer's and the system-calculated net unit price. |
Access the Price Hold Release page (Order Management, Quotes and Orders, Update Price, Update Price Discrepancies).
System Information Tab
Order |
Select the order for which you want to change the price. When you select an order, additional fields become available to edit. |
List Price (Base) and Net Unit Price (Base) |
View the system-calculated prices and override them as necessary. Any changes are passed to the sales order. |
Customer Prices Tab
The prices that are on this page are the customer's purchase order prices that differ from the system-calculated prices. You can override them as necessary. Any changes are passed to the sales order.
PO Price (Base) |
Displays the customer's price before discounts. |
Net Price (Base) |
Displays the customer's price after discounts. |
Bill Back (Base) |
Displays the bill-back discount for the line that the customer takes as a credit or payment. |
Off Invoice (Base) |
Displays the off-invoice discount for the line that the customer takes off the net price. |