Results for “xdp_adapter_conns_count_v”

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

Overview

XDP_ADAPTER_CONNS_COUNT_V is a reporting view in the Oracle E-Business Suite XDP (Provisioning) module. It summarizes how many provisioning adapters are registered against each Fulfillment Element, together with the connection ceiling configured for those adapters. In the context of EBS 12.1.1 and 12.2.2, the XDP schema underpins the Service Fulfillment Manager (SFM) and related provisioning infrastructure, where fulfillment elements represent discrete provisioning tasks (for example, activating a service or assigning a resource) that the provisioning engine must execute.

The view answers a capacity-planning question: for each fulfillment element name, how many adapters exist, and what maximum connection value is associated with them. Because SFM dispatches work to adapters concurrently, understanding adapter counts and connection limits per fulfillment element is essential for diagnosing throughput bottlenecks and validating configuration after cloning, patching, or migrations. As documented in the ETRM metadata, the view is not implemented in every database; its presence depends on whether the XDP provisioning components have been installed and configured.

The user search term "fulfillment_element_name" maps directly to the grouping column of this view, indicating an interest in enumerating or auditing fulfillment elements and their associated adapter registrations.

Underlying Base Objects

The view text is documented as follows:

• XDP_FES FES — the fulfillment element (FE) table, aliased FES, supplying FE_ID and FULFILLMENT_ELEMENT_NAME.
• XDP_ADAPTER_REG ARG — the adapter registration table, aliased ARG, supplying adapter registrations and the MAX_CONNECTION attribute.

The join is expressed with an outer join on the adapter side: FES.FE_ID = ARG.FE_ID(+). This guarantees that every fulfillment element in XDP_FES is returned, even when no adapter is registered for it. In such cases, COUNT(*) reflects only the joined row (yielding a non-null count attributable to the FE row itself), and MAX_CONNECTION is null. The ETRM metadata documents no other referenced base objects and records the view as not implemented in the documented database instance. In practice, DBAs should confirm installation by querying ALL_VIEWS or DBA_VIEWS for the view name before relying on it.

Key Columns

• FULFILLMENT_ELEMENT_NAME — the descriptive name of the fulfillment element; the grouping key for the aggregation. This is the column most commonly filtered or matched against FE metadata.
• COUNT(*) — the number of rows produced by the join per fulfillment element, effectively the count of adapter registrations associated with that FE.
• MAX_CONNECTION — also part of the GROUP BY clause, exposing the maximum connection threshold defined for the FE's adapters. Because it participates in grouping, multiple distinct MAX_CONNECTION values for a single FE produce multiple result rows.

The presence of MAX_CONNECTION in the GROUP BY, rather than inside an aggregate function, is a notable characteristic: it means the view returns one row per unique combination of fulfillment element name and connection limit, not strictly one row per FE.

Common Use Cases and Queries

Typical scenarios include auditing adapter coverage across fulfillment elements, identifying FEs with no registered adapter, and reviewing connection limits ahead of load testing or tuning.

• List all fulfillment elements with adapter counts and limits:

  SELECT fulfillment_element_name,
         COUNT(*)        AS adapter_count,
         max_connection
  FROM   xdp_adapter_conns_count_v
  ORDER  BY fulfillment_element_name;

• Find fulfillment elements lacking adapters (null MAX_CONNECTION):

  SELECT fulfillment_element_name
  FROM   xdp_adapter_conns_count_v
  WHERE  max_connection IS NULL;

• Highlight elements with the highest connection ceilings:

  SELECT fulfillment_element_name, max_connection
  FROM   xdp_adapter_conns_count_v
  WHERE  max_connection IS NOT NULL
  ORDER  BY max_connection DESC;

Because implementation varies by environment, always validate view availability and reconcile results against XDP_ADAPTER_REG and XDP_FES directly before drawing operational conclusions.