Results for “oke_attribute_flowdowns_u1”

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

Overview

OKE.OKE_ATTRIBUTE_FLOWDOWNS is a reference and setup table within the Oracle E-Business Suite Oracle Contracts (OKE) module. It defines the flowdown rules that govern how attribute groups propagate through the contracting hierarchy, enabling the application to determine which attribute groups apply within a given business area and attribute group type. The table resides in the APPS_TS_SEED tablespace, which is characteristic of seeded setup and reference data rather than high-volume transactional content.

The object is documented as VALID in ETRM 12.2.2, with an identical structure supported across 12.1.1 and 12.2.2. It carries the FND Design Data identifier OKE.OKE_ATTRIBUTE_FLOWDOWNS and is classified by heuristic analysis of its foreign-key structure as standalone. In Data Vault modeling terms, this suggests treating the object as a reference or lookup structure rather than a classic hub, link, or satellite; its three-part business key makes it a natural candidate for a reference table whose rows are reused across multiple contracting contexts rather than accumulating transactional history.

Key Information Stored

The table contains eight documented columns. The three leading columns form both the primary key and the unique business-key candidate:

• BUSINESS_AREA_CODE (VARCHAR2, 30) — identifies the business area to which the flowdown rule applies, scoping the rule to a functional domain within Contracts.
• ATTRIBUTE_GROUP_TYPE (VARCHAR2, 30) — classifies the category or type of the attribute group being flowed down.
• ATTRIBUTE_GROUP_CODE (VARCHAR2, 30) — the specific attribute group identifier subject to the flowdown rule.

These three columns together constitute the primary key OKE_ATTRIBUTE_FLOWDOWNS_PK and are also defined by the unique index OKE_ATTRIBUTE_FLOWDOWNS_U1 (BUSINESS_AREA_CODE, ATTRIBUTE_GROUP_TYPE, ATTRIBUTE_GROUP_CODE). The remaining five columns are standard Oracle EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These track who inserted or last modified each row, when, and through which login session, providing the audit trail expected of all seeded EBS setup tables.

Notably, the table has no surrogate numeric primary key; the business key itself is the primary key, which reinforces its character as a controlled reference list rather than an entity with independent identity.

Common Use Cases and Queries

Typical usage centers on validating or reporting which attribute groups flow down for a given business area and group type. A common query pattern retrieves all flowdown rules for a specific business area:

• SELECT ATTRIBUTE_GROUP_TYPE, ATTRIBUTE_GROUP_CODE FROM OKE.OKE_ATTRIBUTE_FLOWDOWNS WHERE BUSINESS_AREA_CODE = :business_area;
• Reconciling seeded flowdown definitions against attribute groups actually configured within Contracts.
• Auditing changes to setup data using the CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE columns.
• Supporting migration or comparison scripts between 12.1.1 and 12.2.2 environments, verifying that flowdown rules remain consistent across releases.

Because the table is seeded, most administration is performed through the Contracts setup user interface; direct DML should be avoided and limited to controlled extracts or reporting.

Related Objects

The ETRM dependency data indicates that OKE.OKE_ATTRIBUTE_FLOWDOWNS does not reference any other database object through foreign keys, and it is referenced only by its own shadow object OKE_ATTRIBUTE_FLOWDOWNS# within the OKE schema. The logical join is therefore driven by business columns rather than enforced foreign keys. In practice, it is correlated with attribute group definition and attribute group type tables in the OKE schema:

• OKE_ATTRIBUTE_GROUPS — joined on ATTRIBUTE_GROUP_CODE to resolve the descriptive details of each flowed-down group.
• OKE_ATTRIBUTE_GROUP_TYPES — joined on ATTRIBUTE_GROUP_TYPE to resolve the type description.
• OKE_ATTRIBUTE_GROUP_USAGES — describes where attribute groups are applied, providing context for flowdown behavior.
• OKE_ATTRIBUTE_GROUP_COLUMNS — defines the individual attributes contained within each group.
• OKE_BUSINESS_AREAS (or the corresponding business-area reference used by Contracts) — joined on BUSINESS_AREA_CODE to resolve the business area name and context.
• OKE_ATTRIBUTE_FLOWDOWNS# — the shadow-dependent object automatically maintained by Oracle for the base table.

These relationships should be treated as logical associations rather than referential constraints, since the documented dependency listing shows no inbound or outbound foreign keys.