1 Feature Summary

Column Definitions

• Feature: Provides a description of the feature being delivered.

• Delivered: Identifies whether the feature is Enabled or Disabled upon initial delivery.

• 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.

  • Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

• 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	Delivered	Scale	Customer Action Required?
Sales Audit Transaction Web Service	Merchandising, Sales Audit	Disabled	Larger	Yes
Auto Open and Close Store Days	Merchandising, Sales Audit	Disabled	Smaller	Yes
Fiscal Document Generation and Services	Merchandising	Disabled	Larger	Yes
Enhanced RTV Integration with WMS Cloud	Merchandising	Disabled	Small	Yes
Updated Oracle WMS Cloud Integration for Outbound Container Modify and Cancel	Merchandising, RICS	Disabled	Small	Yes
Manage Transaction Data Web Service	Merchandising	Enabled	Small	No
Updated PO Inbound Integrations	Merchandising	Disabled	Larger	Yes
Accounting Option for In-store Sales	Merchandising, Sales Audit	Disabled	Small	Yes
Dummy Carton Purge	Merchandising	Enabled	Small	No
Conversion Tool Updates	Merchandising	Enabled	Small	No
Updated Tab Title Translations	Merchandising, Sales Audit, Invoice Matching, Pricing	Disabled	Small	Yes
Added Third-Party Payee on Documents	Merchandising, Invoice Matching	Disabled	Small	Yes
Jurisdiction Spreadsheet Upload	Merchandising	Enabled	Small	No
Enabled E-mail for Notifications	All	Disabled	Small	Yes
New/Updated DAS Tables	Merchandising	Disabled	Small	Yes
Merchandising Subscription Metrics	Merchandising	Disabled	Small	Yes

Sales Audit Transaction Web Service

A new Sales Audit service is being introduced in this update that can be used as an alternative to the flat file (RTLOG) based method of uploading sales. This provides a more flexible format for selling solutions, like POS or OMS, to integrate with Sales Audit. The service works by staging the data received from the selling solution through the service. Then, a new batch process will use the staged data to generate an RTLOG file that is used by the import batch process (SAIMPTLOG). From there, processing is as usual for transaction processing into Sales Audit.

Additionally, if using this service, you will be able to take advantage of a feature that provides Merchandising with a near real time view of "in progress sales" data - sales transactions received via the service that have not yet been audited. By default, the in-progress sales information will be updated asynchronously as data is processed into the service. However, you can also change this to be processed synchronously by updating the system option described below. This view of in progress sales will be included in available inventory calculations for replenishment and customer ordering to provide a more real time view of inventory based on sales than was previously available. Once the sales data completes the audit process, the bucket for stock on hand will be updated and the bucket for in progress sales will be decremented. There is also a new batch process that will run at the end of the store day to remove any orphan records in the in progress sales table for the store data.

Note:

Oracle Retail Xstore and Oracle Retail Order Management CS (OROMS) will continue to support only the RTLOG method of integration with this update.

Steps to Enable

In order to begin using this functionality, you will need to add a record for each store that you expect to receive transaction data via service (instead of by file) in the Store Data table. If no record exists, then it is assumed that the transaction data will be sent by file. To configure this information, the following steps should be followed:

1. In the Sales Audit task list, select Foundation Data > Data Loading > Download.

2. In the Download Data page, select template type Administration and template Store Data. Then click Download.

3. In the spreadsheet application of your choice, navigate to a blank row in the Store Data tab to add new records.

   1. Enter the action type of Create and the store you wish to add.

   2. For System, select Import using REST service called from Selling Solution from the dropdown and select Import in the Import/Export column.

   3. Repeat for all applicable stores.

4. Once all store data has been entered, save and close the spreadsheet.

5. In the Sales Audit task list, select Foundation Data > Data Loading > Upload.

6. In the Upload Data page, select template type Administration and template Store Data. Then select the file you updated in step 3.

7. Click Upload.

8. Validate there were no errors with the updates by viewing the status of the submitted upload in Foundation Data > Data Loading > Review Status.

No other configurations are required, as the new batches will be automatically enabled on patching. However, if you choose to change the value of the system option described below to have in-progress sales processed synchronously, you can do that as well by logging an SR. For more details on the services, see the Merchandising Foundation Operations Guide - Volume 2. 

See also New/Updated DAS Tables for details on enabling the DAS Updates.

System Option Updates

Attribute Name	New/Updated?	Description	Patch Default
INPROGRESS_SALES_RUN_TYPE	New	Holds the in-progress sales run type. The update of in-progress sales quantity can be run in two different modes, asynchronous or synchronous.	ASYNC

Batch Schedule Impacts

Process Name	Process Type	New/Updated?	Delivered
Create RTLOG (SA_CREATE_RTLOG_JOB, SA_CREATE_RTLOG_CYCLE_JOB) - this new job creates the RTLOG from the data staged from the new service	Nightly, Cyclic	New	Enabled
In Progress Sales Purge (SA_INPROGESS_PURGE_JOB) - this new job performs a daily clean up of the in progress bucket at end of a store day to get rid of any orphan records for a store	Nightly	New	Enabled
RTLOG Data Purge (SA_RTLOG_DATA_PURGE_JOB) - this new job purges the staging tables used by the REST service based on the configured retention days (DAYS_BEFORE_PURGE)	Nightly	New	Enabled
SA_TRANSACTION_LOADING_PROCESS - new jobs added: Create RTLOG (SA_CREATE_RTLOG_JOB) In Progress Sales Purge (SA_INPROGESS_PURGE_JOB) RTLOG Data Purge (SA_RTLOG_DATA_PURGE_JOB)	Nightly	Updated	Enabled
SA_TRANSACTION_LOADING_PROCESS_ADHOC - new job added: Create RTLOG (SA_CREATE_RTLOG_JOB)	Ad hoc	Updated	Enabled
SA_TRANSACTION_LOADING_CYCLE_PROCESS - new job added: Create RTLOG (SA_CREATE_RTLOG_CYCLE_JOB)	Cyclic	Updated	Enabled

Code Updates

