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?

Corporate Rules Maintenance Using ReST Service

Allocation

Small

Yes

No

Updated Merchandising Tile in Retail Home with Invoice Matching Metrics

Invoice Matching

Small

No

Yes

Invoicing Enhancements for Allowance Deals

Invoice Matching

Small

Yes

No

Financial Integration Enhancements

Merchandising, Invoice Matching

Medium

No

Yes

Bill Backs and Rebate Deals Enhancements – On Demand Billing

Merchandising

Medium

Yes

No

Bill Backs and Rebate Deals Enhancements – Retroactive Deals

Merchandising

Small

Yes

No

WAC Update Spreadsheet Upload

Merchandising

Small

Yes

No

Ability to Replenish Items on Clearance

Merchandising

Small

No

Yes

Ability to Approve Parent Items with No Child Items

Merchandising

Small

Yes

No

AI Generated Item Description Suggestion

Merchandising

Small

No

Yes

New Transaction Type to Support Capturing Pre-Payment for a Customer Order

Merchandising

Small

Yes

No

Capability to Capture/Calculate/Reset Item/Store Selling Start Date

Merchandising

Small

No

Yes

AI-Powered Oracle Digital Assistant

Merchandising, Invoice Matching, Pricing, Allocation

Small

Yes

No

RFMCS Changes to Support Brazilian Tax Reform – Part I

Fiscal Management

Medium

Yes

No

New RFMCS Workflow for Standalone Fiscal Document Receiving (DNIFDR)

Fiscal Management

Medium

Yes

No

RFMCS Support for Financial Integration – Part II

Fiscal Management

Medium

Yes

No

Corporate Rules Maintenance Using ReST Service

This cloud service update introduces a ReST Service to upload and maintain the set of corporate rules within Allocation CS that are expected to be used while creating an allocation.

Integration
API Name Change Type Integration Type Field Name Change Description
Manage Allocation Corporate Rules New REST Service

Rule ID;

Rule Name;

Net Need Indicator;

Location;

Merchandise Hierarchy;

Need Quantity;

 This service provides the ability to create, modify, and delete corporate rules within Allocation CS.

Updated Merchandising Tile in Retail Home with Invoice Matching Metrics

This cloud service update enhances the Merchandising tile in Retail Home to include two Invoice Matching specific metrics, namely ‘Automatch Rate’ and ‘Invoices with Discrepancy’.

Invoicing Enhancements for Allowance Deals

This cloud service update introduces a new resolution action ‘Stock Ledger Adjustment’ (SLA-Allowance) to resolve allowance discrepant invoices as an additional feature to the existing Allowance deals. As part of this enhancement, when allowance variance amount received from Invoice Matching is processed in Merchandising, estimated expense related to the allowance components is recalculated based on cost basis. In case of specific allowance, only estimated expense value is recalculated whereas for value-based allowance, allowance component rate is also recalculated. The average cost is recalculated in both cases, and the variance is captured in Transaction Data posting.

Financial Integration Enhancements

This cloud service update announces the introduction a ReST service-based integration method between Merchandising and Oracle Fusion Cloud Financials (CFIN). This will provide an alternative to the existing Retail integration Cloud Service (RICS) based integration method which uses RFI for point-to-point integration with CFIN. The functionalities included in this update rounds out the new integration framework by complementing functionalities released in previous updates. These enhancements can also be used for integrating external financial systems. The table below represents the complete summary of the various features in the new financial integration framework. This summary includes capabilities added in this update and previous few updates to present the complete picture.

  • Merchandising Inbound Data Interfaces

Type Interface Method
Financial Foundation Data

GL Setup

Spreadsheet Upload

Languages

Spreadsheet Upload

Org Units

Spreadsheet Upload
Financial Accounts

General Ledger Chart of Accounts

Spreadsheet Upload / ReST Service
Currency

Currency Exchange Rate

ReST Service

Currencies

Spreadsheet Upload

Currency Exchange Type

Spreadsheet Upload
Terms

Payment Terms

Spreadsheet Upload / ReST Service

