Scenario 1: CC&B + MWM + WAM v1.9.1.x
In this scenario, the integration product coordinates processing between three Oracle Utilities application products based on the configuration settings described. All three application products and the integration product must be configured to enable this business scenario. This section of the document describes the configuration required for one of the application products.
Configure the following in Oracle Utilities Work and Asset Management v1.9.1.x:
• Code Tables
• Batch Processes
• Sequence Numbers
• Employees
• Storeroom/Stock Code
• Business Rules
• Accounts
Batch Processes
Open the Job Manager module in the Administration subsystem to add the following batch jobs for processing records sent from the integration layer. Integration processes populate the tables that provide the input to these jobs.
In the Oracle Utilities Work and Asset Management v1.9.1.x application, navigate to App Map > Administration subsystem > Job Manager to access these batch processes.
For more information, see the Oracle Utilities Work and Asset Management v1.9.1.x Interfaces Guide.
Description for Common Keywords and Parameters
Job_in - The job number assigned by the Oracle Utilities Work and Asset Management v1.9.1.x application Job Manager.
Plant_in – Character string that identifies Oracle Utilities Work and Asset Management v1.9.1.x plant code.
Direction_in - Single character that identifies Inbound (I) or Outbound (O) processing.
Pre_in - Character string that identifies the custom stored procedure to call before the interface procedure begins.
Post_in - Character string that identifies the custom stored procedure to call after the interface procedure finishes.
Batch Processes Used for Data Synchronization
Configuration of these processes is required before data synchronization can be completed.
For more information on synchronizing these properties with Oracle Utilities Customer Care and Billing, see Synchronization Between CC&B and WAM v1.9.1.x in Chapter 16.
Procedure Name
Batch Process
Setting
Notes
Asset Standard Interface Procedure
WIFP_ASSET_INTERFACE( job_in, plant_in, direction_in, purge_in, option_in, pre_in, post_in);
Example of Job Manager Procedure set up:
WIFP_ASSET_INTERFACE(26, '01', 'I', 'Y', null, null, null);
This process is used for import of Asset data (Service Point and Premise) from CC&B to WAM. The process is run manually.
Customer Standard Interface Procedure
WIFP_CUSTOMER_INTERFACE(job_in, plant_in, direction_in, purge_in, option_in, pre_in, post_in);
Example of Job Manager Procedure set up:
WIFP_CUSTOMER_INTERFACE(43, '01', 'I', 'Y', null, null, null);
This process is used for import of Customer from CC&B to WAM. The process is run manually.
CCB Service Request Interface
sdbp_ccb_service_request.ccb_service_request_interface( job_in, plant_in, purge_in, pre_in, post_in);
Example of Job Manager Procedure set up:
WIFP_ASSET_INTERFACE(55, '01', 'Y', null, null, null);
This should be included in run_all_batch to run after customer and asset interfaces.
Batch Processes Called by Web Services
Procedure Name
Batch Process
Setting
Notes
Service Request Interface Procedure
The Standard Service Request interface is NOT used for this integration.
SDBP_CCB_SERVICE_REQ_INTERFACE ( job_in, plant_in, direction_in, purge_in, pre_in, post_in, addr_in, sr_no_in, message_id_in, dbms_activity, error_no, error_message);
Example of Job Manager Procedure set up:
declare
in_out1 varchar2(2000);
in_out2 number :=0;
in_out3 varchar2(2000);
begin
SDBP_CCB_SERVICE_REQ_INTERFACE('103','01','I','Y',NULL,NULL,'sdbp_CCB_parse_address',NULL,NULL,in_out1,in_out2,in_out3);
end;
This job is used to log error messages generated from inbound Service Requests sent from CC&B. If you want to see a log of errors, look for this batch job number in the Job Manager module.
Batch Processes Used to Post Costs
The following procedures are not called in any of the web service classes, but they are needed to post the costs of the respective expense they process (only posted costs can be sent as billable charges). It is likely that these processes are already configured for Oracle Utilities Work and Asset Management v1.9.1.x. The corresponding log messages can be viewed under the sdbp_run_all_batch.
Procedure
Name
Batch Process
Setting
Notes
Stock Cost
Interface
Procedure
sdbp_cost_stock.cost_stock( job_in, plant_in);
Enter Interval – sysdate + 999
Processes costs for stock transactions which have not yet been posted. Information is selected from the table SA_INVENTORY_LOG and posted throughout the system. Once a stock cost transaction is successfully processed, it is marked as posted.
Special Batch Process for Error Logging
In addition to logging of errors in tables and logs, there is pl/sql called from java web services code that logs errors. These pl/sql routines require a batch job to be created so that log messages can be generated to the job manager log message table.
Immediately suspend the created batch job after it is created creation so that it is never run. The easiest and safest way to create the batch job is to enter null; in the Procedure field.
Create a Batch Job For Error Logging
To complete this task, you must create three separate batch jobs.
1. Open the Job Manager module in the Oracle Utilities Work and Asset Management v1.9.1.x application.
2. Click New.
3. Select the Suspended or Broken check box.
4. Populate fields according to the following:
Procedure = null; /* SDBP_CCB_SERVICE_REQ_INTERFACE*/
Interval = sysdate+1 (the system defaults to this value)
 
