Field Is Dropped While Executing PCM_OP_CUST_COMMIT_CUSTOMER
(Doc ID 1996372.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Customer Registration
There is a custom field (PIN_FLD_<CUSTOM_NAME>) in the input flist of PCM_OP_CUST_COMMIT_CUSTOMER which is present in the PIN_FLD_NAMEINFO array. But during the execution of the opcode, the custom field (PIN_FLD_<CUSTOM_NAME>) is missing in the upgraded env. This is happening after upgrading BRM from 7.4 to 7.5 PS10.
1. The field is getting dropped from the flist after calling to few of the policy opcodes.
2. Custom logic requires this field PIN_FLD_<CUSTOM_NAME> to be present in the input flist of the policy opcode fm_cust_pol_post_commit.c, but PIN_FLD_<CUSTOM_COUNTRY_NAME> is coming.
It is expected to keep the existing functionality unchanged in the upgraded 7.5 env.
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