Invalid Notification File Generated For Roaming
Last updated on MAY 28, 2009
Applies to:Oracle Communications Billing and Revenue Management - Version: 126.96.36.199.0 to 188.8.131.52.1
Sun Solaris SPARC (32-bit)
-- Problem Statement:
For ROAMING cases, when there is no data for a roaming partner, special type of file called notification
file should be created. Out-Of-Box BRM grammar for generating TAPOUT file prepares this file when it
doesn't detect any CDR for a roaming partner.
Using the TAPOUT grammar "TAP3_v11_OutGrammar.dsc" when you generate a notification file and try to open in a professional TAP editor tool, it gives error.
For example :
'C:\CDFIN2GZMBCZ00017' is not a valid TAP file!
(Versions supported : 3.11,3.10,3.9,3.4,3.3,3.2,3.1)
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