Results for “fnd_svc_comp_types_b”

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

Overview

FND_SVC_COMP_TYPES_B is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the definition of Service Component Types — the registry of component classes that the Service Component architecture uses to instantiate, render, and parameterize configurable service components across the EBS technology stack. In Oracle EBS 12.1.1 and 12.2.2 this table acts as the master reference for every component type registered with the Service Component framework, providing the metadata that drives the configuration user interface, the Java class binding, and the runtime behavior of each component.

From a dimensional modeling perspective, the foreign-key topology indicates a hub-leaning classification: COMPONENT_TYPE is a stable, non-transactional business key referenced by multiple dependent tables (FND_SVC_COMPONENTS, FND_SVC_COMP_PARAMS_B, and the translation table FND_SVC_COMP_TYPES_TL), which is characteristic of a hub entity in a Data Vault model.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• COMPONENT_TYPE — the business key identifying each service component type. This column forms the primary key FND_SVC_COMP_TYPES_B_PK1 and also participates in the unique index FND_SVC_COMP_TYPES_B_U1.
• COMPONENT_CLASS_NAME — the fully qualified Java class that implements the component type at runtime.
• CONFIG_UI_REGION — the Oracle Forms or OA Framework region used to render the configuration interface for the component.
• CUSTOMIZATION_LEVEL — controls the degree to which the component type may be customized or overridden by administrators.
• OBJECT_VERSION_NUMBER — the optimistic-locking version counter used by the OAF framework to detect concurrent updates.
• ZD_EDITION_NAME — the editioning column introduced for Oracle Database Edition-Based Redefinition (EBR) support. It appears in the composite unique index FND_SVC_COMP_TYPES_B_U1 (COMPONENT_TYPE, ZD_EDITION_NAME), which is the true business-key candidate.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and update provenance.

The surrogate primary key is FND_SVC_COMP_TYPES_B_PK1 on COMPONENT_TYPE; however, the composite unique index including ZD_EDITION_NAME establishes the edition-aware business key.

Common Use Cases and Queries

Typical scenarios include diagnosing component registration failures, auditing custom component types added by third-party integrations, and reporting on the set of available component types delivered versus those customized. A frequent query pattern joins the base table to its translation table to retrieve user-facing names:

• SELECT ct.COMPONENT_TYPE, ct.COMPONENT_CLASS_NAME, ctl.USER_COMPONENT_TYPE_NAME FROM FND_SVC_COMP_TYPES_B ct, FND_SVC_COMP_TYPES_TL ctl WHERE ct.COMPONENT_TYPE = ctl.COMPONENT_TYPE AND ctl.LANGUAGE = USERENV('LANG');
• Identifying all component parameters associated with a given component type by joining FND_SVC_COMP_PARAMS_B on COMPONENT_TYPE.
• Detecting custom or overridden component types by comparing CUSTOMIZATION_LEVEL against Oracle-delivered defaults, useful during patching and upgrade validation.

Related Objects

The following objects reference or depend on FND_SVC_COMP_TYPES_B through documented foreign keys:

• FND_SVC_COMPONENTS — relates via FND_SVC_COMPONENTS.COMPONENT_TYPE → FND_SVC_COMP_TYPES_B.COMPONENT_TYPE; stores instantiated service components.
• FND_SVC_COMP_PARAMS_B — relates via FND_SVC_COMP_PARAMS_B.COMPONENT_TYPE → FND_SVC_COMP_TYPES_B.COMPONENT_TYPE; holds parameter definitions for each component type.
• FND_SVC_COMP_TYPES_TL — relates via FND_SVC_COMP_TYPES_TL.COMPONENT_TYPE → FND_SVC_COMP_TYPES_B.COMPONENT_TYPE; provides multilingual translations of component type names and descriptions.

Together these tables form the Service Component metadata layer within the Application Object Library, with FND_SVC_COMP_TYPES_B serving as the central hub from which all component instantiation and parameterization flows.