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 Merchandising 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 Enabled | Customer Action Required? |
|---|---|---|---|---|
|
Merchandising |
Small |
Yes |
No |
|
|
Merchandising |
Small |
Yes |
No |
|
|
System Activation Screen Renamed to Initial System Configuration |
Merchandising |
Small |
Yes |
No |
|
Merchandising |
Small |
Yes |
No |
|
|
Wrong Store Receiving Support for Wrong Transfers to Warehouse |
Merchandising |
Small |
Yes |
No |
| New Column NET_ORIGINAL_RETAIL Is Added To V_SA_TRAN_ITEM_NET_ROLLED |
Sales Audit |
Small |
Yes |
No |
|
Enhanced Processing of ‘OTHER’ Transaction Type for a Closed Store Day |
Sales Audit |
Small |
Yes |
No |
|
Direct table-based Sales Data Export from Sales Audit to Merchandising |
Merchandising, Sales Audit |
Large |
No |
Yes |
|
Fiscal Management |
Medium |
Yes |
No |
Shipment Publication ReST Service
This cloud service update introduces a new ReST service that will publish details related to all forms of stock order shipments created using the MFCS online screen to downstream systems. Store and warehouse locations that are not capable of handling these shipments at their end can subscribe to this service in order to be updated with the latest inventory movement information.
Batch Schedule
| Process Name | Process Type | New or Updated? | Delivered |
|---|---|---|---|
|
MERCHAPI_DELTA_EXT_SHIPMENT_ADHOC_PROCESS |
Ad Hoc |
New |
Enabled |
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Get Stock Order Shipment Created in Merchandising |
New |
REST Service |
/services/inventory/shipmentsAndReceipts/stockOrder/shipment |
This new web service can be used to get Stock Order Shipment(s) created in Merchandising based on the input filter criteria. |
Allocation Subscription Enhancement for Status Management
This cloud service update introduces an enhancement to provide a placeholder for the user to specify the status of an allocation while defining it using the existing XAlloc API or the equivalent ReST service. This will support the creation of an allocation in the Reserved ('R') and Approved ('A') status, with the latter being the default one.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
/services/inventory/allocations/create |
Update |
REST Service |
status |
Added status field |
|
/services/inventory/allocations/update |
Update |
RIB Message |
status |
Added status field |
|
Allocation Subscription API |
Update |
RIB Message |
status |
Added status field |
System Activation Screen Renamed to Initial System Configuration
The recently introduced System Activation functionality has been renamed to Initial System Configuration to avoid confusion with the OCI-IAM activation process. The screen title, tasks list link, descriptions under code type SYSA, and several error messages were updated to reflect the new terminology.
Short Description Field to the Omni Channel Item Publish API
As part of this cloud service update, the Item Short Description field will be added to the Omni Channel Item Publish API to provide Merchandising managed short description to XStore suite.
Wrong Store Receiving Support for Wrong Transfers to Warehouse
This version of Merchandising introduces an enhancement to support the Wrong Store Receiving workflow for receipt of a transfer/allocation, which was intended for a warehouse at any redirected store
New Column NET_ORIGINAL_RETAIL Is Added To V_SA_TRAN_ITEM_NET_ROLLED
As part of this cloud service update, a new column NET_ORIGINAL_RETAIL (that is, ITEM_QTY * ORIG_UNIT_RETAIL) will be added to the view V_SA_TRAN_ITEM_NET_ROLLED. This can be used while calculating net discount given on an item that had its price overridden at POS.
Enhanced Processing of ‘OTHER’ Transaction Type for a Closed Store Day
This cloud service update introduces an enhancement to Sales Audit to successfully process certain transactions classified as Transaction Type ‘Other’ even when the store day is closed. Prior to this update, transactions/RTLOGs from a point-of-sale system are rejected if the associated store day is closed in Sales Audit. This enhancement is needed for transactions that are performed and sent by POS system outside a store day. These transactions are usually internal store operation transactions such as clock in, clock out, training mode transactions, and so on. Note that Sales Audit does not really have any use for such transactions, but they are sent to ensure full visibility for audit trail purposes and proper accounting of transaction sequence. As part of this enhancement, Transaction Upload web service and batch process have been modified to process RTLOGs containing only transactions of the type ‘Other’ without reopening a closed store day.
Direct table-based Sales Data Export from Sales Audit to Merchandising
This cloud service update introduces the option of direct table-based processing of sales data from Sales Audit to Merchandising in addition to file (POSU) based integration. The method of integration can be chosen based on a Sales Audit system level option (Merchandising Sales Export Integration). A new sales export batch (saexprocsales) will be introduced for the new integration method.
Steps to Enable
Navigate to the Sales Audit System Options screen through the System Options link under the Foundation Data folder in the Tasks list. In the System Options screen, go to the System Constraints container and select the option Table-based from the Merchandising Sales Export Integration dropdown to enable this new capability.
System Options
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
RESA_TO_RMS_DIRECT_EXP_IND |
New |
Option to
export Sales Audit sales records to Merchandising directly with no POSU files. Valid values are |
N |
Retail Fiscal Management Cloud Service Enhancements
RFM Functional Overview
Oracle Retail Fiscal Management Cloud Service is designed to help retailers manage their fiscal and compliance requirements related to fiscal documents. RFMCS is intended to enable compliance for retailers that operate in regions with complex tax and regulations that affect the supply chain and financial-related features in the scope of Retail Merchandising Cloud Service.
Fiscal Document Management
RFMCS main objective is the management of fiscal documents and the support to fiscal document receiving and generation based on a pre-defined business workflow. This module introduces the workflow-based development concept in which the business rules applied to a transaction processing flow is defined and kept separated from the components that execute the flow. With this approach, users have total visibility of what is being processed in the system, the exchange of messages, the errors, and validations.
Fiscal Document Generation Workflows
The Fiscal Document Generation feature is meant to support the generation of fiscal documents associated with a transaction and based on the request from inventory systems, such as Store Inventory Operations Cloud Service (SIOCS) or any external Warehouse Management System (WMS) system. Based on the request document type informed, a pre-defined processing workflow will be called to generate and have the fiscal document approved with local fiscal authorities.
The following document generation workflows are now available:
-
RTVDG - Return to Vendor Fiscal Document Generation: This workflow is meant to support the generation of a return to vendor fiscal document based on the request from inventory systems.
-
RNFDG - Return NF Document Generation: This workflow is meant to support the generation of a return fiscal document in case of discrepancies identified in the POFDR workflow.
-
CRNDG - Credit Note Document Generation: This workflow is meant to support the generation of a credit note in case of discrepancies identified in the POFDR workflow.
-
TSFDG – Transfer Fiscal Document Generation: This workflow is meant to support the generation of a stock order transfer fiscal document based on the request from inventory systems.
-
DIFDG – Direct Import Fiscal Document Generation: This workflow is meant to support the issuance of a direct import fiscal document based on the request from third party specialist systems.
-
DNODG – Direct Note Outbound Document Generation: This workflow is meant to support the generation of a standalone fiscal document based on the request posted via RFMCS processPreDoc API.
-
DNIDG - Direct Note Inbound Document Generation: This workflow is meant to support the generation of a standalone fiscal document based on the request posted via RFMCS processPreDoc API.
Fiscal Document Receiving Workflows
The Fiscal Document Receiving feature is meant to support the receiving of fiscal documents associated with a transaction in Merchandising like a purchase order, import order and stock counts. The first workflow available in RFMCS is the Purchase Order Fiscal Document Receiving (POFDR) of Brazilian NFe model 55. With this update, the below additional workflows are also available:
-
TSFDR – Transfer Fiscal Document Receiving: This workflow is meant to support the receiving of stock order transfers with the creation of an entry fiscal document based on the physical receipt submitted by inventory systems.
-
DIFDR – Direct Import Fiscal Document Receiving: This workflow is meant to support the receiving of a direct import fiscal document based on the request from third party specialist systems.
Foundation Data
RFMCS foundation data enables the configuration of user access to locations and workflows, the setup and maintenance of transaction codes to be applied during fiscal document processing flows, data loading of setup data and now the capacity to assign a document sequence that will be used in the Fiscal Document Generation workflows.
Manage Document Sequences
Fiscal Document Management features will have a configuration to support fiscal document sequencing in a gapless format. In Brazil and in other countries, fiscal documents must have a gapless sequence as per a Government requirement. The Manage Document Sequences feature allows the creation of sequences at fiscal document issuing location level, with the possibility of having more than one sequence available for the same location.
DAS Administration Enhancement for Replication or Re-Export
This enhancement to the Data Access Schema (DAS) Administration screen provides the ability to request replication or the re-export of one or more already replicated DAS Tables. A new section entitled DAS Replication Administration was added to the DAS Administration screen.
Steps to Enable
Navigate to the Merchandising System Options screen through the System Options link under the Application Administration folder in the Tasks list. In the System Options screen, go to the System container and check the Allow Data Access Schema (DAS) Replication checkbox to enable this new capability.