Results for “fnd_svc_components”

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

Overview

FND_SVC_COMPONENTS is a core configuration table within the Oracle E-Business Suite Application Object Library (FND) product, owned by the APPLSYS schema. It stores the definition and runtime state of service components registered with the Oracle EBS Service Infrastructure, commonly referred to as the Service Manager / Service Component layer. These components correspond to the background listener processes and container-based agents that manage distributed communication, concurrent processing coordination, and inbound/outbound messaging across an EBS instance. In EBS 12.1.1 and 12.2.2, this table underpins the Service Manager architecture that enables tiers of an EBS deployment (Web, Forms, Concurrent Manager, and application tiers) to register, start, stop, and monitor their service components.

The ETRM Data Vault classification, mined heuristically from the foreign-key structure, is satellite-leaning. This suggests modeling FND_SVC_COMPONENTS as a satellite attached to a hub representing the component type or component identity, since it carries descriptive and state attributes (status, mode, timing) rather than acting purely as a connecting link between two independent hubs. This is offered as a modeling suggestion, not a mandated design.

Key Information Stored

The table contains 22 documented columns. The most operationally significant are listed below.

• COMPONENT_ID — Surrogate primary key, enforced by FND_SVC_COMPONENTS_PK1. Also participates in the unique index FND_SVC_COMPONENTS_U1 alongside ZD_EDITION_NAME.
• COMPONENT_NAME — Human-readable business identifier for the component. Forms the business-key candidate FND_SVC_COMPONENTS_U2 together with ZD_EDITION_NAME.
• COMPONENT_STATUS and COMPONENT_STATUS_INFO — Current lifecycle state of the component and any diagnostic detail describing that state.
• COMPONENT_TYPE — Foreign key to FND_SVC_COMP_TYPES_B, classifying the component (for example, a listener or container component).
• STARTUP_MODE — Determines whether the component starts automatically or manually.
• CONTAINER_TYPE and STANDALONE_CONTAINER_NAME — Define the container model hosting the component and, where applicable, its standalone container identity.
• APPLICATION_ID — Associates the component with a registered EBS application.
• CONCURRENT_QUEUE_ID — Links the component to a concurrent manager queue where relevant.
• INBOUND_AGENT_NAME and OUTBOUND_AGENT_NAME — Named agents used for inbound and outbound service communication.
• CORRELATION_ID and MAX_IDLE_TIME — Support message correlation and idle-timeout behavior for the running component.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard EBS audit and optimistic-locking columns.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching (12.2.x), which distinguishes edition-specific rows.

Common Use Cases and Queries

Administrators and developers query this table to audit component registration, diagnose Service Manager failures, and verify startup configuration after cloning or patching. Typical reporting checks which components are enabled, their startup modes, and their last known status.

• List active components: SELECT COMPONENT_NAME, COMPONENT_TYPE, COMPONENT_STATUS, STARTUP_MODE FROM FND_SVC_COMPONENTS WHERE COMPONENT_STATUS = 'RUNNING';
• Join to the type table for classification: SELECT c.COMPONENT_NAME, t.USER_COMPONENT_TYPE_NAME FROM FND_SVC_COMPONENTS c, FND_SVC_COMP_TYPES_B t WHERE c.COMPONENT_TYPE = t.COMPONENT_TYPE;
• Edition-aware filtering on 12.2.x: include ZD_EDITION_NAME predicates to isolate the active edition during online patching.

Related Objects

• FND_SVC_COMP_TYPES_B — Parent lookup table; joined via COMPONENT_TYPE.
• FND_SVC_COMP_TYPES_TL — Translation table for component type names.
• FND_SVC_COMPONENT_STATUS — Runtime status records for components defined here.
• FND_CONCURRENT_QUEUES — Referenced through CONCURRENT_QUEUE_ID.
• FND_APPLICATION — Referenced through APPLICATION_ID.
• FND_SVC_COMPONENTS_PK1 / _U1 / _U2 — Primary and unique indexes enforcing identity and business keys.