How to Handle Rejections in Pipeline with TAP3 Input Grammar
(Doc ID 763900.1)
Last updated on SEPTEMBER 20, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.1 to 18.104.22.168.0 [Release 6.5.0 to 7.2.1]
Information in this document applies to any platform.
Checked for relevance on 31-Oct-2011
Checked for relevance on 30-Oct-2013
How to setup an input grammar, in order to process files rejected from a pipeline with a standard TAP3 input grammar.
The TAP3 input grammar does not accept the format of rejected files, as is, because rejected files miss the header/trailer structure which is typical of a TAP3-standard file.
Say, for example, we have a formally correct TAP file, but some of its CDRs gets rejected by the processing pipeline for a duplication check failure (FCT_DuplicateCheck), What the FCT_Reject does is to output only rejected records ?
The resulting rejected file would only include a "copy" of the input records, but it would miss the specific TAP header and trailer sub-structures.
When recycling rejected files using the FCT_Recycle, this plugin will do nothing more than moving the rejected files back to the input directory (apart from setting internal status flags, for proper reprocessing - see documentation for more details).
By applying this procedure with TAP rejections, the TAP input grammar would fail, as the rejected file format is incomplete. A modified grammar would needed to recycle those files.
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