Search Results config_ui_region

Overview

FND_SVC_COMP_TYPES_VL is a validation view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product and exposes the definition of service component types used by the Oracle EBS service infrastructure. In Oracle EBS naming conventions, the "_VL" suffix denotes a validation view that joins a base ("_B") table with its translation ("_TL") table and applies the session language through USERENV('LANG'), so that descriptions are returned in the language of the current user session. The view is documented in ETRM with a status of VALID and supplies both technical attributes of each component type — such as its implementing Java class and its configuration UI region — and its user-facing display name and description. Because it presents a single denormalized row per component type, it is a convenient source for reports, concurrent programs, and integration interfaces that must enumerate the components available to the Service Fulfillment and Service Assurance frameworks without manually joining the base and translation tables.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed to APPS through synonyms:

• FND_SVC_COMP_TYPES_B — the base table holding language-independent attributes of each component type, including the component type key, class name, configuration UI region, customization level, object version number, and standard WHO audit columns.
• FND_SVC_COMP_TYPES_TL — the translation table holding the language-dependent DISPLAY_NAME and DESCRIPTION, keyed by COMPONENT_TYPE and LANGUAGE.

The view text joins the two sources on COMPONENT_TYPE and restricts the translation rows to the current session language: WHERE B.COMPONENT_TYPE = T.COMPONENT_TYPE AND T.LANGUAGE = USERENV('LANG'). Because the join is an inner join, only component types that have a translation row in the active language are returned. This structure is consistent with other FND validation views and means the view is read-only and directly reflects the contents of the underlying tables, including multi-language installations where translated rows are maintained for each installed language.

Key Columns

• ROW_ID — the ROWID of the corresponding FND_SVC_COMP_TYPES_B row, supplied for update-capable form blocks.
• COMPONENT_TYPE — the primary identifier of the service component type and the join key between the base and translation tables.
• COMPONENT_CLASS_NAME — the fully qualified Java class that implements the component type.
• CONFIG_UI_REGION — the region used to render the component's configuration user interface.
• CUSTOMIZATION_LEVEL — indicates the degree to which the component type may be customized, distinguishing seeded, extensible, and user-defined behavior. This is the column most frequently referenced when administrators search for "customization_level" against this object.
• DISPLAY_NAME and DESCRIPTION — the translated, user-facing name and description sourced from FND_SVC_COMP_TYPES_TL.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — the standard audit and optimistic locking columns replicated from the base table.

Common Use Cases and Queries

Typical uses include validating which component types are installed and extensible, reporting the class and UI region associated with each type, and driving configuration or diagnostic screens that must display component types in the user's language.

Listing all component types (example; CUSTOMIZATION_LEVEL values vary by configuration):

SELECT component_type, display_name, customization_level
FROM   apps.fnd_svc_comp_types_vl
ORDER  BY component_type;

Identifying extensible or user-customizable component types, a frequent requirement given the search on CUSTOMIZATION_LEVEL:

SELECT component_type, display_name, component_class_name, customization_level
FROM   apps.fnd_svc_comp_types_vl
WHERE  customization_level = :p_level;

Resolving the implementing class and configuration region for a specific component type:

SELECT component_type, component_class_name, config_ui_region, display_name
FROM   apps.fnd_svc_comp_types_vl
WHERE  component_type = :p_component_type;

Because the view applies USERENV('LANG') automatically, callers need not join the translation table themselves; however, tools executing outside an initialized EBS session should initialize the language context or query FND_SVC_COMP_TYPES_B and FND_SVC_COMP_TYPES_TL directly.