Running the UBE R96987111st June 2017
Are you experiencing system performance issues, installing multiple ESUs, heavy development or getting ready for go-live after an upgrade? Do you want to be more proactive with knowing the health of your JDE tables? If you answered yes to any of those questions, the R9698711 UBE could be your best friend.
The R9698711 identifies all tables that have differences in columns and indexes between the physical database and the E1 specs. It gives a list of tables that would require generating an index for.
Let’s take a look at some scenarios where the R9698711 would be beneficial to run.
Scenario 1 – Your E1 system is experiencing performance issues and you have noticed entries in the logs for missing indexes for standard JDE tables. You would like a list of all the tables that are currently experiencing issues with missing indexes. Running UBE R9698711 and choosing the PD environment would give you a list of the tables currently not in sync.
Scenario 2 – Your E1 system has recently been upgraded from 9.0 to 9.2 and the go-live is upcoming in a few weeks. This is a great time to check tables for missing indexes and gives you time to resolve any discrepancies before the system is turned over to end users
Scenario 3 – You just installed multiple ESUs for fix current or for a project like the Affordable Care Act where there were multiple fixes coming out daily and you were trying to stay current as quick as possible to allow for testing and submission of IRS files. A good way to verify if any tables got new indexes during the installation, and if special instructions for generating indexes were missed, is to run the R9698711.
Scenario 4 – As the CNC in charge of your companies E1 system, you want to be proactive instead of reactive when it comes to maintenance and keeping the system functioning as efficient as possible. Periodically running the R9698711 gives a CNC the awareness of a potential problem of tables with missing indexes.
In all 4 of the scenarios, running the R9698711 UBE will give you access to the information you need in finding issues with current tables and mismatched indexes with E1 specs.
Running the UBE R9698711
- Login to the environment you want to examine for index issues on a fat client. In this example, DV910 is being used.
- Fastpath to BV (Batch Versions).
- Enter R9698711 into the Batch Application window and click find.
The XJDE0001 version can be used and processing options changed during the submission or you can copy and create your own for future use to save specific processing options. In this example, we will use the XJDE0001 version.
- Highlight the XJDE0001 version and hit select.
- Select Data Selection.
- Click on ADVANCED in the form exit.
- Choose Override Location and click OK.
- Click Submit.
- Choose LOCAL and click on SELECT.
- Click okay on the Data Selection pop-up.
- Choose your processing options and click OK.
If you logged into the environment you are running the UBE for, the first option will default to that environment. It can be changed if you want to run for a different environment. In the Summary/Detail option, 1 is the default and is the optimal choice.
- Click OK.
- The UBE will run for several minutes to an hour and a .pdf report will be returned.
- Here is an example of what the report will show.
The report shows the F15153 has index issues and the indexes that should be re-generated. Since there is only 1 table with index issues, this can be accomplished thru OMW and the design tools. If there were multiple tables with index discrepancies, E1 has a UBE, R9698713, that can be run to re-index all tables or the select few that need it by changing the data selection on the version. The report also shows there are several tables with missing columns. This can be addressed through OMW and the design tools as well for each individual table.