Common Database Objects

A common object is an object that could be used by multiple groups. It could be a generic function, such as one to retrieve the ID for a user. It could be a table that multiple groups could query to get the same information (i.e. serial numbers).

You do not need to wait to see if multiple groups need your object before deciding that it could be a common one. If you feel there is potential for your object to be used by other groups, go ahead and create it as a common one.

Naming Standards:

• The object should be named according to the naming standards for that object.
• If an object was created as something specific to one group and then later decided that it could be a common one, the name of the object should be changed if the existing coding changes could easily be updated. If it is difficult to update the existing code with a new name for an object, then leave the object name as it is.

Schemas:

• Common objects should be created under the ASCX schema (if table or sequence) or under the APPS schema (if function, view, or procedure).
  
  Note: There may be exceptions for objects created for a single group, then converted to a common one.

Modifications to Common Objects:

If a common object needs to be updated, an email should be sent to the development team with the details of the desired change. If there are no objections to the change, the requestor can modify the common object and update any pertinent information in the list below. If there are objections, requestor can set up a meeting with opposing parties to see if a common solution can be reached or requestor should create a similar, but private object with exact needs.