Code Type	Code Type Description	Code	Code Description	New/Updated?	Delivered
SYSI	Sales Audit System Import Interfaces	TLOG	Import using TLOG sent from Selling Solution	New	Enabled
SYSI	Sales Audit System Import Interfaces	REST	Import using REST service called from Selling Solution	New	Enabled

Data Access Schema (DAS) Updates

Table Name	View Name	New/Updated?	Change Notes
ITEM_LOC_SOH	DAS_WV_ITEM_LOC_SOH	Updated	Added the IN_PROGRESS_SALES_QTY field
ITEM_LOC_SOH_EOD	DAS_WV_ITEM_LOC_SOH_EOD	Updated	Added the IN_PROGRESS_SALES_QTY field
REPL_RESULTS	DAS_WV_REPL_RESULTS	Updated	Added the IN_PROGRESS_SALES_QTY field
SA_STORE_DAY	DAS_WV_SA_STORE_DAY	Updated	Added column TRANSACTIONS_LOADED, which indicates the number of transactions that have been imported from the Sales Service for the store day.
SA_INPROGRESS_SALES	DAS_WV_SA_INPROGRESS_SALES	New	Added the new table and created a DAS view
SVC_RTLOG_DATA_REJECT	DAS_WV_SVC_RTLOG_DATA_REJECT	New	Added the new table and created a DAS view

Integration Impacts

Name	New/Updated?	Integration Type	Field Name	Change Notes
Load Transactions	New	REST Service		This service accepts transactions from a Point of Sale (POS) or Order Management Solution (OMS) into Sales Audit. It provides an alternative to transactions processed from an RTLOG file via the Sales Audit sales process documented under the Scheduled Integration section in the Merchandising Operations Guide Volume 2.
Get Rejected Transactions since Previous Query	New	REST Service		The purpose of this service is to return transactions that were rejected during processing to the calling process or application, for use in troubleshooting and error

Auto Open and Close Store Days

Sales Audit uses a store day as its unit of work, which is intended to represent the hours that a POS in the store is open. Typically, POS solutions have had explicit Open and Close transactions that create the store day and mark it closed at the end. However, for transactions sent to Sales Audit from an order management solution, which never really opens or closes, the creation and closing of a store day has represented a bit of a challenge. To better support stores that are always open, a new feature has been added in the existing Create Store Day for Expected Transactions batch process that will automate the creation and closure of store days. This process will be based on two key attributes:

1. A new system option, Create Store Day, which indicates how many days in advance a store day should be created.

2. A new store level attribute, Online Store, which indicates the stores that should be considered for this process. This will only be available for stores that are non-stockholding and a company (non-franchise) store.

When closing a store day, if your OMS can send a DCLOSE transaction, that can still be used to indicate the close of business day. But if not, updates were made to the existing Complete Transaction Import Processing batch process to automate the closure. This will occur when processing transactions if the business date of the transaction is equal to the vdate - 1 and the store has been flagged as an Online Store.

Note:

Oracle Retail Order Management CS (OROMS) will continue to create store open and close transactions with this update, so the new store level attribute should not be set to checked if integrating with OROMS.

Steps to Enable

The new store level attribute will default to unchecked on patching. To enable a store to be eligible for the auto create process, the Online Store attribute should be checked. This will start auto creating store day open and close transactions starting the next business day.

See also New/Updated DAS Tables for details on enabling the DAS Updates.

System Option Updates

Attribute Name	New/Updated?	Description	Patch Default
Create Store Day	New	This field contains the number of days prior to the business date when Sales Audit Store Days will be created for stores that are set up as online stores in Merchandising. Valid values are 1 and 2.	1

Data Access Schema (DAS) Updates

Table Name	View Name	New/Updated?	Change Notes
SA_STORE_DAY	DAS_WV_SA_STORE_DAY	Updated	Added column AUTO_CLOSED, which indicates whether the store day was auto closed by Sales Audit or by consuming a DCLOSE transaction.
SA_SYSTEM_OPTIONS	DAS_WV_SA_SYSTEM_OPTIONS	Updated	Added column CREATE_STORE_DAY_PRIOR
STORE	DAS_WV_STORE	Updated	Added column ONLINE_STORE_IND

Integration Impacts

Name	New/Updated?	Integration Type	Field Name	Change Notes
Store Publication API	Updated	RIB	Online Store Indicator	This field has been added to indicate if a store is an online store or not. Valid values are Y or N.
Store Subscription API	Updated	RIB	Online Store Indicator	This field has been added to indicate if a store is an online store or not. Valid values are Y or N.

Fiscal Document Generation and Services

Countries and regions worldwide are implementing electronic document exchange between businesses and governments in order to have more visibility and control over the transactions and tax collection. E-Waybill is an example of such electronic documents that represents a shipment of goods and is required to be approved by local governments before the physical shipment is released. To centralize the generation and integration of documents with local governments, a new Fiscal Document Generation (FDG) feature was added in Merchandising.

FDG oversees centralizing the communication of electronic documents with local governments through an integration with third party specialist systems. This feature consists of a set of REST services that will be used by inventory systems to support shipping and by third party specialist systems to capture documents that need approval. New screens in Merchandising will provide visibility to the fiscal documents being processed as well as any errors. Additionally, this feature will support enabling custom flex attributes (CFAS) and non-merchandise codes when necessary to support information in fiscal documents.

New duties and privileges were added to support this feature and are described in the tables below.

New Duties

Duty	Duty Description	Child Duties	Base Role	New/Updated?
RMS_FISCAL_DOCUMENT_MGMT_DUTY	A duty for re-submitting and rejecting fiscal documents. This duty is an extension of the Fiscal Document Inquiry Duty.	RMS_FISCAL_DOCUMENT_INQUIRY_DUTY	RMS_APPLICATION_ADMINISTRATOR_JOB INVENTORY_ANALYST_JOB INVENTORY_MANAGER_JOB CORPORATE_INVENTORY_CONTROL_ANALYST_JOB INVENTORY_CONTROL_MANGER_JOB SUPPLY_CHAIN_ANALYST_JOB FINANCIAL_MANAGER_JOB	New
RMS_FISCAL_DOCUMENT_INQUIRY_DUTY	A duty for searching for and viewing fiscal documents.		FINANCIAL_ANALYST_JOB	New

