Search Results wf_svc_container_type

Overview

APPS.FND_SVC_COMPONENTS_V is a reporting and integration view in the Oracle E-Business Suite service-oriented framework. It exposes the runtime configuration of Service Components, the agent-based building blocks that support Business Event System messaging, Workflow background processing, and other Service-oriented architecture (SOA) infrastructure. Rather than querying the base configuration table directly, the view joins component definitions to their type definitions, concurrent queue assignments, and translated lookup descriptions, presenting a human-readable, denormalized projection of each Service Component instance.

In the EBS 12.1.1 and 12.2.2 releases, this view is central to administrator-facing forms and diagnostic queries that need to display component status, queue binding, and agent assignments without performing the multi-table joins themselves. It is read-only from a reporting perspective; the underlying writable table remains FND_SVC_COMPONENTS.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects:

• FND_SVC_COMPONENTS (synonym to the base table) — the primary source of component rows, including status, type, container, agent, and queue identifiers.
• FND_SVC_COMP_TYPES_VL (view) — provides the component type name, the implementing class name, and the translated display name.
• FND_CONCURRENT_QUEUES_VL (view) — supplies the concurrent queue name and user-facing queue display name. The join is outer (+), so components without an assigned queue are retained.
• WF_LOOKUPS (view) — used in scalar subqueries to translate COMPONENT_STATUS, CONTAINER_TYPE, and STARTUP_MODE codes into their MEANING values.
• WF_AGENTS (synonym) — used in scalar subqueries to resolve INBOUND_AGENT_DISPLAY_NAME and OUTBOUND_AGENT_DISPLAY_NAME.
• WF_CORE (package) — invoked via WF_CORE.TRANSLATE('WF_SYSTEM_GUID') to bind agent lookups to the correct system GUID.

Key Columns

• COMPONENT_ID / COMPONENT_NAME — unique identifier and name of the Service Component.
• COMPONENT_TYPE / COMPONENT_TYPE_DISPLAY_NAME / COMPONENT_CLASS_NAME — the component category, its translated label, and the implementing Java/PL/SQL class.
• COMPONENT_STATUS / COMPONENT_STATUS_DISPLAY_NAME — the raw status code (e.g., RUNNING, STOPPED) and its WF_LOOKUPS meaning.
• CONTAINER_TYPE / CONTAINER_TYPE_DISPLAY_NAME — the container hosting the component, with its translated description.
• CONCURRENT_QUEUE_ID / CONCURRENT_QUEUE_NAME / CONCURRENT_QUEUE_DISPLAY_NAME — the queue binding for the component.
• INBOUND_AGENT_NAME / INBOUND_AGENT_DISPLAY_NAME and OUTBOUND_AGENT_NAME / OUTBOUND_AGENT_DISPLAY_NAME — agent names and their WF_AGENTS display names, resolved against the WF_SYSTEM_GUID.
• APPLICATION_ID — owning application, sourced from the queue view.
• CORRELATION_ID, MAX_IDLE_TIME, STARTUP_MODE, STANDALONE_CONTAINER_NAME, CUSTOMIZATION_LEVEL, OBJECT_VERSION_NUMBER, CREATED_BY — operational and audit attributes.

Common Use Cases and Queries

Administrators query this view to audit which Service Components are active, confirm their queue and agent wiring, and diagnose messaging failures. A typical status report:

• SELECT component_name, component_type_display_name, component_status_display_name FROM fnd_svc_components_v;
• SELECT component_name, concurrent_queue_name, inbound_agent_display_name, outbound_agent_display_name FROM fnd_svc_components_v WHERE component_status = 'RUNNING';
• SELECT component_name, container_type_display_name, startup_mode FROM fnd_svc_components_v WHERE inbound_agent_name IS NOT NULL;

Because the view resolves the WF_SYSTEM_GUID internally, callers do not need to supply it themselves when tracing agent assignments — which is precisely the lookup the user was investigating.