Results for “seed_status_updateable_flag”

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

Overview

CSI_INSTANCE_STATUSES is a reference (lookup) table in the CSI – Install Base product schema of Oracle E-Business Suite, holding the master list of lifecycle statuses that can be assigned to an instance of an item in the Install Base. Each row defines a named status — such as an active, terminated, or pending state — together with the behavioral flags and effective-dating attributes that govern how the Install Base application processes instances carrying that status. The table is delivered with seeded rows and is exposed to administrators who may define additional, user-maintained statuses, as indicated by the SEEDED_FLAG and UPDATEABLE_FLAG columns.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as hub-leaning. That is a modeling suggestion rather than a physical property: INSTANCE_STATUS_ID behaves as the durable business key around which descriptive attributes such as NAME, DESCRIPTION, and the various control flags are carried, and which is referenced by multiple transactional and interface tables.

Key Information Stored

The table is defined with 37 documented columns in ETRM 12.2.2. The most significant are:

• INSTANCE_STATUS_ID — surrogate primary key, enforced by the unique index CSI_INSTANCE_STATUSES_PK. The composite unique index CSI_INSTANCE_STATUSES_U01 (INSTANCE_STATUS_ID, ZD_EDITION_NAME) is the documented business-key candidate in an online-patching (Edition) context.
• NAME and DESCRIPTION — the user-visible status name and its explanation.
• UPDATEABLE_FLAG and SEEDED_FLAG — control whether a status is user-maintainable and whether it was shipped by Oracle.
• TERMINATED_FLAG — identifies terminal statuses marking an instance as ended.
• STATUS_CHANGE_ALLOWED_FLAG — governs whether an instance in this status may transition to another status.
• INCIDENT_ALLOWED_FLAG and SERVICE_ORDER_ALLOWED_FLAG — determine whether service requests and service orders may be raised against instances in this status.
• SEED_STATUS_UPDATEABLE_FLAG — controls whether the seeded status value itself may be modified.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating range for the status definition.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-organization data security.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the standard EBS DFF (descriptive flexfield) container.
• MIGRATED_FLAG, ZD_EDITION_NAME, OBJECT_VERSION_NUMBER — migration indicator, online-patching edition label, and optimistic-locking version.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The principal use case is joining statuses to installed item instances to report lifecycle state. A typical query returns the status description alongside the instance:

SELECT ii.instance_id, s.name, s.description
FROM csi_item_instances ii, csi_instance_statuses s
WHERE ii.instance_status_id = s.instance_status_id;

Validation queries confirm which statuses permit changes or termination — for example, filtering on STATUS_CHANGE_ALLOWED_FLAG = 'Y' before proposing a transition, or on SERVICE_ORDER_ALLOWED_FLAG = 'Y' when deciding whether service orders can be raised. Effective-dating logic uses START_DATE_ACTIVE and END_DATE_ACTIVE to restrict the status list to currently valid values. Administrators reviewing the seeded set can query on SEEDED_FLAG and UPDATEABLE_FLAG to distinguish Oracle-provided statuses from customer-defined ones.

Related Objects

• CSI_ITEM_INSTANCES — the primary transactional consumer; joined on CSI_ITEM_INSTANCES.INSTANCE_STATUS_ID = CSI_INSTANCE_STATUSES.INSTANCE_STATUS_ID. This is the dominant relationship of the table.
• CSI_T_TXN_LINE_DETAILS — transaction line details referencing INSTANCE_STATUS_ID.
• CSI_INSTANCE_INTERFACE — the open interface that loads instance data and resolves statuses via INSTANCE_STATUS_ID.
• FND_SECURITY_GROUPS — referenced by CSI_INSTANCE_STATUSES.SECURITY_GROUP_ID, providing the security group context for the lookup rows.

Collectively these relationships confirm the table's role as a stable reference hub supporting instance, transaction, and interface data across the Install Base module.