Directory structure on the server:

      SERVER SIDE DIRECTORY TREE TO STORE FILES

  • Bin : Contains executable code of your concurrent programs written in a programming language such as C, Pro*C, Fortran, or an operating system script.
  • Lib : Contains compiled object code of your concurrent programs.
  • Sql : Contains concurrent programs written in SQL*Plus and PL/SQL scripts.
  • Rpt : Contains concurrent programs written with SQL*Reports.
  • Log : Contains log files from concurrent programs.
  • Forms/(Language) : Each language has a subdirectory ( such as US ). The language subdirectory holds the forms .fmx files.
  • Srw : Contains concurrent programs written with Oracle Reports.
  • Out : Contains output files from concurrent program.
  • Mesg : Holds your application message files for Message dictionary.
  • PLSQL : Contains PL/SQL libraries used with Oracle reports.

Salient features of Aol and Sysadmin functions:

APPLICATION OBJECT LIBRARY:

      As evident from the name AOL i.e. Application Object Library is the Library that contains all the Objects of an Application. For Oracle Apps. To recognize any object, such object must be registered with this Library.

      Salient Features

  • Registering Tables with Oracle Apps.
  • Registering Forms with Oracle Apps.
  • Registering Concurrent Programs with Oracle Apps.
  • Building Menus.
  • Building Flexfields.
  • Enabling Zoom.
  • Building Message Dictionary.

SYSTEM ADMINISTRATION:

  • Manage Oracle Applications security.
  • Manage Concurrent programs & Reports.
  • Manage Concurrent processing.
  • Manage Printers.
  • Manage Profile Options.
  • Manage Document Sequences.

Creating a customized form in Apps:

      You will find it in c:\Apps10\Fnd75\Forms\Us

      Features

      Starting your form with TEMPLATE is the only way to ensure you get the following:

  • Applications Property Classes and Visual Attributes.
  • Toolbar.
  • Menu.
  • Calendar.
  • Required Form-Level triggers.
  • Required Procedures.
  • Applications color palatte.
  • Required Parameters.
  • Required LOVs and Record Groups.
  • And much more !

PlSql libraries used in customization of form and their purpose:

      Attached Libraries Used in forms development

  • APPCORE - Supports Form and User Interface Features.
    1. Packages and Procedures that support the menu, Toolbar and other standard behaviours.
    2. Use APPCORE routines to enable fields to enable fields dynamically, maintain dependencies between items, and control specific window behaviours.
  • GLOBE
  • FNDSQF Supports Many Application Object Library Features.
    1. Most AOL extensions such as message dictionary, multicurrency, WHO information tracking.
    2. Includes Flexfield packages and procedures.
  • JA
  • JL
  • JE
  • CUSTOM Supports Zoom.
  • APPDAYPK - Supports the Calendar.

ZOOM:

      ENABLING ZOOM

      In certain cases, it is useful to be able to access one form directly from another. For example, it may be very convenient to be able to open the Customers form directly from the Sales Orders form, to allow entry of a new customer while creating a new order, or to view information about a customer that has already been defined. From within certain forms you can open another form directly by using the Special menu or, depending on how Oracle Applications has been customized at your site, by choosing Zoom from the Go menu.

      Oracle Applications ship with no Zooms defined, and the Zoom entry on the Action menu is disabled. When this feature is available and how it behaves are determined by how Oracle Applications is customized at your site.

      Zoom allows the addition of user-invoked logic on a per-block basis.

Registering tables in Apps :

      With Release 10.6 and 10.7, you now register your custom application tables using a PL/SQL routine in the AD_DD package.

      Procedures in the AD_DD Package

      procedure register_table (p_appl_short_name in varchar2,
            p_tab_name in varchar2,
            p_tab_type in varchar2,
            p_next_extent in number default 512,
            p_pct_free in number default 10,
            p_pct_used in number default 70);

      procedure register_column (p_appl_short_name in varchar2,
            p_tab_name in varchar2,
            p_col_name in varchar2,
            p_col_seq in number,
            p_col_type in varchar2,
            p_col_width in number,
            p_nullable in varchar2,
            p_translate in varchar2,
            p_precision in number default null,
            p_scale in number default null);

      procedure delete_table (p_appl_short_name in varchar2,
            p_tab_name in varchar2);

      procedure delete_column (p_appl_short_name in varchar2,
            p_tab_name in varchar2,
            p_col_name in varchar2);

p_appl_short_name The application short name of the application that owns the table (usually your custom application).
p_tab_name The name of the table (in uppercase letters).
p_tab_type Use 'T' if it is a transaction table (almost all application tables), or 'S' for a "seed data" table (used only by Oracle Applications products).
p_pct_free The percentage of space in each of the table's blocks reserved for future updates to the table (1-99). The sum of p_pct_free and p_pct_used must be less than 100.
p_pct_used Minimum percentage of used space in each data block of the table (1-99). The sum of p_pct_free and p_pct_used must be less than 100.
p_col_name The name of the column (in uppercase letters).
p_col_seq The sequence number of the column in the table (the order in which the column appears in the table definition).
p_col_type The column type ('NUMBER', 'VARCHAR2', 'DATE', etc.).
p_col_width The column size (a number). Use 9 for DATE columns, 38 for NUMBER columns (unless it has a specific width).
p_nullable Use 'N' if the column is mandatory or 'Y' if the column allows null values.
p_translate Use 'Y' if the column values will be translated for an Oracle Applications product release (used only by Oracle Applications products) or 'N' if the values are not translated (most application columns).
p_next_extent The next extent size, in kilobytes. Do not include the 'K'.
p_precision The total number of digits in a number.
p_scale The number of digits to the right of the decimal point in a number.