Last updated on SEPTEMBER 15, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 15-Sep-2017.
In the customization for publishing event, PCM_OP_PUBLISH_GEN_PAYLOAD Opcode opened a transaction with new context and committed to the aq_sync (advanced queue) even when there was an error. This resulted in sending the notification to the end user (as per a business case) even though the actual transaction has failed and returned from the PUBLISH_GEN_PAYLOAD.
How to fix this problem?
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 hundreds of Community platforms