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?
Bill Back and Bill Back Rebate Deal Enhancements Merchandising Large Enabled No
Capability to Manage Selling Phase Start Date at Item/Store Level Merchandising Small Disabled Yes
Configurable Attribute Mapping for Financial Data Publication Merchandising Large Disabled Yes
Data Conversion Changes to Support Suggested Retail at Item Location Merchandising Small Enabled No
Dynamic Response Field Filtering in Merchandising Publish APIs Merchandising Small Enabled No
Enhanced Transaction Data API to Process Records for Non-Ranged Item Locations Merchandising Small Enabled No
Extended Control for Duplicate and Missing Transaction Validation Sales Audit Small Enabled No
Merchandising ReST Service for General Ledger Cross Reference Maintenance Merchandising Small Enabled No
New ReST Service to Maintain General Ledger Cross Reference in Sales Audit Sales Audit Small Enabled No
Provide Functionality/Mechanism to Avoid Month-End Abort of General Ledger Batches When There Are Missing Financial Mapping Merchandising Small Enabled No
Support for General Ledger Cross Reference Dynamic Mapping Merchandising Large Disabled Yes
Fiscal Management Support for Financial Integration Fiscal Management Small Enabled No
Fiscal Management Support for Fiscal Document Data Migration Fiscal Management Small Enabled No
Invoicing Enhancements for Allowance Deals Invoice Matching Larger Disabled Yes
Support for User Specific Number and Date Format Preferences for Data Loading in Pricing Pricing Larger Disabled Yes

Bill Back and Bill Back Rebate Deal Enhancements

This cloud service update introduces multiple enhancements to Bill Back and Bill Back Rebate type of deals which will allow users to:

  • Define purchase order specific deals
  • Use the Suggested Retail value at the item location level for sales-based deals as an alternative to the Actual Selling Retail value
  • Use the invoice-matched quantity as an additional deal-invoicing basis for purchase-based deals
  • Have a single bill generated for the entire period at deal closure time
  • Associate a tax region with a deal different from ones linked with locations and supplier associated with the deal
  • Specify whether to include franchise locations in sales or purchase-based deals
Integration
API Name Change Type Integration Type Field Name Change Description
/services/item/locations/update Update REST Service MFG_SUG_RETAIL_INCL_TAX, MFG_SUG_RETAIL_EXCL_TAX New fields added
Item Location Create Update RIB Message MFG_SUG_RETAIL_EXCL_TAX, MFG_SUG_RETAIL_INCL_TAX New fields added
Item Location Update Update RIB Message MFG_SUG_RETAIL_EXCL_TAX, MFG_SUG_RETAIL_INCL_TAX New fields added
/services/item/locations/create Update REST Service MFG_SUG_RETAIL_INCL_TAX, MFG_SUG_RETAIL_EXCL_TAX New fields added
Code Impact
Code Type Code Type Description Code Code Description New or Updated? Delivered
DLBP Code that identifies the bill-back period D Deal End New Enabled
AALC Indicates when the deal component should be applied I Invoice Matched New Enabled
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
ITEM_LOC RDS_WV_ITEM_LOC Update New fields "MFG_SUG_RETAIL_INCL_TAX", "MFG_SUG_RETAIL_EXCL_TAX" added
DEAL_HEAD DAS_WV_DEAL_HEAD Update

New fields USE_MFG_SUG_RETAIL_IND, INCLUDE_FRANCHISE_PURCH_IND, INCLUDE_FRANCHISE_SALES_IND and VAT_REGION are added.

Column comment updated for BILL_BACK_PERIOD.
DEAL_HEAD RDS_WV_DEAL_HEAD Update

New fields USE_MFG_SUG_RETAIL_IND, INCLUDE_FRANCHISE_PURCH_IND, INCLUDE_FRANCHISE_SALES_IND and VAT_REGION are added.

Column comment updated for BILL_BACK_PERIOD.
ITEM_LOC DAS_WV_ITEM_LOC Update New fields "MFG_SUG_RETAIL_INCL_TAX", "MFG_SUG_RETAIL_EXCL_TAX" added

Capability to Manage Selling Phase Start Date at Item/Store Level

This cloud service update introduces the ability to maintain a date that marks the beginning of the selling phase for an item at a location. This date can be used as a basis by Lifecycle Pricing Optimization (LPO) Cloud Service to determine the appropriate date on which the item can be evaluated for markdown optimization.

