Overflow in Tapout 3.11 Fields (Datavolumeincoming, Datavolumeoutcoming, Chargableunit and Chargedunit)
Last updated on AUGUST 04, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.1 [Release 7.3.1]
Information in this document applies to any platform.
TAP3.11 format for fields (DataVolumeIncoming, DataVolumeOutcoming, ChargableUnit and ChargedUnit) should be 8 Bytes unsigned Integer.
However, in the solution part, all these field are using 4 Bytes signed Integer. It makes some of production GPRS calls (uplink or downlink over 2G) overflow in these fields and it showed zero in the TAP3.11 Output and settlement DB.
Also, records are rejected in production environment.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms