CDRs Going to Suspense With "Customer In Transaction" Error
(Doc ID 3038412.1)
Last updated on AUGUST 08, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Goal
While testing, Call Details Records(CDRs) are going into suspense with a "Customer in Transaction" error. Initially, these CDRs went to suspense with a "Product not found" error. Upon reprocessing the same CDRs, they again go into suspense, but this time with a "Customer in Transaction" error.
What could be reason for the "java.lang.NullPointerException" and "Customer in Transaction" errors?
Solution
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
Goal |
Solution |
References |