4 Configuring Reasons for Adjustments, Disputes, and Settlements
When your CSRs enter an adjustment, dispute, or settlement, they can provide a reason for the action such as "Net Speed Was Slow". In Oracle Communications Billing and Revenue Management (BRM), you define the reasons in reason codes.
Topics in this document:
Configuring Reason Codes for Adjustments, Disputes, and Settlements
Reason codes explain why an adjustment, dispute, or settlement is being granted. You typically select from a list of reasons appropriate to the action.
To implement reason codes, you create and load a reasons.locale file that lists each reason code and associates it with a reason code domain. The domain classifies the reason code according to the type of activity it applies to. You can also include information in the reasons.locale file that prevents inappropriate event adjustments based on the reason code and service type.
The reasons.locale file defines each reason code domain, the reason codes that belong to the domain, and the event G/L ID. The domain and reason code information is used to build the /strings object, and the event G/L ID is used to build the /config/map_glid object.
For event adjustments, you can also use the service block to define which services are valid for the reason code and specify the valid event types within those services. The service block is optional; it is used to define the reason code scope. If you do not include it, BRM adjusts all events in the batch regardless of whether the reason for the adjustment makes sense for the service and event.
The following example shows a single reasons.locale file segment defining a reason code domain.
DOMAIN = "Reason Codes - Event Adjustment Reasons"; STR ID = 3; VERSION = 22; STRING = "Net Speed Was Slow"; SERVICE TYPE = "/service/ip"; EVENT TYPE = "/event/session"; EVENT-END EVENT TYPE = "/event/session/call"; EVENT-END SERVICE-END SERVICE TYPE = "/service/telco/gsm/data"; EVENT TYPE = "/event/session/gsm/telco"; EVENT-END SERVICE-END EVENT-GLID "/event/billing/adjustment/event" 105; EVENT-GLID END END
For more information about the reasons.locale file, see "String Manipulation Functions" in BRM Developer's Reference.
To define reason codes for adjustments, disputes and settlements, you edit the reasons.en_US sample file in the BRM_home/sys/msgs/reasoncodes directory. You then use the load_localized_strings utility to load the contents of the file into the /strings, /config/map_glid, and /config/reason_code_scope objects. See "load_localized_strings" in BRM Developer's Guide for more information.
When you run the load_localized_strings utility, use this command:
load_localized_strings reasons.locale
Note:
-
If you are loading a localized version of this file, use the correct file extension for your locale.
-
If you add your own reason codes to the reasons.locale file, use IDs above 100,000.
Caution:
The load_localized_strings utility overwrites existing /config/map_glid and /config/reason_code_scope objects. If you are updating these objects, you cannot load new G/L ID maps and reason code only. You must load complete sets of data each time you run the load_localized_strings utility. This is also true when using the /strings object, but only if you specify the -f parameter. Otherwise, the load_localized_strings utility appends the new data to the object.