Tap File Regenrated From The Suspended And Recycled Server Rap Records Does Not Have Recentitycode P

(Doc ID 1275731.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: and later   [Release: 7.4.0 and later ]
Information in this document applies to any platform.


TAP file regenerated from suspended and recycled Server RAP records doesn't have RecEntityCode populated

Processed Severe RAPIN file and loaded the records through Suspended Event (SE) Loader. When we are recycling them to generate the new TAP file with new sequence number,regenerated TAP file is missing Manadatory field RecEntityCode.Reason is RecEntityCode is being populated based on DETAIL.ASS_GSMW_EXT.ORIGINATING_SWITCH_IDENTIFICATION, and this field is populated While processing Severe RAP from the field RecEntityId. Since RecEntityId is not present in the Severe RAP we are getting this issue.

To Reproduce:
Process Severe RAP in the RAPInProcessing Pipeline
Load the generated output through Suspended Event (SE) Loader
Recycle the suspended record
TAPoutCollect will regenerate the new TAP file

Expected result:
New TAp file should have RecEntityId and RecEntityCode populated with original values

Actual result:
New TAp file does not have RecEntityId and RecEntityCode populated with original values


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