1 Feature Summary

The enhancements below are included in this release.

Column Definitions

Small: 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: 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
System Management Enhancements
Audit Changes to Web Service Authorization and Clients		Larger	None
Pre-Order/Active PO Enhancements		Larger	Schedule new periodic function if integrating with Order Broker 20.2 or higher
User Interface Enhancement
Modern View User Interface Enhancements		Larger	None
Payment Processing Enhancements
Pass ReconciliationID Override in ccAuthService for Conditional Deposits		Small	None
External Payment Service Enhancements		Larger	Set version number to 2.0 for the External Authorization Service
PayPal Refunds to not Exceed Deposited Amount		Larger	None
Web Service Enhancements
Hold Order through CWPickIn Message		Small	Use new version of web service message to support passing hold reason
Order Maintenance API		Larger	Configure CWServiceIn OAuth authentication before using new web service
Import and Export Enhancement
Customer Engagement File Transfer Service		Larger	Complete two new system control values
Reporting Enhancement
Custom Reporting		Larger	Review the Custom Reporting guide and download the data model zip file

Custom Reporting

With this update, you can design, generate, and schedule custom reports through Oracle Analytics Cloud (formerly known as Oracle Business Intelligence Publisher).

A data model zip file is available for you to use when you design custom reports.

See the OMS Custom Reporting Guide on My Oracle Support (2149144.1) for more information.

Modern View User Interface Enhancements

This update includes enhancements to the OMS Modern View user interface.

Oracle Redwood: Oracle Redwood is our new user interface standard, focused on being predictive, and empowering the user with the information that they need in a quick and intuitive way. This is our next-generation user experience, including new colors, backgrounds, iconography, and forms.

Field descriptions are now within the enterable area of the field, and if the field is required, it is indicated below.

If the field is required and not entered, the field outline and name change to red and the message “This field is required” is displayed below.

Differently colored badges illustrate statuses of orders and order lines.

Edit and delete options are now available in various places by clicking an action menu ().

The Classic View option is now available in the drop-down menu under the user name at the upper right of the screen, rather than in the left-hand panel.

Changing company is now available by clicking the company name at the top of the page, rather than from the drop-down menu under the user name.

Check Gift Card Balance: When you select the Check Gift Card Balance option from a menu, such as the Order Entry menu, the Check Gift Card page opens rather than the Check Gift Card Balance window.

Home page enhancements include:

• Added Customer and Order Search.

• Enhanced Quick Links to provide access to additional quick links, if more than three are defined for the user class.

• Added links to the five most recent pages for the user’s current session.

• Removed large and small placeholder images that were formerly displayed toward the bottom of the page if there were no quick links and the user did not have authority to the options related to the summary tiles at the top of the page.

Searching for an item or SKU: Searching for an item or SKU now uses a single entry field to search across item code, description, and keyword. If there is an exact match, only the matching item is displayed in the search results; otherwise, full or partially matching items are displayed. When you first advance to this step in order entry, an illustration indicates that there are not yet any items on the order, and to use the search option to select an item.

Customer order list enhancements: Modern View now provides a more focused customer order list screen with customer totals, including:

• Customer totals (Purchases, Lifetime Value, and Return Rate) now displayed as tiles to the right of the customer information.

• Removed list of Most Frequent Purchases, and instead added link to Frequently Purchased Items drawer for the customer. This drawer is available regardless of whether order or item information is currently displayed.

Order Summary page enhancements: A streamlined Order Summary page shows shipment tracking details at the ship-to and line levels. Messages are now consolidated for the order and customer under a single Messages tab. Also, changed the Invoice Detail page to display more frequently required information, including Gross Margin information if the user has the required authority, deposit totals and dates, and invoices related to net exchange billing.

Pass ReconciliationID Override in ccAuthService for Conditional Deposits

In this update, changed the Conditional Deposit request message (an authorization + deposit request) to CyberSource to include the reconciliationID in the ccAuthService node as well as in the ccCaptureService node.

Prior to this change, the reconciliationID was passed only in the ccCaptureService node. The reconciliationID is still passed only in the ccCaptureService node or the ccCreditService node for other request message types.

