Results for “status_type_code”

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

Overview

XNP_SV_STATUS_TYPES_TL is the translation (language) table paired with the base table XNP_SV_STATUS_TYPES_B in the Oracle EBS Number Portability (XNP) module. It stores the language-specific display text for the status type codes that drive service and number-portability status handling. In Oracle EBS, an "_TL" table holds one row per (entity, language), while the corresponding "_B" table holds one row per entity and carries the language-independent attributes. This design allows seeded and customer-defined status types to be presented in the user's session language without duplicating the base definition.

ETRM classifies this object as satellite-leaning using a heuristic derived from its foreign-key structure — a modeling suggestion rather than a documented fact. The table's role is to hold descriptive, versioned-by-language attributes that hang off the base status type, which is the behavior of a Data Vault satellite.

Key Information Stored

The table is defined as XNP.XNP_SV_STATUS_TYPES_TL and exposes 12 documented columns. The most significant are:

• STATUS_TYPE_CODE — the business key relating each translation row to its parent record in XNP_SV_STATUS_TYPES_B.
• LANGUAGE — the NLS language for the translated text.
• SOURCE_LANG — the language the row was originally authored in, used by the translation framework.
• DISPLAY_NAME — the translated, user-facing label for the status type.
• DESCRIPTION — the translated long description of the status type.
• ZD_EDITION_NAME — the editioning column supporting Oracle's Edition-Based Redefinition (EBR) model.
• SECURITY_GROUP_ID — the Multi-Org / security group identifier, which references FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns.

The primary key is XNP_SV_STATUS_TYPES_TL_PK, defined on (STATUS_TYPE_CODE, LANGUAGE). A separate unique index, XNP_SV_STATUS_TYPES_TL_U1, is defined on (STATUS_TYPE_CODE, LANGUAGE, ZD_EDITION_NAME), making the edition-qualified tuple the effective business-key candidate under EBR. No surrogate numeric key is documented; identity is expressed through the composite business key.

Common Use Cases and Queries

Typical usage centers on resolving status type codes into readable labels for reports, porting request screens, and interfaces. A standard join returns the translated text alongside base attributes:

• Lookup of a display name for a known code and language: SELECT display_name FROM xnp_sv_status_types_tl WHERE status_type_code = :code AND language = USERENV('LANG').
• Reporting all status types with their translated names by joining to XNP_SV_STATUS_TYPES_B on STATUS_TYPE_CODE.
• Auditing translations for a given language or detecting missing translations via an outer join from the _B table.
• Concurrent program or view definitions that resolve labels for Number Portability workflows.

Because the table is edition-enabled (ZD_EDITION_NAME), queries run under EBR should account for the editioning column, typically by relying on the enabling views or the session edition rather than filtering the column explicitly.

Related Objects

The most significant objects related to XNP_SV_STATUS_TYPES_TL are:

• XNP_SV_STATUS_TYPES_B — the base table; joined on STATUS_TYPE_CODE. This is the primary foreign-key relationship.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, governing multi-org security access.
• FND_LANGUAGES — the standard source for valid values of the LANGUAGE column.
• XNP porting request tables — status type codes are used to classify service status values in Number Portability processing.
• Standard EBS audit and translation utilities that populate _TL tables via the Translatable Columns / language seed process.

Together these objects form the lookup-and-translation layer that presents Number Portability status types to users and to downstream porting interfaces.