Results for “routing_number_id”

50+ results




Overview
Explore in AI Chat

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

Overview

XNP_INTERCONNECT_AREAS is a table owned by the XNP schema within the Oracle E-Business Suite Number Portability module. It stores the geographic areas covered by a given routing number, providing the associative relationship between routing numbers and the geographic coverage definitions used in number portability processing. The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and consists of nine physical columns.

From a Data Vault modeling perspective, the metadata heuristic classifies XNP_INTERCONNECT_AREAS as a link table. This is a natural fit: the table resolves a many-to-many style association between two business entities — routing numbers and geographic areas — and its unique business key is composed entirely of the two foreign keys that identify those entities. Modelers implementing a raw or derived Data Vault layer may therefore treat this object as a link between the routing number hub and the geographic area hub, with the intersection row representing the coverage assertion itself.

Key Information Stored

The table's structure separates a surrogate primary key from a composite business key, which is characteristic of EBS intersection tables.

The unique index XNP_INTERCONNECT_AREAS_U2 (ROUTING_NUMBER_ID, GEO_AREA_ID) is the business-key candidate: it prevents duplicate coverage rows for the same routing number and geographic area pair.

Common Use Cases and Queries

Typical uses involve answering "which geographic areas does this routing number cover?" and "which routing numbers cover this area?" — both directions of the link. A common query joins the table to XNP_ROUTING_NUMBERS to retrieve routing-number attributes alongside the geographic scope:

  • Listing routing numbers and their covered geographic areas for portability analysis or carrier reporting.
  • Filtering by SECURITY_GROUP_ID to honor EBS security-group isolation in multi-org deployments.
  • Diagnosing duplicate or missing coverage by comparing XNP_INTERCONNECT_AREAS rows against expected routing-number/area combinations.
  • Extract and reporting routines that publish routing-number coverage to downstream number portability systems.

A representative pattern joins on ROUTING_NUMBER_ID and GEO_AREA_ID to reach the descriptive columns of the parent tables, order by routing number for readability, and constrain SECURITY_GROUP_ID to the calling user's security context.

Related Objects

  • XNP_ROUTING_NUMBERS — the parent of the ROUTING_NUMBER_ID foreign key. The most significant dependent table, and the source for routing-number descriptive attributes.
  • XNP_GEO_AREAS_B — the parent of the GEO_AREA_ID foreign key; supplies geographic area definitions.
  • FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID, providing EBS security-group validation and partitioning.
  • XNP_INTERCONNECT_AREAS_PK / U1 / U2 — the primary key and unique indexes that define row identity and the routing-number/area business key.

Together these objects form the routing-number coverage model in the XNP Number Portability module, with XNP_INTERCONNECT_AREAS acting as the resolving link between routing numbers and the geographic areas they serve.