Results for “xnp_sv_status_types_b_u1”

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

Overview

XNP.XNP_SV_STATUS_TYPES_B is a seed data table in the Oracle E-Business Suite (EBS) XNP schema, which supports subledger accounting and transaction processing. In the 12.1.1 and 12.2.2 releases, this table stores the valid statuses that may be assigned to a SOA subscription version. The subscription version status governs what information can be inserted into the associated records and determines what information is written to historical tables. Because updates to this table should be limited to a system administrator, it functions as a controlled reference object rather than a transactional table.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as seed data. Its primary key is XNP_SV_STATUS_TYPES_B_PK, defined on STATUS_TYPE_CODE. The unique index XNP_SV_STATUS_TYPES_B_U1, which the user searched for, is defined on the columns STATUS_TYPE_CODE and ZD_EDITION_NAME, making that pair a composite business-key candidate. Under the heuristic Data Vault classification provided in the metadata, the object is hub-leaning — meaning it is best understood as a hub-like reference table holding the distinct business keys for subscription version statuses, with descriptive attributes carried alongside.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• STATUS_TYPE_CODE — VARCHAR2(20), mandatory; the code identifying the status type. This forms the surrogate/simple primary key and is also the leading column of the unique index.
• ZD_EDITION_NAME — VARCHAR2(30); the editioning column paired with STATUS_TYPE_CODE in the unique business-key index XNP_SV_STATUS_TYPES_B_U1. This supports the Edition-Based Redefinition model in 12.2.x.
• PHASE_INDICATOR — VARCHAR2(20); indicates the phase of the status type code. A nonunique index, XNP_SV_STATUS_TYPES_B_N2, exists on this column.
• ACTIVE_FLAG — indicates whether the status is currently in use.
• INITIAL_FLAG — marks the initial status of a subscription version; documented as not used. A nonunique index, XNP_SV_STATUS_TYPES_B_N1, exists on this column.
• INITIAL_FLAG_ENFORCE_SEQ — NUMBER; enforces the rule that only one row has INITIAL_FLAG set; documented as not used.
• DISPLAY_SEQUENCE — NUMBER; controls the sequence in which statuses appear on screens and reports.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns tracking record creation and maintenance.
• SECURITY_GROUP_ID — NUMBER; used in hosted environments, with a foreign key to FND_SECURITY_GROUPS.

Together, STATUS_TYPE_CODE and ZD_EDITION_NAME provide the unique business key, while the remaining descriptive columns supply the semantic detail associated with each status.

Common Use Cases and Queries

Typical usage centers on validating subscription version statuses, driving workflow transitions, and producing administrative reports on the statuses available in the system. Because it is seed data, querying is far more common than updating.

The most common retrieval filters on the unique index columns and on the active status:

• SELECT status_type_code, phase_indicator, active_flag, display_sequence
  FROM   xnp.xnp_sv_status_types_b
  WHERE  active_flag = 'Y'
  ORDER  BY display_sequence;

• SELECT status_type_code, phase_indicator
  FROM   xnp.xnp_sv_status_types_b
  WHERE  status_type_code = :status_type_code
  AND    zd_edition_name = :edition_name;

Reporting use cases include joining to XNP_SV_SOA to determine the current and previous status of subscription versions, and joining to XNP_SV_STATUS_TYPES_TL to obtain translated status descriptions. Administrators may query INITIAL_FLAG and INITIAL_FLAG_ENFORCE_SEQ to verify sequencing rules, although the metadata notes these columns are not used.

Related Objects

The following objects are most significant in relation to this table:

• XNP.XNP_SV_SOA — references this table through STATUS_TYPE_CODE and PREV_STATUS_TYPE_CODE, linking subscription version statuses to SOA records.
• XNP.XNP_SV_STATUS_TYPES_TL — the translation table, joined on STATUS_TYPE_CODE, providing language-specific descriptions.
• XNP.XNP_SV_STATUS_TYPES_V — a view that exposes the valid statuses assigned to a SOA subscription version.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for hosted environments.
• Index XNP_SV_STATUS_TYPES_B_U1 — the unique index on STATUS_TYPE_CODE and ZD_EDITION_NAME that the user searched for.

These relationships make XNP_SV_STATUS_TYPES_B a foundational reference object for the XNP subledger subscription status model.