This content has been marked as final. Show 2 replies
Current recommendation is that all custom code follow the XX naming convention and be owned by the APPS schema - this is to get around the issue of privileges. All other objects (tables, indexes etc) should be in a custom schema with appropriate privileges granted to APPS (just like the seeded schemas such as GL etc)
864641 wrote:Please see these docs/links.
Another no-brainer for the gurus - not for me though....
What are Oracle's stated development standards as far as placement of custom code (packages, procedures and functions)
Are they mandated to go in a custom schema or into the APPS schema>
At our shop we do things a little differently - including creating public synomyms for all objects - whether they are in the apps schema or not.
So given this, is it the APPS schema or custom schema that these custom objects should go into?
Integrating Custom Applications with Oracle Applications [ID 176852.1]
Step By Step Guide to Creating a Custom Application in Applications 11i [ID 216589.1]
Oracle E-Business Suite Developer's Guide -- Chapter 28, Customization Standards