Freight Terms

Spreadsheet Upload / ReST Service

Suppliers and Partners

Supplier and Partners

ReST Service / Online Screen

  • Merchandising Outbound Data Interfaces

Type Interface Method

Merchandising and Sales Audit to General Ledger

STG_FIF_GL_DATA (Merch staging table) to FIF_GL_PUBLISH (Merch staging table specific to CFIN) and then to CFIN

Batch Process / ReST Service

Invoice Matching to General Ledger

IM_FINANCIALS_STAGE (IMCS staging table) to FIF_GL_PUBLISH (IMCS staging table specific to CFIN) and then to CFIN

Batch Process / ReST Service

Invoice Matching to Accounts Payable

IM_AP_STAGE_HEAD (IMCS staging table) to FIF_AP_HEAD_PUBLISH (IMCS staging table specific to CFIN) and then to CFIN

Batch Process / ReST Service
IM_AP_STAGE_DETAIL (IMCS staging table specific to CFIN) to FIF_AP_DETAIL_PUBLISH (IMCS staging table specific to CFIN) and then to CFIN

Batch Process / ReST Service

General Ledger Cross Reference / Account Validation

Merchandising

Spreadsheet Upload / ReST Service

Sales Audit

Spreadsheet Upload / ReST Service

Invoice Matching

Online Screen

  • GL Export Flexible Attribute Mapping

    This configuration allows for the flexible mapping of generic reference attributes on the Oracle Retail staging tables and the target CFIN tables. It offers an easy means of adjusting mappings to accommodate pre-existing usage of certain attributes. This is available to be maintained in Merchandising and Invoice Matching through the spreadsheet upload functionality.

  • GL Cross Reference Dynamic Mapping

    Dynamic mapping functionality allows for the classification of select account segments as dynamic, deriving the value for these segments based on key values (Department, Class, Subclass, Location, GL Ref No) in the transaction data record and managing this “dynamic mapping” independent of the cross-reference creation. Merchandising combines the information in these dynamic mappings with the cross-reference information to create complete account combinations for postings. (This feature was introduced in the Merchandising update 25.0.201).

  • Updated System Level Options for Financial Integration

    This Merchandising update makes FINANCIAL_AP option obsolete by introducing the following new set of options controlling specific functional features.

    • External Supplier Management

      This new configuration indicates whether suppliers are managed externally or within Merchandising. If suppliers are configured to be externally managed, then they are not allowed to be created in Merchandising, and only a subset of attributes are allowed to be updated. Additionally, the enrichment of suppliers is supported based on additional options.

    • Filter Inactive Suppliers

      This new configuration indicates whether Merchandising should subscribe inactive suppliers and only impacts suppliers and partners created via the Supplier and Partner Upload service. This option does not impact the update flow and updates will be subscribed for all valid suppliers in Merchandising, irrespective of status.

    • Use Purchase Pay Site Flags

      This new configuration indicates whether Purchase/Pay Site flags associated with the supplier site should be used to create Purchase and Remittance addresses respectively. This allows for the simplification of supplier address subscription by allowing to not specify address types specific to Merchandising.

    • Use Site Details

      This new configuration indicates whether supplier site related information should be used to build missing supplier details for a subset of the fields in the input payload of the Supplier and Partner Upload Service.

    • Use Supplier Alternate Name

      This is an existing configuration and controls whether the alternate name sent from the financials system will be used as the supplier site name in Merchandising.

    • External Account Validation

      This configuration indicates whether account combinations created via the GL cross reference processes should be validated via a web service call to an external financial system if the account does not exist in Merchandising.

  • Service Integration Configurations

    This Merchandising update provides service configurations (service URLs and Credentials) to be set up for Merchandising and CFIN direct integration.

  • External Reference ID Management

    The merchandising data model has been extended to use entity IDs maintained in the external financial systems. To use the new integration, it will be required to configure these external IDs for the following entities in Merchandising - Supplier, Partners, Payment Terms, Freight Terms, Languages, VAT Codes, Org Units and Set of Books.

Steps to Enable

