Encapsulated Pcm_op_subscription_set_discount_status Sets Wrong Status Value
(Doc ID 1233606.1)
Last updated on MAY 06, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS opcode is encapsulated into a custom opcode. When the custom opcode is called, PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS is called to change the status from 1 to 2. After the call, check the results using a READ_OBJ and the status is still 1.
Steps to reproduce:
You can see that before the commit, the NON_CACHEABLE_WRITE is correct (it's gone direct to the database). When the transaction is committed, the cached version is flushed and it ends up with incorrect data.
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