Setup guide
14-4 Oracle Application Management Pack for Oracle E-Business Suite Guide
Applications Standards Validation
Customization Manager has a standards checker to check that the files included in a
custom package meet certain coding standards. This checker tests all code for standards
compliance and cannot be turned on or off.
Some standards are mandatory and will result in failure when Customization Manager
attempts to build the package. Other standards are recommended, and the standards
checker will give a warning but the package will be built.
For example, Customization Manager mandates that each file included within a
customization package has an Oracle-compliant source header present within the file. If
a file in a package is missing this header, the package cannot be built.
Oracle-compliant Source Header
Each file included within a customization package is recommended to have an
Oracle-compliant source header present within the file.
The following is an example of an Oracle-compliant header:
$Header: sample.txt 10.1 2012/04/06 09:38 lmathur ship $
The header contains the following elements:
• Filename
• Revision ID - This needs to be incremented every time a file is checked in
• Date and time of checkin
• Author
• Shipment state - ship/noship. For custom files, use the value ship.
Automatic Header Update and Insertion
This option can be enabled while defining or updating the "File Source Mapping" used
for package creation. When the "Automatic header update" option is selected,
Customization Manager takes care of querying the source control repository to derive
the revision number and updates the Oracle-compliant header present within the file
with the same, during the process of package creation.
It is important to ascertain that the correct "Version command" is provided to
lookup/query the revision number from the given source control repository, except
when using CVS or File System. This feature is not supported when the source
repository is 'File System'. Also, for CVS there is no need to specify the version
command as the header is always looked up from the $Header string present within the
file.