Setting The Impact Type For The Event (Doc ID 1962605.1)

Last updated on MAY 27, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Oracle Communications BRM - Elastic Charging Engine - Version 11.2.0.4.0 to 11.2.0.4.0 [Release 11.2.0]
Information in this document applies to any platform.

Symptoms

On :  BRM 7.5.0.10.0 and 11.2.0.4.0 version ECE  

ACTUAL BEHAVIOR  
------------------------
It's observed that IMPACT_TYPE is same in case of charge and discount for ECE rated event.

ex:
0 PIN_FLD_INVOICE_DATA    STR [0]
"INTEGRATE#639791500179#6392197600012#SMS#1.0#NORM##287034107502504270 0#608#1.0##0.89#16384|1 /item/sms 287034107502504270
0#1200010#1.000000000000000##1.00#16384|1 /item/sms 287034107502504270
0#608#1.000000000000000##-0.89#16384|>"

All the impact types are 16384 and is not distinguished for rating, discounting , rerating etc.
1     PIN_FLD_IMPACT_TYPE    ENUM [0] 16384

EXPECTED BEHAVIOR
-----------------------
This IMPACT_TYPE is required to distinguish charge and discount from INVOICE_DATA.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms