E1: UPG: ESU: Resetting The Solution Explorer Merge UBE R9690002 / R9690002O (Doc ID 639722.1)

Last updated on JULY 28, 2017

Applies to:

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

Goal

Customers may need to rerun the Solution Explorer Merge UBE R9690002 (for an upgrade) / R9690002O (for an update) for during an upgrade or to reapply the Solution Explorer changes from a Software Update - ESUs and ASUs (e.g. Update 2 for EnterpriseOne 9.0 application release level). The Solution Explorer Merge process merges in new tasks and task views (tables F9000, F9001, F9002, F9005, F9005D, F9006, F9006D, F9020, F9022 and F9050) into the Control Tables datasource for the environment.
For an upgrade, the new task records for the new release are merged into the existing Control Tables datasource by the Solution Explorer Merge process.
For an software update (ESUs and ASUs), the new or changed task records are merged into the Control Tables datasource for the environment the update is being applied to.

The "revision level" controls the associated levels for the task levels during the merge process. The Solution Explorer merge process uses the revision levels to determine if a merge is required.

The "From revision level" is the level the environment is starting with (for example, an Xe environment with Update 3 applied to it would be at a revision level of 3).

The "To revision level" is the level the environment is to be updated to. This could be a change in terms of a Software Update where the To revision level would be 10 if you were installing Xe Update 8 to the environment.

In addition, it could be in terms of an upgrade where the "To revision level" would be 700 if you were upgrading the environment to application release 9.1. If the system reads either of these revision levels incorrectly, the merge will not occur or will not complete properly. A listing of the revision levels is at the bottom of this solution. For example, with an upgrade of an environment with Xe Update 6 to 9.0 base, the "From revision level" would be 6 and the "To revision level" would be 600. Another example, For a 9.1 system where the Update 2 is being installed to a new E1 9.1 environment, the "From revision level" would be 700 and the "To revision level" would be 702.

A common error message for the Solution Explorer merge during a software update on the R9690002* PDF is that the "From" and "To" revisions levels are the SAME. This requires reviewing and modifying the revision levels so that the "From" and "To" are correct (and not at the same level) and then rerunning the Solution Explorer merge.

A similar error message may be seen during an upgrade, if an ASU Update for the release has been applied to an environment that has already been upgraded to the new release. For example, you may have upgraded DV7333 to DV910 and then installed 9.1's Update 2 to DV910. When you attempt to upgrade PY7333 to PY910, the system incorrectly reads the "To Revision level "as 702 (9.1 Update 2) rather than 700 (9.1 base) as it should be. The error seen under these circumstances on the R9690002* is:

"Empty Change Tables".

In other words, the process is unable to find records in the change table (F969000) for the "From revision level" and "To revision level" that it has retrieved from the system.

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