Search Results comp_seq

Overview

The APPLSYS.JDR_COMPONENTS table is a core repository table within the Oracle E-Business Suite (EBS) architecture, specifically for the Oracle Application Framework (OA Framework or OAF). It stores metadata that defines the hierarchical structure and composition of OA Framework components, such as pages, regions, and beans. This table is integral to the runtime generation and rendering of the user interface. As indicated by the warning in the documentation, this is an internal Oracle table; direct access or modification is not supported except through standard Oracle Applications programs. Its data is seeded in the APPS_TS_SEED tablespace, underscoring its foundational role in the application.

Key Information Stored

The table's structure captures the parent-child relationships and attributes of UI components. The primary key is a composite of COMP_DOCID and COMP_SEQ. Key columns include:

• COMP_DOCID: A foreign key linking the component to its parent document or definition in related metadata tables (e.g., JDR_DOCUMENTS).
• COMP_SEQ: A sequence number that, with COMP_DOCID, uniquely identifies a row and often dictates the order of components.
• COMP_LEVEL: Indicates the nesting level of the component within the hierarchy.
• COMP_ELEMENT: The type of the UI component (e.g., a specific bean or region type).
• COMP_ID: The unique identifier (name) of the component instance within its document.
• COMP_REF: Used for referencing other components or definitions.
• COMP_EXTENDS and COMP_USE: Support inheritance and reuse of component definitions.
• COMP_COMMENT: Can store descriptive notes or metadata about the component.

Common Use Cases and Queries

This table is primarily accessed by the OA Framework engine. For diagnostic or analysis purposes, developers may query it to understand page structure or debug rendering issues. A fundamental query retrieves the component tree for a specific document:

SELECT COMP_LEVEL, LPAD(' ', (COMP_LEVEL-1)*2) || COMP_ELEMENT AS INDENTED_ELEMENT, COMP_ID, COMP_REF FROM APPLSYS.JDR_COMPONENTS WHERE COMP_DOCID = &DOCUMENT_ID ORDER BY COMP_DOCID, COMP_SEQ;

Another common pattern is investigating component usage or inheritance by querying the COMP_USE or COMP_EXTENDS columns. Reporting might involve joining with JDR_DOCUMENTS to map components to specific application pages or modules.

Related Objects

Based on the provided dependency information, the primary related object is the synonym APPS.JDR_COMPONENTS, which provides the standard access point for application code. The table's structure implies a critical relationship with JDR_DOCUMENTS (or similar), where COMP_DOCID is a foreign key, although this specific reference is not listed in the provided excerpt. The defined indexes (JDR_COMPONENTS_U1, _N1, _N2) optimize access via the primary key, COMP_ELEMENT, and COMP_ID, which are frequent lookup paths for the framework.