New Privileges

New Privilege	Privilege Description	Parent Duty	New/Updated?
VIEW_FISCAL_DOCUMENTS_PRIV	A privilege for viewing fiscal documents via the Fiscal Document Generation screen.	RMS_FISCAL_DOCUMENT_INQUIRY_DUTY	New
MAINTAIN_FISCAL_DOCUMENTS_PRIV	A privilege for re-submitting fiscal documents in ‘Error’ status or rejecting fiscal documents via the Fiscal Document Generation screen. Users with this privilege must also have the View Fiscal Documents Priv.	RMS_FISCAL_DOCUMENT_MGMT_DUTY	New

Note:

Oracle Retail Store Inventory and Operations Cloud Service (SIOCS) and Oracle WMS Cloud do not yet support using these new services as of this update.

Steps to Enable

In order to start leveraging this feature, there are several steps that need to be taken.

1. Turn on functionality via System Options to enable the other configurations, as well as the Fiscal Document Generation page located under Finance in the main task list.

   1. From the Merchandising task list, select Application Administration > System Options

   2. Navigate to the Localization section of the page and click on the checkbox labeled Fiscal Document Generation.

   3. Click Save and Close to save your changes.

2. Configure FDG specific options, along with flex attributes and non-merchandising codes, as needed.

   1. From the Merchandising task list, select Foundation Data > Download Foundation Data.

   2. In the Download Foundation Data page, select the template type Finance Administration and template Fiscal Document Attributes. Then click Download.

   3. Open the downloaded file in the spreadsheet application of your choice and update the configurations, as needed.

      1. Attributes - the spreadsheet should contain all flex attributes you've configured in the solution with the Fiscal Doc Indicator set to No. To configure one or more of those attributes to be included in a fiscal document, navigate to the appropriate row in the spreadsheet and set the document type (waybill or invoice) and update the Fiscal Doc indicator to Yes. Repeat until the configurations are complete for all applicable attributes.

      2. Non-Merchandise Codes - the spreadsheet should contain all non-merchandising codes configured in Merchandising with the Fiscal Doc Indicator set to No. To configure one or more of these codes to be included in a fiscal document, navigate to the appropriate row in the spreadsheet and set the type (freight or insurance) and the document type (waybill or invoice). Finally, update the Fiscal Doc indicator to set to Yes. Repeat until the configurations are complete for all applicable codes.

      3. FDG Options - update the values in this table to set the rounding precision to use, the default fiscal address number, retention days, and whether to enable auto reject functionality.

   4. Once all configurations are complete, save your updated spreadsheet and close the document.

   5. In the Merchandising task list, select Foundation Data > Upload Foundation Data.

   6. In the Upload Foundation Data page, select template type Finance Administration and template Fiscal Document Attributes. Then, for the Source File, select the file where you made your updates. Click Upload.

3. Configure the new privileges and duties

   1. Based on these new duties and privileges, the following actions are required in the order described below in order to enable the features. For more information on the workflows used to support the actions described below, see the Merchandising Administration Guide.

      Step 1: Add New Duties

      For each of the new duties listed above, follow these steps:

      1. Select Settings > Security > Roles

      2. Click on the Add iconic button or select Add from the Actions menu

      3. Add the first new duty, including the name, and optionally the description in the popup displayed. Then click OK.

      4. Repeat for all new duties listed above

      Step 2: Add New Duties to Roles

      Each of the new duties should then be added to the roles that require the access as defined in the privileges above.

      1. Select Settings > Security > Role Mappings

      2. Selecting a role that will be assigned one or more of the duties

      3. For each role, click Select and Add and then select the the duties you want to add to the role using the popup

      4. Repeat for each role where you want to add the new duties

      Step 3: Add Child Duties

      For any new duty listed above that contains other duties, the child duty will also need to be mapped to the new duty using the below steps.

      1. Select Settings > Security > Role Mappings

      2. Highlight the parent duty

      3. Click Select and Add and then select the the duties you want to add to the role using the popup. 

      4. Repeat until you have added all child duties to the parent duties

      Step 4: Synchronize Privileges with New Duties

      Each new duty then needs to have its privileges synchronized. 

      1. Select Settings > Security > Policy Patching

      2. Select Sync with Patch

      3. Under the Base Policies tab, working through the duties one at a time, select the checkbox next to each the corresponding privileges

      4. Click Copy to Custom and then select the duty

      5. Repeat until you have synchronized each duty

      Note: the Copy to Custom option does not clear the check boxes that you selected, so be sure to de-select the check boxes after each duty.

      Step 5: Synchronize Modified Privileges

      Each privileges that had changed permissions from previous updates and will need to be synchronized to update these permissions for the patch. 

      1. Select Settings > Security > Policy Patching

      2. Select Sync with Patch

      3. Under the Base Policies tab, select the checkbox next to each the corresponding privileges and click Sync

      4. Repeat this for each privilege that had updated permission

4. Configure your store and warehouse systems to call the new services.

   1. The details for the services can be found in the Merchandising Foundation Cloud Service Operations Guide - Volume 2.

System Option Updates

Attribute Name	New/Updated?	Description	Patch Default
Fiscal Document Generation (FDG_IND)	New	Enables the use of Fiscal Document Generation functionality in Merchandising. This option will enable the task menu link and screen. Fiscal Document Generation functionality leverages services that are used by Merchandising to communicate with government entities for required fiscal documentation, such as e-waybills. (Table LOCALIZATION_CONFIG_OPTIONS)	N

Code Updates

Code Type	Code Type Description	Code	Code Description	New/Updated?	Delivered
FDST	Fiscal document Status	C	Canceled	New	Y
FDST	Fiscal document Status	E	Error	New	Y
FDST	Fiscal document Status	N	New	New	Y
FDST	Fiscal document Status	R	Ready	New	Y
FDST	Fiscal document Status	RJ	Rejected	New	Y
FDST	Fiscal document Status	S	Submitted	New	Y
FDST	Fiscal document Status	V	Validated	New	Y
FDET	Fiscal Document Internal Entity Type	CUST	Customer	New	Y
FDET	Fiscal Document Internal Entity Type	PTRN	Partner	New	Y
FDET	Fiscal Document Internal Entity Type	ST	Store	New	Y
FDET	Fiscal Document Internal Entity Type	SUPP	Supplier	New	Y
FDET	Fiscal Document Internal Entity Type	WH	Warehouse	New	Y
FDTY	Fiscal document Type	INV	Invoice	New	Y
FDTY	Fiscal document Type	WBL	Waybill	New	Y
FDED	Fiscal Document Entity Type	CR	Carrier	New	Y
FDED	Fiscal Document Entity Type	DEST	Destination	New	Y
FDED	Fiscal Document Entity Type	LOC	Location	New	Y
FDED	Fiscal Document Entity Type	SHIPP	Shipping	New	Y
FDED	Fiscal Document Entity Type	VENDOR	Vendor	New	Y
FDRT	Fiscal Document Reference Type	ALLOC	Allocation Number	New	Y
FDRT	Fiscal Document Reference Type	BOLN	BOL Number	New	Y
FDRT	Fiscal Document Reference Type	CONO	Customer Order Number	New	Y
FDRT	Fiscal Document Reference Type	DISTRO	Distro Number	New	Y
FDRT	Fiscal Document Reference Type	FDOC	Fiscal Document	New	Y
FDRT	Fiscal Document Reference Type	FULLF	FullFilement Number	New	Y
FDRT	Fiscal Document Reference Type	ORDER	Order Number	New	Y
FDRT	Fiscal Document Reference Type	RTVAUT	Return Authorization Number	New	Y
FDRT	Fiscal Document Reference Type	RTVNO	Return vendor Number	New	Y
FDRT	Fiscal Document Reference Type	SHIPN	Shipment Number	New	Y
FDRT	Fiscal Document Reference Type	TSFNO	Transfer Number	New	Y
FDPT	Fiscal Document Process Type	PD	Process Document	New	Y
FDPT	Fiscal Document Process Type	PPD	Process Pre Document	New	Y
FDPT	Fiscal Document Process Type	RD	Reim Document	New	Y
FDER	Fiscal Document Error Type	D	Deduction	New	Y
FDER	Fiscal Document Error Type	I	Integration	New	Y
FDER	Fiscal Document Error Type	V	Validation	New	Y
FDNT	Fiscal Document Non-Merchandise Type	F	Freight	New	Y
FDNT	Fiscal Document Non-Merchandise Type	I	Insurance	New	Y
FDGV	Fiscal document Global Validation	2	Validation 2	New	Y
FDGV	Fiscal document Global Validation	309	Validation 309	New	Y

Integration Impacts

Name	New/Updated?	Integration Type	Change Notes
processPreDoc	New	REST Service	Service to be called by store and warehouse systems for fiscal document request. The payload to be sent is based on the pre-shipment message (Shipinfo). FDG will take this request and create a fiscal document to be processed.
processDoc	New	REST Service	Service to be called by third party systems to request a fiscal document. The payload is more comprehensive than processPreDoc service and can have costs and taxes informed. This service is meant to generate e-waybill for small vendors that don´t have the infrastructure to do it.
nextDocumentDetail	New	REST Service	Service to be called by third party specialist systems that will request for documents to be interfaced to local governments. The response to this service will have the full payload of a fiscal document.
processDocStatus	New	REST Service	Service to be called by third party specialist systems to provide updated approval data for documents interfaced to local governments.
documentStatusDetail	New	REST Service	Service to be called by store, warehouse, or third party systems, that previously requested a fiscal document to be generated. This request will return the approved document number so the transaction (shipment) can be resumed.
processDocCancel	New	REST Service	Service to be called by store, warehouse, or third party systems that previously requested a fiscal document to be generated. This request will be used to cancel the generation of a fiscal document and eventually inform local governments about it.
documentDetail	New	REST Service	Service to be called by third party specialist systems that will request for a particular document. The response to this service will have the full payload of a fiscal document.

Enhanced RTV Integration with WMS Cloud

Previously, the return to vendor (RTV) integration between Merchandising and Oracle WMS Cloud only supported returns from available inventory. This was due to both limitations in what was supported in WMS Cloud, as well as how Merchandising communicated the details of unavailable statuses in RTV requests sent to WMS. However, given that it is often the case that inventory that needs to be returned is either damaged or defective and is hence not available to sell to the end customer, in a recent WMS Cloud update (20D) support was added for for unavailable inventory returns. To take advantage of this feature, updates have been made in this Merchandising service update to support both communicating the inventory status codes on RTV requests, as well as to handle the statuses passed back through the shipment process. The Merchandising updates for sending status codes in the RTV requests will be able to be used by other WMS solutions as well.

Note:

This feature also includes updates in the Oracle Retail Integration Cloud Service to support the changes described above.

Steps to Enable

In order to start leveraging this feature, there are several steps that need to be taken.          

1. In Merchandising to communicate the multiple codes that could be applicable for an RTV line item, map the inventory status codes to relevant inventory status, as needed. The inventory status codes will be sent as a comma delimited list in the new From Disposition field in the RTV Request Publication API.

   1. From the Merchandising task list, select Foundation Data > Download Foundation Data

   2. In the Download Foundation Data page, select the template type Inventory and template Inventory Status and Adjustment. Then click Download.

   3. Open the downloaded file in the spreadsheet application of your choice and update the Inventory Status Types and Inventory Status Codes configurations, as needed.

   4. Once all configurations are complete, save your updated spreadsheet and close the document.

   5. In the Merchandising task list, select Foundation Data > Upload Foundation Data.

   6. In the Upload Foundation Data page, select template type Inventory and template Inventory Status and Adjustment. Then, for the Source File, select the file where you made your updates. Click Upload.

