The Opcode PCM_OP_CUST_UPDATE_CUSTOMER Doesnot Sincronyze AAC_ACCESS Data in ECE
(Doc ID 2522339.1)
Last updated on AUGUST 23, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.6.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.5.0.19.0 version, Customer Registration
ACTUAL BEHAVIOR
--------------------------
When executing the opcode PCM_OP_CUST_UPDATE_CUSTOMER, the data AAC_ACCESS from /account object did not synchronized to ECE, only in BRM.
EXPECTED BEHAVIOR
--------------------------
It should be synchronized to ECE.
STEPS
--------------------------
1) Created an account which has the AAC_ACCESS=<CUSTOM_NAME> into the /account object
2) Verified that the ECE cache contains the same field and the same value AAC_ACCESS=<CUSTOM_NAME>
3) Executed the opcode PCM_OP_CUST_UPDATE_CUSTOMER in order to modify the value of AAC_ACCESS field.
Call the opcode PCM_OP_CUST_UPDATE_CUSTOMER with FList:
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 414450167
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 414450167
0 PIN_FLD_PROGRAM_NAME STR [0] "IEL"
0 PIN_FLD_ACCTINFO ARRAY [0] allocated 20, used 1
1 PIN_FLD_POID POID [0] 0.0.0.1 /account 414450167
1 PIN_FLD_AAC_ACCESS STR [0] "CUSTOM_VALUE"
4) Verified that the AAC_ACCESS has been modified in BRM AAC_ACCESS=<CUSTOM_VALUE>.
But the modification never arrived to ECE which is still having the same previous value for the field, i.e. AAC_ACCESS=<CUSTOM_NAME>.
It is not showing in the ECE logs.
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 |