1. Release Readiness Guide
  2. Feature Summary
  3. Noteworthy Enhancements

Noteworthy Enhancements

Note:

Oracle Retail has adopted a new numbering system to correlate the release numbers with Major Updates and the calendar for better clarity. The first two digits are the calendar year; the next digit is the Major release number; the third three digits reflect the calendar quarter and the month within that quarter; and the final digit represents the hot fix sequence.

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.

    • 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 Customer Action Required?
Enhanced Upcharge Calculations

Merchandising

Small

Disabled

Yes
Inclusion of Upcharges in Pricing Cost for Company-owned Locations

Merchandising

Small

Disabled

Yes
Detailed Mapping of Upcharges to GL Accounts

Merchandising

Small

Disabled

Yes
Min/Max Optimization in Replenishment Attributes

Merchandising

Small

Disabled

Yes
Web Service Configuration

Merchandising

Small

Disabled

Yes
Cost Change ReST Web Service

Merchandising

Small

Enabled

No
ReST Service Enabling of External Integration

Merchandising

Large

Disabled

Yes
Enabled Custom Flex Attributes (CFAS) for Promotion Offers

Pricing

Large

Disabled

Yes

Enhanced Upcharge Calculations

The current process that is used for calculation of Up Charges for movement of goods cannot cater to certain legal requirements around these charges, such as one cost being based to an extent on another one (i.e., one up charge defined as a % of another up charge), the charge being calculated based on the supplier cost (and not the weighted average cost), and so on. To handle this, the existing Up Charge functionality has been expanded to include the above features in their definition process. Upcharge functionality has also been expanded to support a different cost basis besides the weighted average cost but including the option to use the Supplier Unit Cost or the Off-Invoice Net Cost as the basis.

Steps to Enable

To enable upcharge compounding in Merchandising, Computation Value Bases (CVBs) have been utilized. To use an upcharge value as the basis for another a CVB must be defined and associated to an upcharge. The upcharge calculation basis must be of type Value.

Code Updates

Code Type Code Type Description Code Code Description New/Updated? Delivered

EXCB

Expense Cost Basis

W

Weighted Average Cost/Acquisition Cost

Update

Enabled

ICTP

Default Intercompany Transfer Price

R

Retail Based

Update

Enabled

ICTP

Default Intercompany Transfer Price

S

Supplier Cost

Update

Enabled

ICTP

Default Intercompany Transfer Price

W

Weighted Average Cost

Update

Enabled

UCCB

Up Charge Cost Basis

N

Off-Invoice Net Cost

Update

Enabled

UCCB

Up Charge Cost Basis

S

Supplier Cost

Update

Enabled

UCCB

Up Charge Cost Basis

W

Weighted Average Cost/Acquisition Cost

Update

Enabled

Data Access Schema (DAS) Updates

Table Name View Name New/Updated? Change Notes

DEPT_CHRG_DETAIL

RDS_WV_DEPT_CHRG_DETAIL

Update

Added columns CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND, DISPLAY_ORDER

DEPT_CHRG_DETAIL

DAS_WV_DEPT_CHRG_DETAIL

Update

Added columns CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND, DISPLAY_ORDER

ELC_COMP

RDS_WV_ELC_COMP

Update

Added Column INCLUDE_IN_TOTAL_UP_CHRG_IND

ITEM_CHRG_DETAIL

DAS_WV_ITEM_CHRG_DETAIL

Update

Added columns CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND, EST_UP_CHRG_VALUE

SUBCLASS

RDS_WV_SUBCLASS

Update

Added Column INCLUDE_IN_TOTAL_UP_CHRG_IND, INCLUDE_UP_CHRG_IN_PRC_COST

SVC_ITEM_CHRG

RDS_WV_SVC_ITEM_CHRG

Update

Added columns CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND, EST_UP_CHRG_VALUE

Integration Impacts

Name New/Updated Integration Type Field Name Change Notes

Computation Value Base (Induction)

Update

Table-based

Up_Charge_CVBs, Up_Charge_CVB_Trans

Two new worksheets (Up_Charge_CVBs and Up_Charge_CVB_Trans) have been added to Computation Value Base template