About the reconciliationID: You can use the reconciliationID to pass either the invoice number or the alternate order number (such as an e-commerce order number), as a reference number for the transaction to CyberSource. A reconciliationID is passed to CyberSource only if the Override Reconciliation Id field for CyberSource is not left blank in Work with Authorization Services (WASV). If the field is blank and no reconciliationID is passed to CyberSource, then CyberSource assigns its own system-generated reconciliationID as a reference number and returns it in the response message.

Audit Changes to Web Service Authorization and Clients

With this update, the following activities are automatically logged in the User_Audit table:

• Creating or deleting inbound web service users in Work with Web Service Authentication (WWSA).

• Creating, deleting, or updating outbound web service users in Work with Web Service Authentication (WWSA).

• Generating clients in Manage External Application Access (MEAA), or regenerating client secrets.

• Editing web service access for a client in Manage External Application Access (MEAA).

• Refreshing the displayed client information in Manage External Application Access (MEAA).

Note:

The Work with Web Service Authentication (WWSA) option is available in Classic View, while the Manage External Application Access (MEAA) is available in Modern View.

The User_Audit entries for these activities are not included in the User Authority Change Report (PUSA).

Customer Engagement File Transfer Service

With this update, the Order Management System now supports transferring data to Customer Engagement 20.0+ through the Customer Engagement file transfer service for the following periodic functions:

• Customer Engagement Sales Feed (RLTSLSF)

• Customer Engagement Item Feed (RLTITMF)

• Customer Upload (RLTCSUP)

To use the file transfer service you need to complete two new system control values:

• ORCE File Service URL (M62)

• ORCE Import Folder Path (M63)

These system control values are now included on the ORCE Integration Values screen (L52). See the Customer Engagement Playbook on My Oracle Support (1994453.1) to verify the settings for these system control values.

The file transfer service uses OAuth authentication, specified through the new outbound ORCE File Service (WWSA). The client ID specified here must be assigned the FileReview role in Customer Engagement.

Note:

Use of the file transfer service is required for integration with Oracle Retail Customer Engagement 20.0 or higher; however, it is not supported in earlier releases of Customer Engagement.

Note:

For integration with Customer Engagement 20.0+, the Organization Descriptor (L50) system control value now controls the web service messages structure rather than the organization descriptor, and must be set to ws.

Hold Order through CWPickIn Message

With this update, a new version 3.0 of the CWPickIn message supports a hold_reason tag in the CWPickIn element.

If the new tag is populated and the transaction_type specified in the message is B (partial backorder), R (void/keep reservation), U (void/unreserve), or V (void), the hold reason specified is applied as a user hold on the order, replacing the current user hold reason, if any. If the order was not previously in held status, it is now held.

If the hold reason specified does not already exist, the system creates it. The description is set to AB — AUTO CREATED, where AB is the hold reason specified in the CWPickIn message. If the hold reason specified in the message exceeds 2 positions, it is truncated to 2. If the hold reason is specified in lower case, it is treated as upper case when comparing it with existing hold reason codes or creating a new hold reason code.

Order Maintenance API

With this update, a new API provides limited order maintenance options:

• Updating the arrival date for individual order lines.

• Removing a user hold.

The order maintenance request message can include multiple updates, for example, changing the arrival date on two lines as well as removing a user hold. However, if the order is ineligible for any part of the specified changes, none of the changes are applied.

Limitations: You cannot use the API to remove system-assigned holds, or to update orders that are currently locked. Also, you cannot change the arrival date for an order line that is fully or partially shipped or printed. Order lines that are sold out, canceled, or being fulfilled through Order Broker are also excluded from update.

Authentication: Set up OAuth authentication for the client ID under CWServiceIn.

PayPal Refunds to not Exceed Deposited Amount

With this update, changed deposit processing to retain the PayPal Capture ID in the Credit Card Deposit History table. Also:

• Changed refund integration with PayPal to base a refund on the deposit history record with a matching deposit amount, if any, and otherwise the largest deposit amount, or split against multiple deposit amounts if needed; also, reconciles the amount of the refund against the deposits so that the total refund amount does not exceed the deposit total for the order.

• Changed the Note displayed at the Display Order Payment History screen to indicate when a deposit was partial or exceeded the limit.

Pre-Order/Active PO Enhancements

This update includes enhancements to pre-order processing and fulfillment through Order Broker.

New ACTPO periodic function:Added a new ACTPO periodic function to be used instead of the existing PREORDER periodic function if you are integrating with Order Broker 20.2 or higher. The ACTPO periodic function:

