Search Results oke_object_attributes_u1

Overview

OKE.OKE_OBJECT_ATTRIBUTES_B is a seeded metadata table in the Oracle E-Business Suite Contracts (OKE) module. It stores the definitive catalogue of contract attributes that the application uses to describe, secure, and control the behavior of contract objects. Each row defines a single attribute belonging to a specific database object (for example, a contract header, line, or party), and these attributes are subsequently grouped into attribute groups for reuse in security access rules and flow down matrix definitions.

Because the table is seeded during installation and patched by Oracle, its contents are not user-definable. Records exist primarily to drive runtime configuration — determining whether an attribute is securable, queryable, exposed as a view column, or rendered as a form item. The table resides in the APPS_TS_SEED tablespace, consistent with its role as reference and setup data rather than transactional data.

From a Data Vault modeling perspective, the metadata classifies this object as hub-leaning. The composite key of DATABASE_OBJECT_NAME and ATTRIBUTE_CODE identifies each unique attribute, while descriptive flags and grouping codes behave as satellite-style attributes attached to that hub. This classification is a modeling suggestion only; in Oracle EBS the table functions as a conventional reference table with a unique primary key.

Key Information Stored

The primary key, OKE_OBJECT_ATTRIBUTES_PK, is defined on DATABASE_OBJECT_NAME and ATTRIBUTE_CODE. Together these columns form the natural business key of the seeded catalogue rather than a synthetic surrogate. DATABASE_OBJECT_NAME identifies the contract object to which the attribute belongs, and ATTRIBUTE_CODE names the attribute itself.

A second unique index, OKE_OBJECT_ATTRIBUTES_U1 (DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, ZD_EDITION_NAME), extends the same business key with the edition name in 12.2.2, reflecting the Editioning architecture used for online patching. The user's search for oke_object_attributes_u1 therefore resolves to this uniqueness constraint.

The most significant descriptive columns are:

• DATATYPE — the data type of the attribute, governing how values are interpreted at runtime.
• SECURABLE_FLAG — indicates whether the attribute participates in security access rules.
• QUERYABLE_FLAG — indicates whether the attribute can be exposed in queries and search criteria.
• VIEW_COLUMN_FLAG — indicates whether the attribute appears as a column in contract views.
• FORM_ITEM_FLAG — indicates whether the attribute is rendered as a form item.
• ATTRIBUTE_GROUP_CODE — the group to which related attributes are assigned for reuse.
• PARENT_ATTRIBUTE_CODE — the internal code of a parent attribute, enabling hierarchical attribute relationships.

Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide auditability for seed and patch operations.

Common Use Cases and Queries

The table is most frequently queried to understand the attribute model available for contract security and flow down configuration. A typical query retrieves the attributes belonging to a specific database object:

SELECT ATTRIBUTE_CODE, DATATYPE, SECURABLE_FLAG, QUERYABLE_FLAG, ATTRIBUTE_GROUP_CODE FROM OKE.OKE_OBJECT_ATTRIBUTES_B WHERE DATABASE_OBJECT_NAME = :object_name;

Reporting scenarios include auditing which attributes are securable, listing all attributes within a group, or tracing parent-child attribute hierarchies via PARENT_ATTRIBUTE_CODE. Join patterns with access-rule tables identify which secured object names are actually enforced.

Related Objects

The following objects reference or depend on OKT_OBJECT_ATTRIBUTES_B:

• OKE.OKE_OBJECT_ATTRIBUTES_B — a self-referencing foreign key on DATABASE_OBJECT_NAME supports hierarchical attribute definitions.
• OKE.OKE_COMPILED_ACCESS_RULES — SECURED_OBJECT_NAME references this table, linking compiled rules to the attributes they protect.
• OKE.OKE_K_ACCESS_RULES — SECURED_OBJECT_NAME references this table, providing the access-rule definition source.
• OKE.OKE_OBJECT_ATTRIBUTES_U1 — the unique index enforcing the business key, including ZD_EDITION_NAME in 12.2.2.
• OKE.OKE_OBJECT_ATTRIBUTES_N1 — a non-unique index on DATABASE_OBJECT_NAME and ATTRIBUTE_GROUP_CODE supporting attribute-group lookups.

These relationships establish the table as a central reference object within the OKE security and flow down infrastructure, and confirm that changes to its seeded content propagate into access-rule evaluation.