OCECE-DC Type DETAIL:ASS_SUSPENSE_EXT:ERROR_CODE in BADRECNAR Record
(Doc ID 2171212.1)
Last updated on OCTOBER 06, 2023
Applies to:
Oracle Communications Offline Mediation Controller Cartridges - Version 6.0.0.3.0 to 6.0.0.3.0 [Release 6.0]Information in this document applies to any platform.
Goal
On : 6.0.0.3.0 version, Cartridge Pack
One user has suspense records when Elastic Charging Engine (ECE) responses contain an error. Users read BADRECNAR output files and process them to Suspense Distribution Cartridge (DC), and use Suspense DC for error detected during Oracle Communications Offline Mediation Controller (OCOMC) processing.
In one case, the user uses suspense handler (oracle.communications.brm.nm.nplhook.SuspenseMethodHandlerImpl) to append suspense fields to a NiFi Archive (NAR). Unfortunately there is a difference between datatype of the filed DETAIL:ASS_SUSPENSE_EXT:ERROR_CODE.
In BADRECNAR file, its ID is of type String, e.g. 60018; whereas the field generated by the suspense handler is of type Long, e.g. 400267.
Question:
May the user ask for changing datatype of the filed DETAIL:ASS_SUSPENSE_EXT:ERROR_CODE to Long in OCECE DC?
It will allow user to have common suspend records handling in Suspense DC.
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 |