Search Results xnp_service_providers




Overview
Explore in AI Chat

Overview

The XNP_SERVICE_PROVIDERS table is a core master data table within the Oracle E-Business Suite (EBS) Number Portability (XNP) module. It serves as the central repository for defining and managing all telecommunications service providers (SPs) involved in number portability processes. In the context of EBS 12.1.1 and 12.2.2, this table is fundamental to the XNP application's operation, as it uniquely identifies every entity—such as donor, recipient, or mediator—that participates in the porting of telephone numbers between networks. Its integrity is critical for routing, auditing, and executing all portability transactions.

Key Information Stored

While the provided metadata does not list individual columns, the primary and unique key structures define the table's essential identifying attributes. The primary key is the SP_ID column, which is a unique system-generated identifier for each service provider record. The table also enforces a unique constraint (XNP_SERVICE_PROVIDERS_UK1) on the CODE column, which typically stores a business-friendly, unique abbreviation or code for the service provider (e.g., 'TELCO_A'). Other columns, inferred from standard practice and related foreign key relationships, would include descriptive fields such as NAME, STATUS, ADDRESS information, and configuration flags that control the provider's role and behavior within the number portability ecosystem.

Common Use Cases and Queries

This table is primarily referenced for master data lookups, validation, and reporting. Common operational and technical use cases include validating a service provider's existence during order entry, determining roles in a porting request, and generating provider-specific audit reports. A typical query would join this table to various transaction tables to enrich data with provider names.

  • Basic Lookup: SELECT sp_id, code, name FROM xnp_service_providers WHERE status = 'ACTIVE';
  • Transaction Enrichment: SELECT sv.order_number, sp_donor.code AS donor_code, sp_recipient.code AS recipient_code FROM xnp_sv_soa sv JOIN xnp_service_providers sp_donor ON sv.donor_sp_id = sp_donor.sp_id JOIN xnp_service_providers sp_recipient ON sv.recipient_sp_id = sp_recipient.sp_id;
  • Reporting Active Providers: SELECT sp.code, sp.name, COUNT(rng.number_range_id) AS assigned_range_count FROM xnp_service_providers sp LEFT JOIN xnp_number_ranges rng ON sp.sp_id = rng.assigned_sp_id GROUP BY sp.code, sp.name;

Related Objects

The XNP_SERVICE_PROVIDERS table has extensive foreign key relationships, underscoring its central role. Key related transactional and master tables include: