Overflow in Tapout 3.11 Fields (Datavolumeincoming, Datavolumeoutcoming, Chargableunit and Chargedunit)

(Doc ID 1322926.1)

Last updated on AUGUST 04, 2014

Applies to:

Oracle Communications Billing and Revenue Management - Version to [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

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