2. In WMS Cloud to support multiple inventory status codes in the stock return request from Merchandising as well as to send RTV shipment with the inventory from a locked status to Merchandising, the following configurations are required for the RTV order type:

   1. Go to the Order Type screen and click the Edit button.

   2. Set Eligible Lock Code for Allocation to a comma delimited list of all lock codes that could have RTVs created against them. In Merchandising, these lock codes are mapped to the inventory status codes within an inventory status.

   3. Uncheck Wave Flag to allow RTV orders to be allocated and picked using “RF Direct Allocation” or “RF Pick and Allocate” modules in WMS.

   4. Check Allocate during Pick to allow allocation when order is picked for return.

3. WMS Cloud generates the Activity Code 65 when an order is waved as "Return to Vendor" and the related packing task is completed. Following configurations must be done in WMS Cloud to interface activity code 65 as inventory adjustment message to Merchandising via USM:

   1. In the Scheduled Job UI, the value ‘65’ to be added to the list of Activity Codes configured for the job type 'Generate Inventory History Extract'.         

   2. In the Output Interface Configuration UI for the interface type 'Inventory History Export', the value ‘65’ to be added to the list of Activity codes configured for the InvAdjustCre message type.

See also the Retail and WMS Cloud Implementation Guide for more details on the configurations described above.

Integration Impacts

Name	New/Updated?	Integration Type	Field Name	Change Notes
Return to Vendor Request	Updated	RIB	from_disposition	This will contain the status of the inventory that needs to be returned to the vendor.

Updated Oracle WMS Cloud Integration for Outbound Container Modify and Cancel

In Oracle WMS Cloud, the audit of an outbound container before a shipment is dispatched from the warehouse sometimes results in reduction in the quantity being shipped out, or the shipment being cancelled. Such modifications have been communicated via the Stock Order Status message to Merchandising in order to update stock orders. However, there was a limitation in the information shared from Oracle WMS Cloud in this integration due to the activity codes that were supported in Oracle WMS Cloud for this function (29 and 30), in that it did not support updates to multiple items or multiple stock orders on an outbound container. This is because these  activity codes were primarily designated for inbound shipments. These gaps are addressed in the Oracle WMS Cloud 21B release by enhancing functionality around activity codes 31 (outbound container modify) and 32 (outbound container cancel) to write inventory history transactions for each impacted order/item in the outbound container. With this change, activity codes 31 and 32 in Oracle WMS Cloud will be configured as SO status messages for the outbound container (OBLPN) modification and cancellation respectively, replacing activity codes 29 and 30.

Note:

This feature also includes updates in the Oracle Retail Integration Cloud Service to support the changes described above.

Steps to Enable

Because activity codes 31 and 32 previously existed but were not integrated, it is critical to ensure only new records are integrated to Merchandising when these codes are configured in the integration. Therefore, it is recommended to integrate these generated by RF Modify/Cancel module using "Enable Auto Send" option on the Inventory History Activity Parameters screen in Oracle WMS Cloud. This option enables real time integration of the activity codes and only future transactions for these activity codes in the Inventory History table would get interfaced to Merchandising. This would require also configuring activity codes 12 and 27, which are also mapped as Stock Order Status updates, to use the Enable Auto Send option, as they are generated along with 31 and 32 in the same group in Oracle WMS Cloud. This would ensure these SO status messages are interfaced in the desired sequence for consistent updates to inventory in Merchandising.   The steps to do this are described below.

1. Configure activity codes 31 and 32 as SO Status Message

   1. The values 31 and 32 to be added to the list of activity codes configured for the SOStatusCre message type in the Output Interface Configuration UI for the interface type Inventory History Export within Oracle WMS Cloud.

   2. Set Enable Auto Send option in the Inventory History Activity Parameters screen for activity code 31 - OB Container Modified.

   3. Set Enable Auto Send option in the Inventory History Activity Parameters screen for activity code 32 - OB Container Cancelled.

2. Remove previously configured activity codes 29 and 30 as SO Status Message

   1. The values 29 and 30 to be removed from the list of activity codes configured in Scheduled Jobs for the job type Generate Inventory History Extract within Oracle WMS Cloud.

   2. The values 29 and 30 to be removed to the list of activity codes configured for the SOStatusCre message type in the Output Interface Configuration UI for the interface type  Inventory History Export within Oracle WMS Cloud.

3. Modify configuration for activity codes 12 and 27 in WMS from a schedule job to a real time interface

   1. The values 12 and 27 to be removed from the list of Activity Codes configured in Scheduled Jobs for the job type Generate Inventory History Extract within Oracle WMS Cloud.

   2. Set Enable Auto Send option in the Inventory History Activity Parameters screen for activity code 12 - Order Detail Shorted.

   3. Set Enable Auto Send option in the Inventory History Activity Parameters screen for activity code 27 - Order Cancellation.

See also the Retail and WMS Cloud Implementation Guide for more details on the configurations described above.

Manage Transaction Data Web Service

A new REST web service has been introduced with this update to allow you to create tran data records in the stock ledger, such as to adjust previously posted transactions. The functionality in the service mirrors that which is currently supported in the External Transaction Data Upload, which is a batch-based flat file upload. Like the flat file upload, the service also allows you to choose whether weighted average cost (WAC) should be updated based on the transaction created. The service processes transaction data in a synchronous request/response manner and returns success/failure as the response to the service call. The service writes the transaction data to the table once the input data passes all validations, and if the transaction is marked for WAC recalculation, it recalculates the WAC for the item/location at the same time.

Note:

The transactions written by this service will not impact unit inventory in Merchandising.

Integration Impacts

Name	New/Updated?	Integration Type	Change Notes
Transaction Data Upload REST Service	New	REST	Transaction data consists of the individual transaction records created when various merchandising processes are completed and recorded in Merchandising. Merchandising also allows additional costs to be included in stock ledger valuation that cannot be included based on existing Merchandise functionality through this service, which processes transaction uploads in a synchronous request/response manner.

Updated PO Inbound Integrations

Merchandising has multiple methods of uploading new purchase orders, or updates to existing orders, via integration. This includes an upload via spreadsheet, web service, bulk batch-based upload, and a RIB API. Prior to this update, each of the methods had slightly different attributes supported, and some attributes for a purchase order were not present in any of the methods. To provide more consistency and flexibility to what data can be updated externally, all the mentioned methods have been rounded out to include missing attributes at the PO header and detail levels.