The new options, can be enabled and turned on, by navigating :

  1. System Options > Foundation container - External Supplier Management, Filter Inactive Suppliers, Use Purchase Pay Site Flags, Use Site Defaults and Use Supplier Alternate Name

    Note:

    The additional options are available for selection if External Supplier Management is selected. If External Supplier Management is unselected, then the additional options will be reset, unselected and disabled for edit on the UI.
  2. System Options > Financials container - External Account Validation
System Options
Attribute Name New or Update? Attribute Description Default Value
Use Site Defaults New This new configuration will indicate if Supplier Site information should be used to build missing supplier details for a subset of the fields in the input payload of the Supplier and Partner Upload Service. If set to No, it will be expected that all supplier details will be sent explicitly via the integration. This option is only available when External Supplier Management is Yes. N
External Supplier Management New This new configuration will indicate if Suppliers will be managed externally or within Merchandising. If Suppliers are configured to be externally managed, then a subset of supplier related fields in Merchandising will be view only and restricted for update via Merchandising Screens. The Create Supplier Task will not be accessible in this configuration. Additionally, when Suppliers are configured to be managed Externally , enrichment of the supplier will be supported based on the additional options described below. If External Supplier Management is not selected, then there shall be no restrictions imposed in Merchandising with regard to Creation, Updation and Deletion of Supplier Data via the UI screens. There shall also be no selective enrichment of the input payload provided to the Supplier and Partner Upload service. N
External Account Validation New This configuration will indicate if Account Combinations introduced via the Cross Reference processes, should be validated against an external financial system. If selected, a webservice call will be invoked to validate account combinations that are not found locally (FIF_GL_ACCT). If unselected, account validation will be limited to validating against the accounts available locally (FIF_GL_ACCT) N
Filter Inactive Suppliers New This new configuration will indicate if Inactive Suppliers should be subscribed to. This configuration will only impact Suppliers/Partners being created via the Supplier and Partner Upload service If checked, Inactive Suppliers will not be subscribed to on a Create payload. If not checked, suppliers will be subscribed to irrespective of status. This option will not impact the update flow and updates will be subscribed to irrespective of status as long as the supplier exists in Merchandising. This option is only available when External Supplier Management is Yes. N
Use Purchase Pay Site Flags New This new configuration will indicate if Purchase/Pay Site flags associated with the supplier site should be used to create Purchase and Remittance addresses respectively. This option is only available when External Supplier Management is Yes. N
Use Supplier Alternate Name Update This pre-existing configuration will control if the alternate name sent from the Financials system will be used as the supplier site name in Merchandising. This option is now available when External Supplier Management is Yes. N
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
SYSTEM_OPTIONS RDS_WV_SYSTEM_OPTIONS Update Added EXTERNAL_SUPP_MGMT, USE_PROC_PAY_SITE_IND_FOR_ADDR, FILTER_INACTIVE_SUPP, USE_SITE_DEFAULTS and EXTERNAL_ACCOUNT_VALIDATION
FINANCIAL_UNIT_OPTIONS DAS_WV_FINANCIAL_UNIT_OPTNS Update Added EXTERNAL_ACCOUNT_VALIDATION
FINANCIAL_UNIT_OPTIONS RDS_WV_FINANCIAL_UNIT_OPTIONS Update Added EXTERNAL_ACCOUNT_VALIDATION
SYSTEM_OPTIONS DAS_WV_SYSTEM_OPTNS Update Added EXTERNAL_SUPP_MGMT, USE_PROC_PAY_SITE_IND_FOR_ADDR, FILTER_INACTIVE_SUPP, USE_SITE_DEFAULTS and EXTERNAL_ACCOUNT_VALIDATION.
FOUNDATION_UNIT_OPTIONS DAS_WV_FOUNDATION_UNIT_OPTNS Update Added EXTERNAL_SUPP_MGMT, USE_PROC_PAY_SITE_IND_FOR_ADDR, FILTER_INACTIVE_SUPP, USE_SITE_DEFAULTS
FOUNDATION_UNIT_OPTIONS RDS_WV_FOUNDATION_UNIT_OPTIONS Update Added EXTERNAL_SUPP_MGMT, USE_PROC_PAY_SITE_IND_FOR_ADDR, FILTER_INACTIVE_SUPP, USE_SITE_DEFAULTS

