Oracle Apps use forms, OAF, and ADF tools to design user interfaces. The look and feel are the same across all the forms, OAF pages to have consistency across Oracle Apps.
Your custom form should also follow the same standards so that it does not look alien when registered with Oracle Apps. So let’s see how you can have same look and feel for custom forms.
Setup forms development environment (Oracle Apps 11i and R12)
Oracle Apps provides TEMPLATE.fmb and APPSTAND.fmb modules which you can use it as a starting point when you want to create a custom form in Oracle Apps.
APPSTAND.fmb:- It is a collection of standard objects like triggers, canvas, windows, blocks, LOV.
TEMPLATE.fmb:- It has sample block, canvas, window, libraries. This form inherits objects properties from APPSTAND.fmb.
This inheritance is important here, if while developing any custom form if it breaks your form behavior would change. Each child form checks these dependencies in $AU_TOP/forms/US and $AU_TOP/resource/US. There is an equivalent path in windows env forms_path. All parent objects should be there in form_path.
1. find forms_path
Below are the steps to find forms_path in Windows.
Navigate to Start–>Run and type regedit to open the registry editor. Click on Edit –> Find. Enter FORMS_PATH in the text box. Click the Find Next button.
It is C:\DevSuiteHome_1\forms. All dependent objects should be under this path.
2. Copy TEMPLATE.fmb, APPSTAND.fmb and PLL
Download TEMPLATE.fmb, APPSTAND.fmb from $AU_TOP/forms/US path and common standard PLL mentioned below from the $AU_TOP/resource path. You can use any FTP client like WinSCP or Filezilla. Copy all these files to your development environment form the path shown above paragraph, in this case, C:\DevSuiteHome_1\forms.
List of Libraries (PLL),
3. Open TEMPLATE.fmb file
Now, launch form builder and TEMPLATE.fmb. The form should open without any error and you should see all files attached to the forms. This should work, but sometimes you may get FRM-10102 error, as form builder could not attach the required libraries.
In this case, you need to attach libraries individually as shown below.
4. Attach PLL to Template.fmb
Below are the steps to attach pll to Template.fmb.
Note:- Do not save TEMPLATE.fmb file till the time all files are attached and you do not get FRM-10102 error, else library attachment will be lost.
Launch form builder and open TEMPLATE.fmb file. Click Ok when you get error popup as shown below.
You will get an error like missing libraries. Click each library and attach it to the forms builder one by one. There is a minimum of 36 libraries you need to attach.
Select the Attached Libraries node and click on the + symbol. This opens Attach Libray pop-up where you can browse and select the file.
Click the Attach button. You may get the error APPCORE.pll contains a non-portable directory specification. Remove path?
Click the Yes button.
Form builder tries to attach the library. But you may get additional pll errors if there is any dependency. So you need to attach that library first and then the original one.
PDE-PLI018 Could not find library FNDSQF
File get attached to the TEMPLATE.fmb form.
We explained how to attach PLL libraries to the TEMPLATE.fmb form to set forms development environment.