• Identifies order lines for items that are considered Active PO items, based on the setting of the flag. These order lines can be either brokered backorders or lines on ship-for-pickup orders.

• Uses the Order Broker inventory availability web service to request the current available to promise quantity for Active PO order lines. This request specifies each Active PO item and requests information on the items’ availability in locations that support delivery (brokered backorder) orders, ship-for-pickup orders, or both, depending on the fulfilment types supported by the company and whether there are Active PO order lines for each fulfillment type. For example, the response can indicate that 20 units are available in locations supporting delivery orders, and 15 units are available in location supporting ship-for-pickup orders.

• Based on the available to promise quantities returned in the inventory availability response for each fulfillment type, releases order lines to Order Broker, using the same rules as the existing PREORDER function, for example: oldest to newest order lines; partial quantities not submitted; and so on.

• Updates the item warehouse records for the Active PO items based on the information returned from Order Broker in the item availability response as well as the orders submitted to Order Broker.

• Submits the backorder quantity update notification to RMFCS based on any related updates that affected the backorder quantity for each Active PO item.

Screen changes: Made the following changes to the Display Item/Warehouse Information screen (DINI):

• Changed the name of the Pre-order field to Active PO.

• Changed the name of the Pre-order Updated field to PO Updated.

• Changed the name of the Pre-orders Released field to Released Qty.

• Changed the sequence of the fields on the screen.

Also, changed the Pre-order flag in Work with Items/SKUs (MITM) to Active PO.

Change to import of future available information: The OCDSFA periodic function no longer sells out order lines if the available quantity is less than the backorder quantity. Also, the function now always updates the PO Updated date when it updates any purchase order information (PO Updated or PO Receipts) for the Item Warehouse record.

New properties to support the ACTPO periodic function: Added the OROB_INVENTORY_AVAILABILITY_URL and the OROB_INVENTORY_AVAILBILITY_SKU_LIMIT to Work with Customer Properties (PROP).

External Payment Service Enhancements

Change to batch authorizations: With this release, batch authorizations using the External Payment Service update individual Credit Card Authorization Transaction table (CCAT00) records with a status of *RCVD and an SU (service unavailable) response code if a valid response was not received for the payment method, even though communication during batch authorizations was successful. In this case, the order is put on AT hold. When this occurs, you need to contact the payment processor to see if the authorization was actually successful. If so, you can void the record and release the hold reason, so that the payment method is eligible to be submitted again the next time you run batch authorizations rather than applying a manual authorization to avoid any potential errors that might occur as a result of a manual authorization.

To avoid potential timeout issues, Oracle recommends that you set the Response Time high enough for the authorization service to prevent issues that could potentially occur if the authorization process times out while processing multiple authorizations for an order.

New version number field: New Message Version field at the Work with External Authorization Service screen enables you to use the new tags required to support subsequent authorization requests, described below. Set to 2.0 by default when creating a new authorization service record; otherwise, set to 1.0 for an existing record.

Change to order API processing: The order payment method is now updated with the ci_transaction_id if it is passed in the CWOrderIn message if there is also an auth_number and transaction_id passed for the payment method.

Multiple captures and customer-initiated transaction IDs:The integration now passes information identifying multiple captures and customer-initiated transactions, including:

• Storing the customer-initiated transaction ID if it is received through the CWOrderIn message or received through the External Payment Service. This ID is deleted if you change the credit card number for the order payment method.

• Tracking the number of capture (deposit) requests through the External Payment Service if there are multiple requests. Multiple requests are supported only if the Void auth at deposit flag is not selected in Work with Authorization Services, and you should leave this flag unselected only if your end payment processor supports split shipments (multiple captures against a single authorization).

• Sending additional information in new tags through the External Payment Service for subsequent authorization requests to indicate whether it is considered a Merchant-Initiated (MIT) or Customer-Initiated Transaction (CIT) with a Card on File (COF).

Note:

Authorizations for gift cards through the External Payment Service now use the Void auth at deposit flag specified for the authorization service rather than the Retain Unused Stored Value Card Authorization After Deposit (J21) system control value.

The multiple capture logic takes place for:

• Resubmission of failed deposits.

• Split shipments (when an order is not fulfilled in a single shipment).

• Deferred or installment billing.

Multiple capture logic is not currently implemented for membership orders.