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? |
|---|---|---|---|---|
| Merchandise Hierarchy Markdown Zone Groups |
Pricing |
Small |
No |
Yes |
| Support for User Specific Number and Date Format Preferences for Data Loading |
Merchandising |
Small |
No |
Yes |
| Alternate Stock Ledger Calculation Option for Retail |
Merchandising |
Small |
No |
Yes |
| Enhanced Inventory Movement Tracking Option using Inventory Layers |
Merchandising |
Medium |
No |
Yes |
| Transfer-Based Deals |
Merchandising |
Small |
Yes |
No |
| Allowance Deals |
Merchandising |
Medium |
No |
Yes |
| Direct Database Integration for Revised Transactions from Sales Audit to Store Inventory Operations (SIOCS) |
Sales Audit |
Small |
No |
Yes |
| Retail Fiscal Management Cloud Service (RFMCS) Enhancements |
Fiscal Management |
Medium |
Yes |
No |
Merchandise Hierarchy Markdown Zone Groups
This cloud service update introduces an ability to associate additional price zone groups with the merchandise hierarchy which may be used for markdown recommendations by Lifecycle Pricing Optimization Cloud Service (LPO). Within the Pricing Cloud Service (RPCS), groupings of locations known as price zone groups can be used for the creation of price changes, clearances and promotion offers. The system supports identifying one price zone group for each merchandise hierarchy to be used for initial price setting. This is referred to as the primary zone group for the merchandise hierarchy.
Within RPCS, the Initial Price Zone Definition workflow has been renamed to Merchandise Hierarchy Zone Groups. In this workflow, users can now optionally choose one or more price zone groups as the markdown zone groups for a given merchandise hierarchy and can mark one of them as the default markdown zone group. The primary price zone group and the markdown zone groups associated with the merchandise hierarchy are subsequently made available in LPO for selection and use in the generation of recommendations. This enhanced feature is controlled by a new RPCS system option named ‘Allow Merchandise Hierarchy Markdown Zone Groups’, which must be checked (set as Yes) to start assigning price zone groups as the Markdown Zone Groups for the merchandise hierarchy.
Steps to Enable
-
Log into RPCS
-
Go to Application Administration —> System Options.
-
Mark the Allow Merchandise Hierarchy Markdown Zone Groups option to checked.
System Options
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
ALLOW_MARKDOWN_ZONE_GROUPS_IND |
New |
ALLOW_MARKDOWN_ZONE_GROUPS_IND will say functionality is enabled or disabled. |
it will be set zero as '0' |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
RPM_MARKDOWN_ZONE_GROUP_DEF |
DAS_WV_RPM_MARKDOWN_ZONE_GROUP_DEF |
New |
Contains MARK DOWN information created for primary zone group from UI |
|
RPM_SYSTEM_OPTIONS_V |
DAS_WV_RPM_SYSTEM_OPTIONS_V |
Update |
ALLOW_MARKDOWN_ZONE_GROUPS_IND says functionality is enabled or disabled. |
|
RPM_SYSTEM_OPTIONS_V |
RDS_WV_RPM_SYSTEM_OPTIONS_V |
Update |
ALLOW_MARKDOWN_ZONE_GROUPS_IND says functionality is enabled or disabled. |
|
RPM_MARKDOWN_ZONE_GROUP_DEF |
RDS_WV_RPM_MARKDOWN_ZONE_GROUP_DEF |
New |
Contains MARK DOWN information created for primary zone group from UI |
|
RPM_ZONE_CONFIG_OPTIONS |
DAS_WV_RPM_ZONE_CONFIG_OPTIONS |
Update |
ALLOW_MARKDOWN_ZONE_GROUPS_IND says functionality is enabled or disabled. |
|
ALLOW_MARKDOWN_ZONE_GROUPS_IND |
RDS_WV_RPM_ZONE_CONFIG_OPTIONS |
Update |
ALLOW_MARKDOWN_ZONE_GROUPS_IND says functionality is enabled or disabled. |
Support for User Specific Number and Date Format Preferences for Data Loading
Note:
There are Known Issues related to this enhancement. The fixes for those issues are in active development.This cloud service update introduces ability to support a user’s preferred numeric and date formats in data loading spreadsheets in Merchandising. The spreadsheet templates have been enhanced to obtain and use the Number Format and Date Format selected by the user in the system’s User Preferences – Regional settings. When data is downloaded to a spreadsheet for a user, the system converts numeric and date values into the user’s selected format for display in the spreadsheet. Similarly, when a user enters data into a spreadsheet template, numeric and date values can be entered in the user’s selected format. Upon uploading the spreadsheet, the system converts the values in the format needed when storing the value in the database. This feature is controlled by a Use User Date/Number Formats system configuration on the spreadsheet configuration table (s9t_config). This flag is initially set to No. Customers must submit a service request to have this setting toggled to Yes, which will enable this functionality.
Alternate Stock Ledger Calculation Option for Retail
This cloud service update introduces an option to use alternate logic to calculate the Half-to-date Goods Available For Sale (HTD_GAFS) value when running the Retail Method of Accounting by choosing to exclude the ‘Transfer Out’ and ‘Book Transfer Out’ transactions. This updated calculation logic results in a value that is closer to a true Cumulative Markon Percent (CMO%) and is also similar to an aggregated weighted average cost (WAC) determined at the subclass level. This is aimed to avoid cost distortions that may happen for warehouse locations and supply chain-based inventory movement, especially crossdocking. This option is controlled by the new ‘Include Outbound Transfers in Goods Available for Sale Calculation’ system option.
Steps to Enable
The following steps need to be executed to use the alternate calculation method which excludes the Transfer out parameters -
-
Log into MFCS.
-
Go to Application Administration —> System Options UI.
-
Under Financials section, uncheck the Include Outbound Transfers in Goods Available for Sale Calculation option.
System Options
| Attribute Name | New or Update? | Attribute Description |
|---|---|---|
|
HTD_GAFS_INCL_TSF_OUT_IND |
New |
This indicates whether or not to include outbound transfers (Tran code 32) and outbound book transfers (Tran code 33) while determining Inventory Additions Cost and Inventory Additions Retail as part of the Half-to-Date Goods Available for Sale (HTD_GAFS) Cost and Retail calculations for departments running the Retail Method of Accounting method. Valid values are Yes (Y) and No (N). |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
FINANCIAL_UNIT_OPTIONS |
RDS_WV_FINANCIAL_UNIT_OPTIONS |
Update |
Added new column HTD_GAFS_INCL_TSF_OUT_IND. |
|
WEEK_DATA |
RDS_WV_WEEK_DATA |
Update |
Column comment updated for HTD_GAFS_RETAIL and HTD_GAFS_COST |
|
WEEK_DATA |
DAS_WV_WEEK_DATA |
Update |
Column comment updated for HTD_GAFS_RETAIL and HTD_GAFS_COST |
|
MONTH_DATA |
RDS_WV_MONTH_DATA |
Update |
Column comment updated for HTD_GAFS_RETAIL and HTD_GAFS_COST |
|
MONTH_DATA |
DAS_WV_MONTH_DATA |
Update |
Column comment updated for HTD_GAFS_RETAIL and HTD_GAFS_COST |
|
FINANCIAL_UNIT_OPTIONS |
DAS_WV_FINANCIAL_UNIT_OPTNS |
Update |
Added new column HTD_GAFS_INCL_TSF_OUT_IND. |
Enhanced Inventory Movement Tracking Option using Inventory Layers
With this cloud service update, there is now a new option to identify and track logical inventory layers (identifiable chunks of inventory) as they move through the retailer’s distribution system and are eventually sold. Inventory layers are primarily based on PO/Receipt, with an optional feature to track based on an identifier that is different/more granular than PO/Receipt. Inventory identifiers can be defined and maintained by retailers as codes, and there is Department / Class level configuration to allow for the use of such identifiers. If the system is configured to use inventory identifiers, it will require all systems that handle inventory (that is, receipts, shipments, sales, adjustments, and so on) to include the identifier with transactions to enable correct recording. A new database table has been introduced to hold the layered view of inventory. All inbound transaction ReST APIs have also been modified to have an optional field for the identifier.
The primary use case for the layered inventory view is to update inventory value (stock ledger and weighted average cost) for events after initial receipt that impact inventory value (IFRS, GAAP Legal Requirements, and so on). In Merchandising, this information is initially utilized for accurate Deal Income impacts. Retailers can optionally leverage RDS to utilize this data for more use cases as needed.
Steps to Enable
-
Log into the MFCS Application.
-
Go to Application Administration —> System Options.
-
Mark the Inventory Identifier option to checked in the Functional section.
System Options
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
INVENTORY_LAYER_HIST_DAYS |
New |
This field indicates the number of days Inventory Layer data would be retained in Merchandising before they are purged. The value must be at least 7 days but no more than 365. |
7 |
|
INVENTORY_LAYER_IND |
New |
This field indicates whether the inventory layer tracking functionality is available in Merchandising. Valid values are Y and N. |
'N' |
Batch Schedule
| Process Name | Process Type | New or Updated? | Delivered |
|---|---|---|---|
|
ITEM_LOC_SOH_LEDGER_INIT_LOAD_PROCESS |
Nightly |
New |
Enabled |
|
ITEM_LOC_SOH_LEDGER_PURGE_PROCESS |
Nightly |
New |
Enabled |
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
services/inventory/shipmentsAndReceipts/purchaseOrder/receipts/manage |
Update |
REST Service |
INVENTORY_IDENTIFIER_TYPE and INVENTORY_ID |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
/services/inventory/shipmentsAndReceipts/receipts/manage |
Update |
REST Service |
INVENTORY_IDENTIFIER_TYPE and INVENTORY_ID |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
/services/inventory/shipmentsAndReceipts/stockOrder/receipts/manage |
Update |
REST Service |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
/services/inventory/shipmentsAndReceipts/outboundAsn/create |
Update |
REST Service |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
Receiving Subscription API |
Update |
RIB Message |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
Inventory Adjustment Subscription API |
Update |
RIB Message |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
ASN Outbound Subscription API |
Update |
RIB Message |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
RTV Subscription API |
Update |
RIB Message |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
/services/merchandiseHierarchy/class/update |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/merchandiseHierarchy/department/update |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/foundation/merchhier/deps/{dept} |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/inventory/shipmentsAndReceipts/dsd/create |
Update |
REST Service |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
/services/inventory/returnsToVendor/manage |
Update |
REST Service |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
DSD Receipt Subscription API |
Update |
RIB Message |
"INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" |
New field "INVENTORY_IDENTIFIER_TYPE" and "INVENTORY_ID" added on the mentioned integration. |
|
/services/merchandiseHierarchy/class/create |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/foundation/merchhier/class |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/foundation/merchhier/class/{uniqueClassId} |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/merchandiseHierarchy/department/create |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" added on the mentioned integration. |
|
/services/foundation/merchhier/deps |
Update |
REST Service |
"INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" added on the mentioned integration. |
|
Merchandise Hierarchy Subscription API |
Update |
RIB Message |
"INVENTORY_LAYER_IDENTIFIER_TYPE" "APPLY_INV_IDENTIFIER_TYPE" |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added on the class and department integration. New field "INVENTORY_LAYER_IDENTIFIER_TYPE" and "APPLY_INV_IDENTIFIER_TYPE" added on department integration. |
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
IIDT |
Inventory Identifier Types |
D |
Import Doc ID |
New |
Enabled |
|
IIDT |
Inventory Identifier Types |
E |
Expiry Date |
Update |
Enabled |
|
IIDT |
Inventory Identifier Types |
L |
Lot ID |
New |
Enabled |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
CLASS |
DAS_WV_CLASS |
Update |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added. |
|
DEPS |
DAS_WV_DEPS |
Update |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added. |
|
INV_TRACK_UNIT_OPTIONS |
DAS_WV_INV_TRACK_UNIT_OPTNS |
Update |
New field "INVENTORY_LAYER_IND" added. |
|
SYSTEM_OPTIONS |
DAS_WV_SYSTEM_OPTIONS |
Update |
New fields INVENTORY_LAYER_IND and INVENTORY_LAYER_HIST_DAYS added |
|
TRAN_DATA |
DAS_WV_TRAN_DATA |
Update |
New field TRAN_DATA_ID added. |
|
TRAN_DATA_B |
DAS_WV_TRAN_DATA_B |
Update |
New field TRAN_DATA_ID added. |
|
TRAN_DATA_HISTORY |
DAS_WV_TRAN_DATA_HISTORY |
Update |
New field TRAN_DATA_ID added. |
|
CLASS |
RDS_WV_CLASS |
Update |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added. |
|
DEPS |
RDS_WV_DEPS |
Update |
New field "INVENTORY_LAYER_IDENTIFIER_TYPE" added. |
|
INV_TRACK_UNIT_OPTIONS |
RDS_WV_INV_TRACK_UNIT_OPTIONS |
Update |
New field "INVENTORY_LAYER_IND" added. |
|
SYSTEM_OPTIONS |
RDS_WV_SYSTEM_OPTIONS |
Update |
New fields INVENTORY_LAYER_IND and INVENTORY_LAYER_HIST_DAYS added |
|
TRAN_DATA_A |
DAS_WV_TRAN_DATA_A |
Update |
New field TRAN_DATA_ID added. |
|
TRAN_DATA |
RDS_WV_TRAN_DATA |
Update |
New field TRAN_DATA_ID added. |
|
TRAN_DATA_A |
RDS_WV_TRAN_DATA_A |
Update |
New field TRAN_DATA_ID added. |
|
TRAN_DATA_B |
RDS_WV_TRAN_DATA_B |
Update |
New field TRAN_DATA_ID added. |
|
TRAN_DATA_HISTORY |
RDS_WV_TRAN_DATA_HISTORY |
Update |
New field TRAN_DATA_ID added. |
|
ITEM_LOC_SOH_LEDGER |
DAS_WV_ITEM_LOC_SOH_LEDGER |
New |
New DAS view created on new table ITEM_lOC_SOH_LEDGER. |
|
ITEM_LOC_SOH_LEDGER |
RDS_WV_ITEM_LOC_SOH_LEDGER |
New |
New RDS view created on new table ITEM_lOC_SOH_LEDGER. |
|
INV_ADJ |
RDS_WV_INV_ADJ |
Update |
Added new fields INVENTORY_IDENTIFIER_TYPE and INVENTORY_ID. |
|
INV_ADJ |
DAS_WV_INV_ADJ |
Update |
Added new fields INVENTORY_IDENTIFIER_TYPE and INVENTORY_ID. |
Transfer-Based Deals
This cloud service update introduces the ability to define a supplier deal to generate income based on the movement of items from warehouses to company store locations for bill back rebate type of deals via transfer or allocation shipments. Several modifications have been made to Deals online screens and deal income calculation logic to achieve this capability. Additionally, there is now a new transaction code to capture income from such deals. Retailers must opt to maintain inventory layers by purchase order/receipt to correctly attribute shipped units to a purchase order and thereby to the deal supplier.
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
AALC |
Indicates when the deal component should be applied |
S |
Shipment |
Update |
Enabled |
|
DLRP |
Rebate Application Types |
I |
Issues |
Update |
Enabled |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
DAILY_DATA |
RDS_WV_DAILY_DATA |
Update |
Added new column - DEAL_INCOME_ISSUES |
|
MONTH_DATA |
DAS_WV_MONTH_DATA |
Update |
Added new column - DEAL_INCOME_ISSUES |
|
MONTH_DATA |
RDS_WV_MONTH_DATA |
Update |
Added new column - DEAL_INCOME_ISSUES |
|
WEEK_DATA |
DAS_WV_WEEK_DATA |
Update |
Added new column - DEAL_INCOME_ISSUES |
|
WEEK_DATA |
RDS_WV_WEEK_DATA |
Update |
Added new column - DEAL_INCOME_ISSUES |
|
DEAL_HEAD |
DAS_WV_DEAL_HEAD |
Update |
Column comment updated for REBATE_PURCH_SALES_IND |
|
DEAL_HEAD |
RDS_WV_DEAL_HEAD |
Update |
Column comment updated for REBATE_PURCH_SALES_IND |
|
DAILY_DATA |
DAS_WV_DAILY_DATA |
Update |
Added new column - DEAL_INCOME_ISSUES |
Allowance Deals
Note:
See the passage below for an important note about Oracle Retail Invoice Matching and this functionality.With this cloud service update, the Deals functionality has been expanded to support deals based on a negotiated discount between a retailer and a vendor reducing the payment on the invoice, usually known as Allowance. A new feature has been added to allow setting up such deals. The associated allowance components will need to be set up as a cost component like expenses and assessments and associated with allowance nonmerchandise codes. Modifications to Invoice Matching to enable matching of allowances are planned and in development. Allowance values will be captured as part of transaction posting similar to other cost components during order receiving. Such discounts will not reduce purchase cost or invoice item unit cost.
Steps to Enable
This functionality will be available if “Estimated Landed Cost” is enabled in MFCS. The below steps are required to enable the same.
-
Log into MFCS.
-
Go to Application Administration —> System Options screen.
-
Enable the Estimated Landed Cost checkbox in the Functional section.
Codes
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
CCDF |
Cost Component Defaulted from Values |
C |
Country Expense Profile |
New |
Enabled |
|
CCDF |
Cost Component Defaulted from Values |
D |
Allowance Deal |
New |
Enabled |
|
CCDF |
Cost Component Defaulted from Values |
E |
Cost Component Definition |
New |
Enabled |
|
CCDF |
Cost Component Defaulted from Values |
M |
Manually Added |
New |
Enabled |
|
CCDF |
Cost Component Defaulted from Values |
P |
Partner Expense Profile |
New |
Enabled |
|
CCDF |
Cost Component Defaulted from Values |
S |
Supplier Expense Profile |
New |
Enabled |
|
CTYP |
Component Type |
L |
Allowance |
Update |
Enabled |
|
DLBT |
Deal Billing Types |
ALW |
Allowance |
Update |
Enabled |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
NON_MERCH_CODE_HEAD |
RDS_WV_NON_MERCH_CODE_HEAD |
Update |
Added new column - ALLOWANCE_IND |
|
NON_MERCH_CODE_HEAD |
DAS_WV_NON_MERCH_CODE_HEAD |
Update |
Added new column - ALLOWANCE_IND |
|
DEAL_THRESHOLD_REV |
RDS_WV_DEAL_THRESHOLD_REV |
Update |
Added new columns ALLOWANCE_COMP_ID, ALLOWANCE_COMP_RATE, ALLOWANCE_COMP_BASIS |
|
DEAL_THRESHOLD_REV |
DAS_WV_DEAL_THRESHOLD_REV |
Update |
Added new columns ALLOWANCE_COMP_ID, ALLOWANCE_COMP_RATE, ALLOWANCE_COMP_BASIS |
|
ELC_COMP |
RDS_WV_ELC_COMP |
Update |
Comment updated for column COMP_TYPE |
|
ELC_COMP |
DAS_WV_ELC_COMP |
Update |
Comment updated for column COMP_TYPE |
|
ORDLOC_EXP |
RDS_WV_ORDLOC_EXP |
Update |
Comment updated for columns ORIGIN, DEFAULTED_FROM and KEY_VALUE_1 |
|
ORDLOC_EXP |
DAS_WV_ORDLOC_EXP |
Update |
Comment updated for columns ORIGIN, DEFAULTED_FROM and KEY_VALUE_1 |
|
DEAL_THRESHOLD |
RDS_WV_DEAL_THRESHOLD |
Update |
Added new columns ALLOWANCE_COMP_ID, ALLOWANCE_COMP_RATE, ALLOWANCE_COMP_BASIS |
|
DEAL_THRESHOLD |
DAS_WV_DEAL_THRESHOLD |
Update |
Added new columns ALLOWANCE_COMP_ID, ALLOWANCE_COMP_RATE, ALLOWANCE_COMP_BASIS |
Direct Database Integration for Revised Transactions from Sales Audit to Store Inventory Operations (SIOCS)
This cloud service update introduces table-based integration for revised transactions from Sales Audit to Store Inventory Operations Cloud Service (SIOCS) as a replacement for the current batch file-based scheduled integration (saexpsim) that generates an SIMT file.
Steps to Enable
To enable the new table-based process, in MFCS POM, disable the job SAEXPSIM_JOB (and SAEXPSIM_POST_JOB and RESA2SIM_JOB) and enable the new job SAEXPSIM_EXPORT_JOB ( and SAEXPSIM_EXPORT_POST_JOB) and optionally SAEXPSIM_EXPORT_CYCLE_JOB ( and SAEXPSIM_EXPORT_POST_CYCLE_JOB). Make
sure SAEXPSIM_EXPORT_PURGE_JOB is enabled to ensure purging of data in the interface tables.
Retail Fiscal Management Cloud Service (RFMCS) Enhancements
This cloud service update introduces two new Fiscal Document Generation Workflows:
-
Customer Orders Fiscal Document Generation (COFDG) – This workflow is meant to support the generation of fiscal documents, more specifically the Brazilian "NFe" document, based on the request from inventory systems such as Store Inventory Operations Cloud Service (SIOCS) or any external Warehouse Management System (WMS) system, to support customer orders’ shipments. In addition, this workflow leverages customer order specific data available exclusively in Order Management Systems via new integration that leverages the existing RFMCS FLX integration REST API.
-
Return Merchandise Authorization Document Generation (RMADG) – This workflow is meant to support the generation of the Brazilian fiscal document "NFe" to support customer order returns based on requests from external Order Management Systems via the new integration that leverages the existing RFMCS FLX integration REST API.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Fiscal Ledger Get Service |
New |
REST Service |
New Payload |
New Service |
|
Documents Status Get Service |
New |
REST Service |
New Payload |
New Service |
|
Integration Configuration Update Service |
New |
REST Service |
New Payload |
New Service |
|
Documents Get Service |
New |
REST Service |
New Payload |
New service |
|
Integration Configuration Get Service |
New |
REST Service |
New Payload |
New Service |