Cost Components (Induction)

Update

Table-based

INCLUDE_IN_UPCHARGES_IND

Added new column 'Include in upcharge indicator' to the Cost_Components worksheet of Cost Components induction template

Item Master (Induction)

Update

Table-based

CVB_CODE, COST_BASIS, EST_UP_CHRG_VALUE, INCLUDE_IN_UPCHARGES_IND

Added new columns in Item Upcharges Worksheet of Item Master Data induction template: Computation Value Base Cost Basis Value Include in Total Up Charges

Item Subscription

Update

RIB Message

CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND

Added new attributes to “RIB_XItemUCDtl_REC” for creating and updating item upcharges: CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND

Merchandise Hierarchy Department Subscription

Update

RIB Message

CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND

Added new attributes to “RIB_XMrchHrDeptUCDtl_REC” for create and update messages: CVB_CODE COST_BASIS INCLUDE_IN_TOTAL_UP_CHRG_IND

Store Subscription

Update

RIB Message

CVB_CODE, COST_BASIS, INCLUDE_IN_TOTAL_UP_CHRG_IND

Add new attributes to “RIB_XStoreUpChrgDtl_REC” for create and update message: CVB_CODE COST_BASIS INCLUDE_IN_TOTAL_UP_CHRG_IND

Merchandise Hierarchy Subclass Subscription

Update

RIB Message

DEFAULT_IC_TSF_PRICE

Modified RIB_XMrchHrSclsDesc_REC to add new attribute default_ic_tsf_price

Inclusion of Upcharges in Pricing Cost for Company-owned Locations

In the Pricing Cloud Service, the Pricing Cost can be used and referred to while making decisions to determine the price of an item at a location. This Pricing Cost is maintained by Merchandising in the PRICING_COST column of the FUTURE_COST table, at the item/supplier/origin country/location level. Also, the ‘Acquisition Cost’ is maintained in the ACQUISITION_COST column of the mentioned table.

Currently, in addition to the supplier cost, the pricing cost and the acquisition cost can have different elements such as ELC components and Deals incorporated. As different suppliers can technically supply the same items for a location, the elements that go into the pricing cost and the acquisition cost are based on the Primary Supplier and Country specified for the item/location. The two mentioned costs do have the ability to include Up Charges in the existing system, but it is only for the Franchise stores, and is achieved by defining the Cost Templates. The Company-owned stores, however, do not have the feature to include Up Charges in the pricing cost, which is something that may be useful to certain retailers. With this enhancement, the ability to optionally include Up Charges in the pricing cost for items against company-owned stores has been added in Merchandising.

Steps to Enable

By default, upcharges will not be included in the Pricing Cost. To include an upcharge value in the Pricing Cost for items in a subclass, the Include Up Charges in Pricing Cost checkbox must be checked in the Subclass Maintenance screen.

Detailed Mapping of Upcharges to GL Accounts

Changes have been done to ensure that the Upcharge GL posting can be done at a more detailed level. When transfers occur in MFCS, the system can include additional financial transactions related to these transfers in addition to just the cost of the merchandise. These additional costs are defined as Up Charges in Merchandising and are based on the retailer’s definition of different types of charges, along with setup to determine which charges should be applied and under which circumstances. When the transfer occurs, the Upcharges defined for that transfer will be aggregated and posted in TRAN DATA under two heads namely Profit Upcharges (Transaction Code 28) and Expense Upcharges (Transaction code 29).  The Upcharge definition includes additional parameters such as up charge group that can be used to further breakdown the overall up charge into further sub-heads, but currently the transaction posting logic as well as the posting logic into financials does not support posting of upcharges at a level lower than transaction code.

With this enhancement, it is ensured that the existing subgroup categorizations such as the upcharge group is respected during the transaction recording as well as posting to financials. This in turn would give retailers the flexibility to further categorize and track each of their different Up Charges, or groups of related upcharges together in the general ledger.

Steps to Enable

When upcharges are posted to TRAN DATA, they now include the Upcharge Group in the GL Reference Number column. To map these upcharges to the General Ledger at the Type / Group level the General Ledger cross reference mappings must be updated to include the GL Reference Number. The General Ledger Cross Reference details can be accessed through the Foundation Data Loading feature under the template type Financial Administration and template GL Cross Reference.

