Feature Summary

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?
New and Updated Options
Global Tax Solution (GTS) External Integration Enhancement	Fiscal Management	Medium	Yes	No
Induction Support for Conditional Tariff Treatments	Merchandising	Small	Yes	No
Manage Franchise Orders ReST Service	Merchandising	Small	Yes	No
Average Weight Recalculation for Inventory Adjustments	Merchandising	Small	Yes	No
Ownership Change Screen Changes to Support Mass Management	Merchandising	Small	Yes	No
Addition of Supplier Options Master in Invoice Matching	Invoice Matching	Small	Yes	No
Retry Support in Case of Functional Errors in SIOCS to MFCS Integration	Merchandising	Small	Yes	No
Enhancement to Use Translated UOM Codes in Spreadsheet Templates	Merchandising	Small	Yes	No
New ReST Service to Reserve Item Numbers from External Systems	Merchandising	Small	Yes	No
Purchase Order Level Obligations Sent for Payment before Order Closure	Merchandising	Small	Yes	No
Additional Reference Fields in the Sales Audit Transaction Search Screen	Sales Audit	Small	Yes	No
New ReST Service to Get Service Status	Merchandising	Small	Yes	No
Critical Business Alert Notifications	Merchandising	Small	No	Yes
Pricing Reclass Batch Performance and History Maintenance Enhancement	Pricing	Medium	Yes	No
New Screen for System Activiation	Merchandising	Medium	Yes	Yes
Data Access Schema (DAS) Administration	Merchandising	Small	No	Yes

Global Tax Solution (GTS) External Integration Enhancement

This cloud service update introduces new ReST services that can be used by an external system to fetch tax information from Global Tax Solution. This functionality is aimed to support external systems that require tax data. For example – POS systems. These new services have tax setup data provided in three main structures: tax region or tax location, tax group and tax rule. This enhancement also brings a new tax group ID included at item/location level in the Omni Channel item/location service.

Batch Schedule Updates

Process Name	Process Type	New or Updated?	Delivered
MERCHAPI_GTS_TAX_LOC_ITEM_ADHOC_JOB	Ad Hoc	New	Enabled

Integration Updates

API Name	Change Type	Integration Type	Field Name	Change Description
Get Store Tax Location	New	REST Service	Check the Inbound and Outbound Integration Guide for the detailed payload	New API
Get Item Location Tax Rules	New	REST Service	Check the Inbound and Outbound Integration Guide for the detailed payload	New API
Get Tax Rule Groups	New	REST Service	Check the Inbound and Outbound Integration Guide for the detailed payload	New API

DAS/RDS Updates

Application Table	DAS/RDS Table or View	Change Type	Change Description
VAT_CODES	RDS_WV_VAT_CODES	Update	Added the column TAX_AUTHORITY_ID
VAT_CODES	DAS_WV_VAT_CODES	Update	Added the column TAX_AUTHORITY_ID

Induction Support for Conditional Tariff Treatments

This cloud service update provides the user the ability to associate conditional tariff treatments with items to indicate the item’s eligibility for that tariff treatment. These tariff treatments are special programs established by governments/import authorities to facilitate trade into their country and are vital from an Import Management perspective. Conditional tariff treatments are those for which the duty rates are only made available to items that meet certain criteria. Items that satisfy these conditions are considered eligible for the tariff treatment. As part of this change, conditional tariff treatments can be associated with items via the Item Upload Service, the Item spreadsheet upload and/or Item Subscription APIs.

This feature provides the user with the flexibility to add or remove conditional tariff treatment data for items via any of the following methods:

