Search Results oke_object_attributes_b




Overview
Explore in AI Chat

Overview

OKE_OBJECT_ATTRIBUTES_B is a foundational metadata table in the Oracle EBS Project Contracts (OKE) module. It stores the definition of contract attributes—the discrete data elements that describe contract objects such as contract headers, contract lines, deliverables, and funding records. Rather than holding transactional contract data itself, this table acts as a registry or catalog that describes which attributes exist on each database object, their data types, and how they are exposed through security rules, queries, views, and forms. It is the backbone of the configurable, extensible attribute framework that lets Project Contracts support customer-specific and industry-specific contract fields without schema changes.

From a Data Vault modeling perspective, the relationship structure suggests this object leans toward a hub. Its primary key, OKE_OBJECT_ATTRIBUTES_PK, is composed of two business-identifying columns (DATABASE_OBJECT_NAME and ATTRIBUTE_CODE), and the table is referenced by dependent access-rule tables. The self-referencing foreign key on DATABASE_OBJECT_NAME and PARENT_ATTRIBUTE_CODE indicates an internal hierarchy, while downstream objects reference it as a lookup source, consistent with hub behavior.

Key Information Stored

The table's documented columns (15 total) capture both the identity and the behavioral characteristics of each attribute definition. The most significant columns are:

  • DATABASE_OBJECT_NAME — Identifies the secured business object (for example, a contract header or line) to which the attribute belongs. This column participates in the primary key and in the self-referencing foreign key.
  • ATTRIBUTE_CODE — The unique code identifying a specific attribute within its object. Together with DATABASE_OBJECT_NAME, it forms the composite primary key OKE_OBJECT_ATTRIBUTES_PK.
  • DATATYPE — Defines the attribute's data type, guiding validation and display behavior.
  • SECURABLE_FLAG — Indicates whether the attribute can be secured through the access-rule framework.
  • QUERYABLE_FLAG — Marks attributes that are exposed for query and reporting purposes.
  • VIEW_COLUMN_FLAG — Determines whether the attribute is surfaced as a column in a database view.
  • FORM_ITEM_FLAG — Controls whether the attribute appears as a form item in the contracts user interface.
  • ATTRIBUTE_GROUP_CODE — Groups related attributes together for presentation and organization.
  • PARENT_ATTRIBUTE_CODE — Establishes a hierarchical or dependent relationship to another attribute, enabling nested attribute definitions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS auditing columns capturing who created and last modified each row and when.
  • ZD_EDITION_NAME — The edition column supporting Online Patching in EBS 12.2.2.

The unique index OKE_OBJECT_ATTRIBUTES_U1 spans DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, and ZD_EDITION_NAME, confirming the business key while accommodating multi-edition storage. Note there is no separate surrogate key column; the primary key is the business key itself.

Common Use Cases and Queries

Typical use cases include discovering which attributes exist for a given contract object, determining which attributes are securable or queryable, and building metadata-driven reports and integrations. Reporting queries frequently join this table to access-rule tables to determine which attributes are protected.

  • Listing all attributes for a contract object: SELECT ATTRIBUTE_CODE, DATATYPE, ATTRIBUTE_GROUP_CODE FROM OKE_OBJECT_ATTRIBUTES_B WHERE DATABASE_OBJECT_NAME = :object_name;
  • Identifying securable and queryable attributes: SELECT ATTRIBUTE_CODE FROM OKE_OBJECT_ATTRIBUTES_B WHERE SECURABLE_FLAG = 'Y' AND QUERYABLE_FLAG = 'Y';
  • Resolving parent-child attribute hierarchies: SELECT CHILD.ATTRIBUTE_CODE, PARENT.ATTRIBUTE_CODE PARENT_CODE FROM OKE_OBJECT_ATTRIBUTES_B CHILD, OKE_OBJECT_ATTRIBUTES_B PARENT WHERE CHILD.PARENT_ATTRIBUTE_CODE = PARENT.ATTRIBUTE_CODE;
  • Auditing configuration changes: filter on LAST_UPDATE_DATE to track recently added or modified attribute definitions.

Related Objects

Several dependent objects reference OKE_OBJECT_ATTRIBUTES_B, and the primary key joins outward to the security framework:

  • OKE_COMPILED_ACCESS_RULES — Joins on SECURED_OBJECT_NAME and ATTRIBUTE_CODE; stores compiled access rules governing secured attributes.
  • OKE_K_ACCESS_RULES — Joins on SECURED_OBJECT_NAME and ATTRIBUTE_CODE; holds the key access-rule definitions for secured objects.
  • OKE_OBJECT_ATTRIBUTES_B (self-reference) — Joins on DATABASE_OBJECT_NAME and PARENT_ATTRIBUTE_CODE, enabling hierarchical attribute relationships.

Together, these objects form the metadata and security layer that makes the Project Contracts attribute model configurable, reportable, and secure across Oracle EBS 12.1.1 and 12.2.2.