Min/Max Optimization in Replenishment Attributes

The Replenishment workflow has been updated to include an Optimize flag on the min / max replenishment method. This flag will be used by the Inventory Optimization (IO) application to determine which item/locations should be considered for optimization of the Minimum and Maximum Stock attributes. When the Optimize flag is selected, the min / max replenishment method will include a Service Level holding the percentage value used as the ‘in stock’ target level. The use of the Optimize flag will be controlled via a new system option - Allow Optimize Option for Min / Max Method.   If this system option is enabled, the Optimize flag will be displayed when the Min / Max Replenishment Method is selected. The ‘Allow Optimize Option for Min / Max Method’ should be left unchecked for customers not using Inventory Optimization (IO) to integrate with Merchandising to optimize replenishment Min / Max parameters.

The Optimize flag and Service Level are applicable to all methods of updating Replenishment attributes including:  

  • Replenishment Attributes (create and manage)

  • Scheduled Replenishment Updates (create and manage)

  • Mass Update of Replenishment Attributes

  • Mass Change of Replenishment Attributes (from Item List)

  • Master Replenishment Attributes

  • Spreadsheet induction

  • Web Service: Replenishment Scheduled Services

  • Batch Update: Upload Replenishment Data (replindbatch.ksh)

Additionally, as part of this requirement, the Replenishment Method container in the maintenance screens has been redesigned, repositioning all the existing fields to a cleaner more efficient layout. The functionality and validations of the fields in the Method container will not change, just their positioning on the screen.  

The rplatupd batch will now populate the optimize indicator and service level columns in REPL_ITEM_LOC, MASTER_REPL_ATTR and REPL_ATTR_UPD_HIST tables for replenishment method Min/Max based on the item forecast indicator.

Steps to Enable

The use of the Optimize flag will be controlled with a new system option called: Allow Optimize Option for Min / Max Method. To enable the use of this feature the checkbox of this new system option should be checked. This can be done through System Options UI following these steps:

  • In the Merchandising task list, select Application Administration → System Options.

  • Navigate to the Replenishment sub section under Inventory section.

  • Check the Allow Optimize Option for Min / Max Method field.

  • Click Save and Close to save the changes and exit the system options screen.

A new version of the Replenishment Spreadsheet template must be downloaded to use the Optimize column.

System Option Updates

Attribute Name New/Updated? Description Patch Default

Allow Optimize Option for Min / Max Method

New

This system option controls the use of the new Optimize flag in min / max replenishment method. If this option is checked i.e. Y, the Optimize flag will be displayed when the Min / Max Replenishment Method is selected. This system option must be left unchecked for customers not using Inventory Optimization (IO) to integrate with Merchandising to optimize replenishment Min / Max parameters.

N

Data Access Schema (DAS) Updates

Table Name View Name New/Updated? Change Notes

MASTER_REPL_ATTR

DAS_WV_MASTER_REPL_ATTR

Update

Added column OPTMIZE_IND

PROCUREMENT_UNIT_OPTIONS

RDS_WV_PROCUREMENT_UNIT_OPTIONS

Update

Added Column: ALLOW_OPTIMIZE_FOR_MIN_MAX

REPL_ATTR_UPDATE_HEAD

RDS_WV_REPL_ATTR_UPDATE_HEAD

Update

Added column OPTMIZE_IND

REPL_ITEM_LOC

DAS_WV_REPL_ITEM_LOC

Update

Added column OPTMIZE_IND

REPL_RESULTS

DAS_WV_REPL_RESULTS

Update

Added column OPTMIZE_IND

SYSTEM_OPTIONS

DAS_WV_SYSTEM_OPTNS

Update

Added column ALLOW_OPTIMIZE_FOR_MIN_MAX

Web Service Configuration

With this update, there are several ReST Webservices added for data publication from Merchandising to external applications. To enable or disable these services, the Web Service Configuration screen had been added to the Merchandising application. The existing Merchandising to Omnichannel integration ReSTful services can also be enabled for external applications using this screen. 

