Search Results comp_seq

Overview

APPLSYS.JDR_COMPONENTS is a seed-data table within the Oracle E-Business Suite Applications schema (APPLSYS). It stores the individual component definitions that make up Java Dependency Repository (JDR) documents, which drive the generation of Oracle EBS Java applet and forms runtime artifacts. Backed by the FND design data object FND.JDR_COMPONENTS and resident in the APPS_TS_SEED tablespace, the table holds reference metadata consumed by Oracle Applications infrastructure rather than transactional end-user data. It is explicitly marked Oracle Internal Use Only: Oracle Corporation does not support direct access from external programs, and reads should generally occur only from standard Oracle Applications code or controlled reporting queries.

Heuristically, the mined relationship structure classifies this object as standalone in Data Vault terms. Modelers may treat it as a reference/satellite-style table: its primary key is a composite of the document identifier (COMP_DOCID) and sequence number (COMP_SEQ), and it carries descriptive attributes describing each component. No parent foreign key drives the vault structure, although one outbound relationship is documented.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• COMP_DOCID — Numeric (10) identifier of the owning JDR document; first component of the composite primary key.
• COMP_SEQ — Numeric sequence position of the component within the document; second component of the primary key.
• COMP_LEVEL — Numeric depth or nesting level of the component.
• COMP_GROUPING — Character grouping label (30) used to organize components.
• COMP_ELEMENT — Character element name (40) participating in the JDR hierarchy.
• COMP_ID — Character identifier (60) of the component; the documented outbound foreign key points to IEO_SVR_COMPS.
• COMP_REF — Character reference string (255) linking the component to its target artifact.
• COMP_EXTENDS — Character inheritance indicator showing which component this one extends.
• COMP_USE — Character use declaration (510) describing how the component is consumed.
• COMP_COMMENT — Free-form comment (4000) providing descriptive context.
• ZD_EDITION_NAME — Edition identifier supporting Oracle's Editioning (EBR) feature in 12.2.x.

The composite primary key JDR_COMPONENTS_PK (COMP_DOCID, COMP_SEQ) is the surrogate identifier for each row. The unique index JDR_COMPONENTS_U1 (COMP_DOCID, COMP_SEQ, ZD_EDITION_NAME) acts as the business-key candidate, extending uniqueness across editions. Two non-unique indexes support retrieval: JDR_COMPONENTS_N1 on (COMP_ELEMENT, COMP_DOCID) and JDR_COMPONENTS_N2 on (COMP_ID, COMP_DOCID).

Common Use Cases and Queries

Typical use cases include auditing JDR document contents, verifying component sequencing, and diagnosing classloader or applet-generation issues in Oracle EBS 12.1.1 and 12.2.2. Because COMP_SEQ is the second element of the primary key, it is the natural ordering column for extracting a document's components in defined order. A standard retrieval pattern:

• SELECT COMP_DOCID, COMP_SEQ, COMP_LEVEL, COMP_ELEMENT, COMP_ID, COMP_REF FROM APPLSYS.JDR_COMPONENTS WHERE COMP_DOCID = :docid ORDER BY COMP_SEQ;
• Grouping analysis: SELECT COMP_GROUPING, COUNT(*) FROM APPLSYS.JDR_COMPONENTS GROUP BY COMP_GROUPING;
• Cross-reference lookup: join COMP_ID to IEO_SVR_COMPS to resolve server component definitions.

Reporting should remain read-only and account for the ZD_EDITION_NAME value in 12.2.x environments where editioning applies.

Related Objects

• APPLSYS.IEO_SVR_COMPS — target of the outbound foreign key on COMP_ID; resolves component identifiers to server component records.
• APPS.JDR_COMPONENTS — the APPS synonym/view layer exposing the table for supported application access.
• FND.JDR_COMPONENTS — the FND design data definition driving deployment of the physical table.
• JDR_COMPONENTS_PK / JDR_COMPONENTS_U1 / JDR_COMPONENTS_N1 / JDR_COMPONENTS_N2 — primary key and supporting unique/non-unique indexes on COMP_DOCID, COMP_SEQ, COMP_ELEMENT, and COMP_ID.
• JDR document header tables in APPLSYS that supply the COMP_DOCID document context against which these components are ordered.

Collectively these objects form the metadata backbone for JDR-based Java component resolution in Oracle EBS.