document 626548
DESCRIPTION
Document 626548TRANSCRIPT
PowerView is Off Profile (0)Sanoj Help
In this Document
Purpose
Scope
Details
Overview
Launching ER Compare
How to Use Visual ER Compare
Display
Features
Changing Source File
Changing Target Event Rules
Using the AutoMerge Feature
Printing a Visual ER Compare Report
Using ER Compare after Upgrade
Location of Source Specifications : Central Objects Path Codes
Location of Source Specifications : Remote Specifications
Location of Source Specifications : Compressed object archive (only file with .par extension)
Reported Issues with ER Compare
ER Merge Completed but ER Compare Shows Variables are Different
Compare PAR with LOCAL Fails to Show Global Scope Variables
ER Compare Error Saving Specs "didn't find GBRLINK record"
References
APPLIES TO:
JD Edwards EnterpriseOne Tools - Version 8.93 and later
Information in this document applies to any platform.
PURPOSE
This document details how to use the Event Rule (ER) comparison tool, ER Compare, found within the design tools in Object Management Workbench (OMW).
This document is part of an Information Center. To see other documents related to Form Design Aid and Object Management Workbench, use the links provided
below:
E1: FDA: Form Design Aid Information Center > Compare Tools > Document 626548.1
Information Center: Using Object Management Workbench in the JD Edwards EnterpriseOne Tools and Technology Product > Miscellaneous
Tools > Document 626548.1
SCOPE
This document is intended for the EnterpriseOne developer who will be using the tool to compare Event Rules. Frequently the tool is useful to retrofit custom
modifications after an upgrade or after applying an ESU.
DETAILS
Overview
ER Compare is a utility that enables you to compare an application on the local workstation (target application) to the source application defined in:
Central Objects data source of any defined path code
Remote specifications
Compressed Object Archive.
ER Compare provides a detailed, on-screen comparison of event rules. You can change the target object (your local version) within the utility by moving lines
directly from the source. You can also remove or disable lines. In addition to providing an on-screen comparison, you can select to print a report detailing the
changes as well.
The attachment Visual ER Compare Overview is a 2.451 mb overview Power Point presentation on the Visual ER Compare tool. Although this presentation was
developed at the Xe release of the software, the information is still relevant for current releases of EnterpriseOne.
Launching ER Compare
E1: FDA: Using the ER Compare (Event Rule Compare) Tool (Doc ID 626548.1) To Bottom
Modified: 23-Dec-2013 Type: BULLETIN Status: PUBLISHED [ EXTERNAL ] (5)
Authoring RCA Customer Exceptions CMSKnowledge Search Knowledge Base Advanced
Document 626548.1 https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLo...
1 of 6 2/5/2014 9:27 PM
ER Compare can be started from within Form Design Aid (FDA), directly from Object Management Workbench (OMW) or by selecting the VSMerge.exe executable
from the \system\bin32 directory.
To start the ER Compare from OMW:
Launch Object Management Workbench (OMW in the FastPath)1.
Check out the object that you wish to compare. This will usually be done at a project status of 21.2.
Make sure the object is highlighted, and then select the design button3.
Select the Design Tools tab4.
Press the button for Visual ER Compare5.
When the ER Compare starts, a window appears. On this window, entitled Select the Location of Source Specifications, select one of these locations:
Central Objects data source of any defined path code
This will pull the Object specifications directly from the logged in Environments Central Objects Tables.
Remote specifications
Per Bug 11028006, this option applies only to TAM (.ddb & .xdb) spec files. Therefore this option cannot used to compare against pathcode specs in
source release 8.12 and above. For more information, read section Using ER Compare after Upgrade.
Upon selecting this option, you will be prompted with a Windows application that will allow you to select the location and file that you wish to be the
source. First map a network drive to the deployment server, select the path to the spec folder of the Full Package in the Select folder pop-up window,
click Open.
Compressed Object Archive
This will pull the object specifications from a PAR file saved in OMW. Saving an object in OMW to a PAR file is available starting with tools release
8.98.1.0, review Document 654394.1 E1: OMW: How to Save an Object as XML Specs to a ZIP/PAR file in OMW.
NOTE: The source is the specifications that you are going to compare against the target specifications. The target specifications are going to come from your
local ER.
The attachment Launching Visual ER Compare is a 3.038 mb multimedia demonstration on launching ER Compare. Although this presentation was developed at the
Xe release of the software, the information is still relevant for current releases of EnterpriseOne.
NOTE: Starting the ER Compare under FDA freezes all other programs running on your system, including FDA itself. Finish your work in ER Compare and then
exit ER Compare to restore normal operation. The purpose of this action is to prevent two programs from potentially modifying the same set of specifications at
the same time.
When using ER Compare on a UBE Batch Application, there is no option to select the version from the source when you perform the ER compare for a batch
version. ER Compare for a batch application will compare both the template and version and display if there are actual ER lines in the events. To differentiate
between the event name at the version level and the event name at the template level, [V] is appended to the version event name.
For example, in ER compare you might see two Do Section events for the same section. One will be displayed as "Do Section" (template level event) and the other
displayed as "Do Section [V]" (version level event). The key to differentiate between the template level event rules and the version level event rules is the [V]
appended to the version level event.
How to Use Visual ER Compare
Use the application tree view to identify and display specific application and ER components that have changed. If a parent node is identified as having changed,
expand it to see which of its children are different. Expand an event in the tree structure to display its associated code. You can display more than one event at a
time. You can change the target ER with JD Edwards ER Compare. You can also print the ER.
Display
In the ER menu, the system uses fonts of different colors to show differences between the rules that exist in both source and target. The system indicates a change
in the parent node if one or more of its children have been changed. In the ER panes, the system highlights the lines that differ.
If lines have been added to or deleted from one side, blank lines appear on the other.
Disabled lines are indicated with an exclamation point.
The system uses fonts of different colors to show the rules that have changed in content or that have been added or deleted.
Document 626548.1 https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLo...
2 of 6 2/5/2014 9:27 PM
You can change the display colors by selecting User Options from the View menu and then selecting Set Colors.
Features
Use the ER menu to identify and display specific ER components that have changed. If a parent node is identified as being changed, expand it to see which of its
children are different. Double-click an event in the ER menu to display its associated code. You can display more than one event at a time. Use the Tile option in
the Window menu to view different ER events simultaneously. You can also move from change to change by right-clicking in either the source or target pane and
choosing Next Difference to move forward or Previous Difference to move backwards. These options are also available as buttons on the toolbar.
Changing Source File
Changing the Source file is simple. Simply select File | Select Source and then choose your desired source file.
Changing Target Event Rules
Perform any of the following actions to change your target ER:
To copy selected lines from source to target
Select the lines to copy, right-click in the source pane, and then choose Copy Right.
To delete selected lines from the target
Select the lines to delete, right-click in the target pane, and then choose Delete.
To enable or disable selected lines in the target
Select the lines to enable or disable, right-click in the target pane, and then choose Enable/Disable ER.
Document 626548.1 https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLo...
3 of 6 2/5/2014 9:27 PM
NOTE: Use the shift key to select multiple, contiguous lines and the control key to select multiple, noncontiguous lines.
After making your changes, select the Save option on the Toolbar.
The Copy All command, available under the Edit pull down menu, copies ER lines from the source to the target, but only within the currently displayed event. The
command will not delete lines from target ER if they do not exist in the source location. The command also does not necessarily copy all lines. It does not copy lines
that would produce any of these types of invalid ER:
Duplicate variables.
Unbalanced IF and ENDIF statements.
Unbalanced WHILE and ENDWHILE statements.
Statements referencing an ER variable that is not defined in the target application.
Statements referencing an ER variable that is defined differently in the target application.
The attachment General Functionality ER Compare is a 4.001 mb file that gives a demonstration that will help familiarize you with the general functionality and use
of ER Compare.Although this presentation was developed at the Xe release of the software, the information is still relevant for current releases of EnterpriseOne.
The attachment General Functionality Continued is a 2.169 mb file that continues the demonstration by showing how to change sensitivity and source files.
Although this presentation was developed at the Xe release of the software, the information is still relevant for current releases of EnterpriseOne.
When launching ER Compare by selecting the VSMerge.exe executable, the program will search for the object that will be compared and adds that object to the
Object Management Workbench (OMW) Default project before doing the compare. Some users are unable to run the ER Compare successfully using the standalone
mode, because the Default project in OMW was not set up with a developer role. Therefore, the object could not be added to the Default project. To resolve this
issue, in OMW, ensure that the user who will be running the ER Compare application has the appropriate allowed actions to add objects into the Default project.
This can be done by assigning the user the Developer or PVC Administrator role. Once the user has the appropriate role to add objects to their default project, they
will be able to successfully run the ER Compare in a standalone mode.
Using the AutoMerge Feature
The Auto Merge Application command resides under the Edit menu. It lets you copy ER lines from all events in the source application to the corresponding events in
the target application. It works like the Copy All command, but it works on all events at once. The command will not delete lines from target ER that do not exist in
the source location. The command also attempts to avoid copying lines that would result in invalid ER.
As with any ER Compare command, you might create invalid ER by using the Auto Merge Application command. As of version 8.98, ER Compare attempts to protect
you from this by disabling unsafe operations. For example, ER Compare prevents the accidental creation of references to undefined ER variables. However, it does
not recognize references to other kinds of undefined objects.
Regardless of how you modify the ER, you should validate event rules prior to saving. This command is found under the File menu. If any ER violations occur,
delete the offending lines and use EditER to reenter them after you have exited the ER Compare.
NOTE: Before performing an AutoMerge for an entire object, do a comparison to be certain that you really want all of the changes that the system detects.
The attachment Auto Merge presentation is a 1.884 mb file demonstrating the AutoMerge, enable/disable and delete functionality. Although this presentation was
developed at the Xe release of the software, the information is still relevant for current releases of EnterpriseOne.
Printing a Visual ER Compare Report
You can print a report comparing the source and target ER. You can show the comparison for a particular event or for all of the ER in the object. To print a report
for an event, double-click the event in the ER menu, right-click in either pane, and then choose Print ER. To print a report for the entire object, choose Print from
the Toolbar or File menu.
Using ER Compare after Upgrade
In order to use the ER Compare Tool to compare event rules from a Previous release after upgrading the EnterpriseOne software, follow steps described depending
on the option selected for the location of the source specifications :
Location of Source Specifications : Central Objects Path Codes
NOTE: This example is for an upgrade of the Prototype (PY) environment.
Create a Database Data Source called "Central Objects - PYTEMP" (if you upgraded the PY environment).1.
The easiest way to do this is to go into Database Data Sources application on menu GH9011. Choose the "System-B7333" data source, and copy the
"Central Objects-PY7333" data source.
When making a copy, it asks for a Data Source Name, put in a name such as "Central Objects-PYTEMP".
The release you are upgrading from will determine how to fill out the rest of the screen. If you are upgrading from B73.3.x, then use the
appropriate owner (i.e. PY7333 or PY7334) and point the data source to the server that holds the B73.3.x Central Objects. The Database Name
would then be "Central Objects- PYTEMP".
Create a Path Code called PYTEMP. The Path Code Master application is located on GH9053.2.
The easiest way to create this path code is to copy the PY7333 path code and change the Deployment Data Source to the newly created data source
above (i.e. "Central Objects-PYTEMP").
Location of Source Specifications : Remote Specifications
Previous releases Xe, 8.0, 8.9, 8.10, 8.11, 8.11SP1 when pathcode specifications are in TAM (.ddb & .xdb) format
This option applies when comparing to source release prior to 8.12 when spec files are stored in TAM format (.ddb & .xdb) per Bug 11028006.
Map a network drive to the deployment server of the previous release1.
Document 626548.1 https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLo...
4 of 6 2/5/2014 9:27 PM
Select the path to the spec folder of the Full Package in the Select folder pop-up window, click Open.2.
Previous releases 8.12 and above when pathcode specifications are in metadata-xml format
Update package specifications are still in TAM (.ddb & .xdb) format) in releases 8.12 and above
Build an update package containing the customized objects in the previous release1.
Copy the update package folder from the deployment server to the development fat client on the target release or map a network drive to the package
directory containing the update package on the deployment server.
2.
Location of Source Specifications : Compressed object archive (only file with .par extension)
This option applies only in source releases 8.12 and above when the previous release allows save of an object in OMW to a file with a .par extension. Prior to
tools release 8.98.1.0, the OMW object is saved to a file with a .zip extension and cannot be used with this option as the .zip file content differs from the .par
file content. For more information, review Document 654394.1 E1: OMW: How to Save an Object as XML Specs to a ZIP/PAR file in OMW.
Ensure the previous release developement fat client is updated with the latest pathcode specs1.
In OMW, add a project. Add the customized objects to the project, click the Save icon on the project, Yes to use Zip file, let the PAR file save in the \e1install
\<pathcode>\spec\ directory.
2.
Copy the saved project par file PRJ_xxx_60_99.par to the development fat client on the target release.3.
Reported Issues with ER Compare
The following table provides links to documents that report known issues with the ER Compare tool.
ER Merge Completed but ER Compare Shows Variables are Different
Even after merging variables, they still show as not having the same ER, although the ER is the same on both sides. Here is the response from development.
The 'line number' in this case is really a spec ID. Each spec has a numeric ID not a relative position in the code but an index to the spec) so they do not do what
you might expect or want. If ID 233 is already being used because you created another variable with that number the 'copy' would have to get a new ID. This is a
time when a 'nice' GUI ER Editor tool isn't really the same as coding it in a normal source editor.
SR # 3-6744915391[This section is not visible to customers.]
Compare PAR with LOCAL Fails to Show Global Scope Variables
When comparing object specs in compressed file (PAR) with very same object in LOCAL, global scope variables are not shown in the source from the PAR file.
Bug:16740805 ER COMPARE DOES NOT SHOW GLOBAL VARIABLES FROM OBJECT IN PAR exists for the issue.
ER Compare Error Saving Specs "didn't find GBRLINK record"
After copying an entire new event, Save fails. Get error message "The program encountered an error saving specs. See log file for possible messages."
jde.log has "4300/4224 MAIN_THREAD Mon Nov 18 13:51:18.380000 SavePrepVis.cpp175
SavePrepVis::VisitEnter - didn't find GBRLINK record"
This is reported and fixed in Bug: 17951654.
Document Title/Bu Document Hyperlink
E1: FDA: ER Compare Displays Entry "OPT: Using Defaults" as a Difference Document 946862.1
E1: FDA: Visual ER Compare for ESU Backup Ends in Error in Release 9.0 Document 806190.1
E1: RDA: Using Visual ER Compare Tool for Different Report Names Document 647915.1
E1: FDA: ER Compare Failed to Launch From a Project Name that Contains a Space Document 889083.1
E1: RDA: In Report Level Events, "Copy Right" causes ER Compare to Crash Document 1335296.1
E1: FDA: Different Object Names Displayed in Event Rules in ER Debugger or ER Compare For Power Form Subforms with Tools Release 8.98 Document 1231724.1
E1: FDA: Find Option under Edit Menu in ER Compare Document 957233.1
E1: FDA: "Copy Right" Fails To Save The Changes in ER Compare Document 877862.1
Bug 11025105 - ER COMPARE MEMORY ERROR BSFN - SAR: 8944001 Bug 11025105
Comparing large text file is not for ER Compare. For C business function, please use tools such as Windiff, please see document
E1: ESU: How To Find Out The Source Code Changes Done To An Application Or BSFN Object In An ESU Using WinDiff Tool (Doc ID 654378.1)
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the Design Tools & Output Technologies - JDE1
Community.
To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details Document 548764.1. If your topic is not currently scheduled please suggest it.
REFERENCES
NOTE:806190.1 - E1: FDA: ER Compare for ESU Backup Ends in Error in Release 9.0
NOTE:647915.1 - E1: RDA: Using the Visual ER Compare Tool for Reports
Document 626548.1 https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLo...
5 of 6 2/5/2014 9:27 PM
NOTE:654378.1 - E1: ESU: How To Find Out The Source Code Changes Done To An Application Or BSFN Object In An ESU Using WinDiff Tool
NOTE:889083.1 - E1: FDA: ER Compare Failed to Launch From a Project Name that Contains a Space
NOTE:1335296.1 - E1: RDA: Using "Copy Right" to copy Report Level Event codes from Source to Target causes ER Compare to Crash
NOTE:654394.1 - E1: OMW: Saving or Restoring Objects Specifications into or from a ZIP/PAR file in OMW
NOTE:1231724.1 - E1: FDA: Different Object Names Displayed in Event Rules in ER Debugger or ER Compare For Power Form Subforms with Tools Release 8.98
NOTE:626593.1 - E1: FDA: Using the FDA Compare Tool
Attachments
Visual ER Compare Overview (2.39 MB)
Launching Visual ER Compare (2.97 MB)
General Functionality ER Compare (3.91 MB)
General Functionality Continued (2.12 MB)
Auto Merge (1.8 MB)
Related
Products
JD Edwards EnterpriseOne > Tools and Technology > EnterpriseOne Tools > JD Edwards EnterpriseOne Tools > Output Mgmt - Report Design Aid
JD Edwards EnterpriseOne > Tools and Technology > EnterpriseOne Tools > JD Edwards EnterpriseOne Tools > Tools - Form Design Aid
JD Edwards EnterpriseOne > Tools and Technology > EnterpriseOne Tools > JD Edwards EnterpriseOne Tools > Tools - Object Management Workbench
Knowledge Categories
JD Edwards EnterpriseOne > JDE E1 Tools > JDE E1 Design Tools > JDE1: TLS DESIGN Form Design Aid ( Primary )
.Old GCS Categories > JD Edwards EnterpriseOne > Tools and Technology > Tools - Form Design Aid
Keywords
COMPARE REPORT; ER COMPARE; ESU; EVENT RULES; JDE1FDACOMPARE; JDE1OMWTOOLS; JDE1RDACOMPARE; REPORT
Document AttributesAuthor: DAH-FAT.US;WHMCDONA.US; Status: PUBLISHED(EXTERNAL)
Owner: [email protected] Publisher: DAH-FAT.US
Alias: Content Type: TEXT/X-HTML
Visibility: EXTERNAL Priority: 3
Created By: [email protected] Created: 02-Jun-2004
Modified By: [email protected] Modified: 23-Dec-2013
Reviewed By: DAH-FAT.US Reviewed: 19-Jun-2012
Source: AWIZ Exception: No
Comments
Back to Top
Copyright (c) 2014, Oracle. All rights reserved.
Legal Notices and Terms of Use
Privacy Statement
Edit Comment Type Status Priority From To
Consider adding infortion on newly reported issue Internal Feedback IMPLEMENTED 3 [email protected] OWNER
merge ER still shows as not equal Internal Feedback IMPLEMENTED 2 OWNER
ER compare for Batch versions Internal Feedback IMPLEMENTED 3 [email protected] OWNER
Using the Visual ER Compare Tool (See attachments) IMPLEMENTED 3 IMPORT OWNER
ZZTOE521:E1: Using the Visual ER (Event Rule) Compare Tool:ZZTOE521 IMPLEMENTED 3 IMPORT OWNER
Document 626548.1 https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?_afrLo...
6 of 6 2/5/2014 9:27 PM