BRM Pipeline: TAP Testing CDs Increments TAPS CDs Sequences
(Doc ID 1480527.1)
Last updated on SEPTEMBER 30, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.4.0]
Information in this document applies to any platform.
There are 278 network operators configured to generate TAPs to send to the DCH (like CDXXXXXXXXXX00225). If sending an EDR with events for 1 operator the pipeline creates 278 CDs (TAPs), 1 for that operator with the events and 277 CDs without events (notification files).
Question #1: Is it correct behavior for the outcollect pipeline?
Question #2: Can the pipeline generate only one CD for the specific operator when the EDR was sent, and at the end of the day if the input file of the outcollect rating pipeline doesn't contain any roaming EDRs for the other 277 network operators, the pipeline generates 277 notification files without the events, and plus the one with events (like a summary of the day)? How to achieve this?
Question #3: There is not much information about TAP testing in the online documentation. Do you have some documentation on it?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document