Configuring Lookups
The following table lists the lookups and integration processes where these lookups are used.
Lookup Name
Integration Name
Purpose
OUTL-BRT-NOTIFHUB_
EmailSubject
Oracle Utilities Responsys CCB Cust Contact Create
Maps the template to the email subject
OUTL-BRT-NOTIFHUB_
DeliveryChannel
Oracle Utilities OCI Stream Responsys Notif Send
Maps CCB Delivery Type to the Integration-defined delivery type of “sms” or “email”.
OUTL- BRT-NOTIFHUB_
DeliveryInstance
Oracle Utilities OCI Stream Responsys Notif Send
Maps the Integration-defined Oracle Responsys delivery instance ID to the actual Oracle Responsys identifier. The ResponsysId can be anything that identifies a Oracle Responsys instance.
 
Example: Description, URL, Instance ID, etc.
 
This Responsys ID is used in the error email notifications sent to identify the Oracle Responsys instance where the invocation failed.
 
Note: The values in the Intg_DeliveryInstanceId should be RESP1,RESP2,RESP3.
OUTL-BRT-NOTIFHUB_
DeliveryRouting
• Oracle Utilities OCI Stream Notif linkChannel
• Oracle Utilities CCB OCI Stream Notif Upload
Maps CCB CIS Division to the Oracle Responsys delivery Instance to route the message. The Oracle Responsys instances provided out of the box are identified as RESP1 , RESP2 and RESP3 in the DeliveryInstance column.
 
Note: These values in the DeliveryInstance column should match Intg_DeliveryInstanceId of OUTL- BRT- NOTIFHUB_ DeliveryInstance.
OUTL-BRT-
NOTIFHUB_
ConfigProps
• Oracle Utilities OCI Stream Responsys Notif Send
• Oracle Utilities OCI Stream Notif linkChannel
• Oracle Utilities CCB OCI Stream Notif Upload
• Oracle Utilities NMS OCI Stream Notif Upload
Maps the PropertyName column to the respective Value column. Do not change the value in the PropertyName column.
OUTL-BRT-
NOTIFHUB_Email_ID
• Oracle Utilities OCI Stream Notif linkChannel
• Oracle Utilities CCB OCI Stream Notif Upload
• Oracle Utilities NMS OCI Stream Notif Upload
• Oracle Utilities OCI Stream Responsys Notif Send
Maps the “from” and “to” recipient values to the mentioned email IDs. Configure multiple emails using a comma to separate the email IDs.
OUTL-BRT-
NOTIFHUB_NMS_CCB_NotifTypes
 
Maps the CCB Notification Types to the NMS Trigger Code and Planned/Unplanned Flag values. The DVM column, TriggerCode_Planned is combination of two parts. The first part is a number which represents NMS trigger code and the second is the planned or unplanned flag Y or N. “N” means unplanned outage and “Y” mean Planned outages.
 
For example: “1N” means Unplanned outage started and “4N” means Unplanned outage cancelled. The flags are case sensitive and must be in uppercase.
 
The following are the NMS trigger codes and can be combined with Planned or Unplanned outages flags:
 
1 - Outage started
2 - Outage restored
3 - Outage scheduled
4 - Outage scheduled
5 - Outage updated ERT
 
Note: “Unplanned outage schedule (3N) is not supported”.
OUTL-BRT-NOTIFHUB-Priority
 
Maps the CCB Notification Types to a priority, 'H' is used for High Priority.
OUTL-BRT-NOTIFHUB_
CustContactStatus
Oracle Utilities Responsys CCB Cust Contact Create
Maps the customer contact status between Oracle Responsys status and CCB create customer contact status.
OUTL-BRT-NOTIFHUB_
OriginSystem
Oracle Utilities Responsys CCB Cust Contact Create
Originating system and its code details.
 
 
 
 
 
 
Editing Lookups
To edit a lookup to add or update any value in it:
1. Login to Oracle Integration for Cloud.
2. Navigate to Integrations > Designer > Lookups.
3. Click the look up to edit.
4. Make the necessary changes.
5. Click Save and Close.
Note: While editing a lookup, if the changes are not reflected during the runtime, make sure to deactivate and activate the integration that is using the edited DVM for the changes to reflect. Refer to the Activating Integration Flows section for more details.