For more details on the ReSTful Webservices and Web Service Configuration screen, see the Merchandising Administration Guide, and Operations Guide Volume 2 – Message Publication and Subscription Designs Guide.

Steps to Enable

To access the Web Service Configuration screen, follow the security configuration instructions for this release to add the respective duty to the role that needs the access.

New Duties

Duty Duty Description Child Duties Base Role New/Updated?

RMS_WEB_SERVICE_CONFIG_INQUIRY_DUTY

A duty for viewing web service configurations.

    

New

RMS_WEB_SERVICE_CONFIG_MGMT_DUTY

A duty for maintaining web service configurations. This duty is an extension of the Web Service Configuration Inquiry Duty.

    

New

New Privileges

New Privilege Priv Description Parent Duty Change Type

MAINTAIN_WEB_SERVICE_CONFIG_PRIV

A privilege for maintaining web service configurations. Users with this privilege must also have the View Web Service Configurations Priv.

RMS_WEB_SERVICE_CONFIG_MGMT_DUTY

New

VIEW_WEB_SERVICE_CONFIG_PRIV

A privilege for viewing web service configurations

RMS_WEB_SERVICE_CONFIG_INQUIRY_DUTY

New

Cost Change ReST Web Service

A new ReST Service has been introduced to support creating, updating, and deleting cost change and cost change details in RMS. The action attribute will determine the action to be performed on a cost change.

This new service will use the cost change induction staging tables, populate the same followed by the invoking existing cost change induction core service that validates the data and populates the base tables.  Any validation errors and exceptions, including unprocessed records from the execution of the core service will be returned via a response object.

Data Access Schema (DAS) Updates

Table Name View Name New/Updated? Change Notes

CORESVC_COSTCHG_ERR

DAS_WV_CORESVC_COSTCHG_ERR

Update

Added Columns: COST_CHANGE, LOC, LOC_TYPE

Integration Impacts

Name New/Updated Integration Type Field Name Change Notes

RmsRESTServices/services/private/costChange

New

REST Service

  

This new service will be used to consume cost changes into Merchandising. The action attribute (CRE,MOD,DEL) provided in the input JSON will determine the action to be made on a cost change.

ReST Service Enabling of External Integration

These new services provide an alternate for the previous method of integration, which leverages the Oracle Retail Integration CS (RICS) component (RIB and BDI) between the Merchandising applications and External systems. The existing services via RICS will remain to support integrations with older versions of these solutions, as well as for backward compatibility for 3rd party solutions.

These new services retrieve stored json message from new tables (Integration Cache tables) to serve the external consumer. These new tables require initial seeding from the base tables and continuous maintenance to keep them updated for changes in the base tables. The initial data loading and continuous maintenance is carried out by new batch jobs that support two modes: 

  • Bulk Data Processing: This process is used for bulk maintenance of the json cache table. The bulk data batch processing is generally applicable during the initial loading of the json cache table or if an enhancement to the service requires a refresh of existing cache. This process also supports purging the json cache tables in scenarios where there are no active consumers for a service.

  • Delta Processing: Delta processing is used to populate/merge the delta changes that were made to the base Merchandising and Pricing tables into the respective json cache tables based on interface change log table entries. The delta processing job for each API must be scheduled to run at regular frequency throughout the day to scan the change log tables for changes and build the json messages to keep the delta update ready for the consuming system.

The Integration Cache tables are necessary for serving the data needs of external applications. These tables hold data in JSON/API-friendly objects. These cache tables are initially populated when the API is enabled post implementation (via Web Service (REST) Configuration screen) through Data Refresh wrapper script. In addition, based on the Integration change log (ICL) tables these tables are modified through delta wrapper script. The cache tables contain, in many cases, only a subset of the columns of their corresponding merch table. Only columns useful to external applications are included in the JSON/API-Friendly objects.

The Web Service (REST) Configuration screen will be used for enabling/disabling of the following new services:

  • Suppliers

  • Partners

  • Orders

  • Allocations

  • RTVs

  • Work Orders In

  • Work Orders Out

  • Transfers

  • Merchandise Hierarchy

  • Organizational Hierarchy

  • Receiver Unit Adjustments

  • Differentiator Groups

  • Differentiators

  • Differentiator Types

  • Stores

  • Warehouses

  • Items

  • UDAs

  • Item VAT

