Running Electronic Commerce for Inbound Sales Orders and Quote EIPs

This topic provides an overview of the Electronic Commerce process and discusses how to run Electronic Commerce.

Page Name	Definition Name	Usage
Electronic Commerce Page	RUN_OM_EC	Run Electronic Commerce. Establish process parameters for inbound requests for quotations, sales orders, and sales order changes.
Exclusions by Source Code	SRC_CD_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.
Header	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.
Header Errors	OMEC_HDR_ERR	View the list of errors and their nature at the header level.
Line	OMEC_LIN	Correct Electronic Commerce errors that appear on the document line.
Line (continued)	OMEC_LIN2	Correct Electronic Commerce errors that appear on the document line.
Line (continued)	OMEC_LIN3	Correct Electronic Commerce errors that appear on the document line.
Line Errors	OMEC_LIN_ERR	View the list of errors and their nature at the line level.
Schedule	OMEC_SCH	Correct Electronic Commerce errors that appear on the document schedule.
Schedule (continued)	OMEC_SCH2	Correct Electronic Commerce errors that appear on the document schedule.
Schedule (continued)	OMEC_SCH3	Correct Electronic Commerce errors that appear on the document schedule.
Schedule Errors	OMEC_SCH_ERR	View the list of errors and their nature at the schedule level.
Address	OMEC_ADR	Correct Electronic Commerce errors that appear in the document ship-to or sold-to override address.
Address Errors	OMEC_ADR_ERR	View the list of errors and the nature of the violations in the order address.
Note	OMEC_NOT	Correct Electronic Commerce errors that appear in the document note.
Note Errors	OMEC_NOT_ERR	View the list of errors and their nature for order notes.
User Defined Reference	OMEC_CDATA	Correct Electronic Commerce errors that appear in the user-defined reference data.
User Defined Reference Errors	OMEC_CDATA_ERR	View the list of errors and their nature that are in the user-defined reference data.
Option Header	OMEC_OPH	Correct Electronic Commerce errors that occur in configuration options at the header level.
Option Header Errors	OMEC_OPH_ERR	View the list of errors and their nature for configuration information at the header level.
Option Detail	OMEC_OPD	Correct Electronic Commerce errors that occur in configuration options at the detail level.
Option Detail Errors	OMEC_OPD_ERR	View the list of errors and their nature for configuration information at the detail level.
Error Summary	OM_EIP_ORDERS	Access the individual error pages to make corrections.
Delete Electronic Commerce	RUN_OM_EC_DEL	Clean up the staging tables after the order has been moved to the production order tables.

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.

Use the Electronic Commerce page (RUN_OM_EC) to run Electronic Commerce.

Establish process parameters for inbound requests for quotations, sales orders, and sales order changes.

Navigation:

Order Management > Electronic Commerce > Process Staged Orders and RFQs

Field or Control	Description
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 PeopleTools PeopleBook: PeopleSoft Application Engine

Running Electronic Commerce for Inbound Sales Orders and Quote EIPs

Pages Used to Run Electronic Commerce for Inbound Sales Orders and Quote EIPs

Understanding the Electronic Commerce Process

Electronic Commerce Page