Bill Backs and Rebate Deals Enhancements – On Demand Billing

This cloud service update provides the ability to view the total income generated until the last income calculation processing for Bill Back and Bill Back Rebate deals for the current period where the end date has not yet arrived. This is displayed at a component level in the Deal Performance screen.

Bill Backs and Rebate Deals Enhancements – Retroactive Deals

This cloud service update provides the ability to edit the Billback and Billback Rebate deals at extended points in their life cycle (Worksheet, Approved, and Active status). This includes Deals based on PO Approval, Receipts, Sales and Issues. The update capability allows for changing dates (including backdating) as well as changes to components, item-locations and discount details.

The deal data is refreshed based on the updated deal definitions and the impacts of the change are reflected in the next billing cycle. The deal definition also includes the means to indicate whether the deal income should be used to revalue inventory. If opted for, the Inventory Layers information is used to identify where the inventory contributing to the deal income resides and average cost is revalued for the “deal-eligible” number of units available at each location. For “deal-eligible” units that are no longer present, a cost variance is recorded for the location. If the configuration on the deal is set to not revalue inventory, then the deal income is posted to transaction data as an income using existing transaction codes (tran code 6 and 7). This feature is available for deals created post this update. The number of days a deal can be backdated is controlled by a system level configuration ‘Retroactive Deal Period Days’ which has a default value set as 30 days and can be updated as needed.

System Options
Attribute Name New or Update? Attribute Description Default Value
RETROACTIVE_DEAL_PERIOD_DAYS New This defines the maximum number of days in the past a deal can be made retroactive. The active date on a deal cannot be set or updated to a value that is more than the Retroactive Deal Period days in the past. The deal active date must be no earlier than the current date minus the Retroactive Deal Period days. The value should be a positive integer between 0 and 365 inclusively. 0
Batch Schedule
Process Name Process Type New or Updated? Delivered
DEALACT_REVERSE_PROCESS Nightly New Enabled
DEALS_PROCESS Nightly Update Enabled
Code Impact
Code Type Code Type Description Code Code Description New or Updated? Delivered
GLMT General Ledger Monthly Transactions 69C GL Intf - Deal Cost Variance (Cost) Update Enabled
GLRT General Ledger Rolled Transactions 69C GL Intf - Deal Cost Variance (Cost) Update Enabled
GLST General Ledger Single Transactions 19C GL Intf - Deal Cost Adjustment (Cost) Update Enabled
GLRT General Ledger Rolled Transactions 19C GL Intf - Deal Cost Adjustment (Cost) Update Enabled
GLST General Ledger Single Transactions 69C GL Intf - Deal Cost Variance (Cost) Update Enabled
GLMT General Ledger Monthly Transactions 19C GL Intf - Deal Cost Adjustment (Cost) Update Enabled
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
DEAL_HEAD DAS_WV_DEAL_HEAD Update Two new column RECALC_INVENTORY_VALUE_IND and RETROACTIVE_ELIGIBLE_IND added in the view.
DAILY_DATA RDS_WV_DAILY_DATA Update Two new column DEAL_COST_ADJUSTMENT and DEAL_COST_VARIANCE added in the view.
WEEK_DATA RDS_WV_WEEK_DATA Update Two new column DEAL_COST_ADJUSTMENT and DEAL_COST_VARIANCE added in the view.
PROCUREMENT_UNIT_OPTIONS RDS_WV_PROCUREMENT_UNIT_OPTIONS Update New column RETROACTIVE_DEAL_PERIOD_DAYS added in the view.
SYSTEM_OPTIONS RDS_WV_SYSTEM_OPTIONS Update New column RETROACTIVE_DEAL_PERIOD_DAYS added in the view.
MONTH_DATA RDS_WV_MONTH_DATA Update Two new column DEAL_COST_ADJUSTMENT and DEAL_COST_VARIANCE added in the view.
MONTH_DATA DAS_WV_MONTH_DATA Update Two new column DEAL_COST_ADJUSTMENT and DEAL_COST_VARIANCE added in the view.
DAILY_DATA DAS_WV_DAILY_DATA Update Two new column DEAL_COST_ADJUSTMENT and DEAL_COST_VARIANCE added in the view.
WEEK_DATA DAS_WV_WEEK_DATA Update Two new column DEAL_COST_ADJUSTMENT and DEAL_COST_VARIANCE added in the view.
DEAL_HEAD RDS_WV_DEAL_HEAD Update Two new column RECALC_INVENTORY_VALUE_IND and RETROACTIVE_ELIGIBLE_IND added in the view.
PROCUREMENT_UNIT_OPTIONS DAS_WV_PROCUREMENT_UNIT_OPTNS Update New column RETROACTIVE_DEAL_PERIOD_DAYS added in the view.
SYSTEM_OPTIONS DAS_WV_SYSTEM_OPTNS Update New column RETROACTIVE_DEAL_PERIOD_DAYS added in the view.