Steps to Enable

The following steps are required to enable the use of these new services:

  1. In the Merchandising task list, select Application Administration → Web Service Configuration

  2. Update the enabled checkbox of the service which is required for integration with external.

  3. Click Save and Close to save your changes and exit the Web Service Configuration screen.

  4. Enable Batch Jobs:

  1. If the services are integrated, the batch process should be enabled for full refresh and delta data processing using the Batch Administration screen of POM.

  2. The process MERCHAPI_REFRESH_CYCLE_PROCESS should be enabled for initial load and data refresh.

  3. The following processes should be enabled for delta data processing for the respective entities:

    MERCHAPI_DELTA_EXT_SUPPLIER_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_PARTNER_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_ORDER_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_ALLOCATION_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_RTV_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_WO_IN_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_WO_OUT_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_TRANSFER_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_MERCH_HIER_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_ORG_HIER_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_RUA_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_DIFF_GROUP_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_DIFF_IDS_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_DIFF_TYPE_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_STORE_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_WAREHOUSE_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_ITEM_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_ITEM_VAT_ADHOC_PROCESS

    MERCHAPI_DELTA_EXT_UDA_ADHOC_PROCESS

  4. These processes must be set up as cyclic processes to allow them to be running continuously and hence this should be configured in Recurring tab and at individual hourly cycles. The delta process should be running throughout the day and should be enabled in all the hourly cycles. The process for initial load/refresh can be set up to run less frequently - once or twice a day.

  5. In addition to enabling the cycle process, review the list of the jobs in Batch Administration screen and enable the jobs only for the services that are planned to be used.

  6. Review the job parameter to configure the sleep_seconds parameter for the delta data pre-processing (for Merchandising data only). The sleep time configuration controls the frequency in which the delta updates are processed and loaded into the json cache table. The default configuration is 15 min for every API. This can be changed to configure how soon an update to a data is available for the consuming system in the service call.

  7. The delta and initial jobs for Merchandising also support a parameter called exec_seconds that defines the duration of run for every instance of that batch job run. The delta processing job will keep on polling the ICL table at every sleep_seconds duration and will end the job when exec_seconds is reached. The configuration of exec_seconds should be done based on how many hourly cycles the jobs were configured. The default configuration is for 2 hours run of each batch call.

  8. Along with enabling the jobs and process, the scheduling of the process must be performed using the Scheduler Administrator screen. The enabled process should be selected, and the start time should be configured. Example - If there are 12 cycles for MERCHAPI_REFRESH_CYCLE_PROCESS defined, 12 schedules with a gap of 2 hours should be defined at say 12:30am, 2:30am, 4:30am and so on.

Batch Schedule Impacts

Process Name Process Type New/Updated? Delivered

MERCHAPI_DELTA_EXT_SUPPLIER_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_ORDER_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_WO_OUT_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_TRANSFER_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_MERCH_HIER_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_RUA_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_DIFF_GROUP_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_WAREHOUSE_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_ITEM_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_ITEM_VAT_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_PARTNER_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_ALLOCATION_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_RTV_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_WO_IN_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_ORG_HIER_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_DIFF_IDS_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_DIFF_TYPE_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_STORE_ADHOC_PROCESS

Ad Hoc

New

Disabled

MERCHAPI_DELTA_EXT_UDA_ADHOC_PROCESS

Ad Hoc

New

Disabled

Integration Impacts

Name New/Updated Integration Type Field Name Change Notes

MerchIntegrations/services/foundation/supplier

New

REST Service

  

This service will be used by External applications to retreive all active supplier site details

MerchIntegrations/services/foundation/partner

New

REST Service

  

This service will be used by External applications to retreive all the partner details.

MerchIntegrations/services/procurement/order

New

REST Service

  

This service will be used by External applications to retreive all approved and closed order details.

MerchIntegrations/services/inventory/allocation/{allocNo}

New

REST Service

  

This service will be used by External applications to retreive a specific allocation information.

MerchIntegrations/services/inventory/woin

New

REST Service

  

This service will be used by External applications to retreive all work order details associated with purchase orders.