Steps to Enable

On patching, the base template Purchase Order (PURCHASE_ORDER_DATA) will be automatically updated with this information, so you will need to ensure your users download a new version of the base template, if that is what you are using for spreadsheet uploads. However, a best practice is to copy the base template to create a custom configured version, you will need to add the new columns in your custom templates using the Data Loading Template Configuration screen, if needed. Additionally, because the bulk upload for purchase orders (POINDBATCH) uses the base PO template by default (unless otherwise configured) the XML file sent from an external system will need to be modified to add the new fields as well to prevent errors on upload.

If you are using the PO Subscription API or the PO Management Service and want to leverage any of the newly added fields, the source system will need to be updated to map values to these fields, but this is not required.

Integration Impacts

Name	New/Updated?	Integration Type	Field Name	Change Notes
PO Subscription API	Updated	RIB	Header fields: Order Type Buyer Location Type Location Promotion QC Indicator Earliest Ship Date Latest Ship Date Freight Terms Backhaul Type Backhaul Allowance Ship Pay Method FOB Transportation Responsibility Type FOB Transportation Responsibility Vendor Order Number Freight Contract Number Pickup Location Pickup Number Pickup Date Appointment Date/Time Import Type Import ID Clearing Zone Routing Location Re-approved Indicator Detail updates: Cancelled Quantity Cancelled Code Estimated In-Stock Date	Added key fields at the header and detail levels that were not previously available for orders created or updated through this API.

Accounting Option for In-store Sales

This feature allows retailers to support cross store checkouts of merchandise for stores that are co-located. For example, if a customer takes items from store A and store B to the register at store B. During checkout, the point of sale system would flag the items from store A and pass those details onto Sales Audit with the other transaction details. Sales Audit will then pass those details onto Merchandising, which will ensure that the sale and inventory is accurately accounted for in store A, rather than store B. The exports from Sales Audit to Oracle Retail Insights have also been modified to ensure sales are accounted for at the same store as will be used by Merchandising. This feature is enabled for transaction imports into Sales Audit for both the flat file import, as well as the new service-based import into Sales Audit.

Note:

Changes have not been made to the import from Xstore nor the export to SIOCS related to this enhancement. If you are integrating with Xstore or SIOCS this feature will not be able to be used.

Steps to Enable

In order to begin using this feature, if you are using the flat file import into Sales Audit, you will need to update the format of the file created to the latest version of the file. This includes the addition of other fields that were previously dynamically supported in the THEAD record of the file.

Field	Field Type
Reference No. 28	Char (30)
Reference No. 29	Char (30)
Reference No. 30	Char (30)
Reference No. 31	Char (30)
Fulfillment Location Type	Char (2)
Fulfillment Location	Number (10)
Posting Store	Number (10)

See also New/Updated DAS Tables for details on enabling the DAS Updates.

Data Access Schema (DAS) Updates

Table Name	View Name	New/Updated?	Change Notes
SA_TRAN_ITEM	DAS_WV_SA_TRAN_ITEM	Updated	Added a new column "POSTING_STORE" in both base table and in DAS view
SA_TRAN_ITEM_REV	DAS_WV_SA_TRAN_ITEM_REV	Updated	Added a new column "POSTING_STORE" in both base table and in DAS view

Integration Impacts

Name	New/Updated?	Integration Type	Field Name	Change Notes
Import of Unaudited Transaction Data from POS/OMS to Sales Audit (saimptlog)	Updated	Batch Flat file: RTLOG	posting_store	Added a new field in last of TITEM line of RTLOG file as "Posting Store".
Export of POS transactions from Sales Audit to Merchandising (saexprms)	Updated	Batch Flat file: POSU_*	posting_store	Added a new field in last of THEAD line of POSU file as "Posting Store".
Upload Sales(POSU files) to RMS (uploadsales.ksh)	Updated	Batch Flat file: POSU*	posting_store	Modified a batch to accept the new "Posting Store" value in POSU file.
Export from Sales Audit to Oracle Retail Insights (saexpdw)	Updated	Batch Flat File: RDWT_*	posting_store	Added a new field in last of THEAD line of RDWT file as "Posting Store".
Export Inventory Reservation/Release for In Store Customer Order and Layaway Transactions from Sales Audit (saordinvexp)	Updated	Batch Flat File: ORIN_*	posting_store	Added a new field in last of TDETL line of ORIN file as "Posting Store".
Upload and Process Inventory Reservations from ReSA (ordinvupld)	Updated	Batch Flat file: ORIN_*	posting_store	Modified a batch to accept the new "Posting Store" value in ORIN file.

Dummy Carton Purge

Merchandising has a reconciliation method for transfer and allocation shipments that allows you to assign a dummy carton ID for situations where the carton label cannot be read on receipt. Then, later batch processes, Reconcile Received Dummy Carton IDs (dummyctn) and Detail Receive Damaged or Tampered Cartons (tamperctn), attempt to reconcile the contents of the dummy carton with unreceived cartons on the associated BOLs. After reconciliation, records are removed from the staging table (DUMMY_CARTON_STAGE) used to hold the records. However, if the records cannot be reconciled, then the records remain in the staging table. This enhancement adds a purge process to the existing batches to remove the unprocessed records if they are older than the Close Open Shipments After system option since they were received. 

Conversion Tool Updates

Several new features and operational improvements have been added to the Merchandising Conversion tool in this update. Key enhancements include:

• Added Custom Flex Attribute (CFAS) table conversion for most of the foundation and transaction data entities supported in the tool. Previously, CFAS conversion was only supported in the tool for item, item/supplier, and item/supplier/country levels.

• Enhanced the Price History data entity to support multi-threaded processing. Like other multi-threaded entities, the thread and chunk sizes will be managed through Entity Sequence List screen.

• Additional enhancements to Item conversion to improve the overall performance. These enhancements include:

  • Removing inheritance and defaulting for Price History, Item/Supplier/Country/Dimension, Item/Expenses, and Pack Item Breakout tables. These entities, when needed, should be loaded in separate files.

  • Removing the cascade logic from parent to child items. Each item level should be loaded separately with the complete set of data applicable for that level. 

  • Support for only approved items.

