Trouble Call Entry Process
This section describes data mapping for the following:
Trouble Call Entry Process - Mapping Details
The schema details Trouble Call Entry are as shown in the table below
Oracle Utilities Network Management System field
Oracle Utilities Customer to Meter Message Element
Notes
 
call_source_ID
 
Integration will get the default value from the configuration properties file and map it to the NMS Call Source ID.
 
Trouble calls can be created from different external systems like C2M, IVR or web call entry. Each external system sending trouble calls to NMS will have a unique call_source_ID. This determines where the trouble call originated and makes sure the external ID passed to NMS is unique. NMS prefixes this value to the external ID to make it unique.
service_point_ID
spId
 
external_ID
outageCallId
C2M passes the Outage Call ID
account_number
accounted
Customer's account ID
trouble_code
outageCodes
Trouble code mapping setup between C2M and NMS must be the same.
 
In NMS, the total length of the string is the total number of distinct groups in the SRS_TROUBLE_CODES table.
 
In C2M, it is the Number of Outage Code Characteristic.
call_time
callDateTime
 
callback_flag
callbackRequested
In NMS, the possible values include:
'0' - callback not requested
'1' - callback requested
Defaults to '1' if no value is provided.
If Y or N are passed to NMS:
'Y' is translated to '1'.
'N' is translated to '0'
Use DVM OUC2M_OUNMS_CallBackIndicator to translate C2M value to NMS value.
callback_before_time
callbackDateTime
 
alt_phone
callbackNumber
When the integration populates this field, it should strip off all delimiters and only pass the numeric values.
phone
contactNumber
If trouble call is related to an SP, C2M pass customer phone.
If fuzzy call, C2M pass the caller's phone.
When the integration populates this field, it should strip off all delimiters and only pass the numeric values.
first_name
contactName
If trouble call is related to an SP, the integration maps it to the main person on the account. If fuzzy call, the integration maps it to the caller's name.
addr_street
address1 or location1
If trouble call is related to an SP, the integration maps it to the customer's premise address1.
If fuzzy call, the integration maps it to location1 (It must contain a street name or free format location description).
addr_cross_street
location2
If fuzzy call, check locationType value.
If Street Intersection, populate with location2 (It must contain a cross street).
addr_building
blockNumber
If fuzzy call, check locationType value.
If Street Segment, populate with blockNumber (it must contain a number).
addr_city_state
city state or locationCity locationState
If trouble call is related to an SP, C2M pass the premise city and state. Concatenation of City, State.
If fuzzy call, C2M pass the location city and location state. Concatenation of Location City, Location State.
The delimiter provided by the integration is always comma (,). If city or state is blank, no delimiter (,) is needed.
call_ID
callIdentifier
This is the call identifier's external reference ID (i.e. 911 Reference Number).
call_taker
userFirstName userLastName
The name of the user who created the outage call also known as trouble call. Integration will concatenate First name <space> Last Name.
call_comment
Comments
 
meet_type
meetType
In NMS, 1 if new appointment is set and '0' - default value for all other type jobs.
Valid Values:
0 - for non-meet calls
1 - create new meet
2 - reschedule existing meet
3- cancel existing meet
C2M gets the value from FA Char.
Use DVM OUC2M_OUNMS_MeetType to translate C2M value to NMS value.
meet_time
meetDateTime
C2M will populate meetDateTime only if meet type = 1.
cancel_flag
Y or null (base on Status)
If Status is Canceled, the integration populate this field with Y, otherwise it is null.
Use DVM OUC2M_OUNMS_CallCancelIndicator to translate C2M value to NMS value. outageCallAction
The possible values in NMS are:
0 - insert new call
1 - update existing call
update_flag
outageCallAction
Use DVM OUCC_OUNMS_NewCallIndicator to translate C2M value to NMS value.
device_ID
transformerId
May be null if trouble call is not related to a specific SP.
In C2M from SP Geo Code for Device.
Note: For fuzzy calls, if Location is a street intersection, the mapping of the location from C2M to NMS will be p_customer_address = location1 (street name) and addr_cross_street (cross street). If Location is a street segment, the mapping of the location from C2M to NMS will be p_customer_address = location1 (street name) and addr_building (block number, this must only be a numeric value).

If Location is other (free format description), the mapping of the location from C2M to NMS will be customer address = location1 (location description). All DateTime coming from C2M will be converted to the ISO8601 format which is YYYY-MM-DDHH:MM:SS.
Trouble Call Request Message Mapping
Mapping details for Trouble Call Request Message are shown in the table below:
Oracle Utilities Customer to Meter Trouble Call Request Message
Oracle Utilities Network Management System Trouble Call Stored Procedure Input
 
Element Name
Parent Element
Type
Element Name
DVM Name
Comments
requestMessage
 
OutermostTag
 
 
 
outageCallId
requestMessage
Field
external_ID
 
 
spId
requestMessage
Field
service_point_ID
 
 
premiseId
requestMessage
Field
 
 
 
accounted
requestMessage
Field
account_ID
 
 
contactName
requestMessage
Field
first _name
 
 
contactNumber
requestMessage
Field
Phone
 
 
callIdentifier
requestMessage
Field
call_ID
 
 
callDateTime
requestMessage
Field
call_time
 
 
OutageCallAction
requestMessage
Field
update_flag
OUCC_OUNMS_NewCallIndicator
 
Status
requestMessage
Field
cancel_flag
OUC2M_OUNMS_
CallCancelIndicator
 
faComments
requestMessage
Field
call_comment
 
 
userId
requestMessage
Field
 
 
 
userFirstName
requestMessage
Field
call_taker
 
 
userLastName
requestMessage
Field
call_taker
 
 
country
requestMessage
Field
 
 
 
addressLine1
requestMessage
Field
addr_street
 
 
addressLine2
requestMessage
Field
 
 
 
addressLine3
requestMessage
Field
 
 
 
addressLine4
requestMessage
Field
 
 
 
houseType
requestMessage
Field
 
 
 
number1
requestMessage
Field
 
 
 
number2
requestMessage
Field
 
 
 
inCityLimit
requestMessage
Field
 
 
 
city
requestMessage
Field
city_state
 
 
geographic
requestMessage
Field
 
 
 
county
requestMessage
Field
 
 
 
state
requestMessage
Field
city_state
 
 
postal
requestMessage
Field
 
 
 
locationType
requestMessage
Field
 
 
 
blockNumber
requestMessage
Field
addr_building
 
 
location1
requestMessage
Field
addr_street
 
 
location2
requestMessage
Field
addr_cross_street
 
 
locationCity
requestMessage
Field
addr_city_state
 
 
locationState
requestMessage
Field
addr_city_state
 
 
meetDateTime
requestMessage
Field
meet_time
 
 
meetType
requestMessage
Field
meet_type
OUC2M_OUNMS_MeetType
 
outageCodes
requestMessage
Field
trouble_code
 
 
transformerId
requestMessage
Field
device_ID
 
 
callbackRequested
requestMessage
Field
callback_flag
OUC2M_OUNMS_
CallBackIndicator
 
callbackDateTime
requestMessage
Field
callback_before_time
 
 
callbackNumber
requestMessage
Field
alt_phone
 
 
customElements
requestMessage