MerchIntegrations/services/inventory/woin/{workOrderId}

New

REST Service

  

This service will be used by External applications to retreive a specific work order information that is associated with a purchase order.

MerchIntegrations/services/inventory/woout/{workOrderId}

New

REST Service

  

This service will be used by External applications to specific work order detail associated with a transfer.

erchIntegrations/services/foundation/merchhier/division/{divisionId}

New

REST Service

  

This service will be used by External applications to retreive a specific division information.

MerchIntegrations/services/foundation/merchhier/groups

New

REST Service

  

This service will be used by External applications to retreive all the groups information.

MerchIntegrations/services/foundation/merchhier/deps

New

REST Service

  

This service will be used by External applications to retreive all the department information.

MerchIntegrations/services/foundation/merchhier/deps/{departmentId}

New

REST Service

  

This service will be used by External applications to retreive a specific department information.

MerchIntegrations/services/foundation/merchhier/class

New

REST Service

  

This service will be used by External applications to retreive all the class information.

MerchIntegrations/services/foundation/merchhier/subclass/{subclassId}

New

REST Service

  

This service will be used by External applications to retreive a specific subclass information.

MerchIntegrations/services/foundation/orghier/{param1}/{param2}

New

REST Service

  

This service will be used by External applications to retreive the organization hierarchy details by organization level and Hierarchy Id.

MerchIntegrations/services/foundation/diffgroup/{diffGroupId}

New

REST Service

  

This service will be used by External applications to retreive a specific differentiator group information.

MerchIntegrations/services/foundation/diffid

New

SOAP Service

  

This service will be used by External applications to retreive all the differentiator details.

MerchIntegrations/services/foundation/difftype

New

REST Service

  

This service will be used by External applications to retreive all the differentiator type details.

MerchIntegrations/services/foundation/item/vat

New

REST Service

  

This service will be used by External applications to retreive all the item vat information.

MerchIntegrations/services/foundation/supplier/{supplierId}

New

REST Service

  

This service will be used by External applications to retreive a specific supplier site.

MerchIntegrations/services/foundation/partner/{partnerId}

New

REST Service

  

This service will be used by External applications to retreive information of a specific partner.

MerchIntegrations/services/procurement/order/{orderId}

New

REST Service

  

This service will be used by External applications to retreive a specific order information.

MerchIntegrations/services/inventory/allocation

New

REST Service

  

This service will be used by External applications to retrieve all approved and closed allocation information.

MerchIntegrations/services/inventory/rtv

New

REST Service

  

This service will be used by External applications to retreive all the approved and shipped RTV details.

MerchIntegrations/services/inventory/rtv/{rtvOrderNo}

New

REST Service

  

This service will be used by External applications to retreive a specific RTV Order information.

MerchIntegrations/services/inventory/woout

New

REST Service

  

This service will be used by External applications to retreive all work order details associated with transfers.

MerchIntegrations/services/inventory/transfer

New

REST Service

  

This service will be used by External applications to retreive all the tansfer details.

MerchIntegrations/services/inventory/transfer/{tsfNo}

New

REST Service

  

This service will be used by External applications to retreive a specific transfer information.

MerchIntegrations/services/foundation/merchhier/division

New

REST Service

  

This service will be used by External applications to retreive all the division information.

MerchIntegrations/services/foundation/merchhier/groups/{groupId}

New

REST Service

  

This service will be used by External applications to retreive a specific group information.

MerchIntegrations/services/foundation/merchhier/class/{classId}

New

REST Service

  

This service will be used by External applications to retreive a specific class information.

MerchIntegrations/services/foundation/merchhier/subclass

New

REST Service

  

This service will be used by External applications to retreive all the subclass information.

MerchIntegrations/services/foundation/orghier

New

REST Service

  

This service will be used by External applications to retreive all the organization hierarchy information.

MerchIntegrations/services/foundation/orghier/{orgLevel}

New

REST Service

  

This service will be used by External applications to retreive the organization hierarchy details by organization level.

MerchIntegrations/services/inventory/receiverunitadj

New

REST Service

  

This ReST service will be used by External applications to retreive receiver unit adjustment information.

MerchIntegrations/services/foundation/diffgroup

