Using RDA Compare

This section discusses how to compare and merge specifications using RDA Compare.

To compare and merge specifications using RDA Compare:

  1. Navigate to Object Management Workbench (OMW) from a JD Edwards Development Client.

  2. Check out the object to be the target. The target object should always be a copy of the object received in an ESU or Applications Update.

  3. Click the OMW Design button, click the Design Tools tab and then click the RDA Compare button.

  4. In the Spec Compare Manager, click the Select Source button. The source objects should be the object version that has been customized.

  5. Select the location of the source object under Object Location.

    Source objects may be selected from:

    Location

    Fields

    Central Objects

    Path Code

    Select the path code.

    Object Name

    Select the object name.

    Local

    Path Code

    Select the path code.

    OMW Project (Optional)

    Select the OMW Project

    Filters projects for which you are a member. Specifications come from E1Local

    Object Name

    Select the object name.

    Object History

    Path Code

    Select the path code.

    Object Name

    Select the object name.

    Changed Date

    Displays the date the object was last modified.

    Object Release

    Displays the JD Edwards EnterpriseOne application release.

    Package

    Path Code

    Select the path code.

    Package Name

    Select the name of the full package build.

    Object Name

    Select the object name.

    Development Save

    SAVE Path Code

    Select the path code.

    Save Object Name

    Select the object name.

    file System .par File

    PAR File Name

    Select the file system .par file.

    Value must include the full path and can be a .par or .zip file.

  6. Click the OK button to accept the selection and return to the Spec Compare Manager.

    The selected object version will be extracted from the location and validated. This may take some time depending on the size and location of the object.

    Note: It is not recommended to merge a source report to a target report that is not the same report or copy of the same report. Doing so may result in specifications that are not runnable. RDA Compare tool does not prevent you from doing this, however, if you try this, always back up your report specifications to a PAR file from OMW so they can be restored.
  7. Click the Compare button to display object differences.

    The Compare Specifications form displays with the Source on the left pane and Target on the right pane.

    The Compare Specifications form enables you to compare and merge the specification differences between the specifications.

    The report name row is highlighted in blue. The rows with red text illustrate where the reports are different. Some rows with differences are not selectable and are protected from merge, and the reason why will be displayed in the cell text of the protected object (or, if the object is a field, in the cell text of its parent section object).

  8. Click the OK button to save the merged specifications and exit.

    Note: When a new section is merged into a report that did not previously contain that section, the new section Data Selection will be merged in addition to the above mentioned items.When merging a report, section, or field that has event rules on an event which does not have event rules in the target report the event rules will be copied from the source to the target. When the target event already has event rules, and the event rules are not identical, there will be text in the compare cell indicating that the user must also run Event Rule Compare after merging in the Report Compare Tool to also merge any differences in event rules.