• During upload, the tool will now support only zip format files. However, there can be multiple .dat data files within a zip file.

• Minor changes for a few entities in the way these are organized for data load in the tool. These include:

  • The translation tables for department, class and subclass which were previously loaded separately will be moved under their parent entity. The .dat file containing these will be loaded with other related tables in the same zip folder.

  • Certain correlated tables which were earlier loaded independently from each other will be merged under the same entity. The entities that will now be loaded together are Related Item Header/Detail, Differentiator Ratio Header/Detail and Source Delivery Scheduled Days/Exclusions.

If you are in the process of converting data, you will need to review the above, along with the updated Conversion Guide to leverage these new features. Some of the changes, like the item conversion and zip file update, are mandatory so may require some adjustments to how you are loading files. Others like conversion of CFAS and adjustments to the Price History threading are optional.

Updated Tab Title Translations

In the base templates used for spreadsheet uploads, the tab titles for several translations were updated to meet the 31-character limit that exists in Excel. This impacted templates for Merchandising, Sales Audit, Pricing, and Invoice Matching.

Steps to Enable

If you are using one of the following spreadsheet upload templates in one of the listed impacted languages, you should ensure your users download a new version of the base template after patching before using to create, update, or delete information. For Items, Purchase Orders, and Promotions, if you are using the bulk uploads with the base template configured in the batch scheduler using tags in one of these languages, then you also may need to adjust the tags based on these updates.

Merchandising

Impacted Language	Template Name(s)
Arabic	Custom Flex Attribute Foundation Franchise Customers GL Cross Reference HTS Definition HTS Setup Item Master Outside Locations Purchase Order Replenishment Data Loading Configuration SCACs Style and Style/Color Template Timelines Transfer Entities UOMs User Defined Attributes VAT XItem Data Xorder Data
Croatian	Admin Induction Configuration Entity Exchange Rate Configuration GL Cross Reference Inventory Status and Adjustment Reasons XItem Data
Dutch	Item Master
French	Admin Induction Configuration Background Process Configuration Entity Exchange Rate Configuration GL Cross Reference Inventory Status and Adjustment Reasons Item Master XItem Data
German	Entity Exchange Rate Configuration GL Cross Reference Inventory Status and Adjustment Reasons Item Master XItem Data
Greek	Background Process Configuration Entity Exchange Rate Configuration GL Cross Reference Inventory Status and Adjustment Reasons Item Master Purchase Order States XItem Data
Hungarian	Admin Induction Configuration Entity Exchange Rate Configuration Inventory Status and Adjustment Reasons Replenishment Data Loading Configuration
Italian	Entity Exchange Rate Configuration GL Cross Reference HTS Setup Item Master XItem Data
Polish	Admin Induction Configuration GL Cross Reference Item Master XItem Data
Portugese-Brazil	GL Cross Reference Inventory Status and Adjustment Reasons Item Master Location Traits States XItem Data
Russian	Admin Induction Configuration Entity Exchange Rate Configuration GL Cross Reference Inventory Status and Adjustment Reasons Item Master XItem Data
Spanish	Admin Induction Configuration Entity Exchange Rate Configuration GL Cross Reference Inventory Status and Adjustment Reasons Item Master Non-Merchandise Codes XItem Data
Swedish	GL Cross Reference Item Master XItem Data
Turkish	Background Process Configuration Entity Exchange Rate Configuration GL Cross Reference Item Master Replenishment Data Loading Configuration XItem Data

Sales Audit

Impacted Language	Template Name(s)
Arabic	GL Cross Reference
Portugese-Brazil	Location Closings

Added Third-Party Payee on Documents

This update allows for a 3rd party payee to be included on documents in Invoice Matching. This 3rd party payee is then passed to the financial system where it is used as an override of the remit-to vendor.   This feature provides the flexibility to selectively redirect payment from the standard remit-to vendor to a third party on a document by document basis and can be useful when working with smaller vendors where the payment relationships may change or where receivables may be managed by a third party.

As part of this requirement, the Merchandising batch process that generates files for Invoice Matching was also updated to keep it in sync with the format used by Invoice Matching. It should be noted that this change is not backward compatible with older versions of Merchandising, as it is assumed that these two cloud services will be updated together. Also, the EDIDLINV_EXT_PROCESS job in the batch schedule to allow this file to be used by external invoicing solution is being removed, as this program is intended to be used internally only. It will be automatically removed as a valid job for scheduling when this update is applied.

Steps to Enable

In order to enable use of this feature, you will need to update the new system option, described below, to set it to checked. To do this, follow these instructions:

1. From the Invoice Matching task list, select Foundation > System Options.

2. Navigate to the Finance Integration Setup section and click the check box next to Allow Third-party Payee.

3. Click Save and Close to save your changes.

System Option Updates

Attribute Name	New/Updated?	Description	Patch Default
Allow Third-party Payee	New	This system option when selected will modify the UI to include the Third-party Payee field on entry and maintenance screens in Invoice Matching	Unchecked

Batch Schedule Impacts

Process Name	Process Type	New/Updated?	Delivered
EDIDLINV_EXT_PROCESS	Cyclic	Removed

Jurisdiction Spreadsheet Upload

A new spreadsheet upload process was added for uploading country/state jurisdiction codes and descriptions information in the preexisting COUNTRY_TAX_JURISDICTION table. Additionally, the existing Jurisdiction field was added for display in the address screens throughout Merchandising. It will have a list of values to allow users to select a valid jurisdiction code when creating an address, if required. This is optional information. See the Merchandising Implementation Guide for more details on configuring jurisdictions.

Enabled E-mail for Notifications

One of the features that is available across all the Merchandising cloud services is the ability to configure notifications used by the solutions to be emailed to one or more users. This allows a user to be notified of an exception or a business event, such as a price change that could not be approved, even if they are not logged into the solution at the time.

Steps to Enable

