Hi, we are upgrading to R12.2.9 from R12.1.3. Everything went smooth, and tommorow we will be testing the various "integration points" which involve custom schema. While I am somewhat familiar with R12.2 and the upgrade process itself, having done it before (consultants did the first upgrade here, before I joined the company), I am a bit confused on the integration part. So I know that upgrading involves registering your custom schema within EBS, and that you run readiness reports to find out what those custom shemas are. I understand that after the upgrade is complete, your custom schema are now also editioned (just like anything in APPS), and this way you can apply patches using adop, etc and you won't get into trouble.
What I am confused about is - who owns the objects in those custom schemas - after all is said and done? It seems like the object owner could still be (say) XXROW for an object like a table called XXROW.HRSUPPLEMENTALDATA. In that case, the upgrade involves giving APPS all privelidges to that ojbect so it can edition it - save for owning the object downright itself, correct? On the other hand, I was reading the Oracle R12.2 customization guide and it showed them creating a custom table, and it was owned by APPLSYS.
Where this is leading is- tommorow, when we let some of our devleopers in, they are going to look at and/or test our interfaces. From getting emails of what they need, it sounds like they are used to operating on the APPS schemas directly - eg they want passwords for GL, INV, PO, as well as passwords for their own custom schemas (e.g XXROW, etc). I also need to figure out if they should have the APPS pasword. I discussed this with my manager and I guess he hates giving out the apps password (this is a development environment, our first run of R12.2.9) - I guess in the past they have had problems, and he told me he would much rather give them passwords for particular schemas and we keep the apps password to ourself. However, I said I think in fact with R12.2.9 we may need to do the very opposite: ban these guys from accessing any schemas directly (e.g XXROW) and PARTICULARLY any base schemas in EBS like GL. We should just give out the APPS password and nothing else. Perhaps even create a read-only APPS schema also and whererver these guys can us that, have them use that. From my understanding, going through APPS is so important that these guys may even need to REDEVELOP the customizations for R12.2.9 whereby they query the object FROM APPS (e.g. select * from APPS..HRSUPPLEMENTALDATA) so that apps hits the custom table through the proper edition, with synonyms. Or am I wrong, could we continue to give them passwords to log into (at the very least) these custom schemas like XXROW and keep the apsp password secret.
Thanks in advance for your insight and/or pointers. Marvin