WAC Update Spreadsheet Upload

This cloud service update introduces the option to bulk update weighted average cost (WAC) of item-locations through spreadsheet upload. It is accessible via 'Upload Average Cost Adjustment' option under the Financials folder in the Merchandising task lists. To perform updates, users can download a blank template, provide the necessary adjustments, and then upload the updated spreadsheet with the new WAC for specific item-locations.

Security

Privileges
Priv Name Change Type Priv Description Parent Duty
MAINTAIN_AVERAGE_COST_VIA_SPREADSHEET_PRIV New A privilege for performing Item/Location Average Cost Adjustments via spreadsheet upload. RMS_AVERAGE_COST_VIA_SPREADSHEET _MGMT_DUTY
Duties
Duty Name Change Type Duty Description Child Duty Base Role
RMS_AVERAGE_COST_VIA_SPREADSHEET _MGMT_DUTY New A duty for maintaining item/location average cost via spreadsheet upload.

Ability to Replenish Items on Clearance

This cloud service update introduces the option to include items that are on clearance to replenishment transactions specific to warehouse stocked category. This is controlled by a system level attribute “Replenish Clearance Items from Warehouse Stock” and is initially set as ‘No’.

Steps to Enable

The steps mentioned below need to be followed to enable this feature

  1. Navigate to Application Administration → System Options.
  2. Move to Inventory → Replenishment section.
  3. Check the Replenish Clearance Items from Warehouse Stock option.
System Options
Attribute Name New or Update? Attribute Description Default Value
ALLOW_CLR_ITEM_WH_STOCK New This field specifies if clearance items will be replenished when the replenishment stock category is ''Warehouse Stocked''. Valid values are Yes (Y) or No (N). When set to Yes (Y), during replenishment processing, if the stock category is ''Warehouse Stocked'', items actively on clearance may be replenished. When set to No (N), during replenishment processing items actively on clearance will be excluded from replenishment. N

Ability to Approve Parent Items with No Child Items

This cloud service update introduces the ability to create multi-level items in the approved status via the online screen, Item API and Spreadsheet upload without any validation for the existence of child level items.

AI Generated Item Description Suggestion

This cloud service update introduces an AI-powered workflow to suggest and refine item descriptions in the Merchandising online screen during and after item creation or at the time of submitting or approving an item. This provides users an option to generate various item descriptions with AI assistance, review and subsequently accept. In addition to the Item Description, Secondary Description and Short Description, a new field ‘Long Description’ is introduced in Merchandising to facilitate maintenance of a more descriptive narration suited for online platforms. The option of AI suggestion/refinement is available for all four types of descriptions. This feature is controlled by a system level indicator ‘AI Assist’ and will initially be set as ‘No’

Steps to Enable

Check ‘AI Assist’ option in the System Options screen.