1. Login as an admin user to the Merchandising cloud suite where you want to enable this feature, such as Merchandising.  

2. From the sidebar menu, select the Settings button; click on the Notifications option.

3. In the Notification Setting screen, all notifications will be displayed for the solution. Navigate to the row containing the notification you wish to enable for email. The Query by Example function used to filter the notifications may be helpful with this step. 

4. Click on the Edit iconic button or select Edit from the Actions menu.

5. Enter the desired email address for the notification and then click OK to close the pop up.  

New/Updated DAS Tables

New tables were added for replication in DAS and some DAS views have been modified. The table below lists many of the new/updated tables, but others are also listed as part of the new features added in this release, including Accounting Option for In-store Sales, Auto Open and Close Store Days, and Sales Audit Transaction Web Service.

Steps to Enable

In order to enable this functionality, you will need to replace the modified configuration files with the latest version. The directions for how to download updated files and replace the old versions can be found in the white paper on My Oracle Support (support.oracle.com) under ID 2283998.1.

Data Access Schema (DAS) Updates

Table Name	View Name	New/Updated?	Change Notes
INVC_HEAD	DAS_WV_INVC_HEAD	Updated	Modified comment on REF_RSN_CODE field
ITEM_XFORM_DETAIL	DAS_WV_ITEM_XFORM_DETAIL	New	New table added for DAS Replication.
ITEM_XFORM_HEAD	DAS_WV_ITEM_XFORM_HEAD	New	New table added for DAS Replication.
SA_INPROGRESS_SALES	DAS_WV_SA_INPROGRESS_SALES	New	New table added for DAS Replication.
SVC_ITEM_CHRG	DAS_WV_SVC_ITEM_CHRG	New	New table added for DAS Replication.
SVC_ITEM_EXPENSES	DAS_WV_SVC_ITEM_EXPENSES	New	New table added for DAS Replication.
SVC_ITEM_HTS	DAS_WV_SVC_ITEM_HTS	New	New table added for DAS Replication.
SVC_ITEM_HTS_ASSESS	DAS_WV_SVC_ITEM_HTS_ASSESS	New	New table added for DAS Replication.
SVC_ITEM_SEASONS	DAS_WV_SVC_ITEM_SEASONS	New	New table added for DAS Replication.
SVC_ITEM_SUPP_COUNTRY_CFA_EXT	DAS_WV_SVC_ITEM_SUPP_CTRY_CFA	New	New table added for DAS Replication.
SVC_ITEM_SUPP_COUNTRY_LOC	DAS_WV_SVC_ITEM_SUPP_CTRY_LOC	New	New table added for DAS Replication.
SVC_ITEM_SUPP_CTRY_LOC_CFA_EXT	DAS_WV_SVC_ITM_SUP_CTY_LOC_CFA	New	New table added for DAS Replication.
SVC_ITEM_SUPP_UOM	DAS_WV_SVC_ITEM_SUPP_UOM	New	New table added for DAS Replication.
SVC_ITEM_SUPPLIER_CFA_EXT	DAS_WV_SVC_ITEM_SUPP_CFA_EXT	New	New table added for DAS Replication.
SVC_ITEM_TICKET	DAS_WV_SVC_ITEM_TICKET	New	New table added for DAS Replication.
SVC_ITEM_XFORM_DETAIL	DAS_WV_SVC_ITEM_XFORM_DETAIL	New	New table added for DAS Replication.
SVC_ITEM_XFORM_HEAD	DAS_WV_SVC_ITEM_XFORM_HEAD	New	New table added for DAS Replication.
SVC_ORDDETAIL	DAS_WV_SVC_ORDDETAIL	Updated	Added EARLIEST_SHIP_DATE and LATEST_SHIP_DATE columns
SVC_ORDHEAD	DAS_WV_SVC_ORDHEAD	Updated	Added APP_DATETIME column
SVC_PACKITEM	DAS_WV_SVC_PACKITEM	New	New table added for DAS Replication.
SVC_RPM_ITEM_ZONE_PRICE	DAS_WV_SVC_RPM_ITEM_ZONE_PRICE	New	New table added for DAS Replication.
SVC_UDA_ITEM_DATE	DAS_WV_SVC_UDA_ITEM_DATE	New	New table added for DAS Replication.
SVC_UDA_ITEM_FF	DAS_WV_SVC_UDA_ITEM_FF	New	New table added for DAS Replication.
SVC_UDA_ITEM_LOV	DAS_WV_SVC_UDA_ITEM_LOV	New	New table added for DAS Replication.
SVC_VAT_ITEM	DAS_WV_SVC_VAT_ITEM	New	New table added for DAS Replication.

Merchandising Subscription Metrics

With this update, a new batch process has been added to Merchandising to calculate the average number of active item/locations in a month. This value is then divided by 50,000, which is the metric on which the subscriptions for all the Merchandising cloud services are based. This value is then written to a a platform table to store the information. Then, if you are running Retail Home v20 or later, a standard report, comparing the purchased amount versus actual usage, will be available to view this information.

Steps to Enable

1. To enable the job as part of your batch cycle, follow the instructions below.

   1. Log into the Process Orchestration and Monitoring (POM) - Jet UI application with the Administrator role

   2. In the task list, select  Batch Administration. This will bring up the Batch Administration screen which has the following Tabs:

      1. Nightly

      2. Recurring

      3. Standalone 

   3.  Click on the Recurring Tab, Under Flows section, scroll (or filter) to locate RBM_METRICS_CALC_CYCLE job to be enabled and click the Enabled check box to enable or disable the job.

   4.  Changes are implicitly saved on change. Note: The changes will take effect once the new scheduler day is created.  The changes will not take effect for the current day.

2. To enable the reports to view this information in Retail Home (version 20.0 and later), see the Retail Home Administration Guide.

Batch Schedule Impacts

Process Name	Process Type	New/Updated?	Delivered
RBM_METRIC_CALC_CYCLE_PROCESS - contains two new batch processes used to calculate the metrics described above: RBM_METRIC_CALC_JOB SUBSCRIPTION_METRICS_UPDATE_JOB	Background Process - Cyclic	New	Disabled