OAF Customization/Extension Standards

OAF Customization/Extension Standards

1.       Create only one custom folder under $JAVA_TOP, lets say $JAVA_TOP/xxcust

In order to do so :-
a.  Create a custom directory(for ex:- xxcust) on Application server under $JAVA_TOP
b.  All the custom java files and .xml files will reside inside $JAVA_TOP/xxcust folder

            Having one custom folder will ensure that custom files will be centrally located and will not mingle with any of the directories which contain Oracle provided standard files.

2.       Custom Java files Package Name Naming Convention

As all custom java files reside in $JAVA_TOP/xxcust folder, hence, custom java files must follow following naming convention for package name for ex:-

3.       Custom Java files Naming Convention

a.    All Java file names must begin with first letter being capital letter.

b.    All custom Java files or .XML files will begin with XXCust(or XXCUST) for ex:- XXCustReqLinesVO.xml and XXCustReqLinesVOImpl.java

c.     If Custom java files or XML files extend Standard VO(i.e. oracle provided) then custom java file name must be prefixed with XXCust, followed by standard VO.xml or VOImpl.java name for ex:-

If we are writing custom VO which extends oracle.apps.icx.por.wf.server.ReqLinesNotificationsVO i.e. oracle provided standard VO, then custom VO Name should be

XXCustReqLinesNotificationsVO which resides in xxcust.oracle.apps.icx.por.wf.server package

4.      New attributes added to View Objects during extension

Ensure that the new attributes that you add to view object during extension begin with xx. It then becomes very easy for any other developer to identify the custom columns. Some VO's are developed by Oracle in expert mode that are not too upgrade safe. Therfore identification of the custom attributes is very important.

5.      OA Framework Deployments

When Oracle delivers their code, they do not provide java files in $JAVA_TOP. However for our custom code we need to decide if we will deploy java files on file system or will leave them within the source control itself. Whatever may be the approach followed, we should be consistent with that approach. Whatever, may be the approach, custom Java Source code must be kept safe either in source control or in server so that whenever new changes are required to be done in custom code we have correct version of custom code in place to start with.

6.      Working on Existing Custom Code

Whenever there are new changes which involve modifying existing custom code, for ex:- custom VO, EO, CO etc.. We pick the latest java source files and .XML files from source control (if maintained) or from server (if java source files moved to server) and modify existing custom java files or XML files. And redeploy the changed custom java/xml files into server. Move the changed java/XML files to source control, as the case may be.

7.      Debugging

          All custom code we write should leverage FND Logging technique using fnd_log.string in PL/SQL and writeDiagnostics in Java. You must not re-invent the wheel for debugging custom code, as a great framework for debug logging comes out of the box in eBusiness Suite.