FND_EXECUTABLES

FND_EXECUTABLES stores information about concurrent program executables. Each row includes an application identifier, an executable identifier, an executable name, and the name of the physical executable file as it resides on the operating system. The execution method associated with the executable identifies the tool that is needed to run the executable. A subroutine name is only applicable to immediate concurrent programs and spawned concurrent programs that can be run either as spawned or immediate concurrent program. You need one row for each executable that you are going to submit as a concurrent program. Oracle Application Object Library uses this information to process concurrent requests

Name Datatype Length Mandatory Comments
APPLICATION_ID NUMBER (15) Yes Application identifier
EXECUTABLE_ID NUMBER (15) Yes Executable identifier
EXECUTABLE_NAME VARCHAR2 (30) Yes Developer name for the executable
LAST_UPDATE_DATE DATE
Yes Standard Who column
LAST_UPDATED_BY NUMBER (15) Yes Standard Who column
CREATION_DATE DATE
Yes Standard Who column
CREATED_BY NUMBER (15) Yes Standard Who column
LAST_UPDATE_LOGIN NUMBER (15) Yes Standard Who column
EXECUTION_METHOD_CODE VARCHAR2 (1) Yes Type of execution
EXECUTION_FILE_NAME VARCHAR2 (61)
Developer name for the execution file
SUBROUTINE_NAME VARCHAR2 (30)
Subroutine name for the execution
ICON_NAME VARCHAR2 (30)
Reserved for future use
EXECUTION_FILE_PATH VARCHAR2 (510)
package path will be stored for java concurrent programs.

Usage:


  cursor cur_executable(n_tabid in number
                      , n_appid in number) is
  select e.executable_name  name
  ,      e.execution_method_code
  ,      e.execution_file_name
  ,      e.subroutine_name
  ,      t.user_executable_name
  ,      t.description
  from fnd_executables e
  ,    fnd_concurrent_programs c
  ,    fnd_executables_tl t
  where e.application_id = n_appid
  and   c.concurrent_program_id = n_tabid
  and   c.executable_id = e.executable_id
  and   e.application_id = t.application_id
  and   e.executable_id = t.executable_id
  and   t.language =  userenv('LANG');

FND_EXECUTABLES_TL

FND_EXECUTABLES_TL stores translated information about the executables in FND_EXECUTABLES. Each row includes the language the row is translated to, the translated attributes of the executable, and the executable identifier which uniquely identifies the executable. You need one row for each executable in each of the installed languages. Each row includes a language and source_lang column which can be used to determine if a value has been translated or defaulted.

Name Datatype Length Mandatory Comments
APPLICATION_ID NUMBER (15) Yes Application identifier
EXECUTABLE_ID NUMBER (15) Yes Executable identifier
LANGUAGE VARCHAR2 (4) Yes Language
SOURCE_LANG VARCHAR2 (4) Yes The Language the text will mirror. If text is not yet translated into LANGUAGE then any changes to the text in the source language row will be reflected here as well.
CREATION_DATE DATE
Yes Standard Who column
CREATED_BY NUMBER (15) Yes Standard Who column
LAST_UPDATE_DATE DATE
Yes Standard Who column
LAST_UPDATED_BY NUMBER (15) Yes Standard Who column
LAST_UPDATE_LOGIN NUMBER (15) Yes Standard Who column
USER_EXECUTABLE_NAME VARCHAR2 (240) Yes User name for the executable
DESCRIPTION VARCHAR2 (240)
Description