New

REST Service

  

This service will be used by External applications to retreive all the differentiator group details.

MerchIntegrations/services/foundation/diffid/{diffId}

New

REST Service

  

This service will be used by External applications to retreive a specific differentiator information.

MerchIntegrations/services/foundation/difftype/{diffType}

New

REST Service

  

This service will be used by External applications to retreive a specific differentiator type information.

MerchIntegrations/services/foundation/store

New

REST Service

  

This service will be used by External applications to retreive all the store details.

MerchIntegrations/services/foundation/store/{storeId}

New

REST Service

  

This service will be used by External applications to retreive a specific store information.

MerchIntegrations/services/foundation/warehouse

New

REST Service

  

This service will be used by External applications to retreive all the warehouses.

MerchIntegrations/services/foundation/warehouse/{whId}

New

REST Service

  

This service will be used by External applications to retreive a specific warehouse information.

MerchIntegrations/services/foundation/item

New

REST Service

  

This service will be used by External applications to retreive all the items.

MerchIntegrations/services/foundation/item/{itemId}

New

REST Service

  

This service will be used by External applications to retreive a specific item information.

MerchIntegrations/services/foundation/item/vat/{item}

New

REST Service

  

This service will be used by External applications to retreive vat information for a specific item.

MerchIntegrations/services/foundation/uda

New

REST Service

  

This service will be used by External applications to retreive all the user defined attributes and values.

MerchIntegrations/services/foundation/uda/{udaId}

New

REST Service

  

This service will be used by External applications to retreive information for a specific user defined attribute.

Enabled Custom Flex Attributes (CFAS) for Promotion Offers

Custom Flexible Attributes (CFAS) can now be added to promotion offers in Pricing.  The extension attributes exist for capturing additional attributes for promotional offers for purposes of reporting and/or interfacing to an external/3rd party POS and OMS systems. These attributes can be entered and updated via attributes screens accessed from the Actions menu on the Offers table in the Promotion screen as well as via spreadsheet download/upload and via the promotion’s web service.

Promotion offers will be seeded as one of the entities supporting CFAS. You can add CFAS hierarchy (Group Sets and Groups) for promotion offers in Merchandising using the existing spreadsheet upload functionality. Attributes can then be configured for CFAS groups in the Merchandising screen titled Custom Flex Attributes.  Once the flex attributes are activated users can begin entering values for the attributes by accessing the attribute screens from the Promotion screen via the Actions menu on the Offers table.

Configured flex attributes will be included in the outbound ReST service integration. The CFAS data is sent as name value pairs, including the attribute name and value. Systems receiving promotion data from Pricing will have the option of using this data or ignoring it.

Promotion offer CFAS are also included in the the integration with planning and analytics, by including the extension table in the Goldengate replication script.

Note:

The Oracle Retail Order Management System (OROMS) and Store do not utilize the Promotion Offer CFAS attributes.

Steps to Enable

You can add custom attributes and update any custom promotion induction spreadsheet templates for use with downloading and uploading promotions as desired.

  1. Create the new Custom Flex Attributes and activate them in Merchandising.

  2. Create a new custom template using Template Configuration screen in Merchandising.

  3. Add the custom attributes Group Set as a Worksheet to the newly created template.

  4. Download promotions using the newly created or updated custom template.

  5. Add custom attribute values to the spreadsheet.

  6. Upload the spreadsheet to Pricing.

Data Access Schema (DAS) Updates

Table Name View Name New/Updated? Change Notes

RPM_PROMO_OFFER_CFA_EXT

DAS_WV_RPM_PROMO_OFFER_CFA_EXT

New

Include the new CFA Extension table for Offers in the DAS and RDS.

Integration Impacts

Name New/Updated Integration Type Field Name Change Notes

Create Promotions and Add Offers to Promotions (/services/private/promotion)

Update

REST Service

Name

Holds the attribute name.

Create Promotions and Add Offers to Promotions (/services/private/promotion)

Update

REST Service

Value

Holds the value of the attribute for number and character type attributes

Create Promotions and Add Offers to Promotions (/services/private/promotion)

Update

REST Service

Value Date

Holds the date for date type attributes.