1. Release Readiness Guide
  2. Feature Summary

1 Feature Summary

The enhancement below is included in this update.

Column Definitions

SMALL SCALE: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
LARGER SCALE: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
CUSTOMER ACTION REQUIRED: Indicates if you must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.


FEATURE


SCALE

CUSTOMER
ACTION REQUIRED
OPERATIONAL ENHANCEMENT
Duplicate Order and Item Check larger

none
Inbound SOAP Web Service Version can be no higher than 19.9 larger

Make sure that message version specified for inbound XML messages is not higher than 19.9

Duplicate Order and Item Check

Note:

With this update, Order Broker now always checks for a duplicate order and line before creating the order in the database or returning the SubmitOrder response message. This enhanced duplicate checking catches multiple requests if the originating system sends more than one request at the same time. Duplicate order lines are not created; however, a record is created in a new duplicate order item table for tracking purposes.

SubmitOrder error response: The 2040 error response returned when a submitted order and line number is a duplicate of an existing order line now indicates Validation Error - Duplicate order/line is not allowed for system_cd: [SYSTEM]. duplicate_request_id: 123456, line_item_no:3 where SYSTEM is the system code, 123456 is the existing request ID, and 3 is the existing order line number.

Note:

The Routing Engine does not evaluate any other information on the order, such as product code, quantity, or customer name and address, when checking for duplicates. The check takes place only during the SubmitOrder process, and only for duplicate orders submitted by the same system.

The duplicate order check applies regardless of the version specified in the SubmitOrder message.

New tables: The following new tables are used for the duplicate order check:

  • XOM_ITEM_DUPLICATE: Contains a record for each order line that was not created in Order Broker because a duplicate was found. Duplicate records are retained for 180 days for troubleshooting by Oracle Support.

  • XOM_ITEM_DUP_CHECK: Used temporarily only for the duplicate checking process before order creation.

The Daily Cleanup job purges records from these new tables:

  • XOM_ITEM_DUPLICATE: Records older than 180 days are purged.

  • XOM_ITEM_DUP_CHECK: Records older than 2 days are purged.

Removed setting from System screen: The Use Duplicate Order Checking flag at the Orders tab of the System screen is no longer used, and has been removed.

Note:

Duplicate checking does not take place for drop ship purchase orders.

Inbound SOAP Web Service Version can be no higher than 19.9

With this update, the version tag of each inbound SOAP web service request message should be set to no higher than 19.9. The message version number will no longer be tied to the Order Broker application version number.

Important:

The version tag must include a decimal; for example, 19.0 is valid, but 19 is invalid.