How to generate a specific form through command line and AD "adadmin" utility

 At times, it may be necessary to regenerate a specific form for any number of reasons.


This note provides a detailed example of how to generate a specific form through the AD utility adadmin.


The basic steps are as follows:


1. Select the "Generate Applications Files menu" option.

2. Then select the "Generate forms files" option.

3. Choose the number of workers, the default is recommended and is based off the number of CPUs in your server.

4. Enter "yes" at this prompt to regenerate PL/SQL library files (.pll extension)

5. Enter "yes" at this prompt to regenerate Forms Menu files (.mmb -> .mmx extension)

6. Enter "yes" at this prompt to regenerate Forms Executable files (.fmb -> .fmx extension)

7. Enter the list of products, by short name as they are listed in "$APPL_TOP/". Use commas to separate the product names.

8. If you would like to generate specific files for each product, you may answer "Yes" here and a list of files will be displayed.

9. You may either choose to generate all the previously selected items for all languages or only some of the installed languages.

10. Shows your default and/or selected languages.

11. Enter "yes" if the languages selected are the desired languages.


Start the adadmin Utility

> $AD_TOP/bin/adadmin


Step Through the Initial adadmin Questions
==========================================

Reply to the questions as required:

Your default directory is '**'.

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.

This log file will be saved in $APPL_TOP/admin/<INSTANCE_NAME>/log directory.

The next step which requires user interaction is:


You are about to use or modify Oracle Applications product tables 

in your ORACLE database '' 

using ORACLE executables in ''. 

Is this the correct database [Yes] ?

If correct, hit the [Enter] key. Otherwise, exit this utility by typing "abort" plus the [Enter] 

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 the 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.


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 :  


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


The next question is:


Do you want to generate Oracle Forms objects

If this is your correct character set, hit [Enter].  


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).  


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


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

  &nbsp;FNDFMFUN.fmx   FNDLVMLU.fmx   FNDMDMSG.fmx   FNDMNMNU.fmx   FNDNLDCX.fmx

  &nbsp;FNDNLDLG.fmx   FNDNLDTI.fmx   FNDPMNET.fmx   FNDPOMPO.fmx   FNDPOMPV.fmx

  &nbsp;FNDPOMSV.fmx   FNDPRMPD.fmx   FNDPRMPR.fmx   FNDPRRPS.fmx   FNDPRTYP.fmx

  &nbsp;FNDRSGRP.fmx   FNDRSRUN.fmx   FNDRSSET.fmx   FNDSCAPP.fmx   FNDSCAUS.fmx

  &nbsp;FNDSCDDG.fmx   FNDSCGRP.fmx   FNDSCMON.fmx   FNDSCMOU.fmx   FNDSCPLS.fmx

  &nbsp;FNDSCRSP.fmx   FNDSCSGN.fmx   FNDSNASQ.fmx   FNDSNDCT.fmx   FNDSNDSQ.fmx

  &nbsp;TEMPLATE.fmx


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.


Compile the individual form through the command line
===============================================


1) If using forms customizations (CUSTOM.pll) then run the command below to compile the form.


frmcmp_batch.sh module=<path to fmb file> userid=APPS/APPS output_file=

<full path to fmx output file> module_type=form compile_all=special


frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/forms/US/XXX.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/

12.0.0/forms/US/XXX.fmx module_type=form compile_all=special


2) If you are NOT using form customizations, then run the command below to compile the form.


frmcmp_batch.sh module=<path to fmb file> userid=APPS/APPS output_file=<full path to fmx output file> module_type=form


frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/forms/US/XXX.fmb userid=APPS/APPS  output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/

12.0.0/forms/US/XXX.fmx module_type=form


For reference Oracle Metalink Support Doc ID (178722.1)

Comments

Post a Comment

Popular posts from this blog

How to drop index and before dropping it how to get the DDL.

  Oracle DROP INDEX statement DROP INDEX [schema_name.]index_name; DECLARE index_count INTEGER; BEGIN SELECT COUNT(*) INTO index_count FROM USER_INDEXES WHERE INDEX_NAME = 'index_name' ; IF index_count > 0 THEN EXECUTE IMMEDIATE 'DROP INDEX index_name' ; END IF; END; / In case want to check whether index exists and then delete it. If try to drop a non-existing, you will get the following error: SQL Error : ORA -01418 : specified index does not exist In SQLplus, set these before running the commands set long 100000 set longchunksize 100000 select DBMS_METADATA.GET_DDL( 'INDEX' , 'index_name') from all_indexes where owner in ( USER , 'USER_OTHER_THAN_LOGGED_IN_USER' ); Use below script to fetch metadata other information. SELECT DBMS_METADATA,GET_GRANTED_DDL('SYSTEM_GRANT','SSO******') from dual;
Read more

PRVG-11250 : The check "RPM Package Manager database" was not performed because

Following message reported from cluvfy while performing pre-requisite for Clusterware Installation:  Verifying RPM Package Manager database ...INFORMATION PRVG-11250 : The check "RPM Package Manager database" was not performed because it needs 'root' user privileges. SOLUTION Execute runcluvfy manually with "-method root" option and enter root password when prompted : Example: $/runcluvfy.sh stage -pre crsinst -n <HOSTNAME1>,<HOSTNAME2> -method root Enter "ROOT" password: For reference metalink doc id :  2548970.1
Read more

