Results for “component_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_APP_COMPONENTS_VL is a consolidated, language-aware view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents a unified catalog of three distinct categories of Application Object Library (FND) metadata: concurrent programs, forms, and concurrent manager service instances (queues), plus a filtered set of web-enabled functions. Rather than querying each FND entity separately, a developer or reporting tool can retrieve component definitions from a single relation keyed by a normalized structure.

The view serves two principal roles. First, it acts as a cross-entity reference for tooling that must enumerate deployable application components regardless of type. Second, because it resolves translated display names by joining the base table to its corresponding _TL translation table using USERENV('LANG'), it returns descriptions and user-facing names already localized to the session language. This makes it suitable for building pick lists, registration utilities, and diagnostic reports where a single query must span programs, forms, and queues. The _VL suffix confirms that the underlying query enforces the language filter internally, so callers need not join translation tables themselves.

Underlying Base Objects

The view is defined as a UNION ALL of four branches over the following documented base objects (all exposed to APPS as synonyms): FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_PROGRAMS_TL, FND_FORM and FND_FORM_TL, FND_CONCURRENT_QUEUES and FND_CONCURRENT_QUEUES_TL, and FND_FORM_FUNCTIONS and FND_FORM_FUNCTIONS_TL. Each branch joins the transactional base table to its translation table on the entity's primary key pair (APPLICATION_ID plus the entity ID) and constrains T.LANGUAGE = USERENV('LANG'), guaranteeing one row per component per session language.

The concurrent program, form, and concurrent queue branches share a parallel join pattern: base table supplies the technical name and identifiers, translation table supplies the user-facing name and description. The function branch is subtly different — it carries no application-scoped key, so APPLICATION_ID is hard-coded to -1 and only functions whose TYPE is one of WWW, WWK, JSP, or SERVLET are included. This restriction excludes PL/SQL and other non-web function types from the result set.

Key Columns

• COMPONENT_TYPE — literal discriminator returned by each UNION branch: CONCURRENT_PROGRAM, FORM, SERVICE_INSTANCE, or FUNCTION. Essential for filtering by category.
• COMPONENT_NAME — the internal/technical name: CONCURRENT_PROGRAM_NAME, FORM_NAME, CONCURRENT_QUEUE_NAME, or FUNCTION_NAME.
• DISPLAY_NAME — the translated user-facing name from the corresponding _TL table (USER_* columns).
• APPLICATION_ID — owning application for programs, forms, and queues; fixed at -1 for functions.
• COMPONENT_ID — the entity primary key: CONCURRENT_PROGRAM_ID, FORM_ID, CONCURRENT_QUEUE_ID, or FUNCTION_ID.
• DESCRIPTION — translated description text from the translation table.

Common Use Cases and Queries

A frequent requirement is to locate a concurrent program by its technical name while obtaining the localized display name. Because the view normalizes concurrent_program as a component type, such lookups are direct:

SELECT component_name, display_name, application_id, component_id
FROM   fnd_app_components_vl
WHERE  component_type = 'CONCURRENT_PROGRAM'
AND    component_name = 'FNDSCPRG';

To inventory all components belonging to a specific application, filter on APPLICATION_ID after excluding functions (which carry -1). To build a unified search or audit report, the component type can drive grouping:

SELECT component_type, COUNT(*)
FROM   fnd_app_components_vl
GROUP  BY component_type;

Administrators may also use the view to enumerate localized web functions:

SELECT component_name, display_name
FROM   fnd_app_components_vl
WHERE  component_type = 'FUNCTION';

Because translated rows depend on USERENV('LANG'), results vary with the session language setting; reports run under a different language may return different DISPLAY_NAME and DESCRIPTION values while COMPONENT_NAME and COMPONENT_ID remain stable.