How to Regenerate forms file in Apps R12 using adadmin

1. Start the adadmin Utility 

From a command line session, as the applmgr user, start the adadmin utility. Please note that if your system is configured using more than one tier and more than one APPL_TOP (in contrast to the shared APPL_TOP), you should run this utility from each forms tier.

 $AD_TOP/bin/adadmin

2. Step Through the Initial adadmin Questions

Reply to the questions as required, such as in the following example:

Your default directory is '/u01/oracle/aol11iappl'.
Is this the correct APPL_TOP [Yes] ?

If the above is true, then hit the [Enter] key.

AD Administration records your AD Administration session in a text file
you specify. Enter your AD Administration log file name or press [Return]
to accept the default file name shown in brackets.

Filename [adadmin.log] :

Here you can record your adadmin session in a specific log file.
This log file will be saved in 
$APPL_TOP/admin/<INSTANCE_NAME>/log directory.

You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?

This option only works in UNIX and the purpose of this question is to notify the AD administrator by mail if any failure occurred while adadmin was running in unattended mode.

Please enter the batchsize [1000] :

This option asks for a specific batch size, to reserve memory when adadmin validates package and procedure information. This option only is meaningful when running database administrative related tasks. For the purpose of generating a form, you can leave the default value.

After this last step, the utility will read the ad configuration file and display related information.

The next step which requires user interaction is:

You are about to use or modify Oracle Applications product tables 
in your ORACLE database 'aol11i' 
using ORACLE executables in '/u01/oracle/aol11iora/8.0.6'.

Is this the correct database [Yes] ?

If correct, hit the [Enter] key. Otherwise, exit this utility by typing "abort" plus the [b] key and verify if your environment has been sourced correctly.

AD Administration needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema:

Here you must enter your SYSTEM database user password. There is no default, since adadmin has no way to determine SYSTEM's password.

Connecting to SYSTEM......Connected successfully.

The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :

At this point, provide the APPS database user password. By default, the password is APPS.

After finally reaching this point, the utility will try to connect to your database and get information regarding your system.

The next step which requires user interaction is the main menu:

            AD Administration Main Menu

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

   1.    Maintain Applications Files menu

   2.    Exit AD Administration

   Enter your choice : 1

Note: In this example, we are showing the main menu for a forms tier adadmin.

In single node installations, the menu is:

            AD Administration Main Menu

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

   1.    Maintain Applications Database Objects menu

   2.    Maintain Applications Files menu

   3.    Exit AD Administration

   Enter your choice : 2

3. Navigate Through the adadmin Menus.

Select the option "Maintain Applications Files menu" by entering the number located at the left of this option.

(This is the number '2' in the above example.)

This will lead to the next menu:

         Maintain Applications Files

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

   1.    Create Applications environment file

   2.    Relink Applications programs

   3.    Copy files to destinations

   4.    Convert Character Set

   5.    Verify files necessary for runtime

   6.    Generate message files

   7.    Generate form files

   8.    Generate graphics files

   9.    Generate product jar files

  10.    Return to Main Menu

Enter your choice :  7

In order to generate a specific form, select the option "Generate form files". Do so by entering the number located at the left of the mentioned option (in this case, 7).  Now, you will be asked for the number of parallel workers that will start generating forms:

Enter the number of workers [3] :

In order to determine the optimal number of workers for your system, you should consider the following general rule:

Total of available workers for your system = (Number of processors) x 3 

In our case, we will generate only ONE form, so there is no need to invoke three workers. In our example, we will generate one single form, but for two languages: US (American English) and ESA (Latin American Spanish). Therefore, the maximum number of workers needed will be two.

The next question is:

Do you want to generate Oracle Forms objects
using this character set [Yes] ?

If this is your correct character set, hit [Enter].  Otherwise, please verify your environment.

Do you want to regenerate Oracle Forms PL/SQL library files [Yes] ? 

In this case, we will not generate any PL/SQL library files, so you might reply 'n' to the above question.

Do you want to regenerate Oracle Forms menu files [Yes] ?

Same as above; reply 'n' to this question.

Do you want to regenerate Oracle Forms executable files [Yes] ?

