Results for “oke_termcond_flowdowns”

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

Overview

OKE_TERMCOND_FLOWDOWNS is a reference configuration table in the OKE (Project Contracts) module of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to hold flowdown settings for terms and conditions by term type. In contract authoring, flowdown refers to the propagation of clauses and provisions from a parent agreement — such as a master services agreement, a prime contract, or a government flowdown clause set — into subordinate contracts, subcontracts, or project-level documents. This table therefore records, at the level of a defined term type within a business area, whether and how such flowdown behavior is applied.

The documented schema is compact, comprising seven columns. The primary key is OKE_TERMCOND_FLOWDOWNS_PK, defined on the composite of BUSINESS_AREA_CODE and TERM_TYPE_CODE. A unique index, OKE_TERMCOND_FLOWDOWNS_U1, is defined on the same two columns. From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. That classification is a modeling suggestion only: because no parent tables are registered through foreign keys, the object is best treated as an independent reference or configuration set rather than as a hub, link, or satellite within a conventional Data Vault model. Its grain is one row per business area and term type combination.

Key Information Stored

The table is narrow and its business content is concentrated in its composite key. The most significant columns are:

• BUSINESS_AREA_CODE — The business area identifier that scopes the flowdown setting. This is the first component of the composite primary key and of the unique index, and it partitions configuration between operating units, organizations, or functional areas that maintain separate contract term behavior.
• TERM_TYPE_CODE — The term type to which the flowdown setting applies. This is the second component of the composite primary key and unique index, and it is the column most commonly used as a filter in queries, since it names the specific category of term or clause governed by the record.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording when and by which application user the configuration row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification timestamp, the responsible user, and the login context of that change.

No separate surrogate key column is documented; the business key itself, BUSINESS_AREA_CODE plus TERM_TYPE_CODE, serves as the primary key. The table carries no descriptive or attribute columns beyond the audit set, which indicates that flowdown behavior is expressed through the existence and configuration of the row itself rather than through a wide set of flags.

Common Use Cases and Queries

Typical usage centers on validating and reporting which term types have flowdown configured within a business area. A lookup by term type is the most frequent access path and is fully supported by the unique index:

• Retrieving all configured flowdowns for a given term type: SELECT business_area_code, term_type_code FROM oke.oke_termcond_flowdowns WHERE term_type_code = :p_term_type_code;
• Determining whether flowdown is enabled for a specific business area and term type pair: SELECT COUNT(*) FROM oke.oke_termcond_flowdowns WHERE business_area_code = :p_business_area_code AND term_type_code = :p_term_type_code;
• Producing an inventory of term types with flowdown settings, grouped for administrative review or reconciliation after a patch or upgrade.

Because the table holds configuration rather than transactional history, reporting is usually analytical rather than volume-driven. Analysts use it to reconcile the set of term types configured for flowdown against the term types actually referenced on contract terms, and to confirm that audit columns reflect the expected maintenance window following a setup change.

Related Objects

The metadata documents no foreign key relationships, and the heuristic classification is standalone. Consequently, the most meaningful related objects are those that share the same business keys or that belong to the broader OKE project contracts term and condition configuration area:

• OKE_TERM_TYPES (or the equivalent term type definition object in OKE) — the reference source of TERM_TYPE_CODE values used in this table.
• OKE_TERMS_AND_CONDITIONS and related term/clause definition tables — the clause catalog whose term types are governed by these flowdown settings.
• OKE_CONTRACTS and contract line or term association tables — the transactional contract records where flowdown behavior is applied.
• BUSINESS_AREA_CODE reference data, typically originating from organization or business area setup — the source of the second key component.

Any join to these objects is driven by TERM_TYPE_CODE and BUSINESS_AREA_CODE rather than by a declared foreign key, so query authors should apply the composite key explicitly and confirm value alignment against the respective reference sets.