Oracle Retail Knowledge Base

6 Other Settings

6 min read

Mirror of Oracle documentation

Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.

++

= a

aie ‘7

2. Enable and Schedule Adhoc/Cyclic Jobs through POM to run any specific alert (depending on the business requirement) at a specific time of the day or multiple times a day at specific intervals. The typical usage pattern for these batch jobs is indicated below.

USAGE="

      USAGE: $script Name <connect string> <entity name>
     <connect string>    Username/password@db. Use "'$UP'" if using Oracle
Wallet.

     <Param Ind> (Optional) Indicator to identify the next parameter -
Valid values -I or –

<Param Value> (Optional) Intra Day Run identifier (Valid Values Y or N) or
Notification Type”

The relevant batch jobs for the alerts are listed in the table below.

SL POM JOB NAME & EXPLANATION USE CASE NO DESCRIPTION 1 BATCH_EMAIL_ALERT_AD Default parameter is Case1 – Run All Alerts HOC_JOB #SysOpt.dbwallet Parameters – This job sends automatic Users can modify the #SysOpt.dbwallet email alerts for business parameters to run specific Case2 – validations. It can be alerts by passing the mapped scheduled to run any Notification Type. Run a particular specific alert Refer Use case column for notification/alert which is not an Intraday alert examples. Parameters – #SysOpt.dbwallet -N <Notification_type_code> 2 BATCH_EMAIL_ALERT_CY Default parameter - Case 1 – Process only LCE_JOB #SysOpt.dbwallet -I Y intraday alerts This job sends automatic Users can pass additional Parameters – email alerts for business parameter to run specific #SysOpt.dbwallet -I validations. It can be intraday alert by passing the Case 2 – Process specific scheduled to run only mapped Notification Type intraday alert intraday alerts. -N Parameters – Note-It will only process Alerts whose alert timeline is #SysOpt.dbwallet -I -N set to A in <Notification_type_code> custom_alert_control. Refer V_ALERT_INFO to view details in APEX. User must schedule the time for the cycles they want to run (every 2 hrs., every 1 hr. etc.) in POM application. 3 BATCH_EMAIL_ALERT Parameters are fixed and _JOB cannot be modified. This job sends automatic email alerts for business validations. It will process all alerts that satisfy the alert criteria setup in custom_alert_period table. Refer V_ALERT_INFO view to know the setup in APEX.

#SysOpt.dbwallet -I -N <Notification_type_code>

Administration Guide G59101-01 Copyright© 2026, Oracle and/or its affiliates.

This feature works by creating a channel in Slack when you initiate a conversation for a particular item or PO. In this way, you can reply or monitor the details both through the Merchandising application, as well as in your Slack instance. The instructions for doing this are below.

Create a Slack App

First, create a Slack App that is integrated with Merchandising. These are the basic steps for creating an app in Slack calling out the specifics needed to integrate with Merchandising, but please consult the Slack documentation for specifics.

1. Log into the appropriate Slack Workspace and Select Create New App.

2. Provide a name for your app - this is displayed to the user when they authenticate in Merchandising.

3. You are brought to the Basic Information page. In the navigation bar, under Features, select the OAuth & Permissions link.

4. Add a Redirect URL. This should have a format that matches the hostname for your Merchandising environment and ends with oauth/_callback, something like https://xxx-yyymfcs-mas.oracleindustry.com/Rms/oauth/_callback.

5. Scroll down to the Scopes section on the OAuth & Permissions page. Select the Permission Scopes dropdown and select the following scopes then click Save Changes:

  • chat:write:user

  • groups:history

  • groups:read

  • groups:write

  • users:read

6. Install the Slack App in the Workspace by scrolling back to the top of the OAuth & Permissions link and clicking the Install App to Workspace button.

Configure Slack in App Server

Next, the details of what was configured above will need to be configured in the app server. This needs to be done by the Oracle Cloud Operations team, so will require an SR. In the SR, you will need to include some of the information you set up when you created the app in step 1, including:

  • Slack Workspace URL

  • Redirect URL

  • Client-id and Client-Secrets - these can be found in your new Slack App under the Basic Information link under Settings in the section titled App Credentials. Merchandising will use these to authenticate itself to Slack.

Configure Slack in an Application

Once that step is complete, you will need to configure the related application parameters, following these steps:

1. Select Settings > Applications Properties.

2. In the search criteria, enter RMS as the Deploy Name and type “Conversation” in the Key field. Then click Search.

Administration Guide G59101-01 Copyright© 2026, Oracle and/or its affiliates.

3. You should see several items listed in the results table. For each of the Key Names listed below, highlight the appropriate row and click on the Edit iconic button to make the updates noted:

  • a. Collaboration Conversations Enabled - set current value to true

  • b. Collaboration Conversation Login Scheme - set current value to oauth

  • c. Collaboration Conversation Provider - set current value to slack

  • d. Slack URL - set current value to https://slack.com.

  • e. Slack App Redirect URL - set the current value to that described above in the prerequisites.

  • f. Slack Workspace - set the current value to that described above in the pre-requisites.

These changes will take place immediately after all steps are completed.

Configuring External Services

For several Merchandising services, there is the ability to configure an external URL for the service to use. This is also done in the Application Properties workflow. The services that support this type of configuration are:

Service NameApplication Property Key
General Ledger Account Validation Serviceaccvalidation.service.url
Drill Back Forward Servicedrillforward.service.url
Customer Order Address Servicecustordaddress.service.url
Customer Address Servicecustaddress.service.url

1. To configure the URLs for these functions, log into Merchandising and follow these steps:

2. Select Settings > Application properties from the sidebar menu.

3. Search for the appropriate key, as shown above and click Search.

4. Click on the property and choose Edit.

5. Enter the external URL in the Current Value field.

6. Click on OK to save the updates.

Web Service Configuration

ReSTful web services provide the ability to query data from Merchandising solutions and the ability to create and update data within Merchandising solutions. The Web Service Configuration workflow allows you to enable or disable REST services which require data preprocessing in order to allow consuming systems to replicate the data at their end. If one of these services will not be used, disabling the service via this configuration screen will save system resources by turning off the data processing.

To access the Web Service Configuration page from the Tasks menu, select Application Administration > Web Service Configuration. The Web Service Configuration page appears.

Check or uncheck the Enabled checkbox, to indicate whether or not the service is enabled for integration with external applications. Click on Save or Save and Close to commit the changes.

Administration Guide G59101-01 Copyright© 2026, Oracle and/or its affiliates.

In this guide

Graph View

Backlinks