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 Enabled: Indicates whether the feature is available for use immediately after upgrade. Yes means the feature is delivered enabled. No means the feature must be enabled or configured before use; the required steps are described in the feature details.
-
Customer Action Required: Indicates whether you must take action before the feature can be used. Features marked Yes are delivered disabled, and you choose if and when to enable them.
| Feature | Module Impacted | Scale | Delivered Enabled | Customer Action Required? |
|---|---|---|---|---|
|
Enhanced Data Management for Deals with Delete and Audit Tables in RDS |
Merchandising |
Small |
Yes |
No |
|
Enhanced Duplicate Transaction Prevention for Inventory Adjustments API |
Merchandising |
Small |
Yes |
No |
|
Merchandising |
Small |
Yes |
No |
|
|
Enhanced Support for Item Substitution for Inventory Planning |
Merchandising |
Large |
No |
Yes |
|
Enhanced Support for Linked Allocations for Close and Delete APIs |
Merchandising |
Small |
Yes |
No |
|
Enhanced Support for Two-Legged Transfers Involving Finishers through ReST APIs |
Merchandising |
Large |
Yes |
No |
|
Merchandising |
Small |
Yes |
No |
|
|
Merchandising |
Small |
Yes |
No |
|
|
Sales Audit |
Small |
Yes |
No |
|
|
Included Invoice Attachment Link in Outbound File Publication Workflows |
Invoice Matching |
Small |
Yes |
No |
|
New APIs for Bulk Document Approval, Unmatching and Deletion in Invoice Matching |
Invoice Matching |
Small |
Yes |
No |
|
Pricing |
Small |
Yes |
No |
|
|
Fiscal Management |
Small |
Yes |
No |
Enhanced Data Management for Deals with Delete and Audit Tables in RDS
This update introduces delete and audit tables in RDS for various deals-related data. These enhancements improve data management and auditing capabilities, allowing for better tracking of changes and deletions to deals data. The following tables now have corresponding audit and delete tables: DEAL_HEAD, DEAL_DETAIL, DEAL_COMP_PROM, DEAL_THRESHOLD, DEAL_ITEMLOC_DCS, DEAL_ITEMLOC_DIV_GRP, DEAL_ITEMLOC_ITEM, DEAL_ITEMLOC_PARENT_DIFF, DEAL_COMP_TYPE, DEAL_PROM, FIXED_DEAL, FIXED_DEAL_DATES, FIXED_DEAL_MERCH, and FIXED_DEAL_MERCH_LOC.
DEAL_ACTUALS_ITEM_LOC_DLY table is added to RDS replication.
Enhanced Duplicate Transaction Prevention for Inventory Adjustments API
This update introduces enhancements to help prevent duplicate inventory adjustments and receipts through optional external identifiers, improving data accuracy and transaction traceability. The Inventory Adjustments ReST API now accepts an optional external ID.
When provided, Merchandising verifies that the combination of external ID and location is unique and rejects duplicate requests.
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
INV_ADJ |
DAS_WV_INV_ADJ |
Update |
The DAS_WV_INV_ADJ view now exposes INV_ADJ_REQUEST_ID and EXT_INV_ADJ_ID for replication to the Retail Data Store. These columns provide the reference to the related inventory adjustment request and its external inventory adjustment ID, making the two records easier to trace. |
|
INV_ADJ |
RDS_WV_INV_ADJ |
Update |
The RDS_WV_INV_ADJ view now includes INV_ADJ_REQUEST_ID and EXT_INV_ADJ_ID. These columns expose the related inventory adjustment request ID and its external adjustment ID in inventory adjustment data available to the Retail Data Store. |
Enhanced Duplicate Transaction Prevention for Receipt API
This update introduces enhancements to help prevent duplicate inventory adjustments and receipts through optional external identifiers, improving data accuracy and transaction traceability. The Shipment and Receipt Upload ReST APIs now accept an optional External Receipt ID for each receipt. This identifier helps prevent duplicate receipt processing while maintaining traceability to the related receipt transaction. Valid receipt requests continue to follow the existing processing logic.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Manage Purchase Order Receipts |
Update |
REST Service |
externalReceiptId |
The service supports the optional field externalReceiptId. When provided, its value must be unique within the receiving location and must not be reused for another receipt at that location. |
|
Manage Purchase Order and Stock Order Receipts |
Update |
REST Service |
externalReceiptId |
The service supports the optional field externalReceiptId. When provided, its value must be unique within the receiving location and must not be reused for another receipt at that location. |
|
Manage Stock Order Receipts |
Update |
REST Service |
externalReceiptId |
The service supports the optional field externalReceiptId. When provided, its value must be unique within the receiving location and must not be reused for another receipt at that location. |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
RECEIPT |
RDS_WV_RECEIPT |
New |
This RDS view exposes external receipt headers and their processing trace attributes. |
|
RECEIPT |
DAS_WV_RECEIPT |
New |
This DAS view exposes external receipt headers and their processing trace attributes. |
|
RECEIPT_CARTON |
RDS_WV_RECEIPT_CARTON |
New |
This RDS view exposes external receipt carton details and their shipment/carton trace keys. |
|
RECEIPT_CARTON |
DAS_WV_RECEIPT_CARTON |
New |
This DAS view exposes external receipt carton details and their shipment/carton trace keys. |
|
RECEIPT_ITEM |
DAS_WV_RECEIPT_ITEM |
New |
This DAS view exposes external receipt item details and their SHIPSKU trace keys. |
|
RECEIPT_ITEM |
RDS_WV_RECEIPT_ITEM |
New |
This RDS view exposes external receipt item details and their SHIPSKU trace keys. |
Enhanced Support for Item Substitution for Inventory Planning
With this update, Merchandising expands the current item substitution capabilities to support a broader range of business scenarios, including temporary substitution for situations where the primary item has an extended lead time or is temporarily unavailable. Existing promotional and transitional substitution workflows will also continue to be supported.
This enhancement provides greater flexibility in managing item substitutions and transitions and supports more effective inventory planning and replenishment when Merchandising is integrated with Inventory Planning Optimization (IPO).
Steps to Enable
-
From the Application Maintenance menu, open the System Options screen.
-
Under the Integration section, locate Applications.
-
Locate the Oracle Retail Inventory Planning Optimization option.
-
Select the checkbox to set the option to Yes (Y).
-
Click on Save.
System Options
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
IPO_IND |
New |
Indicates whether Merchandising is integrated with Oracle Retail Inventory Planning Optimization (IPO). Valid values are 'Y' and 'N'. The default is 'N'. |
N |
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Manage Substitute Items |
Update |
REST Service |
substituteItems.details.startDate, endDate, reasonCode |
The POST /item/location/substituteItems/manage service request is extended to accept startDate, endDate, and reasonCode for each substitute-item detail. Existing fields and CREATE, UPDATE, and DELETE actions remain supported. Dates use the YYYY-MM-DD format. When IPO_IND is Y, both dates are mandatory; otherwise both are optional. The service validates dated versus undated relationships and applies the applicable substitute-item overlap rules. |
|
Merchandising Item Location Service |
Update |
REST Service |
substituteItems.details.startDate, endDate, reasonCode |
The Item Location GET response is extended to publish startDate, endDate, and reasonCode in each substituteItems.details record, in addition to substituteItem, primaryReplenishmentPack, and pickPriority. Dates are returned in YYYY-MM-DD format. |
Code Impact
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
SUBR |
Substitute Reason |
S |
Temporary Substitute |
New |
Enabled |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
PRODUCT_CONFIG_OPTIONS |
RDS_WV_PRODUCT_CONFIG_OPTIONS |
Update |
Added IPO_IND to the RDS view to publish the Oracle Retail Inventory Planning Optimization system option. |
|
PRODUCT_CONFIG_OPTIONS |
DAS_WV_PRODUCT_CFG_OPTNS |
Update |
Added IPO_IND to the DAS view to publish the Oracle Retail Inventory Planning Optimization system option. |
|
SYSTEM_OPTIONS |
DAS_WV_SYSTEM_OPTNS |
Update |
Added IPO_IND to the DAS view to expose the Oracle Retail Inventory Planning Optimization system option through SYSTEM_OPTIONS. |
|
SYSTEM_OPTIONS |
RDS_WV_SYSTEM_OPTIONS |
Update |
Added IPO_IND to the RDS view to expose the Oracle Retail Inventory Planning Optimization system option through SYSTEM_OPTIONS. |
Enhanced Support for Linked Allocations for Close and Delete APIs
This update extends the support currently provided for creating linked allocations using a single request payload to the Close Allocations and Delete Allocation Details ReST APIs.
External applications can now submit multiple related allocations within a single request to close allocations or delete allocation details, simplifying the management of linked allocations across multiple distribution tiers. The services also include additional validations to ensure that these operations do not leave active linked allocations dependent on an allocation that has been closed or allocation details that have been deleted.
However, updating linked allocations through a single request payload is not currently supported. In order to modify existing linked allocations, users must submit separate ReST service requests at an individual allocation level.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
MerchIntegrations/services/inventory/allocation/details/delete |
Update |
REST Service |
NA |
Handling linked allocation dependency as part of the Rest service business logic. |
|
MerchIntegrations/services/inventory/allocations/close |
Update |
REST Service |
NA |
Handling linked allocation dependency as part of the Rest service business logic. |
Enhanced Support for Two-Legged Transfers Involving Finishers through ReST APIs
This Merchandising update enhances the existing Transfer Management ReST services to support the creation and maintenance of two-legged transfers involving internal or external finishers. Consistent with the online workflow, users can provide finishers details and freight and routing codes for the second leg of the transfer using the service.
A new ReST service enables users to attach and manage work order activities, item transformations, and packing details for these transfers. Users can assign pre-defined finishing activities with optional costs and instructions, specify item transformations, and define packing changes including converting packs to individual items, individual items to packs, or one pack configuration to another. These details can be added, replaced as a complete set, or removed in full while the transfer is in ‘Input’ status. Once the transfer is approved, the resulting items or packs are reflected in the second leg to support shipping and receiving at the destination location.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Manage Transfer Work Orders |
New |
REST Service |
Refer to Operations Guide. |
This is a new service to manage Work Orders associated to Two-Legged Transfers. |
Enhanced Transfer Management through ReST APIs
This Merchandising update provides greater flexibility in managing and tracking transfers through existing ReST services. Users now can:
-
Close shipped transfers through the Transfer Update service, when no open allocations or appointments are linked to the transaction. A warning is returned if the transfer has not been received.
-
Manage up charges by excluding them during the transfer creation or removing existing up charges while the transfer is in ‘Input’ status.
-
Track transfers using an External Transfer Number, captured through the Create and Update services and displayed as External Transfer in the online screens. Users can search for transfers using this value in the application and retrieve them through the Get Transfer service.
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
TSFHEAD |
DAS_WV_TSFHEAD |
Update |
Added new field EXT_TSF_NO |
|
TSFHEAD |
RDS_WV_TSFHEAD |
Update |
Added new field EXT_TSF_NO. |
|
TSFHEAD_PRG_HIST |
DAS_WV_TSFHEAD_PRG_HIST |
Update |
Added new field EXT_TSF_NO |
|
TSFHEAD_PRG_HIST |
RDS_WV_TSFHEAD_PRG_HIST |
Update |
Added new field EXT_TSF_NO |
Item Reclassification Enhancements
The enhancement allows users to reclassify items even when they are involved in open purchase orders or stock counts, thereby providing more flexibility to re-organize merchandise without waiting for the linked transactions to close.
New/Updated System Options:
-
Reclass Items on Approved Orders (replaces existing checkbox): Allows the user to select one of the following -
-
Never Allow (NA): Reclassification can only occur for items not presently on any approved order. This will work the way the current indicator works in the unchecked state. This will be the default state for new implementations and for existing ones where the indicator was set to unchecked.
-
With or Without Receipts (WWR): Reclassification can occur for items on approved orders, including those where one or more item-locations have receipts, and even if the order has been fully received but not closed yet.
-
With No Receipts (WNR): Reclassification can occur for items on approved orders, but only if no receipts have been posted against the entire order. This will work the way the current indicator works in the checked state. This will be defaulted in case of existing implementations where the indicator was checked.
-
Reclass Items on Open Stock Counts: This new option will work in sync with an existing option ‘Stock Count Lockout Period’ which prevents any modifications to the items within a scheduled stock count by the user specified number of days. E.g.- If the user sets the new option to checked and the specified ‘Stock Count Lockout Period’ is 3 days, no reclassifications would be allowed from 3 days prior to the count date. If only the new checkbox is checked within an implementation and no lockout period has been specified (or set to zero days), the user will not be permitted to perform a reclassification and a stock count on the same business day.
The Reclassification logic has been modified to be able to do the reclass process based on the above system option settings. With the Reclass Items on Open Stock Counts option enabled, the user can also reclassify items included in open Unit & Unit & Value stock counts.
3. New Reclass service: A new GET service has been added under Merchintegrations which will allow the user to fetch all items that are present in one or more reclassification events based on a provided set of parameters out of the following options -
-
Effective Date
-
Style ID
-
Item ID (SKU or Pack ID)
-
From Hierarchy – To Hierarchy
The key benefit of this enhancement is greater flexibility in merchandise hierarchy maintenance while preserving the integrity of existing and subsequent transactions.
System Options
| Attribute Name | New or Update? | Attribute Description | Default Value |
|---|---|---|---|
|
RECLASS_ITEM_ON_APPROVED_ORDER |
New |
Indicates whether items on open purchase orders can be reclassified. Valid values can be - WNR (With No Receipt), WWR (With or Without Receipts) and NA (Never Allow). |
Default Value - 'NA' |
|
RECLASS_ITEM_ON_OPEN_STOCK_COUNTS |
New |
Indicates whether items in open stock counts can be reclassified. Valid values are Y (Yes) and N (No), default value is N. Changes apply only to future reclassification transactions. When set to Y, this option works with STAKE_LOCKOUT_DAYS (Stock Count Lockout Period). If a lockout period is defined, reclassification is not allowed during that period before the stock count date. If the lockout period is NULL or 0, reclassification and stock count processing will not be allowed on the same business day. |
Default value is 'N' |
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Get Reclassification Details |
New |
REST Service |
/services/foundation/itemReclassification/reclassEvents |
This service enables an external system to retrieve item reclassification events. A reclassification event identifies items that will move from their current merchandise hierarchy to a target department, class, and subclass on an effective date. The service returns matching events and the associated SKU, style, or pack details. Requests can be filtered by effective date, style ID, item ID, source hierarchy, target hierarchy, or reclassification identifier. |
Code Impact
| Code Type | Code Type Description | Code | Code Description | New or Updated? | Delivered |
|---|---|---|---|---|---|
|
ORCO |
Order Reclass Options |
NA |
Never Allow |
New |
Enabled |
|
ORCO |
Order Reclass Options |
WNR |
With No Receipts |
New |
Enabled |
|
ORCO |
Order Reclass Options |
WWR |
With or Without Receipts |
New |
Enabled |
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
INV_TRACK_UNIT_OPTIONS |
DAS_WV_INV_TRACK_UNIT_OPTNS |
Update |
New field RECLASS_ITEM_ON_OPEN_STOCK_COUNTS get added. |
|
INV_TRACK_UNIT_OPTIONS |
RDS_WV_INV_TRACK_UNIT_OPTIONS |
Update |
New field RECLASS_ITEM_ON_OPEN_STOCK_COUNTS get added. |
|
PROCUREMENT_UNIT_OPTIONS |
DAS_WV_PROCUREMENT_UNIT_OPTNS |
Update |
New field RECLASS_ITEM_ON_APPROVED_ORDER get added. |
|
PROCUREMENT_UNIT_OPTIONS |
RDS_WV_PROCUREMENT_UNIT_OPTIONS |
Update |
New field RECLASS_ITEM_ON_APPROVED_ORDER get added. |
|
SYSTEM_OPTIONS |
DAS_WV_SYSTEM_OPTNS |
Update |
New fields RECLASS_ITEM_ON_OPEN_STOCK_COUNTS and RECLASS_ITEM_ON_APPROVED_ORDER. |
|
SYSTEM_OPTIONS |
RDS_WV_SYSTEM_OPTIONS |
Update |
New fields RECLASS_ITEM_ON_OPEN_STOCK_COUNTS and RECLASS_ITEM_ON_APPROVED_ORDER. |
Enhanced Audit Tracking Across Key Database Tables
As part of this update, standard audit columns have been added to key tables in Merchandising and Sales Audit to capture record creation and last update details as mentioned below. These fields help downstream integrations, RDS reporting, and Support teams to identify incremental changes directly from source business data tables. This improves traceability for delta extraction, reconciliation, and reporting.
Columns Added:
-
CREATE_ID
-
CREATE_DATETIME
-
LAST_UPDATE_ID
-
LAST_UPDATE_DATETIME
Tables in-scope:
-
Merchandising
-
FUTURE_COST
-
SOURCE_DLVRY_SCHED_DAYS
-
SOURCE_DLVRY_SCHED
-
-
Sales Audit
-
SA_TRAN_DAY
-
SA_TRAN_DISC
-
SA_TRAN_ITEM
-
SA_TRAN_ITEM_ATTRIB
-
SA_TRAN_PAYMENT
-
SA_TRAN_TENDER_ATTRIB
-
SA_TRAN_TENDER
-
SA_TRAN_HEAD (Only CREATE_ID and CREATE_DATETIME)
-
Corresponding Revision tables in-scope:
-
Sales Audit
-
SA_TRAN_DISC_REV
-
SA_TRAN_ITEM_REV
-
SA_TRAN_PAYMENT_REV
-
SA_TRAN_TENDER_REV
-
SA_TRAN_HEAD_REV (Only CREATE_ID and CREATE_DATETIME)
-
Corresponding History tables in-scope:
-
Merchandising
-
FUTURE_COST_PRG_HIST
-
-
Sales Audit
-
SA_TRAN_DISC_HIST
-
SA_TRAN_DISC_REV_HIST
-
SA_TRAN_ITEM_HIST
-
SA_TRAN_ITEM_REV_HIST
-
SA_TRAN_PAYMENT_HIST
-
SA_TRAN_PAYMENT_REV_HIST
-
SA_TRAN_TENDER_ATTRIB_HIST
-
SA_TRAN_TENDER_HIST
-
SA_TRAN_TENDER_REV_HIST
-
SA_TRAN_ITEM_ATTRIB_HIST
-
SA_STORE_DAY_HIST
-
SA_TRAN_HEAD_HIST (Only CREATE_ID and CREATE_DATETIME)
-
SA_TRAN_HEAD_REV_HIST (Only CREATE_ID and CREATE_DATETIME)
-
RDS/DAS views in-scope
-
RDS_WV_FUTURE_COST, DAS_WV_FUTURE_COST
-
RDS_WV_SOURCE_DLVRY_SCHED_DAYS, DAS_WV_SOURCE_DLVRY_SCHED_DAYS
-
RDS_WV_SOURCE_DLVRY_SCHED, DAS_WV_SOURCE_DLVRY_SCHED
-
RDS_WV_SA_TRAN_DISC, DAS_WV_SA_TRAN_DISC
-
RDS_WV_SA_TRAN_ITEM, DAS_WV_SA_TRAN_ITEM
-
RDS_WV_SA_TRAN_PAYMENT, DAS_WV_SA_TRAN_PAYMENT
-
RDS_WV_SA_TRAN_TENDER_ATTRIB, DAS_WV_SA_TRAN_TENDER_ATTRIB
-
RDS_WV_SA_TRAN_TENDER, DAS_WV_SA_TRAN_TENDER
-
RDS_WV_SA_TRAN_ITEM_ATTRIB, DAS_WV_SA_TRAN_ITEM_ATTRIB
-
RDS_WV_SA_STORE_DAY, DAS_WV_SA_STORE_DAY
-
RDS_WV_SA_TRAN_ITEM_REV, DAS_WV_SA_TRAN_ITEM_REV
-
RDS_WV_SA_TRAN_DISC_REV, DAS_WV_SA_TRAN_DISC_REV
-
RDS_WV_SA_TRAN_PAYMENT_REV, DAS_WV_SA_TRAN_PAYMENT_REV
-
RDS_WV_SA_TRAN_TENDER_REV, DAS_WV_SA_TRAN_TENDER_REV
-
RDS_WV_SA_TRAN_HEAD, DAS_WV_SA_TRAN_HEAD
-
RDS_WV_SA_TRAN_HEAD_REV, DAS_WV_SA_TRAN_HEAD_REV
DAS/RDS Updates
| Application Table | DAS/RDS Table or View | Change Type | Change Description |
|---|---|---|---|
|
FUTURE_COST |
DAS_WV_FUTURE_COST |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
FUTURE_COST |
RDS_WV_FUTURE_COST |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_STORE_DAY |
RDS_WV_SA_STORE_DAY |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_STORE_DAY |
DAS_WV_SA_STORE_DAY |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_DISC |
RDS_WV_SA_TRAN_DISC |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_DISC |
DAS_WV_SA_TRAN_DISC |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_DISC_REV |
RDS_WV_SA_TRAN_DISC_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_DISC_REV |
DAS_WV_SA_TRAN_DISC_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_HEAD |
DAS_WV_SA_TRAN_HEAD |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME |
|
SA_TRAN_HEAD |
RDS_WV_SA_TRAN_HEAD |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME |
|
SA_TRAN_HEAD_REV |
RDS_WV_SA_TRAN_HEAD_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME |
|
SA_TRAN_HEAD_REV |
DAS_WV_SA_TRAN_HEAD_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME |
|
SA_TRAN_ITEM |
RDS_WV_SA_TRAN_ITEM |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_ITEM |
DAS_WV_SA_TRAN_ITEM |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_ITEM_ATTRIB |
RDS_WV_SA_TRAN_ITEM_ATTRIB |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_ITEM_ATTRIB |
DAS_WV_SA_TRAN_ITEM_ATTRIB |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_ITEM_REV |
RDS_WV_SA_TRAN_ITEM_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_ITEM_REV |
DAS_WV_SA_TRAN_ITEM_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_PAYMENT |
DAS_WV_SA_TRAN_PAYMENT |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_PAYMENT |
RDS_WV_SA_TRAN_PAYMENT |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_PAYMENT_REV |
RDS_WV_SA_TRAN_PAYMENT_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_PAYMENT_REV |
DAS_WV_SA_TRAN_PAYMENT_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_TENDER |
RDS_WV_SA_TRAN_TENDER |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_TENDER |
DAS_WV_SA_TRAN_TENDER |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_TENDER_ATTRIB |
DAS_WV_SA_TRAN_TENDER_ATTRIB |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_TENDER_ATTRIB |
RDS_WV_SA_TRAN_TENDER_ATTRIB |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_TENDER_REV |
RDS_WV_SA_TRAN_TENDER_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SA_TRAN_TENDER_REV |
DAS_WV_SA_TRAN_TENDER_REV |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SOURCE_DLVRY_SCHED |
RDS_WV_SOURCE_DLVRY_SCHED |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SOURCE_DLVRY_SCHED |
DAS_WV_SOURCE_DLVRY_SCHED |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SOURCE_DLVRY_SCHED_DAYS |
RDS_WV_SOURCE_DLVRY_SCHED_DAYS |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
|
SOURCE_DLVRY_SCHED_DAYS |
DAS_WV_SOURCE_DLVRY_SCHED_DAYS |
Update |
Added audit columns: CREATE_ID, CREATE_DATETIME, LAST_UPDATE_ID, LAST_UPDATE_DATETIME |
Included Invoice Attachment Link in Outbound File Publication Workflows
As part of this update, invoice attachment links will be included in the outbound Accounts Payable (AP) file, for both the publication workflow to Object Storage as well as the direct integration with Oracle Fusion Cloud Payables through ReST services. This enhancement ensures that invoice attachment references are consistently communicated across both integration methods from Invoice Matching, improving document accessibility and supporting more efficient downstream financial processing.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
MFCS to CFIN Account Payload Integration |
Update |
REST Service |
ATTACHMENT_EXT_URL |
In the CSV file that is publish to Account Payable, an additional column has been added to hold invoice attachment URL |
New APIs for Bulk Document Approval, Unmatching and Deletion in Invoice Matching
This update introduces a set of ReST APIs to simplify high volume document processing in Invoice Matching by enabling bulk approval, unmatching, and deletion, thereby reducing manual effort.
Users now can perform the following actions:
-
Approve eligible chargeback documents, including Credit Note Requests (CNRs) and Debit Memos, from Submitted to Approved status in a single operation, with the appropriate approval privileges.
-
Return merchandise documents to Unmatched status before posting.
-
Delete eligible documents in bulk, subject to document type, status, and existing business validations.
All operations continue to enforce existing business rules and security controls.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
POST /services/private/Reim/document/v1/approve |
New |
REST Service |
requests[].requestId, document, type, vendor,doc_date. response[].processId,injectId,status,errors, |
New API to approve eligible deal documents in a single request. Returns an outcome and any business errors per document, along with process and inject IDs for tracking and viewing errors. |
|
POST /services/private/Reim/document/v1/delete |
New |
REST Service |
requests[].requestId, document, type, vendor,doc_date. response[].processId,injectId,status,errors, |
New API to delete eligible documents in a single request using the existing delete validations. Returns an outcome and any business errors per document, with tracking IDs. |
|
POST /services/private/Reim/document/v1/unmatch |
New |
REST Service |
requests[].requestId, document, type, vendor,doc_date. response[].processId,injectId,status,errors, |
New API to unmatch eligible documents in a single request using the existing Match Inquiry flow. Returns an outcome and any business errors per document, with tracking IDs. |
Improved Pricing Web Services Error Handling
Pricing web services now return conflict check errors in the response when price events are sent for approval, allowing for better error handling and streamlined processing.
Integration
| API Name | Change Type | Integration Type | Field Name | Change Description |
|---|---|---|---|---|
|
Clearance Induction |
New |
REST Service |
returnConflictErrorsInd |
Valid Values are Y/N. This is used to fetch the CC errors after the conflict check process. This is an Optional field. |
|
Price Change Induction |
New |
REST Service |
returnConflictErrorsInd |
Valid Values are Y/N. This is used to fetch the CC errors after the conflict check process. This is an Optional field. |
Brazil Tax Reform Fiscal Documents and Events
This update adds processing logic for credit notes associated with IBS and CBS tax offsets on returns, debit notes associated with inventory adjustments, and new fiscal events for exception scenarios in customer orders, inventory adjustments, returns to vendor, customer returns, and returns to warehouse. Fiscal events are represented by their own RFMCS document and remain linked to the fiscal document to which they apply.
How the fiscal event flow works
-
An originating process submits a fiscal event request. The request identifies the target NF-e by the access key and RFMCS document ID, where available. It also identifies the target workflow, event code, and an origin request code that must remain stable on retries.
-
RFMCS creates a separate event document, resolves the target NF-e, and checks that the target document and event are eligible. The event document has its own identifier and does not replace the original NF-e.
-
RFMCS derives the event payload from the request and the target document. It validates the resulting fiscal event data before passing the event for submission through the configured fiscal integration.
-
RFMCS processes the submission response and archives the event and response information. Operators can use the document and workflow views to follow the event document and investigate rejected or incomplete steps.