My Oracle Support Banner

Opcode PCM_OP_BAL_CHANGE_VALIDITY is not Syncing Validity for Resources when Invoked Inside PCM_OP_GL_POL_PRE_UPDATE_JOURNAL (Doc ID 2401907.1)

Last updated on JUNE 11, 2018

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 : 11.3.0.1.0 version, Balance Management

Opcode PCM_OP_BAL_CHANGE_VALIDITY is not syncing validity for resources during pin_cycle_fees invoked inside PCM_OP_GL_POL_PRE_UPDATE_JOURNAL, but when the same input is executed from testnap, sync is successful.

Steps to reproduce:

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

 

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!


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