System Options
Attribute Name New or Update? Attribute Description Default Value
AI_ASSIST_IND New This configuration indicate if Generative AI capabilities are enabled in Merchandising. If set to Y, Gen AI capabilities will be enabled within Merchandising. If set to N, Gen AI capabilities will be disabled within Merchandising. By default this is set to No (N). N
Integration
API Name Change Type Integration Type Field Name Change Description
RIB Subscription - Item Creation/Update Update RIB Message LONG_DESC Long description of the item.
/services/items/update Update REST Service longDescription Long Description of the item.
/services/item/description/translations/create Update REST Service longDescription Long Description of the item.
/services/item/description/translations/update Update REST Service longDescription Long Description of the item.
/services/foundation/item Update REST Service longDescription Long Description of the item.
RIB Publish - Item Publish Update RIB Message LONG_DESC Long description of the item
/services/items/create Update REST Service longDescription Long Description of the item.
ItemManagementService Update SOAP Service long_desc Long description of the item.
/services/private/Item/itemDetail Update REST Service longDescription Long Description of the item.
/services/foundation/item/{itemId} Update REST Service longDescription Long Description of the item.
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
ITEM_MASTER DAS_WV_ITEM_MASTER Update Added column LONG_DESC.
SYSTEM_CONFIG_OPTIONS RDS_WV_SYSTEM_CONFIG_OPTIONS Update Added column LONG_DESC.
"MULTIPLE" RDS_V_ITEMS Update Added column LONG_DESC.
"MULTIPLE" DAS_V_ITEMS Update Added column LONG_DESC.
ITEM_MASTER RDS_WV_ITEM_MASTER Update Added column LONG_DESC.
ITEM_MASTER_TL DAS_WV_ITEM_MASTER_TL Update Added column LONG_DESC.
ITEM_MATSER_TL RDS_WV_ITEM_MASTER_TL Update Added column LONG_DESC.
SYSTEM_OPTIONS RDS_WV_SYSTEM_OPTIONS Update Added column LONG_DESC.
SYSTEM_CONFIG_OPTIONS DAS_WV_SYSTEM_CFG_OPTNS Update Added column LONG_DESC.
SYSTEM_OPTIONS DAS_WV_SYSTEM_OPTNS Update Added column LONG_DESC.
SVC_ITEM_MASTER RDS_WV_SVC_ITEM_MASTER Update Added column LONG_DESC.
SVC_ITEM_MASTER DAS_WV_SVC_ITEM_MASTER Update Added column LONG_DESC.

New Transaction Type to Support Capturing Pre-Payment for a Customer Order

This cloud service update introduces a new transaction type (PREPAY) that allows the system to specifically capture liability with respect to accepted advances against customer orders without order item details. The new transaction type is expected to have only header and tender records be mandatory, with customer details being optional. The value captured on the transaction header must match the tender value accepted. The sign of the value and tender may be either positive or negative to depict an advance received or a refund. These transactions can be used on totals and other roll ups which can in turn be sent to the General Ledger. The transactions themselves are not be exported to other systems.

This prepayment transaction will not impose any dependency on the ORD that can come in on sale transaction later for the same customer order. The customer will be expected to set up totals to reconcile the liability accepted across the PREPAY transaction and the preexisting Customer Order related item statuses ( ORI,ORC,ORD, LIN, LCO, LCA)

Reference Fields -

  1. REF NO 31, with label “IV” (Invoice No.) for tran type SALE.
  2. REF NO 1, with label “CORD” (Customer Order Number) for tran type PREPAY.
Code Impact
Code Type Code Type Description Code Code Description New or Updated? Delivered
TRAT Sales Audit Transaction Types PREPAY Prepayment New Enabled
REFL Sales Audit Reference Labels CORD Customer Order Number New Enabled

Capability to Capture/Calculate/Reset Item/Store Selling Start Date

This cloud service update provides users with a systematic approach to maintain and identify a date which marks the beginning of the selling phase for an item-location combination through Merchandising online screens. This date field always remains flexible for any transaction-based updates and is expected to have the value corresponding to the most recent receipt of significance at all points of time which is used to identify the start of the selling phase for that item-location combination. This feature is controlled by a system level indicator and is initially be set as ‘No’.

