I’ve attached a cut down sample of our packages.

We generally store the package specs and bodies separately as they often get quite large.

We have a standard format all of our packages conform to:

   1. The “CREATE OR REPLACE PACKAGE BL_UTIL IS” definition is always on the first line, capitalized and the package name doesn’t include the schema name with the package name also always capitalized.
   2. The end of the file contains the “END” with the package name explicitly specified.  That is always followed by a /.
   3. The name of the file is always exactly the same as the package name.
   4. We use the .PKS (package spec) and .PKB (package body) extensions which I understand is the standard.

Its possible for us to make changes to this structure if you can only do it a certain way, but we just need to make sure it will still run using sqlplus as we use sqlplus to script our releases.

I also prefer two files for the package (spec and body) as it keeps the code a bit more organized.