Results for “ste_b”

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

Overview

APPS.XNP_SV_SOA_VL is an Oracle E-Business Suite view owned by the APPS schema that consolidates subscription, service provider, routing, and status information used by the Oracle Communications / ETRM (Enterprise Telecommunications Reference Model) Service Fulfillment and Number Management modules. The view presents a denormalized, reporting-friendly projection of the XNP_SV_SOA base table — the "Service Order Administration" or subscription record — joined to status type definitions (both the base and translated tables), service provider master data, and routing number data.

Because of the _VL suffix, this view follows the standard EBS convention of exposing translated (language-dependent) display values alongside the underlying coded values. In this case, the translation is sourced from XNP_SV_STATUS_TYPES_TL, which supplies the DISPLAY_NAME and DESCRIPTION for each subscription status, while the base table XNP_SV_STATUS_TYPES_B provides the language-independent PHASE_INDICATOR. This makes XNP_SV_SOA_VL the preferred access point for forms, concurrent programs, and reports that must render status text in the user's session language rather than raw lookup codes.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over five referenced base objects, all exposed to APPS through synonyms:

• XNP_SV_SOA — the primary driver table (aliased SVA), supplying the subscription / service order attributes, customer and contact details, dates, and flags.
• XNP_SV_STATUS_TYPES_B — the base (non-translated) status type table (aliased STE_B), supplying PHASE_INDICATOR (exposed as STATUS_PHASE).
• XNP_SV_STATUS_TYPES_TL — the translated status type table (aliased STE_TL), supplying DISPLAY_NAME (STATUS_DISPLAY_NAME) and DESCRIPTION (STATUS_DESC). This is the object surfaced when a user searches for "ste_tl".
• XNP_SERVICE_PROVIDERS — service provider master (aliased SPR_DON for the donor provider), supplying SP_TYPE, CODE, NAME, TIMEZONE, SERVED_BY_FLAG, and address attributes.
• XNP_ROUTING_NUMBERS — routing number reference data, joined via ROUTING_NUMBER_ID.

The join between XNP_SV_SOA, the _B status table, and the _TL status table is what enables both language-independent phase logic and language-dependent display text within one result set.

Key Columns

The view exposes identifiers and business keys (SV_SOA_ID, OBJECT_REFERENCE/PORTING_ID, SUBSCRIPTION_TN, SUBSCRIPTION_TYPE), the lifecycle of the subscription (STATUS_TYPE_CODE, STATUS_PHASE, STATUS_DISPLAY_NAME, STATUS_DESC, STATUS_CHANGE_DATE, STATUS_CHANGE_CAUSE_CODE), and the donor/recipient/mediator service provider relationships (DONOR_SP_ID, RECIPIENT_SP_ID, MEDIATOR_SP_ID, CREATED_BY_SP_ID, CHANGED_BY_SP_ID). Donor provider details are denormalized as DON_TYPE, DON_CODE, DON_NAME, DON_TIMEZONE, and the DON_* address columns. A series of due-date columns (ACTIVATION_DUE_DATE, NEW_SP_DUE_DATE, OLD_SP_DUE_DATE, OLD_SP_CUTOFF_DUE_DATE, DISCONNECT_DUE_DATE, INVOICE_DUE_DATE) supports SLA and workflow monitoring, while control flags (PTO_FLAG, BLOCKED_FLAG, LOCKED_FLAG, CONCURRENCE_FLAG, RETAIN_TN_FLAG) drive processing rules. Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are carried through for auditing.

Common Use Cases and Queries

Typical uses include porting/subscription status reporting, service provider workload and due-date monitoring, and integration extracts feeding downstream provisioning or billing systems. A representative query joining status translation to subscription records is:

• SELECT sv_soa_id, subscription_tn, status_display_name, status_phase, status_change_date
• FROM apps.xnp_sv_soa_vl
• WHERE status_phase = 'PENDING' AND activation_due_date < SYSDATE;

Provider-centric reporting selects DON_CODE, DON_NAME and DON_TIMEZONE alongside RECIPIENT_SP_ID to compare inbound and outbound service providers. Because the view already resolves status translations, queries against it require no additional join to STE_TL, which is the principal convenience it offers over the base table.