, ,

Find out the URL of the Application in the database

 Find the URL of the Application in the database:

Option 1:

select HOME_URL from icx_parameters;

Option 2:

Select PROFILE_OPTION_VALUE
From   FND_PROFILE_OPTION_VALUES
WHERE  PROFILE_OPTION_ID =
       (SELECT PROFILE_OPTION_ID
        FROM FND_PROFILE_OPTIONS
        WHERE PROFILE_OPTION_NAME =’APPS_FRAMEWORK_AGENT’)
        AND LEVEL_VALUE=0;
 

/by
,

Functions in Oracle AOL

What is Function?

A function is a part of an application’s functionality that is registered under a unique name for the purpose of assigning it to, or excluding it from, a responsibility.

What are the Function Types?

There are two types of functions:
a] Form (Form Function)

  •   A form function (form) invokes an Oracle Forms form.
  •   Form functions appear in the Navigate window and can be navigated to.

b] Subfunction (Non–Form Function)

  •   A non–form function (subfunction) is a securable subset of a form’s functionality: in other words, a function executed from within a form.
  •   Subfunctions are frequently associated with buttons or other graphical elements on forms.

Forms vs. Subfunctions?

  • Forms appear in the Navigate window and can be navigated to. Subfunctions do not appear in the Navigate window and cannot be navigated to.
  • Forms can exist on their own. Subfunctions can only be called by logic embodied within a form; they cannot exist on their own.
  • A form as a whole, including all of its program logic, is always designated as a function. Subsets of a form’s program logic can optionally be designated as subfunctions if there is a need to secure those subsets.

Advantages of Form Functions

If you want to open the Form in different modes without creating the copies, we can create a Form Function and pass the parameters based on the requirement. The parameter, which is passed in the form function, must be already defined in the form while designing the Form. A menu can be assigned to more than one Responsibility. If you want to restrict some of the Forms from a particular responsibility, we can include Form Function of those Forms in Menu Exclusions of the Responsibility.

What are the standard function types?

  • FORM                                    — Oracle Applications form functions are registered with a type of FORM.
  • SUBFUNCTION                   — Subfunctions are added to menus
  • JSP                                        — JSP functions
  • WWW                                     –PL/SQL functions
  • WWK                                      –PL/SQL functions that open a new window
  • WWR or WWL                      –used for some products in the Oracle Self–Service Web Applications
  • WWJ                                      –OA Framework JSP portlet
  • SERVLET                              –Servlet functions
  • DBPORTLET                        –Database provider portlet
  • WEBPORTLET                    –Web provider portlet
/by
,

Oracle Application Directory Structure

Oracle Application has a file system as shown in the below picture for the APPL_TOP Directory.

GL_TOP: (APPL_TOP/GL/11.5.0) is one of the Module Directory of Oracle Applications. It consists of a release directory (i.e. 11.5.0) under which Forms, Reports, BIN, LIB, SQL, etc.,
Forms/US: Forms directory to store all .FMX (Compiled) Form files of a specific module.
Reports/US: Reports directory to capture all the .RDF (Compiled) Report files of a specific module directory. US is a language specific directory.
BIN: Contains executable code of concurrent programs written in a programming language such as C, Pro*C, Fortran, SQL *LOADER or an operating system script.
LIB: Contains compiled object code (.OBJ files) of your concurrent programs.
SQL: Contains concurrent programs written in SQL*Plus and PL/SQL scripts.
HTML: Contains all .HTML, .HTM web files.
LOG: Contains all .LOG files of concurrent programs.
OUT: Contains output files from concurrent program.
Message: Holds your application message files for Message dictionary.

/by
,

WHO COLUMNS

WHO columns are used to track the information updated or inserted by the users against the tables. FND_STANDARD package is used for this purpose. FND_STANDARD.SET_WHO Procedure is used to update the WHO columns in a Table when a DML operation s (i.e. INSERT, UPDATE) performed.
        1) Created by
        2) Creation date
        3) Last _updated_by
        4) last_update_date
        5) last_update_login

  • Use fnd_profile.VALUE (‘USER_ID’) for retrieving the user_id which will be used by created_by column.

  • Creation date and last_update_date will be normally SYSDATE.

  • last_updated_by is same as created_by.

  • Use USERENV (‘SESSIONID’) for getting the last_update_login id.

    • /by
    , ,

    Key FND Tables in Oracle Application

    Here there are few key FND tables that we use in our AOL queries.

    FND_APPLICATION:
     Stores applications registered with Oracle Application Object Library.
    FND_APPLICATION_TL:
    Stores translated information about all the applications registered with Oracle Application Object Library.
    FND_APP_SERVERS:
    This table will track the servers used by the E-Business Suite system.
    FND_ATTACHED_DOCUMENTS:
    Stores information relating a document to an application entity.
    FND_CONCURRENT_PROCESSES:
    Stores information about concurrent managers.
    FND_CONCURRENT_PROCESSORS:
    Stores information about immediate (subroutine) concurrent program libraries.
    FND_CONCURRENT_PROGRAMS:
    Stores information about concurrent programs. Each row includes a name and description of the concurrent program.
    FND_CONCURRENT_PROGRAMS_TL:
    Stores translated information about concurrent programs in each of the installed languages.
    FND_CONCURRENT_QUEUES:
    Stores information about concurrent managers.

    FND_CONCURRENT_QUEUE_SIZE:
    Stores information about the number of requests a concurrent manager can process at once, according to its work shift.
    FND_CONCURRENT_REQUESTS:
    Stores information about individual concurrent requests.
    FND_CONCURRENT_REQUEST_CLASS:
    Stores information about concurrent request types.
    FND_CONC_REQ_OUTPUTS:
    This table stores output files created by Concurrent Request.
    FND_CURRENCIES:
    Stores information about currencies.
    FND_DATABASES:
    It tracks the databases employed by the eBusiness suite. This table stores information about the database that is not instance specific.
    FND_DATABASE_INSTANCES:
    Stores instance specific information. Every database has one or more instance.
    FND_DESCRIPTIVE_FLEXS:
    Stores setup information about descriptive flexfields.
    FND_DESCRIPTIVE_FLEXS_TL:
    Stores translated setup information about descriptive flexfields.
    FND_DOCUMENTS:
    Stores language-independent information about a document.
    FND_EXECUTABLES:
    Stores information about concurrent program executables.
    FND_FLEX_VALUES:
    Stores valid values for key and descriptive flexfield segments.
    FND_FLEX_VALUE_SETS:
    Stores information about the value sets used by both key and descriptive flexfields.
    FND_LANGUAGES:
    Stores information regarding languages and dialects.
    FND_MENUS:
    It lists the menus that appear in the Navigate Window, as determined by the System Administrator when defining responsibilities for function security.
    FND_MENUS_TL:
    Stores translated information about the menus in FND_MENUS.
    FND_MENU_ENTRIES:
    Stores information about individual entries in the menus in FND_MENUS.
    FND_PROFILE_OPTIONS:
    Stores information about user profile options.
    FND_REQUEST_GROUPS:
    Stores information about report security groups.
    FND_REQUEST_SETS:
    Stores information about report sets.
    FND_RESPONSIBILITY:
    Stores information about responsibilities. Each row includes the name and description of the responsibility, the application it belongs to, and values that identify the main menu, and the first form that it uses.
    FND_RESPONSIBILITY_TL:
    Stores translated information about responsibilities.
    FND_RESP_FUNCTIONS:
    Stores security exclusion rules for function security menus. Security exclusion rules are lists of functions and menus inaccessible to a particular responsibility.
    FND_SECURITY_GROUPS:
    Stores information about security groups used to partition data in a Service Bureau architecture.
    FND_SEQUENCES:
    Stores information about the registered sequences in your applications.
    FND_TABLES:
    Stores information about the registered tables in your applications.
    FND_TERRITORIES:
    Stores information for countries, alternatively known as territories.
    FND_USER:
    Stores information about application users.
    FND_VIEWS:
    Stores information about the registered views in your applications.

    /by