The Item Location Selling Phase Start Date is intended to be a fluid date and contains the latest/most recent date upon which a receipt of significance occurred at the location. It may be reset over time based on type and quantity of receipt that can be configured at the item/location level. Customers can choose whether receipts resulting from direct-to-store orders, store-to-store transfers, warehouse-to-store transfers/allocations or a combination of these, along with minimum units on the transaction, will trigger an update. Additionally, this date can be kept static by setting available options at the item/location level and expect it to be updated by sending from an external source using the Item/Location API. These new fields will be made available in RDS/DAS to be utilized by downstream applications.

This feature is controlled by a system level indicator and will initially be set as No.

Steps to Enable
  1. Navigate to Application Administration → System Options Screen.
  2. Navigate to Foundation section.
  3. Enable Capture Selling Phase Start Date within Item Location section.
System Options
Attribute Name New or Update? Attribute Description Default Value
CAPTURE_IL_SELL_PHASE_START_DATE New This field indicates whether or not the feature to capture Item Location Selling Phase Start Date is enabled in the system. N
UPD_IL_SELL_PHASE_START_DATE_ON_CLEAR_RESET Update This specifies if the Selling Phase Start Date should be updated or not when a clearance reset is executed. This can only be set to Yes (Y) if the Capture Item Location Selling Phase Start Date option is Yes (Y). N
Integration
API Name Change Type Integration Type Field Name Change Description
/services/item/locations/update Update REST Service New fields added

New fields "SELLING_PHASE_START_DATE","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.
Item Location Create Update RIB Message New fields added

New fields "SELLING_PHASE_START_DATE","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/item/locations/create Update REST Service New fields added

New fields "SELLING_PHASE_START_DATE","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.
Item Location Update Update RIB Message New fields added

New fields "SELLING_PHASE_START_DATE","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.
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
SYSTEM_OPTIONS DAS_WV_SYSTEM_OPTNS Update

New fields "CAPTURE_IL_SELL_PHASE_START_DATE","UPD_IL_SELL_PHASE_START_DATE_ON_CLEAR_RESET",

added.
SYSTEM_OPTIONS RDS_WV_SYSTEM_OPTIONS Update

New fields "CAPTURE_IL_SELL_PHASE_START_DATE","UPD_IL_SELL_PHASE_START_DATE_ON_CLEAR_RESET",

added.
ITEM_LOC RDS_WV_ITEM_LOC Update

New fields "SELLING_PHASE_START_DATE","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.
SUBCLASS DAS_WV_SUBCLASS Update

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.
ITEM_LOC DAS_WV_ITEM_LOC Update

New fields "SELLING_PHASE_START_DATE","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.
SUBCLASS RDS_WV_SUBCLASS Update

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.
FOUNDATION_UNIT_OPTIONS RDS_WV_FOUNDATION_UNIT_OPTIONS Update

New fields "CAPTURE_IL_SELL_PHASE_START_DATE","UPD_IL_SELL_PHASE_START_DATE_ON_CLEAR_RESET",

added.
FOUNDATION_UNIT_OPTIONS DAS_WV_FOUNDATION_UNIT_OPTIONS Update

New fields "CAPTURE_IL_SELL_PHASE_START_DATE","UPD_IL_SELL_PHASE_START_DATE_ON_CLEAR_RESET",

added.

Configurable Attribute Mapping for Financial Data Publication

This cloud service update introduces the flexibility to map attributes and reference fields between Merchandising Outbound Staging table for General Ledger (that is, STG_FIF_GL_DATA) and the staging table on Cloud Financials side (that is, GL_INTERFACE). These mapping can be managed through a spreadsheet-based template and will drive transformation of data from STG_FIF_GL_DATA into a new outbound table used for creating import file for Cloud Financial General Ledger.

Steps to Enable

Enable the following jobs in POM:

  • FIF_GL_PUBLISH_JOB
  • FIF_GL_PUBLISH_EXTRACT_JOB
  • FIF_GL_PUBLISH_EXTRACT_ADHOC_JOB
  • FIF_GL_PUBLISH_PURGE_JOB
System Options
Attribute Name New or Update? Attribute Description Default Value
GL_PUBLISH_PURGE_DAYS New This field indicates the number of days that financial records are retained in Merchandising. Default value is 14 days and must not be more than 99. 14
Batch Schedule
Process Name Process Type New or Updated? Delivered
FIF_GL_PUBLISH_EXTRACT_PROCESS Nightly New Disabled
FIF_GL_PUBLISH_EXTRACT_PROCESS_ADHOC Ad Hoc New Disabled
FIF_GL_PUBLISH_PURGE_CYCLE_PROCESS Background New Disabled
FIF_GL_PUBLISH_PROCESS Nightly New Disabled
Code Impact
Code Type Code Type Description Code Code Description New or Updated? Delivered
MFRA Merch Financials Reference and Attribute Fields REF5 REFERENCE5 New Enabled
MFRA Merch Financials Reference and Attribute Fields ATTR1 ATTRIBUTE1 New Enabled
MFRA Merch Financials Reference and Attribute Fields ATTR4 ATTRIBUTE4 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF8 REFERENCE8 New Enabled
MFRA Merch Financials Reference and Attribute Fields ATTR2 ATTRIBUTE2 New Enabled
MFRA Merch Financials Reference and Attribute Fields ATTR5 ATTRIBUTE5 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF1 REFERENCE1 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF2 REFERENCE2 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF3 REFERENCE3 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF7 REFERENCE7 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF10 REFERENCE10 New Enabled
MFRA Merch Financials Reference and Attribute Fields ATTR3 ATTRIBUTE3 New Enabled
MFRA Merch Financials Reference and Attribute Fields ATTR6 ATTRIBUTE6 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF4 REFERENCE4 New Enabled
MFRA Merch Financials Reference and Attribute Fields REF6 REFERENCE6 New Enabled
MFRA Merch Financials Reference and Attribute Fields REFTRC REFERENCE_TRACE_ID New Enabled
MFRA Merch Financials Reference and Attribute Fields REF9 REFERENCE9 New Enabled
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
FIF_GL_PUBLISH DAS_WV_FIF_GL_PUBLISH New This is a view for replicating FIF_GL_PUBLISH to DAS (Data Access Schema).
PURGE_CONFIG_OPTIONS DAS_WV_PURGE_CFG_OPTNS Update Added gl_publish_purge_days column.
PURGE_CONFIG_OPTIONS RDS_WV_PURGE_CONFIG_OPTIONS Update Added gl_publish_purge_days column.
FIF_PUBLISH_STATUS DAS_WV_FIF_PUBLISH_STATUS New This is a view for replicating FIF_PUBLISH_STATUS to DAS (Data Access Schema).
FIF_GL_PUBLISH RDS_WV_FIF_GL_PUBLISH New This is a view for replicating FIF_GL_PUBLISH to RDS (Retail Data Store).
SYSTEM_OPTIONS DAS_WV_SYSTEM_OPTNS Update Added gl_publish_purge_days column.
SYSTEM_OPTIONS RDS_WV_SYSTEM_OPTIONS Update Added gl_publish_purge_days column.
FIF_OUT_ATTRIBUTE_MAPPING DAS_WV_FIF_OUT_ATTRIBUTE_MAPPING New This is a view for replicating FIF_OUT_ATTRIBUTE_MAPPING to DAS (Data Access Schema).
FIF_OUT_ATTRIBUTE_MAPPING RDS_WV_FIF_OUT_ATTRIBUTE_MAPPING New This is a view for replicating FIF_OUT_ATTRIBUTE_MAPPING to RDS (Retail Data Store).
FIF_PUBLISH_STATUS RDS_WV_FIF_PUBLISH_STATUS New This is a view for replicating FIF_PUBLISH_STATUS to RDS (Retail Data Store).

Data Conversion Changes to Support Suggested Retail at Item Location

The following fields have been added to the ITEM_RANGING entity to support Merchandising enhancements for add suggested retail at item location level :

  1. MFG_SUG_RETAIL_INCL_TAX
  2. MFG_SUG_RETAIL_EXCL_TAX

Customer should use the new data conversion template for the modified entity.

Dynamic Response Field Filtering in Merchandising Publish APIs

With this cloud service update, Merchandising Publish APIs have been enhanced to offer a more targeted data retrieval approach by introducing the include and exclude query parameters. These parameters allow you to selectively choose which data fields to be included or excluded in the API response, ensuring it contains only the relevant information. When the include parameter is specified, the API response will contain only the requested fields, providing a concise data response. Conversely, the exclude parameter ensures that all fields are returned, except those explicitly excluded, allowing for a more comprehensive yet focused dataset.

Furthermore, webhook publishing has been upgraded to support dynamic response filtering through the queryParameter field. This field accepts the include and exclude parameters, allowing webhooks to fetch only the necessary data through internal Publish APIs, ensuring that only the required fields are published to the listener URL.

