Project and Portfolio Management Practitioners Forum
cancel

Object Migration Concern after Extensions Upgrade

SOLVED
Go to solution
Highlighted
Raj Ghimire
Outstanding Contributor.

Object Migration Concern after Extensions Upgrade

Hi,
We are a little concerned about what,if any, issues we might run into for Object migrations for objects which have already migrated through one instance and waiting to be moved along to others. Say: an AOL object type has been moved from DEV to TEST using 6.0 versions and then the Oracle Apps & Oracle Technology extensions are upgraded to 7.1->7.5 version.
Has anyone noticed any issues in such schenarios to move the same objects using the SAME package line from TEST to other instances?
Will appreciate if you can share your experience.
Thanks.
-Raj
4 REPLIES
Jim Esler
Acclaimed Contributor.

Re: Object Migration Concern after Extensions Upgrade

Anything that you extracted at 6.0 will fail to import into 7.x but anything that was in the database when you upgraded can be extracted and successfully imported into another instance at the same level.
Raj Ghimire
Outstanding Contributor.

Re: Object Migration Concern after Extensions Upgrade

Thanks for the response Jim !
Do you mean to say that if developers have only added package lines and Saved and have not executed the package yet, those package lines may be effected ?

See, in our case, we will definitely have multiple packages that will be in various stages of migration Workflow.
Using Migration packages which are attached to parent change Projects, our Developers may either have files/conc reqs already migrated to TEST, or QA. But they need to be able to use the same package line again to move the same files forward, say to PLAN or PROD. Will that be an issue ?

Thanks in advance.
-Raj
Jim Esler
Acclaimed Contributor.
Solution

Re: Object Migration Concern after Extensions Upgrade

If you are using object types based off the PPM xxx Migrator types included in the product, it depends on how you use the OTs and how your workflow is set up. We extract the object from each instance and import it into the next instance at each migration step. This works only when the source and target instances are at the same release level. Any object extracted at 6.0 can only be imported into an instance at 6.0.

If your developers are using OTs that migrate stuff to something other than the PPM database, upgrading the PPM instance to a new release will not affect workflows that were in progress at the time of the upgrade.
Raj Ghimire
Outstanding Contributor.

Re: Object Migration Concern after Extensions Upgrade

Thanks Jim !
You surely cleared things up.

We are worried about Migrations between Non-PPM databases which are handled using PPM Object types.
Seems like we don't have to worry too much about this. But of course some testings will follow before PROD implimentation anyway.
Thanks a Lot !
-Raj