Search Results comp_seq

Overview

JDR_COMPONENTS is a transactional configuration table owned by the APPLSYS schema within the FND (Application Object Library) product of Oracle E-Business Suite. It is part of the JDR (Java Development Runtime / "JDeveloper Repository") family used by Oracle Application Framework (OAF) and the Oracle EBS diagnostics and Java runtime infrastructure. The table records the constituent components that make up a component document, capturing hierarchical and grouping metadata for each component element that participates in a given document instance.

The physical schema in ETRM 12.2.2 documents eleven columns. The primary key is JDR_COMPONENTS_PK, defined on (COMP_DOCID, COMP_SEQ). A unique index, JDR_COMPONENTS_U1, covers (COMP_DOCID, COMP_SEQ, ZD_EDITION_NAME), which is the business-key candidate when the edition name participates in uniqueness. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests the table is best modeled as its own hub or as a self-contained component registry rather than as a satellite dependent on another hub. The only documented outgoing foreign key is COMP_ID → IEO_SVR_COMPS, indicating that each component references a defined component in the IEO server component catalog.

Key Information Stored

The most significant columns documented for JDR_COMPONENTS are:

• COMP_DOCID — The component document identifier; part of the composite primary key and the leading column of both the PK and the unique index. It is the primary selector in most application queries.
• COMP_SEQ — The sequence number for a component within its document; the second half of the composite primary key. Together with COMP_DOCID it uniquely identifies a row.
• ZD_EDITION_NAME — The edition name associated with the row. It appears only in the unique index JDR_COMPONENTS_U1 and supports edition-based redefinition (EBR) in 12.2.x; it is not part of the primary key.
• COMP_ID — The foreign key to IEO_SVR_COMPS, linking the row to the registered component definition.
• COMP_LEVEL — The hierarchical level of the component, supporting nested component structures.
• COMP_GROUPING — The logical grouping to which the component belongs.
• COMP_ELEMENT — The component element name or identifier.
• COMP_REF — A reference value for the component.
• COMP_EXTENDS — Indicates the component this entry extends, supporting inheritance.
• COMP_USE — The usage classification of the component.
• COMP_COMMENT — Free-text descriptive commentary for the component entry.

Common Use Cases and Queries

Because the user searched for "comp_docid," the dominant access pattern is retrieval of all components for a given component document. Typical queries include:

• Listing all components in document order: SELECT COMP_SEQ, COMP_ID, COMP_LEVEL, COMP_GROUPING FROM APPLSYS.JDR_COMPONENTS WHERE COMP_DOCID = :docid ORDER BY COMP_SEQ;
• Joining to the component catalog to resolve names: SELECT c.COMP_DOCID, c.COMP_SEQ, s.COMP_ID FROM APPLSYS.JDR_COMPONENTS c, APPLSYS.IEO_SVR_COMPS s WHERE c.COMP_ID = s.COMP_ID AND c.COMP_DOCID = :docid;
• Reporting on hierarchy depth by counting distinct COMP_LEVEL values per document.
• Edition-aware lookups that include ZD_EDITION_NAME to isolate rows for a specific edition in 12.2.x environments.

Administrators and developers use these queries during diagnostics, OAF page analysis, and impact assessment before modifying component definitions.

Related Objects

• IEO_SVR_COMPS — The component catalog referenced by JDR_COMPONENTS.COMP_ID. This is the only documented foreign-key target.
• JDR_COMPONENTS_PK — The primary-key constraint (COMP_DOCID, COMP_SEQ).
• JDR_COMPONENTS_U1 — The unique index on (COMP_DOCID, COMP_SEQ, ZD_EDITION_NAME).
• JDR_COMPONENT_DOCS — The companion document table that provides the COMP_DOCID parent context.
• JDR_PATHS / JDR_ATTRIBUTES — Related JDR repository tables that commonly join on COMP_DOCID for full document reconstruction.

These objects together form the JDR repository layer used by the FND diagnostics and OAF runtime.