E1: CFR11: Enhancement Request: When Auditing Is Enabled Using Tools 9.2, The Index Names Still Include "_ADT"

(Doc ID 2315732.1)

Last updated on OCTOBER 20, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.

Goal

Client states that the R9698711 is a key component of their refresh strategy. 

Every time the client copies the business data from PROD to lower environments, they use the UBE to tell us which tables have to be converted to match the potentially newer specs in the lower environments/pathcodes. 

They refresh each of their lower environments once per month. 

Similarly, the BSFN used by R9698711 is also used frequently. 

It is called EVERY TIME they deploy a table design.

It is used to automatically validate that the database structure matches the design following the deployment. 

When deploying event rule changes in a table that has auditing enabled, the BSFN incorrectly reports that the index structure is wrong. 

Given the frequency that the client uses them, and their dependence on these objects, it is not practical for them disable auditing every time we need to validate the structure of the database objects. 

Having these incorrect reports creates more work for the client.

The developer's have suggested that the client disable auditing in order to run the UBE , and for the client they state that this is unworkable. 

They cannot take the outages required to disable and enable auditing every time we need to validate the database structure. 

There is no value added by the process, and valuable time would be wasted.

Solution

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