Install, Upgrades & Change Mgmt - JDE1 (MOSC)

MOSC Banner

What approach should be used to identify JDE APPLs and UBEs that contain custom modifications?

edited Oct 3, 2014 11:49AM in Install, Upgrades & Change Mgmt - JDE1 (MOSC) 2 commentsAnswered

We're running E1 9.0 Tools Release 8.98

We've applied Update 2 and several ESUs in our QA environment and have found that several of our known custom modifications are now missing.  We had Spec Merge-Mod flags set to "C/1" for them. But it looks like we have "C/1" set for programs we have not modified in addition to the ones we know have been customized.

As we begin to retrofit these modifications in our Dev and QA pathcodes, we want to reach a comfort level that no modifications will be missed. Is there another approach to identify base JDE APPLs and UBEs that contain custom modifications?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

E1 Inst & Change Mgmt Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center