Integration
API Name Change Type Integration Type Field Name Change Description
Multiple Publish API Update REST Service include New Query Parameter
Multiple Publish API Update REST Service exclude New Query Parameter
Manage Webhooks Update REST Service queryParamter New attribute to provide include or exclude field list
Get Webhook Configuration Update REST Service queryParameter New field in the response to view the configured query parameter

Enhanced Transaction Data API to Process Records for Non-Ranged Item Locations

This cloud service update introduces the ability to upload transaction data records through the Transaction Data API for item location combinations that are not ranged and export them to General Ledger specifically for customer-defined transaction codes.

Extended Control for Duplicate and Missing Transaction Validation

This cloud service update introduces enhanced flexibility to manage validation for Duplicate and Missing Transactions in Sales Audit. The existing system option configuration is enhanced to allow opting for Duplicate and Missing Transaction checks independently.

In the System Option screen, choose a value for Check For Duplicate And Missing Transactions

  • Both (Y)- Check for both Duplicate and Missing Transactions
  • None (N)- Do not check for Duplicate or Missing Transactions
  • Only Duplicate (D)- Only check for Duplicate Transactions
  • Only Missing (M)- Only check for missing Transactions.
System Options
Attribute Name New or Update? Attribute Description Default Value
CHECK_DUP_MISS_TRAN Update This field indicates whether to check for missing and/or duplicate transactions, or neither. Valid values are N not to check any, Y to validate both missing and duplicate transactions, the following options only valid when DUP_MISS_TRAN_DB_CHECK_IND is set to Y, D to only check duplicate transactions and M to only check missing transactions. Y
Code Impact
Code Type Code Type Description Code Code Description New or Updated? Delivered
CMDT Checks for Duplicate or Missing Transactions Y Both Update Enabled
CDMT Checks for Duplicate or Missing Transactions N None Update Enabled
CDMT Checks for Duplicate or Missing Transactions M Only Missing New Enabled
CDMT Checks for Duplicate or Missing Transactions D Only Duplicate New Enabled

Merchandising ReST Service for General Ledger Cross Reference Maintenance

This cloud service update introduces a new ReST service for creation and management of General Ledger Cross Reference records in Merchandising. It complements the existing capability of managing these records through the spreadsheet upload process.

Integration
API Name Change Type Integration Type Field Name Change Description
Manage Merchandising General Ledger Cross Reference New REST Service /financials/generalLedger/crossReference/manage New General Ledger Cross Reference Upload Service has been added that allows create, update and delete of cross reference data in Merchandising

New ReST Service to Maintain General Ledger Cross Reference in Sales Audit

This cloud service update introduces a new ReST service for creation and management of General Ledger Cross Reference records in Sales Audit. It complements the existing capability of managing these records through the spreadsheet upload process.

Integration
API Name Change Type Integration Type Field Name Change Description
Manage Sales Audit General Ledger Cross Reference New REST Service /ResaReSTServices/services/private/Resa/manageGlCrossReference New General Ledger Cross Reference Upload Service has been added that allows creation, modification and delete of cross reference data in Sales Audit

Provide Functionality/Mechanism to Avoid Month-End Abort of General Ledger Batches When There Are Missing Financial Mapping

Key Changes:

  1. Removal of EOM Batch Failure Logic
    • The existing EOM batch failure handling logic has been removed from the following programs:
      • fifgldn1
      • fifgldn2
      • fifgldn3
  2. Enhanced Error Handling

    • New logic has been introduced in fifgldn1 and fifgldn2 to increment eom_add_days dynamically based on the newly introduced EXTEND_EOM_ADD_DAYS parameter if there are any unmapped transactions present and absence of clearance account when date = on the system_options.next_eom_date + eom_add_days.

    • New logic has been introduced in fifgldn1, fifgldn2, and fifgldn3 to move error records from tran_data_errors,month_data_errors to stg_fif_gl_eom_errors on last day of the month. That is, vdate = system_options.next_eom_date + eom_add_days + extend_eom_add_days
  3. Data Purge Mechanism

    • Records from stg_fif_gl_eom_errors will be automatically purged when salprg.pc is executed, using the retention period specified in system_options.tran_data_retained_days_no.

  4. Schema Changes: Two new fields have been added to system_options view and financial_unit_options:

    • extend_eom_add_days

    • orig_eom_add_days

    • A new table stg_fif_gl_eom_errors has been introduced to store EOM batch error records

      2 new fields and new table are replicated to DAS/RDS

      For DAS/RDS Replication, refer to Enh 37792989, and Enh 37820942

  5. Management of new system_optoins fields - org_eom_add_days,extended_eom_days
    • During deployment:

      1. system_options.org_eom_add_days will be initialized with the current value of system_options.eom_add_days and system_options.extended_eom_days will be defaulted to 0.

    • •Post-deployment behavior:

      1. Existing Close Month After field in the UI will be mapped to system_options.org_eom_add_days and new Force Close Month After Additional field will be mapped to system_options.extend_eom_add_days

      2. When a user updates the Close Month After field in the UI, then both the system_options.org_eom_add_days and system_options.eom_add_days fields will be updated with the user-keyed-in value.

  6. Backend Update Requirement
    • In this release, customers are expected to raise a Service Request (SR) to update the value of system_options.extend_eom_add_days from the backend, as this is not currently available for UI update.
  7. Resetting eom_add_days on Actual EOM Date
    • On the actual EOM date, eom_add_days will be automatically reset to its original value (orig_eom_add_days).
    • This logic has been implemented in the dtesys batch.

DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
STG_FIF_GL_EOM_ERRORS RDS_WV_STG_FIF_GL_EOM_ERRORS New Added table for RDS Replication
STG_FIF_GL_EOM_ERRORS DAS_WV_STG_FIF_GL_EOM_ERRORS New Added table for DAS replication

Support for General Ledger Cross Reference Dynamic Mapping

This cloud service update introduces an option to maintain dynamic segments for General Ledger (GL) Cross Reference records in Merchandising. This is intended to provide an easier means of managing GL Cross Reference records where the merchandise hierarchy and location form part of the account combination. This feature is controlled by a system-level indicator and will initially be set as No.

This new feature provides the flexibility to classify specific account segments as dynamic for a given set of books and derive the value of such segments based on specific keys in the Merchandising transaction data (Department, Class, Subclass, Location, Reference number). For each segment marked dynamic, the system will expect mappings for the segment values to be defined independent of the cross-reference combination. Such GL Cross Reference records will not require values to be mandatorily specified for segments that are defined as dynamic. Merchandising batch programs will use both the Cross Reference records and the mappings defined for the dynamic segments to automatically build the account combinations for each value of these dynamic segments. This eliminates the need for the user to explicitly define General Ledger cross mappings for all dynamic segment values. For example, if a location is defined as a dynamic segment and supports ‘n’ distinct values and ‘x’ represents the number of GL combinations involving segments other than location, then the user would need to specify define just [n+x] mapping entries, instead of the [ n*x] entries they would need to make in the absence of dynamic segments. Even with this feature enabled in Merchandising, account combinations with values specified even for the dynamic segments as an exception can be defined. These fully formed combinations will not be overwritten by the Merchandising batch while building the account combinations.

Merchandising will continue to support the existing GL cross-reference management process, which requires segment combinations to be fully specified for each mapping if this feature is not enabled.

Steps to Enable
  • In the System Options screen, check the Use Dynamic Segments checkbox under Financials.
  • In POM, enable FIF_GL_DYNAMIC_MAP_PROCESS and FIF_GL_DYNAMIC_MAP_ADHOC_PROCESS.
