Sequence Of Firing Triggers In Oracle Forms

Navigational events occur at different levels of the Form Builder object hierarchy (Form, Block, Record, Item). Navigational triggers fire in response to some navigational events in the below order:

- Logon Triggers are fired first in below sequence:

1.PRE-LOGON
2.ON-LOGON
3.POST-LOGON

- After that, Pre Triggers are fired

1. PRE-FORM

2. PRE-BLOCK

3. PRE-TEXT-ITEM

- After that, WHEN-NEW Triggers are fired

1. WHEN-NEW-FORM-INSTANCE

2. WHEN-NEW-BLOCK-INSTANCE

3. WHEN-NEW-RECORD-INSTANCE

4. WHEN-NEW-ITEM-INSTANCE

- After this focus is on the first item of the Block. If we type some data and press the tab key following trigger will fire in sequence

1.KEY-NEXT-ITEM (This trigger is present on the item level).

2.POST-CHANGE (This trigger is present on the item level).

3.WHEN-VALIDATE-ITEM (This trigger is present on the item level).

4.POST-TEXT-ITEM (This trigger is present on the item level).

5.WHEN-NEW-ITEM-INSTANCE (Block Level Trigger).

- After That, POST TRIGGERS are fired

1. POST-BLOCK
2. POST-FORM

Read more »

Compile Oracle forms in 11i and R12

Steps to compile Oracle Forms in 11i and r12:

1. Login to the Application Server as applmgr and run .env file to set the applications environment.
2. Change directory to $AU_TOP/forms/US.
3. Place “.fmb” file in binary mode
4. Execute the below command to generate “.fmx”.

In 11i use the below command:

$ f60gen module=<formname>.fmb userid=apps/<apps_pwd> output_file=/forms/US/<formname>.fmx

In R12 use the below command:

frmcmp_batch userid=apps/<apps_paswd> module=<Form_Name>.fmb output_file=<Form_Name>.fmx module_type=form batch=no compile_all=special

Read more »

How to upgrade/migrate release 11i custom forms to Release 12.

All custom forms that were built and working fine on release 11i are designed and compiled using the Form Builder 6i, while the developer version for R12 is 10G.  

To Upgrade / Migrate:

1.  Download the Forms(.fmb's) and all PLL's(all the PLL from resource folder in AU_TOP) into a Local Machine Folder
2.  Open the custom forms using Forms Developer 10G and connect to DB
3. Compile  and then save them.
4.  Upload the Saved Forms(.fmb's) into the new R12 server(system) in the respective custom paths(paths similar to 11i Server)
5. Compile all the forms to create the .fmx files
6. Open the form and check in R12 instance

If one finds one cannot open them after doing that, make sure to add the Custom_Top entry to the default.env file on the Applications tier.

Read more »