My Oracle Support Banner

Pipeline Generating Notification Events For A Rollback Transaction (BRM 7.4) (Doc ID 1467125.1)

Last updated on AUGUST 20, 2012

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Oracle Solaris on SPARC (64-bit)


Following lines were added in the FCT_ApplyBalance:

NumberOfNotificationLimit = 5
NotificationOutputDirectory = ${IFW_DATADIR_INPUT}/p3a/out/notifybalancebreach
NotificationOutputPrefix = balancebreach_P3A_

Replication Step:
1) Notification breach feature is added in the module FCT_ApplyBalance
2) Set the credit limit for NCR
3) Process the usage to breach 100% threshold.
4) Inorder to fail the processing of CDR, use the name of an already processed CDR. Even though the CDR did not get processed, the notification XML got generated.
5) The filename was corrected and the CDR was reprocessed successfully. This time the notification XML also got generated and the only difference with the XML from step 4 was the "when_t" was different.

CONCERN: When the CDR processing got failed the notification XML should NOT have been generated. This would result in the notification sent to customer even though the usage was not processed and when we reprocess customer will recevie dulpicate notification.


To view full details, 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 a vibrant support community of peers and Oracle experts.