System Options
Attribute Name New or Update? Attribute Description Default Value
USE_DYNAMIC_SEGMENTS New This column indicates if dynamic segments are being used for GL cross references. Valid values are: Y (Yes), N (No). N
Batch Schedule
Process Name Process Type New or Updated? Delivered
FIF_GL_DYNAMIC_MAP_ADHOC_PROCESS Ad Hoc New Disabled
FIF_GL_DYNAMIC_MAP_PROCESS Nightly New Disabled
Code Impact
Code Type Code Type Description Code Code Description New or Updated? Delivered
DSTP Dynamic Segment Types DEPT Department New Enabled
DSTP Dynamic Segment Types GLRF GL Reference No. New Enabled
DSTP Dynamic Segment Types CLS Class New Enabled
DSTP Dynamic Segment Types LOC Location New Enabled
DSTP Dynamic Segment Types SCLS Subclass New Enabled
Security
Privileges
Priv Name Change Type Priv Description Parent Duty
MAINTAIN_DYNAMIC_SEGMENTS_PRIV New This privilege grants users access to the Manage Dynamic Segments screen and the ability to upload and download dynamic segments for a set of books. RMS_DYNAMIC_SEGMENTS_MGMT_DUTY
VIEW_DYNAMIC_SEGMENTS_PRIV New This privilege grants users access to the Manage Dynamic Segments screen and the ability to download and view dynamic segments for each set of books. RMS_DYNAMIC_SEGMENTS_INQUIRY_DUTY
Duties
Duty Name Change Type Duty Description Child Duty Base Role
RMS_DYNAMIC_SEGMENTS_MGMT_DUTY New A duty for uploading and downloading dynamic segments via the Manage Dynamic Segments screen. RMS_DYNAMIC_SEGMENTS_INQUIRY_DUTY RMS_APPLICATION_ADMINISTRATOR_JOB, DATA_STEWARD_JOB FINANCIAL_ANALYST_JOB, FINANCIAL_MANAGER_JOB,
RMS_DYNAMIC_SEGMENTS_INQUIRY_DUTY New A duty for downloading and viewing the dynamic segments via the Manage Dynamic Segments screen.
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
FIF_DYNAMIC_SEGMENT_DEPT DAS_WV_FIF_DYNAMIC_SEGMENT_DEPT New This is a view for replicating FIF_DYNAMIC_SEGMENT_DEPT to DAS (Data Access Schema).
FIF_DYNAMIC_SEGMENT_CLASS RDS_WV_FIF_DYNAMIC_SEGMENT_CLASS New This is a view for replicating FIF_DYNAMIC_SEGMENT_CLASS to RDS (Retail Data Store).
FIF_DYNAMIC_SEGMENT_SUBCLASS DAS_WV_FIF_DYNAMIC_SEGMENT_SUBCLASS New This is a view for replicating FIF_DYNAMIC_SEGMENT_SUBCLASS to DAS (Data Access Schema).
FIF_GL_CROSS_REF RDS_WV_FIF_GL_CROSS_REF Update Added BASE_IND, UPDATE_IND, PRIORITY, GROUP_ID columns which will be used for processing dynamic segments.
FINANCIAL_UNIT_OPTIONS DAS_WV_FINANCIAL_UNIT_OPTNS Update Added USE_DYNAMIC_SEGMENTS column.
FIF_DYNAMIC_SEGMENT DAS_WV_FIF_DYNAMIC_SEGMENT New This is a view for replicating FIF_DYNAMIC_SEGMENT to DAS (Data Access Schema).
FIF_DYNAMIC_SEGMENT_REF_NO RDS_WV_FIF_DYNAMIC_SEGMENT_REF_NO New This is a view for replicating FIF_DYNAMIC_SEGMENT_REF_NO to RDS (Retail Data Store).
FIF_DYNAMIC_SEGMENT RDS_WV_FIF_DYNAMIC_SEGMENT New This is a view for replicating FIF_DYNAMIC_SEGMENT to RDS (Retail Data Store).
FIF_DYNAMIC_SEGMENT_DEPT RDS_WV_FIF_DYNAMIC_SEGMENT_DEPT New This is a view for replicating FIF_DYNAMIC_SEGMENT_DEPT to RDS (Retail Data Store).
FIF_DYNAMIC_SEGMENT_REF_NO DAS_WV_FIF_DYNAMIC_SEGMENT_REF_NO New This is a view for replicating FIF_DYNAMIC_SEGMENT_REF_NO to DAS (Data Access Schema).
FIF_GL_CROSS_REF_DYNAMIC DAS_WV_FIF_GL_CROSS_REF_DYNAMIC New This is a view for replicating FIF_GL_CROSS_REF_DYNAMIC to DAS (Data Access Schema).
FIF_GL_CROSS_REF_DYNAMIC RDS_WV_FIF_GL_CROSS_REF_DYNAMIC New This is a view for replicating FIF_GL_CROSS_REF_DYNAMIC to RDS (Retail Data Store).
SYSTEM_OPTIONS DAS_WV_SYSTEM_OPTNS Update Added USE_DYNAMIC_SEGMENTS column from FINANCIAL_UNIT_OPTIONS.
FIF_DYNAMIC_SEGMENT_CLASS DAS_WV_FIF_DYNAMIC_SEGMENT_CLASS New This is a view for replicating FIF_DYNAMIC_SEGMENT_CLASS to DAS (Data Access Schema).
FIF_DYNAMIC_SEGMENT_SUBCLASS RDS_WV_FIF_DYNAMIC_SEGMENT_SUBCLASS New This is a view for replicating FIF_DYNAMIC_SEGMENT_SUBCLASS to RDS (Retail Data Store).
FINANCIAL_UNIT_OPTIONS RDS_WV_FINANCIAL_UNIT_OPTIONS Update Added USE_DYNAMIC_SEGMENTS column.
SYSTEM_OPTIONS RDS_WV_SYSTEM_OPTIONS Update Added USE_DYNAMIC_SEGMENTS column from FINANCIAL_UNIT_OPTIONS.
FIF_DYNAMIC_SEGMENT_LOC DAS_WV_FIF_DYNAMIC_SEGMENT_LOC New This is a view for replicating FIF_DYNAMIC_SEGMENT_LOC to DAS (Data Access Schema).
FIF_DYNAMIC_SEGMENT_LOC RDS_WV_FIF_DYNAMIC_SEGMENT_LOC New This is a view for replicating FIF_DYNAMIC_SEGMENT_LOC to RDS (Retail Data Store).
FIF_GL_CROSS_REF DAS_WV_FIF_GL_CROSS_REF Update Added BASE_IND, UPDATE_IND, PRIORITY, GROUP_ID columns which will be used for processing dynamic segments.

