My Oracle Support Banner

"PCM_OP_BAL_CHANGE_VALIDITY" Not Syncing Validity For Resources When Invoked During Accounting (Doc ID 2518407.1)

Last updated on SEPTEMBER 10, 2019

Applies to:

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

Symptoms

On Oracle Communications Elastic Charging Engine(ECE), 11.3.0.1.0 Version, it is observed that "PCM_OP_BAL_CHANGE_VALIDITY' Opcode is not Syncing Validity for Resources when it is invoked inside "PCM_OP_GL_POL_PRE_UPDATE_JOURNAL".

Steps to Reproduce this issue
-----------------------------------------
The issue can be reproduced at will with the following steps:

1) Create a customer with product having rollover configured.
2) Execute pin_bill_accts (PCM_OP_GL_POL_PRE_UPDATE_JOURNAL policy update to extend validity of rollover bucket to NO END (PIN_FLD_VALID_TO TSTAMP [0] (0) )).


Customer encountered the above issue even after applying the patch 11.3.0.8.1. 

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.