My Oracle Support Banner

Is It OK To Stop Auditing Of /account Class ? (Doc ID 2121271.1)

Last updated on MARCH 20, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

On :  BRM 7.5.0.0.0 version,


Scenario:
Customer is looking into turning off auditing of the /account class and purge the au_account_t table.
Currently only these two fields PIN_FLD_BAL_GRP_OBJ and PIN_FLD_OBJECT_CACHE_TYPE are being audited as per default setting for Billing and Revenue Management (BRM) 7.5.

Customer is using only one one balance group per account.
We also see the au_account_t table being accessed by several jobs like pin_collect and pin_deposit using the following query:
select min( au_account_t.effective_t ) from au_account_t where au_account_t.au_parent_obj_ID0 = :1


Please confirm whether we need not audit these fields in the /account class and if not, can we purge records from the existing au_account_t table?
Are there any possible side effects?.
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.