Results for “to_chg_status_type_code”

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

Overview

OKE_CHG_STS_TYPE_FLOWS is a table in the OKE schema, belonging to the Oracle Project Contracts (OKE) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The table is documented in the ETRM repository as "Not in use" and carries a VALID status, meaning the object exists physically in the database but is not referenced by any active application flow logic in the delivered product. Its name suggests an intended role in defining permitted transitions between change status types — essentially a state-transition or workflow-routing definition for change orders and change status codes managed by Project Contracts.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. It has no foreign key dependencies on other tables and no dependents. In Data Vault terms, the structure suggests a link pattern: the composite primary key (CHG_STATUS_TYPE_CODE, TO_CHG_STATUS_TYPE_CODE) joins two status-type values on the same domain, forming a many-to-many relationship representing allowable "from" to "to" transitions. However, because the table is not populated or consumed by delivered functionality, this classification is a modeling suggestion rather than an operational fact.

Key Information Stored

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

• CHG_STATUS_TYPE_CODE — the source (from) change status type code, forming the first component of the primary key and the unique index.
• TO_CHG_STATUS_TYPE_CODE — the target (to) change status type code, forming the second component of the primary key and the unique index. Together with the source code, these two columns define the business key of the table.
• CREATE_NEW_VERSION_FLAG — a control flag indicating whether transitioning between the two status types should produce a new version of the underlying change record. This is the principal payload attribute distinguishing one transition rule from another.
• CREATION_DATE, CREATED_BY — standard WHO-column audit attributes recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO-column audit attributes recording the most recent modification and the session context of that modification.

The surrogate identity of the table is the composite primary key OKE_CHG_STS_TYPE_FLOWS_PK, mirrored by the unique index OKE_CHG_STS_TYPE_FLOWS_U1. No single-column surrogate key is documented; the business key and the primary key are identical.

Common Use Cases and Queries

Given the documented "Not in use" designation, no delivered Oracle EBS 12.1.1 or 12.2.2 concurrent program, form, or API reads or writes this table in standard functionality. Practical scenarios are therefore limited to diagnostics, custom extensions, and data-model audits. Typical queries include:

• Confirming the table is empty in a production instance: SELECT COUNT(*) FROM oke.oke_chg_sts_type_flows;
• Enumerating any custom transition rules that a customer extension may have inserted: SELECT chg_status_type_code, to_chg_status_type_code, create_new_version_flag FROM oke.oke_chg_sts_type_flows ORDER BY 1, 2;
• Auditing stale or manually inserted rows: SELECT * FROM oke.oke_chg_sts_type_flows WHERE last_update_date > :cutoff_date;
• Assessing upgrade impact prior to applying 12.1.1 to 12.2.2 patches, since unused tables are occasionally repurposed or dropped in later releases.

Any custom code that references OKE_CHG_STS_TYPE_FLOWS should be identified during technical upgrade assessments, as Oracle explicitly marks the object as not in use.

Related Objects

The Data Vault analysis returns a standalone classification, so no foreign key relationships are documented in either direction. Consequently, no child tables carry a foreign key to OKE_CHG_STS_TYPE_FLOWS, and the table itself references no parent. The following objects are worth examining as close thematic neighbours within the Project Contracts module, since they concern change status types and change management records:

• OKE_CHG_STATUS_TYPES — the master list of change status type codes referenced conceptually by CHG_STATUS_TYPE_CODE and TO_CHG_STATUS_TYPE_CODE.
• OKE_CHANGE_ORDERS — the transactional change order records whose status transitions this table was apparently intended to constrain.
• OKE_CHANGE_ORDER_TYPES — definitions of change order categories that may be associated with status flows.
• OKE_CONTRACTS — the Project Contracts header table to which change orders belong.
• OKE_K_APIS / OKE_CHANGE_ORDER_PUB — PL/SQL API packages that perform change order lifecycle operations and would have consumed transition rules had the table been implemented.

Because the object is documented as unused, join patterns and referential integrity assumptions should be validated against the actual customer data model before being relied upon.