Search Results jdr_components




Overview
Explore in AI Chat

Overview

The JDR_COMPONENTS table is a core repository table within the Oracle E-Business Suite Application Object Library (FND). It is owned by the APPLSYS schema and is fundamental to the storage and management of declarative application metadata, specifically for the Oracle Application Framework (OA Framework or OAF) components. This table stores the detailed, hierarchical structure of individual UI components that constitute OA Framework pages, such as regions, items, buttons, and tables. Its primary role is to serve as the persistent storage layer for the component definitions that are rendered at runtime by the OA Framework engine, enabling the declarative development and customization model central to EBS.

Key Information Stored

The table's structure is designed to store component metadata in a normalized, hierarchical format. The primary key, JDR_COMPONENTS_PK, is composed of two columns: COMP_DOCID and COMP_SEQ. The COMP_DOCID column is a foreign key that links the component to its parent document or page definition, typically stored in the JDR_DOCUMENTS table. The COMP_SEQ column uniquely identifies a component instance within that specific document. While the provided ETRM excerpt does not list all columns, standard implementation knowledge indicates other critical columns include those storing the component's internal name, type (e.g., region, item), property values, and a reference to its parent component, thereby constructing the complete page hierarchy.

Common Use Cases and Queries

This table is primarily accessed for diagnostic, reporting, and advanced customization purposes. Common scenarios include analyzing the structure of a specific OA Framework page to understand its composition or to troubleshoot rendering issues. Developers and administrators may query it to list all components on a page, find components of a specific type, or trace property inheritance. A typical query pattern involves joining with JDR_DOCUMENTS to filter by a known page path or name.

  • Sample Query: To find all components for a specific document, one would use: SELECT comp_seq, component_name, component_type FROM apps.jdr_components WHERE comp_docid = (SELECT docid FROM apps.jdr_documents WHERE doc_name = 'XX_CUSTOM_PAGE');
  • Use Case: Identifying all personalized items on a page by correlating data with the FND_ICX_CUSTOM_PARAMS or similar personalization tables.

Related Objects

The JDR_COMPONENTS table exists within a tightly coupled schema of OA Framework metadata tables. As indicated by its primary key structure, it has a direct and essential relationship with the JDR_DOCUMENTS table via the COMP_DOCID column. The JDR_DOCUMENTS table stores the root document definition, while JDR_COMPONENTS stores its constituent parts. Other closely related tables in the APPLSYS schema include JDR_ATTRIBUTES (which stores property values for components), JDR_PATHS (for document location), and JDR_MAO_DEFINITIONS. Any customization or patch delivered for OA Framework pages will result in DML operations against this table and its related objects.