5. Click Save.
6. Repeat from step 2 to create two more jobs where:
Procedure = null; /*SDBP_FIELD_WORK.FW_WEB_SERVICE_LOGGING*/

and

Procedure = null; /* SDBP_MWM_INTEGRATION.MWM_WEB_SERVICE_LOGGING */
Business Rules
Configure a Business Rule
1. In Oracle Utilities Work and Asset Management v1.9.1.x, navigate to Application Map > Administration subsystem > Business Rules module.
2. Search for and select the appropriate Rule indicated in the following sections.
3. Enter the relevant information indicated in the following sections.
4. Click Save.
Default Accts for Interfaces Rule
This rule is used while syncing Premise and Service Point information from Oracle Utilities Customer Care and Billing to Oracle Utilities Work and Asset Management v1.9.1.x. It establishes default account values that are used according to the zip code appearing on the Premise or Service Point which creates a new Asset record. Enter DEFAULT in the Zip Code column to establish default values that are used when no zip is present or there are no settings entered on the business rule for a particular zip code.
For example Department/Area/Account combinations could be entered to use zip codes 94596 and 97123 respectively. When a Service Point with any other zip code or no zip code is imported from Oracle Utilities Customer Care and Billing, the values next to DEFAULT is used.
Expense Codes Rule
When costs are sent to Oracle Utilities Customer Care and Billing, they are summarized by the Oracle Utilities Customer Care and Billing Expense code defined in this rule. These expense codes and categories are defined on Expense Codes Rule in Oracle Utilities Work and Asset Management v1.9.1.x. Values for the Oracle Utilities Customer Care and Billing Expense column do not need to be populated.
Note the DVM that must also be set up to create a cross-reference between the Oracle Utilities Work and Asset Management v1.9.1.x values you create for this rule, and the values used by the other applications.
Corresponding DVM - FS_Invoice_ChargeLineTypeCode
Interface Parameters Rule
Configure the Interface Parameters rule to set the parameters that drive business logic in the interface.
Asset Address Parser and Customer Address Parser
Oracle Utilities Work and Asset Management v1.9.1.x stores parts of an address (Street Number, Street Name, Street Suffix and Apartment Number) in individual fields. Oracle Utilities Customer Care and Billing does not store addresses in such detail, rather it stores entire lines of addresses in Address 1, Address 2, and so on.
The parameter entered for these rule keys controls how address parsing occurs when the system processes customers, premises & service points. You can replace the standard batch job procedure with a custom procedure that uses the same parameters. The provided parameter parses out street number and name.
Interface Rules
Configure the Interface business rules to designate which fields should be updated with information from the integration business processes when data is passed between the applications.
You must configure the interface rules for the following modules:
• Asset Interface Rule
• Customer Interface Rule
• Customer Address Interface Rule
• Customer SA Interface Rule
• Standard Service Req Interface Rule
If you set all of the values in the Update column to NO, the system does not update any fields when updated records are passed from the integration processes.
Set the Update column to YES for fields that must be updated when data is transferred from the integration processes.
For more information, see the Oracle Utilities Work and Asset Management v1.9.1.x Interfaces Guide.
Product Integration Rule
This rule defines the integration between Oracle Utilities Work and Asset Management v1.9.1.x and other Oracle Utility products.
• INTEGRATION TYPE – Enter FIELD WORK to set the type required for the three-way integration.
Product Integration MWM Rule
This rule is used to define default values used for fields integrated with Oracle Utilities Mobile Workforce Management.
• WORK ORDER ALERT USER - Enter the Oracle Utilities Work and Asset Management v1.9.1.x user who must be alerted about any errors or warnings that occur during the processing of work orders that are inbound to Oracle Utilities Work and Asset Management v1.9.1.x through the web service.
Product Integration Field Work Rule
This rule is used in place of Product Integration Oracle Utilities Customer Care and Billing and Product Integration Oracle Utilities Mobile Workforce Management rules that are used for point-to-point integrations.
• BILLABLE CHARGES – This includes the rule to determine whether to send billing information as billable charges to Oracle Utilities Customer Care and Billing.
• With this value set to ON, Oracle Utilities Mobile Workforce Management sends a completion to Oracle Utilities Work and Asset Management v1.9.1.x and Oracle Utilities Work and Asset Management v1.9.1.x passes the charges to Oracle Utilities Customer Care and Billing as billable charges.
• COUNTRY CODE – Enter the applicable country code. Values are validated by code table 15 which uses ISO codes for countries.
• PROCESS USER - Enter the Oracle Utilities Work and Asset Management v1.9.1.x user who must be alerted about any errors or warnings that occur during the completion of service requests that are inbound to Oracle Utilities Work and Asset Management v1.9.1.x through the web service.
• SERVICE REQUEST ALERT USER - Enter the Oracle Utilities Work and Asset Management v1.9.1.x user who must be alerted about any errors or warnings that occur during the completion of service requests that are inbound to Oracle Utilities Work and Asset Management v1.9.1.x through the web service.
• TIMEZONE – Enter the applicable time zone in a valid Java Time zone ID (for example America/Los_Angeles)
Web Services Gateway Rule
This rule is used to define the web services that the Oracle Utilities Work and Asset Management v1.9.1.x application must interface with.
Web Service Gateway Key (do not modify) - The values in this column reference the Requester ABCS that the Oracle Utilities Work and Asset Management v1.9.1.x application must interface with. This is for internal use by Oracle Utilities Work and Asset Management v1.9.1.x and must not be modified.
This table lists Web Service Gateway Keys that are used for this integration pack:
Web Service Gateway Key
Description
CCB CREATE CUST CONTACT
Used for sending a Customer Update outbound message from WAM.
CCB ORDER STATUS
Used for sending a Service Request Status Update outbound message from WAM. This controls the service request status. The service request status change request is invoked for all statuses except the COMPLETION (FINISHED/CLOSED) status change.
FW COMPLETE SERVICE ORDER
Used for sending a service request Completion outbound message from WAM.
FW CREATE SERVICE ORDER
Used for sending a service request Creation outbound message from WAM.
FW SEND BILLABLE CHARGE
Used for sending Billable Charges from WAM.
FW UPDATE SERVICE ORDER
Used for sending a service request Update outbound message from WAM. This controls service request details such as the description and other information.
Username & Password - The username and password needed to access the Requester ABCS on BPEL.
Dataset ID (do not modify) - These values indicate to Oracle Utilities Work and Asset Management v1.9.1.x which table to retrieve information from, and provide the keys to use from that table. This is for internal use by Oracle Utilities Work and Asset Management v1.9.1.x and must not be modified.
Consumer Class (do not modify) - The Java class name called by Oracle Utilities Work and Asset Management v1.9.1.x. This is for internal use by Oracle Utilities Work and Asset Management v1.9.1.x and must not be modified.
Service URL - The URL that the consumer class indicated in the previous column uses to call the Requester ABCS on BPEL. Set this to the endpoint URL of the corresponding Requester ABCS BPEL Process. This URL is typically in this format http://<SOA Server name>:<port>/soa-infra/default/<Requester ABCS Name>/<Requester ABCS Name>.
Gateway URL - The Gateway URL path to Oracle Utilities Work and Asset Management v1.9.1.x. The Consumer Class is physically stored on this server. Verify that you have the correct IP address and Port set for these.
Below is a sample table of details that go into the Business Rule – Web Services Gateway:
Web Service Gateway Key
Username
Password
Dataset
ID
Consumer
Class
Service URL
GateWay URL
Log Level
CCB CREATE CUST CONTACT
Weblogic username
Weblogic password
Do not modify
Do not modify
 
