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 Order Management System 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? |
|---|---|---|---|---|
| New and Updated Options | ||||
| Tax Compliance - Exclude Credit Invoice Tax Request for Suppress Refunds | Order Management - Integrations | Small | Yes | No |
Tax Compliance – Exclude Credit Invoice Tax Request for Suppress Refunds
With this update, Order Management was enhanced to prevent an external tax service invoice request during billing when the Order Payment Method is set to suppress refunds and a credit invoice is generated.
When Xstore Point of Service processes a return, the suppress_refund attribute is set to Y in the CWReturnIn message as Xstore records the negative tax liability when issuing the refund to the customer. Prior to this change, Order Management was suppressing the credit invoice from being submitted during deposit processing, but the system was still making the invoice request to the external tax service at the time the invoice was created, causing the tax liability to be understated since it was already reduced by the Xstore credit transaction.
The intended use for setting the suppress refund flag to Y (via the CWOrderIn or CWReturnIn request) is to allow a retailer to exclude the refund that was already processed by another system. The tax request should also be suppressed since the tax would have already been recorded when the other system issued the refund.