Results for “num_of_adapters”

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

Overview

XDP_ADAPTER_SUMMARY_V is a reporting view in the APPS schema belonging to the XDP – Provisioning product within Oracle E-Business Suite. It presents aggregated summary information for every Fulfillment Element defined in the system, combining adapter registration counts with queued job volumes. The view is valid in both EBS 12.1.1 and 12.2.2 and is primarily consumed by provisioning administrators and operational reports that need a single, consolidated picture of adapter coverage and workload per Fulfillment Element.

Because adapter definitions and adapter job queues are stored across several normalized tables, the view exists to denormalize that data into a single queryable row per Fulfillment Element. This is particularly useful when diagnosing provisioning throughput, identifying Fulfillment Elements with an unexpectedly high or zero count of registered adapters, and monitoring outstanding job backlogs.

Underlying Base Objects

The view joins six documented objects. XDP_FES_VL is itself a view and supplies the base Fulfillment Element rows, including translated name columns. XDP_ADAPTER_REG holds the registered adapter definitions; each adapter record links to a Fulfillment Element via FE_ID. XDP_ADAPTER_JOB_QUEUE stores individual adapter jobs, and the view derives job counts from it through an inline aggregate subquery grouped by FE_ID. XDP_FE_GENERIC_CONFIG supplies effective-dated generic configuration for each Fulfillment Element, while XDP_FE_TYPES and XDP_FE_SW_GEN_LOOKUP provide type and software-generation classification used to restrict the view to currently valid configurations.

The join strategy is noteworthy: XDP_ADAPTER_JOB_QUEUE is outer-joined to XDP_ADAPTER_REG, and XDP_FES_VL is outer-joined to the adapter registration, ensuring Fulfillment Elements with no adapters or no queued jobs still appear. The XDP_FE_GENERIC_CONFIG, XDP_FE_TYPES, and XDP_FE_SW_GEN_LOOKUP joins are inner joins, and configuration is filtered by a correlated subquery that selects the maximum START_DATE where SYSDATE falls between START_DATE and NVL(END_DATE, SYSDATE). This guarantees only the currently effective configuration row contributes to each result.

Key Columns

• FE_ID — Primary identifier of the Fulfillment Element; the grouping key for the view.
• FE_NAME — The internal Fulfillment Element name, sourced from XDP_FES_VL.FULFILLMENT_ELEMENT_NAME.
• DISPLAY_NAME — The user-facing display name of the Fulfillment Element.
• NUM_OF_ADAPTERS — The count of adapter registration records (COUNT(XAR.FE_ID)) linked to the Fulfillment Element. This is the column most frequently queried when users search for num_of_adapters; it answers the question of how many adapters are defined for a given element.
• NUM_OF_JOBS — The average number of queued adapter jobs computed as NVL(AVG(XAJQ.NUM_OF_JOBS), 0) from the job queue aggregate. A value of zero indicates no queued jobs for the element.

Common Use Cases and Queries

Typical usage includes auditing adapter coverage, locating elements with no adapters, and sizing provisioning queues. A simple listing of all elements with their adapter and job counts:

SELECT fe_id, fe_name, display_name, num_of_adapters, num_of_jobs
FROM   apps.xdp_adapter_summary_v
ORDER  BY num_of_adapters DESC;

To isolate Fulfillment Elements that have queued jobs but few or no adapters — a common configuration-defect pattern:

SELECT fe_name, display_name, num_of_adapters, num_of_jobs
FROM   apps.xdp_adapter_summary_v
WHERE  num_of_adapters = 0
OR     num_of_jobs > 0 AND num_of_adapters < num_of_jobs;

Because the view applies an effective-date filter on configuration, it always reflects the configuration current at execution time, making it safe to embed in scheduled concurrent-program reports without additional date predicates.