1 Feature Summary
The enhancements below are included in this release.
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Order Management Suite Cloud Services update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module associated with the feature, if any.
-
Scale: Identifies the size of the feature. Options are:
-
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.
-
Medium: These UI or process-based features are typically comprised of field, validation, or program changes. Therefore the potential impact on users is moderate.
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
-
Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.
-
Customer Action Required: 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 | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
| New and Updated Features | ||||
| Create Return Authorization in MV Order Summary |
Order Administration – Modern View Contact Center |
Medium |
Yes |
Yes |
| Get Return Authorization API Enhancements |
Order Administration – Web Service Enhancements |
Small |
No |
Yes |
| Price Table API |
Order Administration – Web Service Enhancements |
Medium |
No |
Yes |
| Database and Retail Data Store Updates |
Order Administration |
Small |
Yes |
No |
| Scope Authentication Format Updates |
Order Orchestration – Web Service Enhancements |
Small |
No |
Yes |
| Performance Enhancements |
Order Orchestration |
Small |
Yes |
No |
| Database and Retail Data Store Updates |
Order Orchestration |
Small |
Yes |
No |
Order Administration Enhancements
Create Return Authorization in MV Order Summary
With this update, a user can create a Return Authorization through MV Order Summary at a Ship-To level for lines shipped and not previously returned. Once created, a customer can reference a return authorization number with the items when sending back to the retailer or request a courier pick up the items.
The Return option for a Ship-To within Order Summary will now allow a user to perform either a streamlined Return or create a Return Authorization based on authority.
Note:
A user must have ALLOW authority to the Enter Return Authorization (A28) Secure Feature for the Return option to be available at the Ship-To level.
Selecting the Return option will advance the user to the Return Ship-To page where they can select Create Return Authorization or Return Ship-To.
Note:
A user must have ALLOW authority to the Receive Return Authorization (A29) and Credit Return Authorization (A34) secured features to perform a Return Ship-To. Otherwise, the page will immediately load the Create Return Authorization contents.
Within the Create Return Authorization page, a user can:
-
Add one or more items that are eligible for return. For a Set item type, if the Main Set item is added, all components will be added. The components can also be added separately if needed.
-
Set the Return Reason for each item.
-
Set the quantity up to the maximum unreturned quantity.
-
Add an exchange item for each returned item and set the Exchange Reason. The item quantity and pricing can be set during Create Return Authorization only when Require Exchange at Time of Receipt (F42) system control value is set to No.
-
Set Refund Options for shipping, additional charges, personalization, and duty charges.
Return Authorizations will continue to be received through Classic View Work with Return Authorizations (WRTA), Receive Returns (WRAR) or using the Return Authorization API.
When a Return Authorization is created through MV Order Summary, the Return Disposition Code will default from Default Disposition Code (C18) system control value and is not manually entered.
Get Return Authorization API Enhancements
With this update, an external application can now search for Return Authorizations using the Delivery Id.
The Delivery Id is generated when a Courier Pickup is scheduled for a specific Return Authorization and must be unique across all companies in Order Administration. When a match is found, this functionality will return all details about a specific Return Authorization and the Courier Pickup Details.
Price Table API
With this update, Order Administration has created new Price Table Services available for merchant applications.
Note:
The Foundation Read/Write or Foundation Read Only scope is required for calling this service. Assign a Client ID access to this scope through the Manage External Application Access screen in Modern View.
Price Table Services includes options to Get, Add, Update and Delete for the following:
-
Price Tables
-
Price Table Groups
-
Price Table Group Details
-
Price Table Items
-
Price Table Item Details
-
Price Table Source Details
Note:
Uploads are performed on each of the Price Table data individually; no parent-child validation will be performed by Order Administration. The retailer is responsible for upload data integrity.
Price Table uploaded data will be available through Work with Price Tables (WPTB) menu option in Classic View.
Order Orchestration Enhancements
Scope Authentication Format Updates
With this update, the format of Order Orchestration scopes has been modified. These scopes are used for external merchant applications to successfully authenticate to Omnichannel services.
The scope format is made up of the application identifier, module, environment and permission (r (Read) or rw (Read/Write)).
-
Old scope format was <application identifier>-<environment>:<module>:<permission>. An example would be OBCS-PROD1:organization:rw
-
New scope format drops application and is now <module>-<permission>-<environment> . An example would be organization-rw-PROD1
Note:
Old scope formats will continue to be supported; however, it is recommended to move to the new scope formats after applying this update for any external merchant application integrations.
The following APIs use scopes:
-
Foundation Data APIs should now use foundation-r and foundation-rw scopes (previously foundation:r and foundation:rw).
-
Eligible Return Locations API should now use organization-r and organization-rw scopes (previously organization:r and organization:rw).