Search Results jdr_components_n2

Overview

APPLSYS.JDR_COMPONENTS is a seed data table within the Oracle E-Business Suite Applications Foundation schema (APPLSYS), registered under the FND design data namespace as FND.JDR_COMPONENTS. The table stores component-level definitions associated with JDR (Java Development Runtime / Oracle Applications development framework) documents, providing the structural metadata that describes how individual components are organized, referenced, and extended within a given document. Its physical home is the APPS_TS_SEED tablespace, a location reserved for Oracle-supplied seed data rather than transactional or user-maintained content, which underscores that rows in this table are typically delivered by Oracle rather than created by end users.

Oracle classifies the object as for Oracle Internal Use Only and states that access to Oracle applications data through this object is unsupported except from standard Oracle Applications programs. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone rather than a hub, link, or satellite, since no foreign-key relationships are enforced inward through the documented schema; the single documented outgoing reference (COMP_ID → IEO_SVR_COMPS) suggests a soft relationship that could be modeled as a link candidate if normalization were attempted.

Key Information Stored

The table contains eleven documented columns in the 12.2.2 physical schema. The composite primary key, JDR_COMPONENTS_PK, is formed by COMP_DOCID and COMP_SEQ, establishing the document identifier and the sequence position of each component within that document. A second unique index, JDR_COMPONENTS_U1, covers COMP_DOCID, COMP_SEQ, and ZD_EDITION_NAME, which acts as the edition-aware business-key candidate in multitenant or editioned environments.

• COMP_DOCID (NUMBER, 10) — Identifier of the parent JDR document to which the component belongs.
• COMP_SEQ (NUMBER) — Ordinal sequence of the component within the document.
• COMP_LEVEL (NUMBER) — Hierarchical depth or nesting level of the component.
• COMP_GROUPING (VARCHAR2, 30) — Logical grouping label used to cluster related components.
• COMP_ELEMENT (VARCHAR2, 40) — The element name, indexed non-uniquely by JDR_COMPONENTS_N1.
• COMP_ID (VARCHAR2, 60) — Business identifier of the component, indexed by JDR_COMPONENTS_N2 and referencing IEO_SVR_COMPS.
• COMP_REF (VARCHAR2, 255) — Reference pointer resolved by the component at runtime.
• COMP_EXTENDS (VARCHAR2) — Declaration of the component this entry extends or inherits from.
• COMP_USE (VARCHAR2, 510) — Usage directive governing how the component is applied.
• COMP_COMMENT (VARCHAR2, 4000) — Free-text documentation or annotation for the component.
• ZD_EDITION_NAME — Edition discriminator supporting Oracle EBS 12.2 online patching and edition-based redefinition.

Common Use Cases and Queries

The table is primarily consumed by Oracle's internal JDR and Applications framework programs rather than by end-user reporting. Typical diagnostic queries retrieve the ordered component list for a given document:

• Retrieve all components for a document: SELECT COMP_SEQ, COMP_LEVEL, COMP_ELEMENT, COMP_ID FROM APPLSYS.JDR_COMPONENTS WHERE COMP_DOCID = :docid ORDER BY COMP_SEQ;
• Locate components by business identifier: SELECT COMP_DOCID, COMP_SEQ, COMP_REF FROM APPLSYS.JDR_COMPONENTS WHERE COMP_ID = :id;
• Find inherited or extended components: SELECT COMP_DOCID, COMP_SEQ, COMP_EXTENDS FROM APPLSYS.JDR_COMPONENTS WHERE COMP_EXTENDS IS NOT NULL;

Reporting use cases include auditing document composition, tracing component hierarchies by COMP_LEVEL, and comparing editioned rows across ZD_EDITION_NAME values to validate online-patching outcomes.

Related Objects

• APPLSYS.IEO_SVR_COMPS — Referenced by COMP_ID; the primary component registry joined for component master data.
• APPS.JDR_COMPONENTS — The APPS-layer synonym or view exposing the same data to application code.
• JDR_COMPONENTS_PK — Primary key index on (COMP_DOCID, COMP_SEQ).
• JDR_COMPONENTS_U1 — Unique index on (COMP_DOCID, COMP_SEQ, ZD_EDITION_NAME); the edition-aware business key.
• JDR_COMPONENTS_N1 / JDR_COMPONENTS_N2 — Non-unique indexes supporting access by COMP_ELEMENT and COMP_ID respectively.