HOW TO ADD A CUSTOM OR MODIFIED APPLICATION FORM TO APPS 10SC

Form Designer: Forms 4.5 (Designer) Version 4.5.7.1.8 (Production)

You can find the version you are running by navigating to Help --> About
Forms.

When designing custom forms or modifying existing forms you have two
types of form files:

.fmb files - form source code

.fmx files - generated form

If you are modifying an existing Application Form

-------------------------------------------------

You need to set your FORMS45_PATH variable to your working directory path.
The working directory will contain the .pll and .plx libraries which reside
in au10\res\plsql and the path where the form you are modifying resides OR
you can set your FORMS45_PATH= C:\APPS10\au10\res\plsql;
C:\APPS10\<schema top>\forms\us.

Here is an example:

1. First create a working directory (this can be any name you choose).
You will create Forms_Dev directory for this example.
2. Copy the contents of C:\APPS10\fnd75\forms\us;
C:\APPS10\AU10\res\plsql
in a directory called Forms_Dev
3. If you modified the User Define Form: fndscaus.fmb then your
FORMS45_PATH variable would be set to Forms_Dev.

If you are designing a custom form using Template.fmb file

----------------------------------------------------------

You need to set your FORMS45_PATH variable to your working directory path.
The working directory will contain the .pll and .plx libraries which reside
in au10\res\plsql and the path where the form you are modifying resides OR
you can set your FORMS45_PATH= C:\APPS10\au10\res\plsql.

Here is an example:

1. First create a working directory ( this can be any name you choose).
You will create Forms_Dev directory for this example.
2. Copy the contents of C:\APPS10\AU10\res\us;
C:\APPS10\<custom schema>\forms\us in a directory called Forms_Dev
3. If you are designing a custom form using Template.fmb file for your
custom schema then your FORMS45_PATH variable would be set to
Forms_Dev.

Develop Custom Forms 4.5 for Applications 10SC using the Template.fmb file
--------------------------------------------------------------------------

*Note: When developing custom forms, adhere to the standards documented

in the following manuals:

Oracle Applications Coding Standards Release 10SC (A42530-2)

Oracle Applications User Interface Standards Release 10G (A31209-4)

When creating a new Forms 4.5 AOL form, always use the Template.fmb file as
a starting point. Copy the existing Template.fmb file from the
apps10\fnd75\forms\us directory and give the file and module a new name.
This template form already has the relevant libraries attached.

TEMPLATE contains the following:

Platform-independent references to object groups in the APPSTAND form

(STANDARD_PC_AND_VA, STANADARD_TOOLBAR, and STANDARD_CALENDAR)

Platform-independent attachments of several libraries

(FNDSQF, APPCORE, and APPDAYPK)

For example:

FNDSQF Required, Routines for message dictionary, profiles, flexfields,

and various other utilities.

APPCORE Required, Packages specifically designed to implement these

standards and various other utilities.

APPDAYPK For any form that utilizes the calendar; Packages to implement
the calendar, used on most date fields

CUSTOM For writing Zooms or other custom code; 'NULL' routines until
customized

Every form requires several standard triggers and procedures to link the
form with the library. Many of these triggers and libraries have a default
behavior that a developer overrides for specific items or blocks.

Standard Forms Triggers User-Named Triggers

-------------------------- ---------------------
KEY-CLRFRM ACCEPT
KEY-COMMIT CLOSE_THIS _WINDOW
KEY-DUPREC CLOSE_WINDOW
KEY-EDIT FOLDER_ACTION
KEY-EXIT FOLDER_RETURN_ACTION
KEY-HELP LASTRECORD
KEY-LISTVAL QUERY_FIND
KEY-MENU STANDARD_ATTCHMENTS
ON-ERROR ZOOM
POST-FORM
PRE-FORM
WHEN-FORM-NAVIGATE
WHEN-NEW-BLOCK-INSTANCE
WHEN-NEW-FORM-INSTANCE
WHEN-NEW-ITEM-INSTANCE
WHEN-NEW-RECORD-INSTANCE
WHEN-WINDOW-CLOSED
WHEN-WINDOW-RESIZED

*Note: It is not enough to simply use Forms 4.5 built-ins

(e.g. SET_ITEM_PROPERTY). You must use APP_ITEM_PROPERTY.SET_PROPERTY
because this provides additional properties that native Oracle Forms
does not. You use APP_ITEM_PROPERTY to make sure that these additional
properties behave correctly.

After the Form has been Designed/Modified

-----------------------------------------

The .fmb is the source file which you would make modifications to if this were
an existing form, or if this was a custom form, then the TEMPLATE.fmb would be
the file you design your custom form from. After the .fmb file has been
designed then the .fmb file will need to be compiled as follows:

*NOTE: If you plan to use your form within Oracle Applications then make
sure your Forms Designer is installed on the client PC that has Applications
10.7.0.16.1G or if on the server then make sure the Forms Designer is
installed in the same environment as Apps 10.7 is installed. The reason
is that the form needs to reference all the libraries and user exits
needed when running the form with Oracle Applications.

To start the Forms Designer:

---------------------------
When starting the Forms Designer from your client PC, make sure you have
the FORMS45_PATH set, you have your Applications 10SC installed, and your
Applications Developers Kit installed. Follow the following steps:

1. Navigate to:
Start --> Programs --> Developer 2000 --> Forms Designer

2. Now you are in the Forms Designer. From the menu bar select:

File --> Open ( select your CUSTOM.fmb) --> Compile All (This will
compile your form )

3. You will get the following message:

Do you want to logon before performing compilation?

Hit the yes button

Connect to the database as: apps/<apps password>

Enter your instance name ( Database name )

4. The compiled .fmb file will then need to be generated to create a

.fmx file. To generate the .fmb do the following:

File --> Administrate --> Generate

5. Copy the <form_name>.fmx file to the relevant

<schema_top>/forms/us directory.

Now the form is ready to be registered your custom form with Oracle
Applications.

Register your Form with Oracle Applications

-------------------------------------------

To add a custom form to Oracle Applications 10SC, follow the steps listed:

1. Log on to your 10SC Applications as SYSAMIN/<password> or user with

Application Developer GUI user responsibility.
2. Navigate to Application --> Form
3. Enter the name of your form (without the extension) and the
application
you want the form to be registered to.
4. Enter the user form name and a description. The user form name is the
 one that is picked up in the Function screen.
5. Navigate to Application --> Function
6. Enter the function name (standard naming convention is <application
shortname>.<form name, e.g. FND_FNDSCAUS for User Define Form).
7. Enter the user form name in the form field.
8. Enter the application name the form will be registered to.
9. Enter a user function name (this is picked up in the menu screen).
10. Enter "FORM" in the type field and the description of the function.
11. Navigate to Application --> Menu.
12. Query up the menu to which you want to add the form (function).
13. Enter the sequence number.
14. Enter the prompt that you want to appear in the Object Navigator.
15. Enter the user function name in the function field and a description
of the menu option.