Business Flows
The integration scope supports the following business processes:
Create Service Call (Oracle Utilities Customer Cloud Service Initiated)
This integration process receives service call create request from Oracle Utilities Customer Cloud Service. The information is sent synchronously from Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service processes the message and sends back response using the acknowledgment service in Oracle Utilities Customer Cloud Service.
The following diagram shows a graphical representation of the Service Call integration flow:
Business Processing
The integration process includes the following activities:
1. Oracle Utilities Customer Cloud Service sends the create service call request to the “Oracle Utilities CCS WACS Create Service Call” flow deployed on Oracle Integration Cloud.
2. The Oracle Utilities CCS WACS Create Service Call flow transforms the create request message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS Process Service Call flow for service call creation.
3. The Oracle Utilities CCS WACS Process Service Call flow transforms the create message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS for service call creation.
4. Oracle Utilities Work and Asset Cloud Service sends the success or failure response to the integration transformed and sent to Oracle Utilities Customer Cloud Service.
5. Any errors are reported back to Oracle Utilities Customer Cloud Service through the global fault handler.
6. An optional email notification with error details is sent to the users configured in the OUTL-BRT-CCS_WACS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities CCS WACS Create Service Call |
Integration Project Name | OU CCS WACS |
WACS API | W1-ServiceCall |
API Operation | createServiceCall |
CCS BO | C1-ServiceCallNewOutMsg |
Update/Cancel Service Call (Oracle Utilities Customer Cloud Service Initiated)
This integration process receives service call update/cancel request from Oracle Utilities Customer Cloud Service. The information is sent synchronously from Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service processes the message sends back as response using the acknowledgment service in Oracle Utilities Customer Cloud Service.
The following diagram shows a graphical representation of the Service Call update/cancel integration flow:
Business Processing
The integration process includes the following activities:
1. Oracle Utilities Customer Cloud Service sends the update/cancel service call request to the "Oracle Utilities CCSWACS UpdateOrCancel ServiceCal" flow deployed on Oracle Integration Cloud.
2. “Oracle Utilities CCSWACS UpdateOrCancel ServiceCal” flow transforms the update/cancel request message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS Process Service Call flow for service update/cancel.
3. “Oracle Utilities CCS WACS Process Service Call” flow transforms the update/cancel message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS for service call update/cancel.
4. Oracle Utilities Work and Asset Cloud Service sends the success or failure response to the integration transformed and sent to Oracle Utilities Customer Cloud Service.
5. Any errors are reported back to Oracle Utilities Customer Cloud Service through the global fault handler.
6. An optional email notification with error details is sent to the users configured in the OUTL-BRT-CCS_WACS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities CCSWACS UpdateOrCancel ServiceCal |
Integration Project Name | OU CCS WACS |
WACS API Operation | Update : createCommunication Cancel : cancelServiceCall |
WACS API | Update : W1-Communication Cancel : W1-ServiceCall |
CCS BO | C1-ServiceCallUpdOutMsg |
Query Service Call (Oracle Utilities Customer Cloud Service Initiated)
This integration process receives the Query Service Call request from Oracle Utilities Customer Cloud Service to query the service call from Oracle Utilities Work and Asset Cloud Service. The information is sent synchronously from Oracle Utilities Customer Cloud Service. Oracle Utilities Work and Asset Cloud Service processes the message and sends it back synchronously.
The following diagram shows a graphical representation of the Query Service Call integration flow:
Business Processing
The integration process includes the following activities:
1. Oracle Utilities Customer Cloud Service sends the query service call request to the “Oracle Utilities CCS WACS Query Service Call” flow deployed on Oracle Integration Cloud.
2. “Oracle Utilities CCS WACS Query Service Call” flow transforms the message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS for service call query.
3. Oracle Utilities Work and Asset Cloud Service sends the success or failure response to the integration transformed and sent to Oracle Utilities Customer Cloud Service.
4. Any errors are reported back to Oracle Utilities Customer Cloud Service through the global fault handler.
5. An optional email notification with error details is sent to the users configured in the OUTL-BRT-CCS_WACS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities CCS WACS Query Service Call |
Integration Project Name | OU CCS WACS |
WACS API Operation | searchServiceCall |
WACS API | W1-ServiceCall |
CCS BO | C1-ServiceCallSearchOutMsg |
Get Service Call Details (Oracle Utilities Customer Cloud Service Initiated)
This integration process is used to accept request from Oracle Utilities Customer Cloud Service to get the Service call details from Oracle Utilities Work and Asset Cloud Service. The information is sent synchronously from Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service processes the message sends back synchronously.
The following diagram shows a graphical representation of the Get Service Call details integration flow:
Business Processing
The integration process includes the following activities:
1. Oracle Utilities Customer Cloud Service sends the query service call request to the “Oracle Utilities CCS WACS Get Service Call Details” flow deployed on Oracle Integration Cloud.
2. The “Oracle Utilities CCS WACS Get Service Call Details” flow transforms the message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS for getting service call details.
3. Oracle Utilities Work and Asset Cloud Service sends the success or failure response to the integration, transforms and sends to Oracle Utilities Customer Cloud Service.
4. Any errors are reported back to Oracle Utilities Customer Cloud Service through the global fault handler.
5. An optional email notification with error details is sent to the users configured in the OUTL-BRT-CCS_WACS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities CCS WACS Get Service Call Details |
Integration Project Name | OU CCS WACS |
WACS API Operation | getServiceCall |
WACS API | W1-ServiceCall |
CCS BO | C1-ServiceCallDetailsOutMsg |
Get Related Documents (Oracle Utilities Customer Cloud Service Initiated)
This integration process is used to accept requests from Oracle Utilities Customer Cloud Service to get the related documents from Oracle Utilities Work and Asset Cloud Service. Information is sent synchronously from Oracle Utilities Customer Cloud Service, and Oracle Utilities Work and Asset Cloud Service processes the message and sends it back synchronously.
The following diagram shows a graphical representation of the Get Related Documents integration flow:
Business Processing
The integration process includes the following activities:
1. Oracle Utilities Customer Cloud Service sends the related documents fetch request to the “Oracle Utilities CCS WACS Get Related Documents” flow deployed on Oracle Integration Cloud.
2. The “Oracle Utilities CCS WACS Get Related Documents” flow transforms the message from Oracle Utilities Customer Cloud Service to the request message format in Oracle Utilities CCS WACS for getting the related documents available.
3. Oracle Utilities Work and Asset Cloud Service sends the success or failure response to the integration, transforms and sends to Oracle Utilities Customer Cloud Service.
4. Any errors are reported back to Oracle Utilities Customer Cloud Service through the global fault handler.
5. An optional email notification with error details is sent to the users configured in the OUTL-BRT-CCS_WACS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Customer Cloud Service and Oracle Utilities Work and Asset Cloud Service artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities CCS WACS Get Service Call Details |
Integration Project Name | OU CCS WACS |
WACS API Operation | getServiceCallEntities |
WACS API | W1-ServiceCall |
CCS BO | C1-RetrieveWorkDocumentsOutMsg |