CCB ORDER STATUS
Weblogic username
Weblogic password
Do not modify
Do not modify
 
FW COMPLETE SERVICE ORDER
Weblogic username
Weblogic password
Do not modify
Do not modify
ALL
FW CREATE SERVICE ORDER
Weblogic username
Weblogic password
Do not modify
Do not modify
ALL
FW SEND BILLABLE CHARGE
Weblogic username
Weblogic password
Do not modify
Do not modify
ALL
FW UPDATE SERVICE ORDER
Weblogic username
Weblogic password
Do not modify
Do not modify
ALL
CCB METER
VALIDATION
Weblogic username
Weblogic password
Do not modify
Do not modify
http://soaserver:port/soa-infra/services/default/ValidateInstalledProductOUWAM
UtilitiesReqABCSImpl/ValidateInstalledProductOUWAM
UtilitiesReqABCSImpl
 
CCB
TRANSACTION
ACK
Weblogic username
Weblogic password
Do not modify
Do not modify
http://soaserver:port/soa-infra/services/default/ProcessWorkOrderResponseOUWAMUtilitiesProv
ABCSImpl/ProcessWorkOrderResponseOUWAMUtilitiesProv
ABCSImpl
 
CCB
TRANSACTION
NACK
Weblogic username
Weblogic password
Do not modify
Do not modify
http://soaserver:port/soa-infra/services/default/ProcessWorkOrderResponseOUWAMUtilitiesProv
ABCSImpl/ProcessWorkOrderResponseOUWAMUtilitiesProv
ABCSImpl
 
