1 Feature Summary
This chapter describes the feature enhancements in this release.
Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Data Store 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 impacted 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 to 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? |
|---|---|---|---|---|
|
Order Management |
Small |
Yes |
No |
|
| Card Token Update |
Order Management |
Medium |
No |
Yes |
Audit of Table Changes
With this update, the following processes now track changes:
-
Classic View Menu Options accessed by users are always tracked now. The “Log Use” flag on the Work with Users (WUSR) screen has been removed as the system will always track usage as if this is set to Yes for all users.
Card Token Update
With this update, tokenized card numbers are now also stored in a payment card token field through the following processes:
-
Work with Batch Tokenization (WBTK) to request and store a card token if the order was previously not tokenized.
-
A new SaveCardToken periodic function for already tokenized cards. The following jobs must be ended before running this periodic function. Otherwise, it will end immediately with a failure: "AUTO_DEP", "DEP_UPDATE", "PICK_GEN", "CNTL_ASYNC", "BTCH_TKN".
Note:
Contact your Oracle Representative to determine whether these processes should be run.The Change List, and the Sales Order Data Extract Files and Schedule Jobs topics are in the online help.