Item Induction (New worksheet 'Item_Cond_Tariffs' added to the existing Item Master template)
Item Data Loading Configuration (New column ‘Cascade Conditional Tariff Treatments' added in Item_Service_Config worksheet)
Item Subscription API
New ReST API
- Create Item Conditional Tariff Treatments
- Delete Item Conditional Tariff Treatments

Integration Updates

API Name	Change Type	Integration Type	Field Name	Change Description
MerchIntegrations/services/item/conditionalTariffTreatments/create	New	REST Service	item, dataLoadingDestination, tariffTreatment, recalculateOrderInd	New service to associate conditional tariff treatments to an item
MerchIntegrations/services/item/conditionalTariffTreatments/delete	New	REST Service	item, tariffTreatment, recalculateOrderInd	New service to delete conditional tariff treatments associated with an item
MerchIntegrations/services/items/create	Update	REST Service	tariffTreatment, recalculateOrderInd	Existing Item service modified to create conditional tariff treatments along with item creation.
MerchIntegrations/services/items/delete	Update	REST Service	The conditional tariff data will be deleted with item deletion.	Existing Item service modified to delete conditional tariff treatments along with item deletion.
Item Subscription API	Update	RIB Message	Tariff Treatment, Recalculate Orders	New message types xitemcttcre and xitemcttdel are introduced to create and delete conditional tariff treatment data for items. Existing message type xitemcre also will handle creation of conditional tariff treatments.

Manage Franchise Orders ReST Service

This cloud service update includes a new ReST service for creation and maintenance (update, delete and cancel) of franchise orders in Merchandising sourced from external system, usually an order management system. Franchise orders created through this service will be systematically approved if the customer is set up for auto-approval, provided the customer has valid credit. A linked transfer, purchase order or store order will be created for the approved franchise orders. The service supports all update capabilities to franchise order header and details similar to user interface.

This new ReST service is used by an external source, usually an order management system, to create and maintain (i.e. update, delete and cancel) franchise orders in Merchandising. JSON payload for the the request contains action field at header and detail node. Acceptable values for status, header and detail cancel reason, actions fields along with necessary functional rules will be validated while processing.

The action field at header and detail determines the type of request (create/update/delete).
The status field at header will be used to derive the target status of franchise order to be created. If sent null, target status determined based on auto approve and credit indicators of franchise customer.
The header cancel reason and detail cancel reason are needed when delete action or cancel request at header and reduction in quantity ordered or deletion of item at detail.
Introduced processedStatus in header to show whether request status is fulfilled (created/updated/deleted).

Integration

API Name	Change Type	Integration Type	Field Name	Change Description
/franchiseManagement/franchiseOrder/manage	New	REST Service	New ReST service	This new service allows to create franchise orders and update or delete the existing franchise orders. This works based on request action type at header and detail node of the request.

Average Weight Recalculation for Inventory Adjustments

This cloud service update enables average weight recalculation for inventory adjustments when adjustment weight value is provided. This is specifically useful for catchweight simple packs and component items of catchweight types 3 and 4. Standalone adjustments to the average weight alone can also be carried out. To support this capability, the existing Inventory Adjustment functionality has been modified to allow capturing of actual weight as an input and to classify whether an inventory adjustment is a conventional adjustment (both stock on hand and weight) or a weight-only adjustment. This flexibility to capture weight is supported via the Inventory Adjustment screens, Inventory Adjustment Subscription RIB and ReST APIs and the Item Transformation ReST service.

This feature is applicable for:

Inventory Adjustments By Item screen
Inventory Adjustments By Location screen
Inventory Adjustment Subscription through RIB
Inventory Adjustment ReST Service
Item Transformation ReST Service

Integration

API Name	Change Type	Integration Type	Field Name	Change Description
MerchIntegrations/services/item/transformations/create	Update	REST Service	weightType, weight, weightUOM	Three new Optional fields added in both the transformationInput and transformationOutput nodesweightTypeweightweightUOM
Inventory Adjustment Subscription	Update	RIB Message	weight_type, weight_only_adjustment	Added weight_type and weight_only_adjustment fields in the RIB_InvAdjustDesc_REC object.
MerchIntegrations/services/inventory/inventoryAdjustments/create	Update	REST Service	WeightOnlyAdjustment, WeightType	Added WeightOnlyAdjustment, WeightType attributes in the payload.

Code Impact

Code Type	Code Type Description	Code	Code Description	New or Updated?	Delivered
INVW	Inventory Adjustment Weight Types	T	Total	New	Enabled
INVW	Inventory Adjustment Weight Types	WPU	Weight Per Unit	New	Enabled

DAS/RDS Updates

Application Table	DAS/RDS Table or View	Change Type	Change Description
ITEM_TRANSFORMATION_DETAIL	DAS_WV_ITEM_TRANSFORMATION_DETAIL	Update	Added WEIGHT_TYPE, WEIGHT and WEIGHT_UOM columns.
INV_ADJ	DAS_WV_INV_ADJ	Update	Added WEIGHT_ONLY_ADJUSTMENT and WEIGHT_TYPE columns.
ITEM_TRANSFORMATION_DETAIL	RDS_WV_ITEM_TRANSFORMATION_DETAIL	Update	Added WEIGHT_TYPE, WEIGHT and WEIGHT_UOM columns.
INV_ADJ	RDS_WV_INV_ADJ	Update	Added WEIGHT_ONLY_ADJUSTMENT and WEIGHT_TYPE columns.

Ownership Change Screen Changes to Support Mass Management

This cloud service update enhances the Ownership Change creation workflow with several mass management capabilities. An Upload List feature has been provided to allow for a list of items to be added to the Ownership Change transaction. The Item management capabilities (on an Ownership Change transaction) have been improved by adding the flexibility to delete details across a selection of items (or all items). Adding details to an Item has also been simplified by offering the capability to copy.

Consignment to Owned Type ownership changes now offer the additional capability to carry out the conversion with no change to costing attributes. If the original consignment item (which is subject to ownership change) used a unit cost-based pricing, then the same cost will be used for the owned item post such an ownership change. If the consignment item used a purchase rate based pricing, then the cost for the owned item would be calculated using the purchase rate and the unit retail of the location involved.

Addition of Supplier Options Master in Invoice Matching

This cloud service update introduces the option of maintaining Supplier Options Master. This is a set of default parameters which are used to build the Supplier Options when a new Parent Supplier is created in Merchandising though user interface or ReST API. This setting is only maintained for the Supplier Level.

The Master Supplier setting is only maintained for the Supplier Level. If a Master Supplier is present, it will be used to automatically populate the Supplier Options at the supplier level when a Parent Supplier is created in MFCS via the Supplier ReST Service, or via the Supplier User Interface (UI).

Steps to Enable

By default, no supplier options master is defined. A user can enable master functionality by defining supplier options master.

Retry Support in Case of Functional Errors in SIOCS to MFCS Integration

This cloud service update introduces an enhanced retry logic for transaction data published from Store Inventory Operations Cloud Service (SIOCS) to Merchandising Foundation Cloud Service (MFCS) using Direct DB integration. Previously, handling of retry had auto-retries for locking error but for functional error, the data was not retried, and the expectation was for the business users to review the error and resubmit retry from the screen. With the enhanced logic, there will be auto-retry 10 times for every failure (including locking) and then have it presented to the business users in the screen to review and take further action.

Enhancement to Use Translated UOM Codes in Spreadsheet Templates

In the Merchandising solutions’ user interface, secondary language users can see and enter units of measure (UOMs) values using translated UOM codes which are defined along with the units of measure. New for this release, these same users are also able to view and enter UOM codes in their specified language within spreadsheet templates. This is facilitated by the addition of several new code types which capture the UOM code translations in groups, as they are needed for UOM columns in the various spreadsheet templates. A new system option, Use Translated UOM Codes for Spreadsheet Templates, was also introduced to allow you to indicate to the system if you want this new feature enabled.

This enhancement allows unit of measure (UOM) values to be displayed in the user's language in spreadsheet templates. The solution takes advantage of the spreadsheet template framework which allows for the display and entry of translated code descriptions via a drop down list. New code types in the code_detail table were added to use this existing framework to contain lists of units of measure which are applicable for the various entities or transactions against which the unit of measure is captured. These new code types are: UEPM, UPMQ, UCPU, UDIM, UMSS, ULVL, UMSC and UOMS. Furthermore, a new system option, Use Translated UOM Codes in Spreadsheet Templates (trans_uom_codes_in_s9t_ind) was added to Merchandising to allow customers to only toggle on this functionality if needed. It is turned off by default and the customer can toggle this indicator in the System Options screen to enable drop downs on unit of measure columns in spreadsheet templates. When the new system option is turned on, spreadsheets downloaded from that point onward will contain a drop down list for each UOM field. The language will be based on user language if a translation exists for the code under the corresponding code type. If the new system option is toggled off, drop down lists will not be displayed on the UOM fields in the spreadsheet templates, and customers are expected to key in the UOM code in English, valid values are in the UOM Class table (uom_class) and are defined via the Units of Measure spreadsheet template.

With this solution, UOM display and validation in downloaded or uploaded spreadsheet templates is no longer dependent on values in the uom_class_tl table. After this fix:

For customers who choose to use LOVs for UOMs in templates
1. Download from RMS or STG to file - Templates will show drop down lists for UOMs as long as the total number of characters do not exceed 256. The UOM will be in user language.
2. Upload - UOMs are expected to be in user lang.
3. Rest API or RIB to STG or RMS - UOMs will continue to be Master/English UOMs
4. Setting the new trans_uom_codes_in_s9t_ind to N will delete the specific code types for UOMs from s9t_list_vals and succeeding upload/download will have the following behavior (B)

For customers who leave trans_uom_codes_in_s9t_ind as N
1. Download from RMS or STG to file - Templates will not have drop down lists for UOMs. UOMs will be displayed in English.
2. Upload - UOMs are expected to be in English.
3. Rest API or RIB to STG or RMS - UOMs will continue to be Master/English UOMs

Note:

There is a 256 character limit for drop downs in Excel and two of the new code types, All Units of Measure (UOMS) and Cases, Pallets and All Units of Measure Except Pack and Miscellaneous Classes (UCPU), will exceed this limit. Therefore, we have selected a subset of the units of measure which are not commonly used and set the Used flag to No (N) to ensure the list of those flagged as Used = Yes (Y) does not exceed this limit. This code type should be reviewed in detail to ensure all units of measure used in your business are have the Used flag set to Yes (Y), any that are not used should have the Used flag set to No (N). This can be done via the Codes and Descriptions spreadsheet template. Beyond flagging unused codes under the All Units of Measure (UOMS) and Cases, Pallets and All Units of Measure Except Pack and Miscellaneous Classes (UCPU) code types to avoid exceeding the 256 character limit, the other new code types listed above should also be reviewed and any unit of measure not needed for your business operations should have the Used flag set to No (N) to minimize the values displayed in the drop down, thus providing a better experience for your users.
New code_detail entries need to have translations created. Translation strings for the new codes are not yet included in this release. Translations for each unit of measure code under the new code types can be added via the Codes and Descriptions spreadsheet template.

Steps to Enable

Perform a thorough analysis to determine the full set of units of measure which are used in your business in each of the units of measure classes.
Review each of the new code types and ensure that all units of measure you use in your business are included in the code types where applicable and have the Used flag set to Yes (Y). The rest of the codes should have the Used flag set to No (N).
Any units of measure that have been added in your system post-installation will also need to be added to the corresponding code type(s).
Add translations for codes under the new code types for all desired languages.
In the System Options screen, check the Use Translated UOM Codes in Spreadsheet Templates checkbox to enable drop downs in spreadsheet templates.
Ensure your users are aware they will need to download new templates after this system option is checked. The impacted spreadsheet templates are:
- Cost Components
- HTS Setup
- HTS Definition
- Tax Rules
- Item Master
- Purchase Order
- Price Changes
- Promotions

New ReST Service to Reserve Item Numbers from External Systems

A new ReST web service has been introduced to allow external systems to reserve a list of predefined item identifiers in Merchandising. This functionality is aimed to prevent the accidental creation of items in Merchandising using numbers that are not yet ready for ingestion. External systems can submit a list of item identifiers to be reserved and the reserved items are stored and remain reserved until the reservation is deleted or until the reserved identifier is explicitly assigned to a new item.

Integration

API Name	Change Type	Integration Type	Field Name	Change Description
Manage Item Numbers	New	REST Service	MerchIntegrations/services/item/itemNumbers/manage	New Service to Manage Item Number Reservations

Purchase Order Level Obligations Sent for Payment before Order Closure

A new option has been made available to generate non-merchandise invoices from Purchase Order (PO) or Purchase Order/Item (POIT) level obligations and transmit them to Invoice Matching prior to the purchase order being closed in Merchandising, as long as the order has just a single location linked with it, or component/location level details are provided on the obligation. This provides the ability to pay the invoice in a timely manner, especially for import orders where obligations may be sent well in advance of the order being received at the final destination. Previously, these level obligations could not be sent to Invoice Matching and from there on to Financials for payment until the associated purchase order was closed.

Additional Reference Fields in the Sales Audit Transaction Search Screen

This cloud service update expands the search capabilities of the Sales Audit Transaction Search screen by allowing for search/filter based on one or more of the thirty-one reference fields on the transaction record. These reference fields spanning transaction header, item, tender, tax and discount lines are made available via the Advanced Search option.

New ReST Service to Get Service Status

This cloud service update introduces a new ReST service that can be used for querying the status of a ReST web service call using an X-Correlation-ID. The correlation ID included in the request HTTP header can be used as the input, or if it was not passed in the original request, the one from the response HTTP header can be used. This service will return all the entries in service_metrics table against that correlation ID. The response supports pagination and if there are multiple pages of response, next link to call subsequent pages can be used. This service additionally checks the input correlation ID against the request_id field to handle the scenario where the x_correlation_id is null in the service_metrics table because it was not included in request HTTP header.An additional query parameter of includePayload, supports a value of yes ('Y') or no ('N') can be used to retrieve the request and response payload for that request. In the case of a service error (response code of 300 or greater) the response payload will be included irrespective of includePayload parameter.

Integration

API Name	Change Type	Integration Type	Field Name	Change Description
Get ReST Service Status	New	REST Service	MerchIntegrations/services/administration/operations/restService/status	New Rest service

Critical Business Alert Notifications

This version of Merchandising introduces a set a notifications for selected business users for application availability during the nightly batch cycle and advance warning for data issues that can potentially hinder successful month-end data processing. For data issue warnings, the framework also provides a way to download data set that has issues, through a Merchandising screen to facilitate appropriate corrective measures.

Month End Processing Data Issue alerts aim to notify users about most common issues related to month-end processing such as missing Stock Ledger related data or open transactions in advance and provide a way to make corrections. These alerts can be configured to be triggered at customer defined intervals else they will automatically trigger 5 days before the month end.

The Application Availability notification informs the user when the applications are available to be used online and for integrations during the nightly batch run before actual completion of the nightly cycle.

The list of users receiving these notifications can be managed in ORAAC. There is also a new security privilege that need to be associated with users who can download data with issues.

Steps to Enable

Open Notification Screen in ORAAC application and setup contact mailing group for the intended audience.
Enable following jobs in POM
1. BATCH_EMAIL_ALERT_ADHOC_JOB (if required)
2. BATCH_EMAIL_ALERT_JOB
To grant access to the Download Alert Data screen, follow the security configuration instructions for this release to set up the new privilege and duty, and grant the respective duty to the role that needs the access.

For more information on Critical Business Alert Notifications, see the Merchandising Administration Guide.

Enable Security Changes

Based on these new/updated duties and privileges, the following actions are required in the order described below in order to enable the features. If this update doesn't contain changes related to one of the steps below, it can be skipped and you can move to the next one. 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:

Select Settings > Security > Roles
Click on the Add iconic button or select Add from the Actions menu
Add the first new duty, including the name, and optionally the description in the popup displayed. Then click OK.
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.

Select Settings > Security > Role Mappings
Selecting a role that will be assigned one or more of the duties
For each role, click Select and Add and then select the duties you want to add to the role using the popup
Repeat for each role where you want to add the new duties

Step 3: Synchronize Privileges with New Duties

Each new duty then needs to have its privileges synchronized.

Select Settings > Security > Policy Patching
Select Sync with Patch
Under the Base Policies tab, working through the duties one at a time, select the checkbox next to each the corresponding privileges
Click Copy to Custom and then select the duty
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.

Batch Schedule

Process Name	Process Type	New or Updated?	Delivered
BATCH_EMAIL_ALERT_ADHOC_PROCESS	Ad Hoc	New	Disabled
BATCH_EMAIL_ALERT_PROCESS	Nightly	New	Disabled

Code Impact

Code Type	Code Type Description	Code	Code Description	New or Updated?	Delivered
MANT	Merch Alert Notification Types	8210	Month End Health	New	Enabled

Security

Privileges

Priv Name	Change Type	Priv Description	Parent Duty
VIEW_SALES_PROCESSING_CHECK_ALERT_DATA_PRIV	New	This privilege grants users access to the Download Alert Data screen and the ability to download Sales Processing Check supporting data, related to email alerts raised during the processing of health checks/notification areas.	RMS_ALERT_DATA_SALES_PROCESSING_INQUIRY_DUTY
VIEW_MONTH_END_HEALTH_CHECK_ALERT_DATA_PRIV	New	This privilege grants users access to the Download Alert Data screen and the ability to download Month End Health Check supporting data, related to email alerts raised during the processing of health checks/notification areas.	RMS_ALERT_DATA_MONTH_END_INQUIRY_DUTY

Duties

Duty Name	Change Type	Duty Description	Child Duty	Base Role
RMS_ALERT_DATA_MONTH_END_INQUIRY_DUTY	New	A duty for downloading and viewing supporting data via the Download Alert Data screen, related to email alerts raised during the processing of the Month End health check/notification area.		RMS_APPLICATION_ADMINISTRATOR_JOB
RMS_ALERT_DATA_SALES_PROCESSING_INQUIRY_DUTY	New	A duty for downloading and viewing supporting data via the Download Alert Data screen, related to email alerts raised during the processing of the Sales Processing health check/notification area.		RMS_APPLICATION_ADMINISTRATOR_JOB

Pricing Reclass Batch Performance and History Maintenance Enhancement

This cloud service update introduces updates to the Pricing Reclass batch program for better performance. The batch operation is now a multi-threaded process, and history tables have been added for troubleshooting purposes with a purge option after a user defined data retention days.

Enhancements include:

Batch is multi threaded based on old_dept, item_parent. Threading LUW is defined in rpm_batch_control with program_name = 'Item Reclass Batch'.
Below history tables are added for troubleshooting purpose. RPM_ITEM_MODIFICATION_HIST - RPM_ITEM_MODIFICATION RPM_ITEM_MOD_THREAD_HIST - RPM_ITEM_MODIFICATION_THREAD

History tables will be purged in purge batch using rpm_purge_config_options.hist_data_purge_days as retention period. Any partition which is older than retention period will be dropped.
Any record being deleted from rpm_item_zone_price will be populated into RPM_ITEM_ZONE_PRICE_HIST. This history table will be purged in purge batch using config_value in rpm_admin_config for config_key = 'RIZP_HIST_DATA_RETENTION_DAYS', as retention period. Any partition which is older than retention period will be dropped.
Once the reclass is processed and batch completes successfully, the data will be deleted from both RPM_ITEM_MODIFICATION and RPM_ITEM_MODIFICATION_THREAD tables. If the batch fails in between, the status column in these 2 tables will determine which records/threads are processed (STATUS = 'C'). Unprocessed records will have status = 'N'.

New Screen for System Activation

Upon provisioning of an environment, the Merchandising solutions will remain unavailable until the system is activated via a new System Activation screen which is accessed via Merchandising. The System Activation screen allows you to enter and modify these install-time parameters in a self-service manner. These system settings can be entered, saved, reviewed and modified as desired. Once the settings are as desired, the system can be activated by clicking an Activate button. Post activation the system will be available for use and values that were entered in the System Activation screen can be viewed via the System Options screen. Non-production environments can be activated individually, and prior to the activation of a production environment, to allow time for thorough review and testing of activation settings to ensure settings are as desired before activating production.

Data Access Schema (DAS) Administration

A new Data Access Schema (DAS) Administration screen is now available to support the downloading of the DAS patch for application in your environment. The task previously required the raising of a service request, but can now be done in a self-service manner. A new system option was also added which allows the ability to indicate whether or not DAS Replication is desired in the system. The option is initially set to No (N), but the capability can be enabled by setting the option to Yes (Y).

Steps to Enable

Navigate to the Merchandising System Options screen via the System Options link under the Application Administration folder in the Tasks list. In the System Options screen, go to the System container and check the Allow Data Access Schema (DAS) Replication checkbox to enable this new capability.

System Options

Attribute Name	New or Update?	Attribute Description	Default Value
allow_das_replication_ind	New	The Allow Data Access Schema (DAS) Replication system option indicates whether or not DAS replication is allowed for the Merchandising solutions. Valid values are Yes (Y) or No (N). This field will default to No (N)	N

Security

Privileges

Priv Name	Change Type	Priv Description	Parent Duty
MAINTAIN DAS ADMINISTRATION PRIV	New	A privilege for downloading a DAS patch via the Data Access Schema Administration screen.	DAS ADMINISTRATION MANAGEMENT DUTY
DAS ADMINISTRATION INQUIRY DUTY	New	A privilege to view the Data Access Schema (DAS) Administration link in the Tasks list.	DAS ADMINISTRATION INQUIRY DUTY

Duties

Duty Name	Change Type	Duty Description	Child Duty	Base Role
DAS_ADMINISTRATION_MANAGEMENT_DUTY	New	A Duty for downloading a DAS patch via the Data Access Schema Administration screen.	DAS_ADMINISTRATION_INQUIRY_DUTY	RMS_APPLICATION_ADMINISTRATOR_JOB
DAS_ADMINISTRATION_INQUIRY_DUTY	New	A duty to access the Data Access Schema (DAS) Administration screen.		RMS_APPLICATION_ADMINISTRATOR_JOB