ORA-00257:archiver error, connect internal only until freed

  Issue: Application log shows below error and users are unable to connect to the database. 0RA-00257:archiver error, connect internal only until freed (OR) 0RA-00257:archiver error, connect internal only until freed ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST Fix: 1) Check if there are any errors for the archive destination(s). Make sure that the number of VALID archive destinations is greater than or equal to the value specified by LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter. set pages 1000 col dest_name for a30 col destination for a60 SELECT dest_id, dest_name, binding, status, destination, error FROM v$archive_dest; SHOW PARAMETER log_archive_min_succeed_dest 2) If space is full in one or more of the archive destinations (or if destination is not available), take any of the following steps: 2.a) Manually move the archives to another location and delete them from archive destination.   (OR) 2.b) Change the archive des...
Read more

Verifying Daemon “Avahi-Daemon” Not Configured And Running …FAILED (PRVG-1360)

  Execute "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" as root user on nodes "shsebs7idb1" to perform the fix up operations manually Press ENTER key to continue after execution of "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" has completed on nodes "shsebs7idb1" Fix: Daemon "avahi-daemon" not configured and running   Node Name                             Status   ------------------------------------  ------------------------   shsebs7idb1                           failed ERROR: shsebs7idb1: PRVG-9023 : Manual fix up command "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" was not issued by root user on node "shsebs7idb1" Result: "Daemon "avahi-daemon" not configured and running" could not be fixed on nodes "shsebs7idb1" SOLUTION: To fix this error, stop and disable avahi-daemon service. 1. Check avahi-daemon status: [root@shsebs7idb1 ~]# ls -...
Read more

Linux OL7/RHEL7: PRVE-0421 : No entry exists in /etc/fstab for mounting /dev/shm

  This is due to below bugs: OL7 -  Unpublished Bug 21441387- 12.2/MAIN/OL7.1: CVU REPORTS /DEV/SHM NOT MOUNTED WHEN IT IS MOUNTED  21441387.8 RHEL 7 - Unpublished Bug 25907259 : RHEL7.2: CVU REPORTS /DEV/SHM NOT MOUNTED WHEN IT IS MOUNTED  25907259.8 As a work-around in OL7: In OL7, the /dev/shm is not mounted in /etc/fstab on a fresh system, it is done in: [root@testc140 u02]# ll /usr/lib/dracut/modules.d/99base/init.sh -rwxr-xr-x. 1 root root 11379 Mar 26 10:14 vi /usr/lib/dracut/modules.d/99base/init.sh and comment the below lines 62 if ! ismounted /dev/shm; then 63 mkdir -m 0755 /dev/shm 64 mount -t tmpfs -o mode=1777,nosuid,nodev,strictatime tmpfs /dev/shm >/dev/null 65 fi so, this validation is not really valid for OL7.    We can also safely ignore this message. For reference metalink id: -  Doc ID 2065603.1
Read more

SKIP DNS RESLOV.CONF CHECK DURING RAC CONFIGURATION

 shsebs7idb1: PRVG-2064 : There are no configured name servers in the file              '/etc/resolv.conf' on the nodes "shsebs7idb1" Solution: [root@shsebs7idb2 ~]# ls -ltr /etc/resolv.conf -rw-r--r--. 1 root root 78 Jul  3 11:02 /etc/resolv.conf [root@shsebs7idb2 ~]# mv /etc/resolv.conf /etc/resolv.conf.sid Rename resolv.conf to resolv.conf.sid for example and re run the installation again . It  worked for me
Read more

CPU Patch Analysis

 Oracle CPU patch analysis Identifying the Latest Critical Patch Update for Oracle E-Business Suite Release 12.2 (Doc ID 2484000.1) Database Quick-Link If you only care about the database patches, this MOS note steps you through really easily. Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patch sets and Base Releases (Doc ID 2118136.2) https://www.oracle.com/security-alerts/ Critical Patch Updates Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. Starting in April 2022, Critical Patch Updates are released on the third Tuesday of January, April, July, and October (They were previously published on the Tuesday closest to the 17th day of January, April, July, and October). The next four dates are: 16 April 2024 16 July 2024 15 October 2024 21 January 2025 A pre-release announcement will be published on the Thursday preceding eac...
Read more

How to write to a CSV file using Oracle SQL*Plus

  SPOOL command  The  SPOOL  command is  unavailable  in the browser-based SQL*Plus version,  iSQL*Plus . To generate files while using iSQL*Plus, change the necessary preference settings to directly output to a file. This is accomplished using the  SPOOL  statement. While  SPOOL  is  active , SQL*PLus will store the output of any query to the specified file. Therefore, the next command to enter is  spool : spool filepath Skipping ahead slightly,  after  your query is inserted, you also need to halt  spool  so the file output is closed by using the  spool off  command: spool off Insert the query  The last step after the settings are modified and  spool  is running is to insert your query. For our simple example, we’re outputting all books from our  books  table. SELECT   title,   author FROM   authors; Don’t forget the semi...
Read more

How to troubleshoot Long Running Concurrent Request in EBS 12.2

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link...
Read more

How To Manage Space of The FRA in the Oracle DB

  Delete Old files connect with the target database using RMAN RMAN target / Delete the old files RMAN> delete obsolete; Remove Restore Points SQL> SELECT name, storage_size FROM gv$restore_point; Drop the restore point SQL> DROP restore point RP; Delete the archive logs RMAN> DELETE archivelog ALL Increase the Space SQL> ALTER SYSTEM SET db_recovery_file_dest_size = 20G scope=both; Disable the Flashback ALTER DATABASE flashback off;
Read more