1 Feature Summary
Oracle Retail AI Foundation Cloud Services 22.2.401.0 is a Critical Update.
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 AI Foundation Cloud Service 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.
-
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.
Table 1-1 Noteworthy Enhancements
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
Size Profiling |
Small |
Yes |
No |
|
|
Promotion Markdown Optimization and Offer Optimization |
Small |
Yes |
No |
|
|
Promotion Markdown Optimization and Offer Optimization |
Small |
Yes |
No |
|
|
Promotion Markdown Optimization, Offer Optimization, and Pricing Cloud Service |
Small |
Yes |
No |
|
|
Promotion Markdown Optimization and Offer Optimization |
Small |
Yes |
No |
New Feature Description
This section describes the new features.
Size Profiling
Attribute Filters
Two fields for attribute and attribute value were added to the output export from Profile Sciences. If the size profiles have an attribute dimension (that is, if attribute was selected in the escalation path in Profile Sciences runs) the attribute fields can be used for filtering the size profiles by attribute (such as brand, silhouette, and so on).
Promotion Markdown Optimization and Offer Optimization
Promotion Markdown Optimization, Offer Optimization, and Pricing Cloud Service
Offer Optimization Workflow
-
There is now an optional mechanism to automatically approve prices and send as approved to Pricing Cloud Service. If a retailer only desires records to be approved in Pricing Cloud Service and not PMO and OO then the approve can be disabled and only use the submitted function. If there are only OO batch run recommendations, then users can submit a record (item/loc/eff date) and then later when decides to Approve, which will then trigger a NEW record in Pricing Cloud Service.
-
Approving in PMO/OO means that records will be sent to Pricing Cloud Service and will change the status to Approved, if there are no conflicts. There can be conflicts in Pricing Cloud Service. If there is a conflict then users can manage conflict exceptions through the Pricing Cloud Service exception management UI.
-
If there are only OO batch run recommendations, then users can submit a record (item/loc/eff date) and cannot later decide to Approve the same record. OO cannot support multiple records due to possibility of presence of multiple pricing events. Work-around for the user is to disable the Submit or Approve on OO side (configuration) and let them submit or approve records as they want.