Results for “oke_attribute_flowdowns”

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

Overview

OKE_ATTRIBUTE_FLOWDOWNS is a reference table owned by the OKE schema in Oracle E-Business Suite, delivered with the Project Contracts module. Its documented purpose is to store the mappings between contract attributes and business areas. In practical terms, the table defines which attribute groups are available within a given business area during contract authoring and management, acting as configuration data that drives the attribute flowdown behavior in Project Contracts.

The table is documented as standalone in the mined Data Vault classification, meaning no foreign key relationships to parent tables were detected during heuristic analysis. From a modeling perspective, this suggests treating OKE_ATTRIBUTE_FLOWDOWNS as a reference or lookup structure rather than a hub or link, though its composite uniqueness pattern (business area plus attribute group) also gives it characteristics of a link between business areas and attribute group definitions. Either interpretation is reasonable; the standalone classification is a heuristic, not an absolute statement about the design.

Because the table is configuration-oriented, records are typically low-volume and change infrequently. They are seeded or maintained through the Project Contracts setup, and their correctness directly affects which contract attributes are presented to users, validated, and flowed down into contract lines.

Key Information Stored

The documented physical schema at 12.2.2 contains eight columns. The most significant are the three business attributes that together form the primary key OKE_ATTRIBUTE_FLOWDOWNS_PK and the unique index OKE_ATTRIBUTE_FLOWDOWNS_U1:

• BUSINESS_AREA_CODE — identifies the Project Contracts business area or functional area within which the attribute flowdown applies.
• ATTRIBUTE_GROUP_TYPE — the type (or category) of the attribute group being mapped.
• ATTRIBUTE_GROUP_CODE — the specific attribute group being flowed down within the business area and group type.

These three columns constitute both the primary key and the unique index, so the surrogate primary key and the business key are one and the same here: (BUSINESS_AREA_CODE, ATTRIBUTE_GROUP_TYPE, ATTRIBUTE_GROUP_CODE). There is no separate sequence-generated identifier documented.

The remaining five columns are standard Oracle EBS audit attributes maintained automatically by the application: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These record who created and last modified each row and support audit reporting. No descriptive or effective-dating columns are documented, so the table appears to hold only the mapping identifiers and audit trail.

Common Use Cases and Queries

Typical uses center on verifying and reporting the configured mappings. A common query lists all attribute groups for a business area:

• SELECT BUSINESS_AREA_CODE, ATTRIBUTE_GROUP_TYPE, ATTRIBUTE_GROUP_CODE FROM OKE.OKE_ATTRIBUTE_FLOWDOWNS WHERE BUSINESS_AREA_CODE = :area_code;
• A lookup by full business key uses the unique index: WHERE BUSINESS_AREA_CODE = :a AND ATTRIBUTE_GROUP_TYPE = :t AND ATTRIBUTE_GROUP_CODE = :g;
• An audit query checks who last changed configuration: SELECT LAST_UPDATED_BY, LAST_UPDATE_DATE FROM OKE.OKE_ATTRIBUTE_FLOWDOWNS;

Reporting scenarios include validating setup during implementations, auditing configuration changes after upgrades from 12.1.1 to 12.2.2, and diagnosing why a particular attribute group is or is not appearing during contract entry. Comparing row counts and key values before and after an upgrade is a useful regression check.

Related Objects

No foreign keys were detected, so no officially dependent child tables are documented. Related objects are therefore inferred from the OKE Project Contracts domain and the meaning of the columns:

• OKE business area and attribute group definition tables referenced by the ATTRIBUTE_GROUP_CODE and ATTRIBUTE_GROUP_TYPE values.
• Project Contracts attribute setup and contract line tables that consume the flowdown configuration.
• Standard audit and descriptive flexfield views that expose the columns of this table.
• The unique index OKE_ATTRIBUTE_FLOWDOWNS_U1 and primary key OKE_ATTRIBUTE_FLOWDOWNS_PK, which enforce mapping uniqueness.

Because relationships are implicit rather than enforced, joins are performed by matching BUSINESS_AREA_CODE, ATTRIBUTE_GROUP_TYPE, and ATTRIBUTE_GROUP_CODE to the corresponding reference definitions in the OKE schema.