Unique Constraint Error On ITEM_NO When Doing Rerating
(Doc ID 1589308.1)
Last updated on MARCH 23, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
When doing rerating for an account with Cycle Arrear and Bill Time discount events (after billing), we are getting unique constraint error on ITEM_NO field, in some cases.
cm pinlog:
What we observed from logs is that after INC_FLDS for creating the adjustment item (in fm_utils_sequence_cache), the new Item_No which is coming is already used once before in same rerating flow for adjustment item of some other event.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |