Search Results xnp_sv_status_types_b




Overview
Explore in AI Chat

Overview

The XNP_SV_STATUS_TYPES_B table is a core reference data object within the Oracle E-Business Suite (EBS) Number Portability (XNP) module. It serves as the master definition table for subscription version statuses. In the context of number portability, a subscription version represents a specific state or iteration of a subscriber's service details during the porting lifecycle. This table defines the discrete status codes (e.g., PENDING, CONFIRMED, CANCELLED, COMPLETED) that a subscription version can transition through. Its primary role is to enforce data integrity and provide a centralized, translatable catalog of valid statuses that govern workflow logic and business rules for service order activation (SOA) processes within the XNP application.

Key Information Stored

As a base table following the EBS multilanguage architecture, XNP_SV_STATUS_TYPES_B stores the non-translatable, code-based attributes of a status type. The primary column is STATUS_TYPE_CODE, which is the unique identifier (primary key) for each status definition. While the full column list is not detailed in the provided metadata, typical base tables in this pattern also include standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for auditing. The human-readable name and description for each status code are stored in the related translation table, XNP_SV_STATUS_TYPES_TL, which is linked via the STATUS_TYPE_CODE.

Common Use Cases and Queries

This table is predominantly used for validation, reporting, and driving application behavior. Common scenarios include validating status transitions in service order workflows, populating list of values (LOVs) in application forms, and generating reports on the distribution of subscription versions across different statuses. A typical query would join the base and translation tables to retrieve a user-friendly status list for the current session language:

  • SELECT b.STATUS_TYPE_CODE, tl.MEANING, tl.DESCRIPTION FROM XNP_SV_STATUS_TYPES_B b, XNP_SV_STATUS_TYPES_TL tl WHERE b.STATUS_TYPE_CODE = tl.STATUS_TYPE_CODE AND tl.LANGUAGE = USERENV('LANG');

Another critical use case involves analyzing service order activity by joining with the XNP_SV_SOA table to count orders by their current or previous status.

Related Objects

The XNP_SV_STATUS_TYPES_B table is central to the Number Portability data model, with several key foreign key relationships documented in the ETRM:

  • XNP_SV_SOA (Service Order Activation): This table references XNP_SV_STATUS_TYPES_B twice. The column XNP_SV_SOA.STATUS_TYPE_CODE holds the current status of a service order, while XNP_SV_SOA.PREV_STATUS_TYPE_CODE stores the immediately preceding status, enabling status history tracking and rollback logic.
  • XNP_SV_STATUS_TYPES_TL (Translation Table): This table holds the language-specific names (MEANING) and descriptions for each status code. It is linked to the base table via the foreign key XNP_SV_STATUS_TYPES_TL.STATUS_TYPE_CODE referencing XNP_SV_STATUS_TYPES_B.STATUS_TYPE_CODE.

These relationships underscore the table's function as the authoritative source for subscription version status codes, ensuring referential integrity across transactional and multilingual components of the XNP module.