Search Results service_instance




Overview
Explore in AI Chat

Overview

APPS.FND_APP_COMPONENTS_VL is a consolidated localization view in the Oracle E-Business Suite Applications (APPS) schema that presents a unified, translated catalog of application components registered in the EBS instance. It is not a base table but a union-all view defined over several foundation (FND) metadata tables, surfacing four distinct component categories through a single queryable interface: concurrent programs, forms, service instances (concurrent queues), and certain function types.

The view is a crucial reference for administrators and integrators who need a single, language-aware listing of deployable components without querying multiple FND tables individually. Because it joins each base table to its corresponding translations table (_TL) using USERENV('LANG'), it returns the user-facing name and description in the session's current language. This makes it appropriate for reporting that must respect the runtime language of the logged-in user, especially in multi-language or global EBS deployments running 12.1.1 or 12.2.2. The "VL" suffix denotes a view that resolves translated (display) values, distinguishing it from untranslated "_B" base tables.

Underlying Base Objects

Per the documented view metadata, FND_APP_COMPONENTS_VL is defined over the following base objects, all referenced through synonyms in the APPS schema:

Each union branch joins the base (definition) table to its translation table on the relevant primary keys (application_id plus the component-specific id) and filters on t.language = USERENV('LANG'). The FUNCTION branch does not carry an application-scoped join key and instead hard-codes the application column to -1, reflecting that form functions are identified by function_id alone in this construction.

Key Columns

The view exposes six positional columns that are consistent across all four union branches:

  • Component type — one of the literals 'CONCURRENT_PROGRAM', 'FORM', 'SERVICE_INSTANCE', or 'FUNCTION', identifying the category of the row.
  • Component name — the internal (base) name: concurrent_program_name, form_name, concurrent_queue_name, or function_name.
  • User name — the translated, user-facing name: user_concurrent_program_name, user_form_name, user_concurrent_queue_name, or user_function_name.
  • Application id — the owning application_id, except for FUNCTION rows where it is fixed at -1.
  • Component id — the surrogate identifier (concurrent_program_id, form_id, concurrent_queue_id, or function_id).
  • Description — the translated description from the corresponding _TL table.

Common Use Cases and Queries

The most frequent use case for the referenced "service_instance" search is isolating the concurrent queue (service instance) rows, which map to the SERVICE_INSTANCE branch of the union. Administrators commonly enumerate all components, list a single type, or find translated display names for migration and audit reporting.

  • List all service instances (concurrent queues) with translated names: SELECT component_name, user_name, application_id, component_id, description FROM apps.fnd_app_components_vl WHERE component_type = 'SERVICE_INSTANCE';
  • List all concurrent programs: SELECT user_name, application_id, component_id FROM apps.fnd_app_components_vl WHERE component_type = 'CONCURRENT_PROGRAM' ORDER BY user_name;
  • Enumerate deployable functions (WWW, WWK, JSP, SERVLET only): SELECT component_name, user_name, component_id FROM apps.fnd_app_components_vl WHERE component_type = 'FUNCTION';
  • Cross-type keyword search by translated name: SELECT component_type, user_name, description FROM apps.fnd_app_components_vl WHERE UPPER(user_name) LIKE '%ORDER%';

Because translation depends on USERENV('LANG'), results reflect the querying session's language; callers requiring a specific locale should set the language environment accordingly. The view is read-only and is best used as a reporting and lookup convenience rather than a data-maintenance target.