Here, hit [Enter] to accept the default 'Yes'.

Enter list of products ('all' for all products) [all] :

Now, we need to specify the Application short name. (gl, for General Ledger, ap for Payables, and so on).  In our example we will be using module fnd (Application Object Library).  In 11i, the entry must be typed using lowercase characters.

Generate specific forms objects for each selected product [No] ?

Answer 'y' to this question, since it will regenerate all forms for the module selected previously if 'No' is answered here.

The current set of installed languages is: US ESA

Please select languages for generating Oracle Forms files.
You may select all of the above languages, or just a subset.

Enter list of languages ('all' for all of the above) [all] :

In this case, reply 'all', since this will regenerate the form for all existing languages.

You selected the following languages: US ESA

Is this the correct set of languages [Yes] ? 

In this case, answer 'y' since this is the correct language.

At this point, you will receive, based on how you answered the questions a list of all possible forms that you are able to regenerate:

Selecting product forms to generate...

Selecting forms for Application Object Library...

List of forms in Application Object Library :

    APPTREE.fmx   FNDADDSQ.fmx   FNDADDTC.fmx   FNDADDVW.fmx    FNDAPLT.fmx
   FNDATCAT.fmx   FNDATDAG.fmx   FNDATDAI.fmx   FNDATDAT.fmx   FNDATDOC.fmx
   FNDATENT.fmx   FNDATFUN.fmx   FNDATTCH.fmx   FNDCPDCL.fmx   FNDCPDCQ.fmx
   FNDCPDCS.fmx   FNDCPDIA.fmx   FNDCPDPD.fmx   FNDCPDSR.fmx   FNDCPMCP.fmx
   FNDCPMMD.fmx   FNDCPMMT.fmx   FNDCPMPE.fmx   FNDCPRNO.fmx   FNDCPVCM.fmx
   FNDCPVWR.fmx   FNDFBMAS.fmx   FNDFBMPA.fmx   FNDFBRFP.fmx   FNDFBTST.fmx
   FNDFFIDF.fmx   FNDFFIIF.fmx   FNDFFMCV.fmx   FNDFFMDC.fmx   FNDFFMHL.fmx
   FNDFFMIS.fmx   FNDFFMSA.fmx   FNDFFMSV.fmx   FNDFFMVS.fmx   FNDFFMWP.fmx
   FNDFFSRA.fmx   FNDFFSRN.fmx   FNDFFTST.fmx   FNDFLADM.fmx   FNDFMFBF.fmx
   FNDFMFUN.fmx   FNDLVMLU.fmx   FNDMDMSG.fmx   FNDMNMNU.fmx   FNDNLDCX.fmx
   FNDNLDLG.fmx   FNDNLDTI.fmx   FNDPMNET.fmx   FNDPOMPO.fmx   FNDPOMPV.fmx
   FNDPOMSV.fmx   FNDPRMPD.fmx   FNDPRMPR.fmx   FNDPRRPS.fmx   FNDPRTYP.fmx
   FNDRSGRP.fmx   FNDRSRUN.fmx   FNDRSSET.fmx   FNDSCAPP.fmx   FNDSCAUS.fmx
   FNDSCDDG.fmx   FNDSCGRP.fmx   FNDSCMON.fmx   FNDSCMOU.fmx   FNDSCPLS.fmx
   FNDSCRSP.fmx   FNDSCSGN.fmx   FNDSNASQ.fmx   FNDSNDCT.fmx   FNDSNDSQ.fmx
   TEMPLATE.fmx

Enter forms to generate, or enter 'all' [all] :

In this example we will try to regenerate FNDCPMCP.fmx.

Enter 'FNDCPMCP.fmx' at the prompt. Once you do so, adadmin will invoke the appropriate forms compiler and will regenerate the forms.

If any error is found, review the adadmin log file and the adworker log file(s).  The adworker log files are also located under $APPL_TOP/admin/<INSTANCE_NAME>/log directory.  The file name is adworkxx.log where xx is the number of the worker that had failed.

If submitting the problem to Oracle Support as a service request, please upload the adadmin log and the relevant adworker log.