Lookups and Configuration Properties
Configuring Lookups
This section describes the lookups and the configuration details in the integration:
- Lookups
- Editing Lookups
- Lookup Tables
- Configuration Properties
Lookups
The following table lists the lookups that are part of this integration:
Lookup Name | Integration Name | Purpose |
|---|---|---|
OUTL-BRT-CCS_OPWR_TechnicalConfigProps | OU OPOWER CCS Affordability File Transfer OU OPOWER CCS Sent Customer Communication Sync OU OPOWER CCS Push Customer Communication Sync OU CCS OPOWER Account Communications Get OU CCS OPOWER Communication Content Get OU Common Notification Handler | The lookup contains the configurations that are setup by admin or devops team. It maps the PropertyName column to the respective Value Column. Do not change the values under PropertyName column. |
OUTL-BRT-CCS_OPWR_BusinessConfigProps | OU OPOWER CCS Sent Customer Communication Sync OU OPOWER CCS Push Customer Communication Sync OU CCS OPOWER Account Communications Get OU Common Notification Handler | This lookup is used to store parameters and default values used in the integrations. It maps the PropertyName column to the respective Value Column. Do not change the values under PropertyName column. |
OUTL-BRT-CCS_OPWR_CommunicationStatus | OU OPOWER CCS Sent Customer Communication Sync OU OPOWER CCS Push Customer Communication Sync OU CCS OPOWER Account Communications Get | Translates Oracle Opower Delivery Status or Event Type to Oracle Utilities CCS Communication Status. |
OUTL-BRT-CCS_OPWR_DeliveryChannel | OU CCS OPOWER Account Communications Get | Translates Oracle Opower Channel to Oracle Utilities CCS Delivery Channel. |
Editing Lookups
To edit a lookup:
- Login to Oracle Integration for Cloud.
- Navigate to Projects.
- Select the project and go to the Lookups section of the project.
- Click Save and Close.
Lookup Tables
This section lists the lookup tables in this integration.
Lookup: OUTL-BRT-CCS_OPWR_CommunicationStatus
The values released in the lookup are the defined values in the edge applications. No need to configure this lookup unless there are custom values. The following table maps Opower email and push delivery events to Customer Cloud Service communication status values:
CCS_CommunicationStatus | Opower_DeliveryStatus | Description |
|---|---|---|
C1ST | RELAYED | Email Communications Relayed Status means the email has been sent out to the customer. |
C1ST | SEND | Push Communication Send status means it has been sent out to the customer |
Lookup: OUTL-BRT-CCS_OPWR_DeliveryChannel
The values released in the lookup are the defined values in the edge applications. No need to configure this lookup unless there are custom values.
The following table maps Opower communication channels to the delivery channel codes used by Customer Cloud Service:
CCS_DeliveryChannel | Opower_Channel | Description |
|---|---|---|
EMAI | ||
MPSH | PUSH | Mobile App Push |
Configuration Properties
Lookup: OUTL-BRT-CCS_OPWR_TechnicalConfigProps
Use the following table to configure technical notification settings, the utility code, and affordability transfer locations and restart tracking:
Property Name | Sample Value | Description |
|---|---|---|
notif.email.technical.error.flag | true | Configures optional technical email notification. If the value is set to true, a technical email notification will be sent to the configured users. Default to true. Valid values: true/false. |
from.email | admin@myCompany.com | The email address is used to identify who is sending the notification. This value is the default email address for all outgoing emails for this project. |
technicalError.to.email | The email address(es) who should receive notification when a technical error is encountered in OIC. Multiple emails can be configured by putting comma to separate the email IDs. | |
opower.utilityCode | VMDL | Customer's utility code. This value is used as one of the parameters for the Oracle Utilities Opower outbound communication queries. |
opower.os.namespace | opowerNamespace | Oracle Utilities Opower object storage namespace serves as a container for all Opower related buckets and objects. |
opower.os.affordability.bucketname | opowerAffordabilityBucketname | Oracle Utilities Opower object storage bucket name where Affordability Indicator files reside. |
opower.affordability.filenamePrefix | /samplefolder/data/clients/affordability/vmdl | Opower LMI Insight filename prefix Object Storage buckets do not have actual subdirectories. To retrieve a file from a folder-like path, include that path in the object name as a prefix, using forward slashes (/) between levels. |
opower.affordability.startAfter | /samplefolder/data/clients/affordability/vmdl/test_2026-08-14T17-35-31.141000_relaxed-1.0.0_1.zip | If the value is specified, it returns object names that are lexicographically greater than the specified value. Leave it empty for the first run. The integration sets the value to the last filename transferred successfully after every run. On subsequent runs, the integration should pick up the file(s) after this value. |
ccs.file.target.transfer.pref | os | Determines the Customer Cloud Service file transfer destination. Valid values are 'os' or 'ftp', os for object storage and ftp for SFTP server.. |
ccs.ftp.affordability.directory | /scratch/AffordabilityDir | Customer Cloud Service FTP directory or folder where Affordability Indicator files reside. Required to be populated if ccs.file.target.transfer.pref is ftp. |
ccs.os.namespace | ccsNamespace | Customer Cloud Service object storage namespace serves as a container for all Customer Cloud Service related buckets and objects. Required to be populated if ccs.file.target.transfer.pref is os. |
ccs.os.affordability.bucketname | ccsAffordabilityBucketnameToCCS | Customer Cloud Service object storage bucket name where Affordability Indicator files reside. Required to be populated if ccs.file.target.transfer.pref is os. |
Lookup: OUTL-BRT-CCS_OPWR_BusinessConfigProps
Use the following table to configure business notifications, communication batch size, and the time intervals and cursors used by scheduled synchronization:
Property Name | Value | Description |
|---|---|---|
notification.channel | Currently only email notifications are supported by the integration. Default value: email | |
notif.email.techerror.info.flag | true | Configures optional technical information email notification. If the value is set to true, a technical information email notification will be sent to the configured users. Default to true. Valid values: true/false. |
notif.email.business.error.flag | true | Configures optional business email notification. If the value is set to true, a business error email notification will be sent to the configured users. Default to true. Valid values: true/false. |
businessError.to.email | The email address(es) who should receive notification when a business error is encountered in OIC. Multiple emails can be configured by putting comma to separate the email IDs. | |
ccs.maxAPICollCount | 500 | The maximum number of customer communications that can be sent to the Customer Cloud Service Customer Engagement API. Default to 500. |
opower.startDateTime.sentComm | 2026-05-26T00:00:00Z | This value is used as one of the parameters for the SENT customer outbound communication query to Opower. It will get all customer communications starting from this startDateTime. It should be in UTC format. This field must be populated during initial setup. After each successful run, the OIC flow updates it with the run’s end date and time. |
opower.endDateTime.sentComm | 2026-05-28T00:00:00Z | This value is used as one of the parameters for the SENT customer outbound communication query to Opower. It will get all customer communications by this endDateTime. If this is empty, the process will use the current datetime when the flow runs. It should be in UTC format. This is blank by default. |
opower.startCursor.sentComm | This is used as a parameter in the SENT customer outbound communication query to Opower. This value is populated only when an error occurs after some customer communications have been sent to Customer Cloud Service. The OIC process stores the end cursor of the last successfully Opower sent communications query result page so the next run can resume from that point without resending the previous page(s) that has been sent to Customer Cloud Service. This is blank by default. | |
opower.startDateTime.pushComm | 2026-05-28T00:00:00Z | This value is used as one of the parameters for the PUSH customer outbound communication query to Opower. It will get all customer communications starting from this startDateTime. It should be in UTC format. This field must be populated during initial setup. After each successful run, the OIC flow updates it with the run’s end date and time. |
opower.endDateTime.pushComm | 2026-05-30T00:00:00Z | This value is used as one of the parameters for the PUSH customer outbound communication query to Oracle Utilities Opower. It will get all customer communications by this endDateTime. If this is empty, the process will use the current datetime when the flow runs. It should be in UTC format. This is blank by default. |
opower.startCursor.pushComm | This is used as a parameter in the PUSH customer outbound communication query to Opower. This value is populated only when an error occurs after some customer communications have been sent to Customer Cloud Service. The OIC process stores the end cursor of the last successfully Opower push communications query result page so the next run can resume from that point without resending the previous page(s) that has been sent to Customer Cloud Service. This is blank by default. |