Setup guide

Customization Manager Coding Standards D-1

Customization Manager Coding Standards

Customization Manager Coding Standards for Files

Customization Manager has a standards checker to check the that the files included in a

custom package meet certain coding standards. This checker tests all code for standards

compliance.

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.

Mandatory File Standards

The standards in the following table must be met. If a file does not meet these standards

then Customization Manager will not build the package containing it.

Standard Name Description

Header Check Each file must have an Oracle-compliant

source header present.

PLD File Location Standard PLD files must be located somewhere under

one of following directories: resource, plsql,

graphs.

SQL using CONNECT Standard SQL files using a "connect" statement must

have a valid dbdrv hint provided within the

file.

Java Destination Path Standard For Java files within a package, the destination

path must start with "java".