pin_rel Not Populating Event Start and End POID in BATCH_REL_T table
(Doc ID 2119112.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.15.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On Oracle Communications Billing and Revenue Management (BRM) version 7.5.0.13.0 when populating events with pin_rel, the START_POID_ID0, END_POID_ID0 and NUM_TOTAL_RECORDS are not populated in the BATCH_REL_T after the installation of IP2.
The installation of IP2 should not stop populating START_POID_ID0, END_POID_ID0 and NUM_TOTAL_RECORDS.
The issue can be reproduced at will with the following steps:
1. Create a Global System for Mobile communications (GSM) account and pass in usage via Oracle Communications Offline Mediation Controller (OCOMC).
2. Check the BATCH_REL_T table after loading Elastic Charging Engine (ECE) rated output file(s).
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 |