Search Results enable_trace

Overview

FND_CONCURRENT_PROGRAMS_VL is a multilingual (VL) view owned by the APPS schema in the Oracle E-Business Suite Application Object Library (FND) product. It exposes the definition of concurrent programs — the executable units that users submit as concurrent requests — joined with the translated (language-specific) display name and description. The view presents the base concurrent program definition stored in FND_CONCURRENT_PROGRAMS together with translation columns from FND_CONCURRENT_PROGRAMS_TL, filtered by the session language.

Because it is a _VL view, it returns the user-facing concurrent program name (USER_CONCURRENT_PROGRAM_NAME) and description appropriate to the current runtime language (USERENV('LANG')), while also exposing the non-translated CONCURRENT_PROGRAM_NAME. This makes it the standard reporting and integration source for concurrent program metadata across Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

• FND_CONCURRENT_PROGRAMS — the primary base table (aliased B) holding the language-independent definition of every concurrent program: application, program name, executable assignment, execution method, class, queue and print controls, and the descriptive flexfield attribute columns.
• FND_CONCURRENT_PROGRAMS_TL — the translation table (aliased T) holding the translated program name and description, one row per installed language.

The join is on APPLICATION_ID and CONCURRENT_PROGRAM_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'), so each program appears once, in the session language, with the translation defaulting to the base language when no translation exists.

Key Columns

• APPLICATION_ID, CONCURRENT_PROGRAM_ID — the composite primary key identifying the program.
• CONCURRENT_PROGRAM_NAME — the internal (language-independent) program short name.
• USER_CONCURRENT_PROGRAM_NAME — the translated, user-facing program name used in the Submit Requests form.
• DESCRIPTION — the translated description of the program.
• EXECUTABLE_APPLICATION_ID, EXECUTABLE_ID — the executable and its owning application that the program runs.
• EXECUTION_METHOD_CODE — how the program runs (e.g., PL/SQL stored procedure, Oracle Reports, Java, host).
• EXECUTION_OPTIONS — method-specific execution parameters (e.g., procedure name, report template).
• ENABLED_FLAG — whether the program is active and can be submitted.
• SRS_FLAG, RUN_ALONE_FLAG, PRINT_FLAG, SAVE_OUTPUT_FLAG — behavioral flags controlling submission and output handling.
• CLASS_APPLICATION_ID, CONCURRENT_CLASS_ID — the concurrent class that governs affinity, priority, and printing.
• NLS_COMPLIANT, MLS_EXECUTABLE_APP_ID, MLS_EXECUTABLE_ID — multilingual and NLS-related settings.
• ATTRIBUTE1…ATTRIBUTE15, ATTRIBUTE_CATEGORY — assigned descriptive flexfield context and segments.
• ROW_ID, SECURITY_GROUP_ID, LAST_UPDATE_DATE, CREATED_BY — standard auditing and row-identity columns.

Common Use Cases and Queries

The view is used to enumerate available programs, audit program-to-executable assignments, and drive integrations that need translated program labels.

• List enabled programs with their executables
  SELECT application_id, concurrent_program_id, concurrent_program_name, user_concurrent_program_name, execution_method_code FROM fnd_concurrent_programs_vl WHERE enabled_flag = 'Y' ORDER BY user_concurrent_program_name;
• Find programs by short name
  SELECT concurrent_program_name, user_concurrent_program_name, description FROM fnd_concurrent_programs_vl WHERE concurrent_program_name LIKE 'FND%';
• Join to executables for method details
  SELECT cp.user_concurrent_program_name, e.executable_name, cp.execution_method_code FROM fnd_concurrent_programs_vl cp, fnd_executables_vl e WHERE cp.executable_application_id = e.application_id AND cp.executable_id = e.executable_id;
• Locate programs in a given concurrent class
  SELECT user_concurrent_program_name, concurrent_class_id FROM fnd_concurrent_programs_vl WHERE class_application_id = :app AND concurrent_class_id = :class;

Because translations are resolved by USERENV('LANG'), queries always return the current-language label, so the view is preferred for user-facing reports and interfaces. When integration requires every defined language, the underlying FND_CONCURRENT_PROGRAMS_TL should be queried directly instead.