Invoicing is Failing but Committed Transaction is not Rolling Back in Multi Schema
(Doc ID 2654551.1)
Last updated on APRIL 02, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
- In the invoice policy fm_inv_pol_prep_invoice.c, one has done some customization to create a custom object using PCM_OP_CREATE_OBJ, for example, /my_custom_object.
- During invoicing, due to some issue there is an error and invoicing failed.
- This error is apparently because it is a multi schema setup and the account is in schema 1 while the invoice object is being stored in schema 2.
- But it is seen that the custom object /my_custom_object gets created and is not rolled back, so there is still an entry getting created in the associated table, which should not be the case.
How to overcome this situation, that is, how to be able to rollback the database updates done in the policy file fm_inv_pol_prep_invoice.c via PCM_OP_CREATE_OBJ?
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