Rerate Job Status not Getting Updated in BRM when Pin_rerate Failed in ECE

(Doc ID 2187195.1)

Last updated on JULY 27, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


On : version, Rerating/Rebilling

Rerate job status not getting updated in BRM when pin_rerate failed in ECE with error as below:

ERROR in CustomerUpdater log

The issue can be reproduced at will with the following steps:

1. Created a new account (/account 4298168859) with a MCF ChargeOffer purchased to a service under the account
2. Changed the price of the ChargeOffer by introducing a new Date Range in the ChargeOffer
    Submitted this change from PDC to BRM
3. Executed pin_rate_change in BRM
    /job/rerate and /job_batch/rerate objects are created for the account (i.e. the account which was created in Step 1)
4. Executed pin_rerate -process jobs and monitored the CM log and CustomerUpdater log.
    The PIN_FLD_STATUS in /job/rerate is changed to 2 (WAITING_ACCOUNT_LOCKED).




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms