Comparing Specs Using P98780H – Work with Repository History
Repository History is created when you apply an ESU, check an object in, promote an object in OMW, etc. You can access the Repository to get information about all historical actions that have been taken affecting object specifications. For this example, after application of an ESU, errors were being received that indicated there was a problem with the structure of one of the JDE tables. The ESU was reapplied using Force Merge for this object, but the error remained. In order to verify that specs were updated by application of the ESU, P98780H was used to export objects and compare them.
This functionality is available in TR 9.2.1 and higher
The errors received after application of ESU were in the package build logs:
b4800470.c(3188) : error C2039: 'nwnumb' : is not a member of 'KEY1_F15017'
The NER logs had messages such as:* CER ERROR #3008 : Invalid table or column */ Function Name: RetrieveLeaseDefaultCurrencyCode Function Description: Retrieve Lease Default Currency Code Event: 0 - Named Event Rule Seq #: 37 Line #: 28 Line Text: F15017.Fetch Single /* F15017:NUMB */
These errors indicate that there’s something wrong with the table structure for F15017
Fast Path to P8780H and input object F15017 for Path Code DV920 to see when/where this object has been updated: (may need to scroll over to see all fields)
This is a display of every time this object was modified in this environment, which includes:
- Original application of the ESU
- Force Merge of the object delivered in the ESU (this was done repeatedly)
- Checking object out (generating) and then checking back in
Highlight F15017 (most recent update of this object) + click Export:
This automatically creates a .par file which you can move to any directory.
Rename .par file to .zip (accept statement that file may become unusable)
Extract Zip file to view contents
Save the .c and .h files locally
To compare to another environment, you can export the same way, just change Path Code in Header, find and repeat.
For this example, we will compare the .c and .h files to what was being delivered with ESU JN15374 to make sure that the files were updated as expected when ESU was applied and/or Force Merge was run to reapply ESU. The .c and .h files are included in the include and source subdirectories extracted when the ESU is applied:
Search Include and Source Folders for F15017
You will need a comparison program. This example uses WinMerge, but other similar products can be used.
The first file was pulled using P98780H
The second file as pulled from the ESU
If the files are not the same, you will get a list of differences that are highlighted:
If the files are the same, you will see the message below.
Repeat for all .c or .h files as necessary for full comparison, and this will be a process you can use to see what differences there are between the two files.