Fiscal Management Support for Financial Integration

Retail Fiscal Management Cloud Service (RFMCS) fiscal document processing workflows is updated to generate data for financial integration. New workflow steps added to existing fiscal document processing workflows to generate financial data required to the integration with financial systems. This enhancement does not handle the integration itself, but only the generation of data necessary.

Batch Schedule
Process Name Process Type New or Updated? Delivered
RFM_CFIN_ADHOC_JOB Ad Hoc New Disabled
RFM_CFIN_CYCLE_JOB Cyclic New Disabled

Fiscal Management Support for Fiscal Document Data Migration

New REST-based API is introduced to support fiscal document data migration in RFMCS. The fiscal document data to be migrated from legacy systems is meant to support the generation of returns and RMA fiscal documents in RFMCS.

Integration
API Name Change Type Integration Type Field Name Change Description
Ledger Get Service New REST Service New This service exports a bulk of ledger records and its tax information from the RFMCS Fiscal Document Management feature. The response payload will have pagination
Document Upload Service New REST Service New This service uploads fiscal document data from legacy systems into RFMCS, to support the generation of returns and RMA documents that require reference fiscal documents

Invoicing Enhancements for Allowance Deals

This cloud service update introduces enhancements to Invoice Matching Cloud Service to support a workflow to validate and match the allowance components received in the supplier invoice against the allowance components applied to a purchase order. This includes matching of invoices with or without allowances specified for items that are part of valid allowance deals in Merchandising. While the invoices with allowance value in the document will be validated against the allowance on the purchase order, when the vendor does not include the allowance discount line on the invoice for item/locations on valid deal, the retailer will still be able to take the discount and show this in the remittance advice and can create a bill back. This feature is controlled by a system-level indicator and will initially be set as No.

Steps to Enable

Check system option Allowance Matching to enable this feature.

System Options
Attribute Name New or Update? Attribute Description Default Value
CREDIT_NOTE_REQ_PREFIX_ALLOW New This column holds the prefix that indicates a document is a Credit Note Request due to allowances. When an automatic Credit Note Request is created to resolve an allowance discrepancy this value will be concatenated to the beginning of the invoice number. This field must be an upper case character string. This field is mandatory not null. 'CNA'
ALLOWANCE_MATCH New Attribute to control allowance matching in IMCS. 'N'
DEBIT_MEMO_PREFIX_ALLOW New This column holds the prefix that indicates a document is a Debit Memo due to allowances. When an automatic Debit Memo is created to resolve an allowance discrepancy this value will be concatenated to the beginning of the invoice number. This field must be an upper case character string. This field is mandatory not null. 'DMA'
CREDIT_MEMO_PREFIX_ALLOW New This column holds the prefix that indicates a document is a Credit Memo due to allowances. When an automatic Credit Memo is created to resolve an allowance discrepancy this value will be concatenated to the beginning of the invoice number. This field must be an upper case character string. This field is mandatory not null. 'CMA'
DAS/RDS Updates
Application Table DAS/RDS Table or View Change Type Change Description
IM_SYSTEM_OPTIONS DAS_WV_IM_SYSTEM_OPTIONS Update

The following attributes have been added to the view DAS_WV_IM_SYSTEM_OPTIONS.

USE_SUFFIX_ON_DOCS,

ALLOWANCE_MATCH,

DEBIT_MEMO_PREFIX_ALLOW,

CREDIT_MEMO_PREFIX_ALLOW and

