Install, Upgrade, Clone, Patch - EBS (MOSC)

MOSC Banner

Editioned columns left on core table following R12.2. upgrade

edited Aug 20, 2021 10:15AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 2 commentsAnswered ✓

Hello all

We are running a very large installation of Oracle EBS - HCM, Payroll and OLM.

We have upgraded one of our development instances from R12.1.3 (latested RUP level) to R12.2.6 (running on RDBMS 11.2.0.4). The actual upgrade path was R12.1.3-to-R12.2, and then applied the R12.2.6 patch immediately afterwards.

Whilst we have a number of items reported from the compliance checker script (ADZDDBCC.sql) one of the main issues we have is with a custom index we have on the core HR table PER_POSITION_DEFINITIONS.

Our custom index is on the columns ID_FLEX_NUM, SEGMENT1, SEGMENT2, SEGMENT3, SEGMENT4, and SEGMENT5 of this table (thus mapping the segments that are in use on our Position Key Flexfield).

Tagged:

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

EBS LCM 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