How to Setup custom form development
environment in Oracle Apps
by Sandi
July 15, 2023
Apps
Oracle Apps use forms, OAF and ADF tools to design user interface. The look
and feel are the same across all the forms, OAF pages to have consistent
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 to Setup custom form development environment in
Oracle Apps
1. Download [Link] and [Link]
ORA-01756: quoted string not proper...
Pause
Unmute
Loaded: 45.20%
Remaining Time -2:18
Fullscreen
Oracle Apps provides a starting point as [Link] and
[Link] module.
[Link]:- collection of standard objects like triggers, canvas,
windows, blocks, LOV.
[Link]:- sample block, canvas, window, libraries. This form inherits
objects properties from [Link].
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.
2. 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 Find Next button.
It is C:\DevSuiteHome_1\forms. All dependent objects should be under this
path.
3. Copy [Link], [Link] and PLL
Download [Link], [Link] 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),
1. [Link]
2. [Link]
3. [Link]
4. [Link]
5. [Link]
6. [Link]
7. [Link]
8. [Link]
9. [Link]
10. [Link]
11. [Link]
12. [Link]
13. [Link]
14. [Link]
15. [Link]
16. [Link]
17. [Link]
18. PQH_GEN.pll
19. [Link]
20. [Link]
21. [Link]
22. [Link]
23. [Link]
24. [Link]
25. [Link]
26. [Link]
27. [Link]
28. IGI_CBC.pll
29. IGI_CC.pll
30. IGI_CIS.pll
31. IGI_DOS.pll
32. IGI_EXP.pll
33. IGI_IAC.pll
34. IGI_MHC.pll
35. IGI_SIA.pll
36. IGI_STP.pll
37. FNDMOAC
4. Open [Link] file
Now, launch form builder and [Link]. 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 required libraries.
FRM-10102: Cannot attach PL/SQL library APPCORE. This library
attachment will be lost if the module is saved.
In this case, you need to attach libraries individually as shown below.
5. Attach PLL to [Link]
Below are the steps to attach pll to [Link].
Note:- Do not save [Link] 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 [Link] 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 + symbol. This opens Attach
Libray pop up where you can browse and select the file.
Click the Attach button. You may get error [Link] 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 error if
there is any dependency. So you need to attach that library first and then the
original one.
PDE-PLI018 Could not fid library FNDSQF
File get attached to the [Link] form.
