Rerating Is Failing Because of Core Dump in the Custom Code
(Doc ID 2873941.1)
Last updated on APRIL 05, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
In a customer scenario, rerating is failing because of core dump in the custom code and the custom code is failing because during re-rating, for adjustment event the SYS_DESCR field is not getting copied from the original event. In 7.5 version, SYS_DESCR is coming as expected.
Steps to reproduce:
- Run rerating on any account with some cycle fees
- Check cm.pinlog for fm_rerate_utils_fillin_adj_items input flist
- See that:
0 PIN_FLD_SYS_DESCR STR [0] "Cycle Forward Fees"
Expected is:
0 PIN_FLD_SYS_DESCR STR [0] "Cycle Forward Fees (srvc): Rerate Testing" - See the value of the field from the event table as follows to validate:
select sys_descr from event_t where poid_id0=337312575221507153;
Cycle Forward Fees (srvc):Rerate Testing
cm.pinlog snippet:
Cause
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
Symptoms |
Cause |
Solution |
References |