Need To Have Separate ChangeSet Status To Track RRE, BRE And Pricing Updater Publish Status
(Doc ID 2947901.1)
Last updated on MAY 10, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Goal
The requirement is to have separate changeSet status to track RealTime Rating Engine (RRE), Batch Rating Engine (BRE) and Pricing Updater publish status while doing PDC-IE-PLUS Loading.
Presently they are not getting this status, so not able to confirm that whether the changeset is published successfully or not and it will result in delay for Pricing Design Center (PDC) file loading.
In the case where PDC Files loading was showing successful but the changeset was not getting published in database (DB) and showing in Pending state only. This also causes delay of PDC-IE-PLUS Files loading where Pricing files took 13+ hrs to complete.
Please find steps below to reproduce this issue:
1. Run ImportExportPricing Utility to load a pricing component (charge offer or discount offer).
2. ImportExportPricing utility returns success message.
3. Check the status of the change set in PDC DB.
4. PDC maintains a common "PENDING", "FAILED", "SUCCESS" statuses to track publish/sync progress for RRE, BRE and Pricing Updater transformation processes.
5. Customer Expectation is to provide a separate change set status to track the RRE, BRE and Pricing updater publish/sync progress.
6. With the above current design, it is not possible to track the status of a particular transformation process using the change set status. Only way is to achieve this is by reviewing the log files of all three transformation processes to understand the status.
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 |