pin_cycle_ fees -cycle Picks Up 10x More Records Than In 7.2
(Doc ID 1634511.1)
Last updated on MARCH 25, 2019
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
On BRM 7.5 PS6, the command pin_cycle_ fees -cycle is picking up 10x times more records to process than in 7.2
This seems to be related to the flags set to 1 vs 3 under 7.2:
In 7.2, a purchased product that charges immediately is always set to 3 (and thus not subject to be picked up by pin_cycle_fees).
In 7.5, any product purchased with an end date (activation fees, promotions, linked services hard-end-dated to align with a promotion) getting this FLAGS set to 1, not 3.
In 7.5, any product purchased with an end date (activation fees, promotions, linked services hard-end-dated to align with a promotion) getting this FLAGS set to 1, not 3.
This is causing the entry to get picked up in the next day’s pin_cycle_fees run, at which time its FLAGS value gets flipped from 1 to 3.
This is causing the job to run between 30 - 60 minutes in production vs a few minutes in 7.2.
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 |