Steps to Enable

The steps mentioned below need to be followed to enable this feature

  1. Navigate to Application Administration → System Options.
  2. Move to Foundation → Item Location section.
  3. Check the Capture Selling Phase Start Date option.
Integration
API Name Change Type Integration Type Field Name Change Description
Subclass Create/Update API Update RIB Message New fields added

New fields "UPD_SELL_DATE_ON_ST_ORD_RECEIPT_IND",

"UPD_SELL_DATE_ON_WH2ST_RECEIPT_IND","UPD_SELL_DATE_ON_ST2ST_RECEIPT_IND",

"MIN_UNITS_FOR_SELL_DATE_RESET" added.
​/services​/merchandiseHierarchy​/subclass​/create Update REST Service New fields added

New fields "UPD_SELL_DATE_ON_ST_ORD_RECEIPT_IND",

"UPD_SELL_DATE_ON_WH2ST_RECEIPT_IND","UPD_SELL_DATE_ON_ST2ST_RECEIPT_IND",

"MIN_UNITS_FOR_SELL_DATE_RESET" added.
/services/merchandiseHierarchy/subclass/update Update REST Service New fields added

New fields "UPD_SELL_DATE_ON_ST_ORD_RECEIPT_IND",

"UPD_SELL_DATE_ON_WH2ST_RECEIPT_IND","UPD_SELL_DATE_ON_ST2ST_RECEIPT_IND",

"MIN_UNITS_FOR_SELL_DATE_RESET" added.

AI-Powered Oracle Digital Assistant

This cloud service update introduces integration with the Oracle Digital Assistant. The Oracle Digital Assistant (ODA) is an AI-powered platform that enables users to interact with various business applications and services through natural conversations via chat interfaces. ODA is being used to bring together information, workflows, and assistance from multiple documentation sources into a single, unified experience.

With ODA, end users can:

  • Get Answers Quickly: Ask questions and receive timely, accurate responses to common queries about applications, policies, or business processes.

  • Personalized Experience: Receive tailored information and notifications based on your role, preferences, and recent activity.

  • Simple Interaction: Use natural language (typing or speaking) to communicate. ODA is designed to understand common phrases and conversational requests.

For the best experience, access the ODA window by clicking the conversation icon at the bottom of the screen, state your request or question clearly, and follow prompts or suggestions as they appear. If ODA cannot resolve your request, consult the documentation or log a service request to get additional support.

If there is an issue accessing ODA, customers are advised to log a service request (SR), so that Oracle can provide a resolution.

RFMCS Changes to Support Brazilian Tax Reform – Part I

This cloud service update introduces the first set of changes necessary in RFMCS to support the Brazilian tax reform. This first set of changes are limited to the addition of a new fiscal attribute to indicate transactions with Government entities, changes in the scenario of validating NFe rules in all FDG flows to account for new item level totalization, and changes in reference fiscal documents access key at item level. This new version also supports the updated NFe xml structure and the new versions of the tax partner APIs used by the fiscal document generation and receiving workflows.

New RFMCS Workflow for Standalone Fiscal Document Receiving (DNIFDR)

This cloud service update introduces a new RFMCS workflow that supports the receiving of fiscal documents generated by third parties as a standalone document with no association with any transaction in MFCS.

RFMCS Support for Financial Integration – Part II

This cloud service update introduces the changes required to post fiscal documents generated or received by RFMCS to Cloud Financials. In addition to the previously released features that generate the integration data based on fiscal documents and financial setup, this second part of the scope brings the capacity to post the combined data into integration staging tables and from there to Cloud Financials. From staging to Cloud Financials, the process uses the MFCS/IMCS integration flow which is not detailed in this enhancement

Batch Schedule
Process Name Process Type New or Updated? Delivered
FIF_RFM_GL_PUBLISH_PROCESS_ADHOC Cyclic New Enabled
FIF_RFM_AP_PUBLISH_PROCESS_ADHOC Cyclic New Enabled