Search Results jdr_attributes

Overview

The JDR_ATTRIBUTES table is a core repository table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It is owned by the APPLSYS schema and is integral to the Oracle Application Framework's (OA Framework) metadata-driven architecture. This table stores the detailed attribute-level metadata for UI components and other objects defined within the Oracle Application Development Framework (Oracle ADF) repository. It functions as a child table to JDR_COMPONENTS, holding the specific properties and configuration settings that define the behavior, appearance, and data binding of individual UI elements, such as items, regions, and beans, within the framework.

Key Information Stored

The table's structure is designed to store attribute metadata in a normalized format, linked to its parent component. The primary key, JDR_ATTRIBUTES_PK, consists of the columns ATT_COMP_DOCID, ATT_COMP_SEQ, and ATT_SEQ, establishing a precise hierarchical relationship. Key columns include ATT_COMP_DOCID and ATT_COMP_SEQ, which together form a foreign key reference to a specific component in the JDR_COMPONENTS table. The ATT_SEQ column uniquely sequences multiple attributes belonging to the same component. Other critical columns typically store the attribute's name (e.g., ATT_NAME) and its corresponding value (e.g., ATT_VALUE), which defines the component's runtime configuration. The table may also include columns for storing the attribute's data type and other metadata necessary for the OA Framework rendering engine.

Common Use Cases and Queries

This table is primarily accessed for diagnostic, customization, and reporting purposes related to the OA Framework's metadata. A common use case involves investigating the properties of a specific UI component to understand its configuration or to identify the source of a behavioral issue. Developers and administrators may query this table to find all attributes set for a particular component or to locate components where a specific attribute has a given value. A sample query pattern is: SELECT att_name, att_value FROM apps.jdr_attributes WHERE att_comp_docid = <DOCUMENT_ID> AND att_comp_seq = <COMPONENT_SEQ> ORDER BY att_seq;. Direct data manipulation (DML) on this table is strongly discouraged outside of official patching or upgrade processes, as it can corrupt the application's metadata integrity.

Related Objects

The JDR_ATTRIBUTES table has a fundamental dependency on the JDR_COMPONENTS table, as indicated by its primary key structure. The documented foreign key relationship is from JDR_ATTRIBUTES.(ATT_COMP_DOCID, ATT_COMP_SEQ) to JDR_COMPONENTS.(DOCID, COMP_SEQ). This relationship ensures every attribute is definitively associated with a parent component. The table is part of a broader metadata schema that includes related objects such as JDR_PATHS, JDR_ATTRIBUTE_VALUES, and potentially JDR_DOCUMENTS. These tables collectively manage the hierarchical structure, component definitions, and attribute data for the OA Framework repository.