11 Naming Convention for Customized Objects

The following table details the naming convention for customized objects.

Table 11-1 Naming Convention

Object Naming Convention Comment
New Table <table_name>_xyz Same as Column Naming Convention
New View <view_name>_xyz Same as Column Naming Convention
New Column in OFSLL Base Version Table abc_<column_name>_xyz  
New Column in OFSLL Base Version View abc_<column_name>_xyz  
New Sequence abc_seqnum_xyz  
New Unique Index abc_udx_xyz/ abc_udx2_xyz  
New Non Unique Index abc_idx_xyz/ abc_idx2_xyz  
New System Parameter (Seed Data) <system_parmeter>_xyz  
New Lookup Type (Seed Data) <lookup_type>_xyz  
New Lookup Code (Seed Data) <lookup_code>_xyz  
New Other (Seed Data) <seed_code>_xyz  
New Correspondence Function <function_name>_xyz  
New Correspondence Element <element_name>_xyz  
New Package Name (EM/EN) xyz<package_name>  
New Package File Name(EM/EN) xyz<package_name>  
New Package Name (EX) <package_name>  
New Package File Name(EX) xyz<package_name>  
New Report File Name xyz<report_name>  
View File Name xyz<view file name>  
  • Where ‘xyz’ is Customer Unique Id
  • Signature of Base OFSLL Package Functions, Package Procedures, Reports, Correspondences and Faxes should not be changed.
  • No New Functions or Procedures should be added to OFSLL Base Packages.
  • List of Objects with exceptions must be published.
When checking-in custom code in version control software, follow theguidelines given below:
  1. Instead of putting all the code in one directory, follow the Base Engine directory structure.
  2. For New custom Engine Create a New Engine directory.
  3. Follow the naming convention for the files. All package files should start with three-character client name.

e.g.: ulnapp_el_100_01.pkb will become : xyzulnapp_el_100_01.pkb for XYZ Bank.

uln_evw.sql will become : xyzuln_evw.sql for XYZ Bank.

DDL scripts should end with the three-character client name.

e.g. crt_vw_applications.sql will become crt_vw_applications_xyz.sql for XYZ Bank.