Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

Does repository merge ignore inactive objects?

edited Aug 13, 2014 5:01AM in Siebel System Admin, Install and Upgrade (MOSC) 1 commentAnswered

I’m supporting a customer that is upgrading from 7.8.2.16 to 8.1.1.11.  The development team had inactivated a large number of objects within the Siebel repository (Opportunities) because they hadn’t planned to use that Siebel functionality in their upgraded application.  They upgraded their dev environment, including repository merge and have been working for several weeks on post upgrade tasks of resolving conflicts and performing unit tests.  The business has now done an about-face and decided to keep the Contracts and Projects functionality within Siebel.

When they initially ran their repository merge were the inactive objects considered and merged with the new 8.1 changes to those objects? Or does the repository merge ignore inactive objects?  Bottom line, should they re-run their Development upgrade or are they OK with re-activating those objects they now plan to use and continuing forward?

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

SBL Sys Admin 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