CREDIT_NOTE_REQ_PREFIX_ALLOW
IM_UNMTCH_RESLN_ACTION_ASSC_ALLW DAS_WV_IM_UNMTCH_RESLN_ACTION_ASSC_ALLW New This is a view for replicating IM_UNMTCH_RESLN_ACTION_ASSC_ALLW to DAS
IM_SYSTEM_OPTIONS RDS_WV_IM_SYSTEM_OPTIONS Update The following attributes have been added to the view RDS_WV_IM_SYSTEM_OPTIONS. USE_SUFFIX_ON_DOCS ,ALLOWANCE_MATCH, DEBIT_MEMO_PREFIX_ALLOW, CREDIT_MEMO_PREFIX_ALLOW and CREDIT_NOTE_REQ_PREFIX_ALLOW
IM_INJECT_DOC_ALLOWANCE_TAX DAS_WV_IM_INJECT_DOC_ALLOWANCE_TAX New This is a view for replicating IM_INJECT_DOC_ALLOWANCE_TAX to DAS
IM_RESOLUTION_ACTION_ASSC_ALLW DAS_WV_IM_RESOLUTION_ACTION_ASSC_ALLW New This is a view for replicating IM_RESOLUTION_ACTION_ASSC_ALLW to DAS
IM_DOC_ALLOWANCE_TAX RDS_WV_IM_DOC_ALLOWANCE_TAX New This is a view for replicating IM_DOC_ALLOWANCE_TAX to RDS
IM_RESOLUTION_ACTION_ASSC_ALLW RDS_WV_IM_RESOLUTION_ACTION_ASSC_ALLW New This is a view for replicating IM_RESOLUTION_ACTION_ASSC_ALLW to RDS
IM_DOC_ALLOWANCE RDS_WV_IM_DOC_ALLOWANCE New This is a view for replicating IM_DOC_ALLOWANCE to RDS
IM_RESOLUTION_ACTION_ALLOWANCE RDS_WV_IM_RESOLUTION_ACTION_ALLOWANCE New This is a view for replicating IM_RESOLUTION_ACTION_ALLOWANCE to RDS
IM_RESOLUTION_ACTION_ALLOWANCE DAS_WV_IM_RESOLUTION_ACTION_ALLOWANCE New This is a view for replicating IM_RESOLUTION_ACTION_ALLOWANCE to DAS
IM_TOLERANCE_DETAIL DAS_WV_IM_TOLERANCE_DETAIL Update Updated comment on column MATCH_LEVEL
IM_REASON_CODES DAS_WV_IM_REASON_CODES Update Updated comment on columns REASON_CODE_TYPE and ACTION
IM_DOC_ALLOWANCE DAS_WV_IM_DOC_ALLOWANCE New This is a view for replicating IM_DOC_ALLOWANCE to DAS
IM_INJECT_DOC_ALLOWANCE DAS_WV_IM_INJECT_DOC_ALLOWANCE New This is a view for replicating IM_INJECT_DOC_ALLOWANCE to DAS
IM_INJECT_DOC_ALLOWANCE RDS_WV_IM_INJECT_DOC_ALLOWANCE New This is a view for replicating IM_INJECT_DOC_ALLOWANCE to RDS
IM_DOC_ALLOWANCE_TAX DAS_WV_IM_DOC_ALLOWANCE_TAX New This is a view for replicating IM_DOC_ALLOWANCE_TAX to DAS
IM_INJECT_DOC_ALLOWANCE_TAX RDS_WV_IM_INJECT_DOC_ALLOWANCE_TAX New This is a view for replicating IM_INJECT_DOC_ALLOWANCE_TAX to RDS
IM_UNMTCH_RESLN_ACTION_ASSC_ALLW RDS_WV_IM_UNMTCH_RESLN_ACTION_ASSC_ALLW New This is a view for replicating IM_UNMTCH_RESLN_ACTION_ASSC_ALLW to RDS

Support for User Specific Number and Date Format Preferences for Data Loading in Pricing

This cloud service update introduces the ability to support a user’s preferred numeric and date formats in data loading spreadsheets in Pricing. 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 will convert numeric and date values into the user’s selected format for display in the spreadsheet. Likewise, 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 will convert 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 will initially be set to No. Customers must submit a service request to have this setting toggled to Yes, which will enable this functionality.

Steps to Enable

Customers need to raise an Service Request to update S9T_CONFIG.USER_PREF_FORMAT_IND to Y.