Code Tables
Configure Code Tables
1. In Oracle Utilities Work and Asset Management v1.9.1.x, navigate to Application Map > Administration subsystem > Code Tables module.
2. Search for and select the appropriate Code Table as indicated in the following sections.
3. Enter the relevant information as indicated in the following sections.
4. Click Save.
5. Define values in the code tables described in this section.
If you have already defined codes you do not need to change them for integration as long as you populate them in the correct DVM so that they properly integrate with the codes used by other integrated application products. The DVM for each code table is indicated with the code table description.
Code Table
Description
Corresponding DVM
Code Table 19: Country Codes
Standard ISO codes already populated.
FS_Country_Code
Asset Type Codes Code Table
Define Asset Type codes to be used.
This code table must be set up before synchronizing Premise and Service point information from CC&B to WAM.
FS_Order_ServicePoint
TypeCode
Code Table 241: Service Request Problem Codes
Define problem codes to be used.
FS_Order_TypeCode.
Code Table 240: Service Request Type
Define SR Type codes to be used.
FS_Order_TypeCode
Code Table 246: Disconnect Location
Define codes for disconnect locations.
The code is used for the Disconnect Location field in the Service Request module Meter Information view.
FS_Order_Disconnect
LocationCode
Code Table 251: Personal ID (Account Segement 1)
Configure this code table based on the account that is configured for the integration.
n/a
For more information on configuring accounts, see the section on configuration for Department, Area and Account.
Department, Area and Account
In Oracle Utilities Work and Asset Management v1.9.1.x, the combination of Department, Area, and Account constitutes an Account. Account configuration is required for any usage of the Oracle Utilities Work and Asset Management v1.9.1.x application, and is not specific to the integration. However, you may want to establish accounts that are specific to field work activities.
Navigation
Guideline
Corresponding DVM
App Map > Resource subsystem > Department
Populate Departments based on your business requirements.
FS_Order_OperationsArea
In addition to mapping codes, this DVM is used to specify a default WAM account code to be used on the service request.
App Map > Resource subsystem > Area module
Populate Areas linked to the created departments based on your business requirements.
App Map > Resource subsystem > Account module
Populate Accounts linked to the created departments and areas based on your business requirements.
Employee for Checkout Transactions
A default Oracle Utilities Work and Asset Management v1.9.1.x employee is referenced on all checkout transactions received from Oracle Utilities Mobile Workforce Management with service request completions. This employee must be set up or identified in Oracle Utilities Work and Asset Management v1.9.1.x and then referenced in the AIA configuration file. Use the following steps if you decide to create a new employee for this purpose.
Note that the values used here are just samples. You can choose appropriate values for your installation.
1. In the Oracle Utilities Work and Asset Management v1.9.1.x application, navigate to App Map > Resource subsystem > Employee module.
2. Click New.
Enter Employee No – FWI001
Enter Last Name – FWI
Enter First Name – 001
Crew – FWI01
Craft – FMIINV
3. Click Save.
Responsibility Configuration for Control of Fields (Optional)
It is recommended that you restrict the user’s ability to update the schedule date and problem description on the service request once the SR has been activated. In three-way integration, fields being updated in Oracle Utilities Work and Asset Management v1.9.1.x do not update the other two applications. For orders integrated two-way these updates however are carried to the other application containing the order.
Configure the Application for Control of the Schedule Date and Problem Code Fields
1. In Oracle Utilities Work and Asset Management v1.9.1.x, navigate to App Map > Administration subsystem > Responsibility.
2. Open the appropriate Responsibility record.
3. Select Service Request as the module in the Modules list.
4. Click Fields.
5. Select the SCHEDULE_DATE field from the list of values.
6. Select the boxes to set the level of ability for the first selected block and/or field.
7. Click Save.
8. Repeat for the PROBLEM_CODE field.
For more information about restricting fields, refer to the Oracle Utilities Work and Asset Management v1.9.1.x User Guide, under “Responsibility.”
Sequence Numbers
1. In the Oracle Utilities Work and Asset Management v1.9.1.x application navigate to App Map > Administration subsystem > Sequence Numbers module.
Search for and select the table name – SA_SERVICE_REQUEST.
2. Enter the following values:
Sequence No – leave as is, do not change
Prefix – You can choose to use a prefix if required by your organization. Or you may leave it blank.
Length – 7 (do not change)
System – True (this setting is required for system generated service request numbers in Oracle Utilities Work and Asset Management v1.9.1.x).
3. Click Save.
Standard Notes
Users have the option to enter remarks when completing work. Remarks are displayed on the Service Request module Closeout view and must be defined in the Standard Notes module with a note type of CIS Remark.