Results for “min_connection”

26 results




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

Overview

XDP_FES is a core provisioning table in the Oracle E-Business Suite (EBS) XDP (Provisioning) module. It holds the master definition of every Fulfillment Element (FE), also referred to as a Network Element, that participates in the service fulfillment and provisioning process. Each row in XDP_FES represents a single fulfillment element together with the configuration attributes and lifecycle dates that govern how that element is activated, connected, and controlled by downstream provisioning, adapter, and network-mapping logic.

In Oracle EBS 12.1.1 and 12.2.2, this table is critical because it acts as the reference point for adapters, event subscriptions, network maps, served number ranges, and service-management mappings. It is owned by the XDP schema and carries the VALID status with the full set of 18 documented columns in 12.2.2. Where editions are enabled, the ZD_EDITION_NAME column supports edition-based redefinition.

From a Data Vault modeling perspective, the FK structure (heuristic classification) suggests XDP_FES should be modelled as a hub. It carries a stable surrogate identifier (FE_ID) and serves as the referenced parent for numerous link and satellite style dependent tables.

Key Information Stored

XDP_FES is anchored by the surrogate primary key FE_ID (XDP_FES_PK). The most significant columns include:

The distinction between surrogate key and business-key candidates is important: FE_ID is the technical identifier, while FULFILLMENT_ELEMENT_NAME (with ZD_EDITION_NAME) is the closest business-key candidate.

Common Use Cases and Queries

Typical use cases include reporting on active fulfillment elements, validating adapter coverage, and diagnosing event subscription configuration. A common reporting query lists each element with its type and geographic area:

  • SELECT f.FE_ID, f.FULFILLMENT_ELEMENT_NAME, t.FE_TYPE_NAME FROM XDP_FES f, XDP_FE_TYPES t WHERE f.FETYPE_ID = t.FETYPE_ID;
  • Adapter coverage check: join XDP_ADAPTER_REG on FE_ID to find elements without registered adapters.
  • Event subscription lookup (the searched term): join XNP_EVENT_SUBSCRIBERS on FE_ID to list subscribers per fulfillment element.
  • Effective dating filter: WHERE SYSDATE BETWEEN VALID_DATE AND NVL(INVALID_DATE, SYSDATE+1).
  • Network topology reporting by joining XNP_NETWORK_MAPS on PARENT_FE_ID / CHILD_FE_ID.

Related Objects

XDP_FES is referenced by many dependent tables through the FE_ID column. The most significant related objects include:

  • XDP_FE_TYPES — referenced via XDP_FES.FETYPE_ID; classifies element types.
  • XNP_EVENT_SUBSCRIBERS — references XDP_FES.FE_ID; event subscriptions per element.
  • XNP_NETWORK_MAPS — references PARENT_FE_ID and CHILD_FE_ID; defines network topology.
  • XDP_ADAPTER_REG — references FE_ID; adapter registration.
  • XDP_FES_TL — references FE_ID; translated attributes.
  • XNP_SERVED_NUM_RANGES — references FE_ID; served number ranges.
  • XNS_CP_FES — references FE_ID; service/control-point mapping.
  • XNP_SP_ADAPTERS and XNP_SV_SMS_FE_MAPS — additional FE_ID references for adapter and service mapping.
  • FND_SECURITY_GROUPS and XNP_GEO_AREAS_B — referenced via SECURITY_GROUP_ID and GEO_AREA_ID.