Search Results comp_docid

Overview

APPLSYS.JDR_COMPONENTS is a seed-data table within the Oracle E-Business Suite Applications Foundation (FND) schema. It stores the component definitions that make up Java Deployment Repository (JDR) documents, which drive the behavior of Oracle EBS Java-based functionality such as Oracle Forms, the OA Framework, and the JDR runtime configuration used by the EBS middle tier. Each row describes an individual component (a class, resource, or element) that belongs to a parent JDR document, identified by COMP_DOCID. The table resides in the APPS_TS_SEED tablespace, confirming it is populated and maintained as Oracle-seeded configuration data rather than transactional user data.

The ETRM metadata is explicit that this object is flagged Oracle Internal Use Only. Oracle Corporation does not support direct access to this data except from standard Oracle Applications programs, so read-only diagnostics and reporting are the only appropriate direct-query scenarios. The mined dependency classification suggests this object is best modeled as a standalone entity (neither a classic hub, link, nor satellite), reflecting that its primary key and relationships are self-contained rather than participating in a broader Data Vault-style integration network.

Key Information Stored

The physical primary key documented for this table is JDR_COMPONENTS_PK (COMP_DOCID, COMP_SEQ). COMP_DOCID identifies the owning JDR document, while COMP_SEQ provides the ordering of components within that document. Together these form the surrogate/composite key that uniquely identifies each component row, and COMP_DOCID is also the column the user searched on, appearing as the leading column of all three indexes.

• COMP_DOCID — Number(10). Identifies the parent JDR document to which the component belongs; the primary search and join column and the leading column of the unique index JDR_COMPONENTS_U1 and nonunique indexes JDR_COMPONENTS_N1 and JDR_COMPONENTS_N2.
• COMP_SEQ — Sequence number ordering the component within the document; the second half of the primary key and the unique business-key candidate.
• COMP_LEVEL — Numeric nesting or hierarchy level of the component within the document structure.
• COMP_GROUPING — Varchar2(30). Groups related components for organizational or processing purposes.
• COMP_ELEMENT — Varchar2(40). The element type or category of the component; indexed by JDR_COMPONENTS_N1.
• COMP_ID — Varchar2(60). The component identifier, indexed by JDR_COMPONENTS_N2; participates in an FK-style relationship to IEO_SVR_COMPS.
• COMP_REF — Varchar2(255). A reference path or pointer associated with the component.
• COMP_EXTENDS — Varchar2(255). Indicates a parent component that this component extends or inherits from.
• COMP_USE — Varchar2(510). Describes how and where the component is used or applied.
• COMP_COMMENT — Varchar2(4000). Free-text descriptive comment for the component.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching (edition-based redefinition).

The unique business-key candidate is JDR_COMPONENTS_U1 (COMP_DOCID, COMP_SEQ, ZD_EDITION_NAME); the inclusion of ZD_EDITION_NAME distinguishes this from the pre-12.2 unique index, which covered only COMP_DOCID and COMP_SEQ.

Common Use Cases and Queries

The principal practical use of this table is diagnosing JDR document composition and resolving component-level deployment issues. Because access is restricted to standard Oracle Applications programs, direct queries should be limited to read-only troubleshooting and support investigations. A representative query retrieves all components for a specific document in sequence order:

SELECT COMP_DOCID, COMP_SEQ, COMP_LEVEL, COMP_ELEMENT, COMP_ID, COMP_REF, COMP_EXTENDS
FROM APPLSYS.JDR_COMPONENTS
WHERE COMP_DOCID = :docid
ORDER BY COMP_SEQ;

Reporting scenarios include listing the distinct element and grouping types present across documents, auditing which components extend or reference other components, and cross-referencing COMP_ID values against IEO_SVR_COMPS to validate component availability. In 12.2 environments, queries should filter or account for ZD_EDITION_NAME where edition-sensitive results are required.

Related Objects

• IEO_SVR_COMPS — Referenced via APPLSYS.JDR_COMPONENTS.COMP_ID; the most significant related object for validating that component identifiers resolve to known server components.
• APPS.JDR_COMPONENTS — The APPS synonym/view layer through which the table is normally accessed by Oracle Applications code; dependent synonym that shields callers from the APPLSYS base object.
• JDR_COMPONENTS_PK — The primary key constraint (COMP_DOCID, COMP_SEQ) enforcing row uniqueness.
• JDR_COMPONENTS_U1 — Unique index (COMP_DOCID, COMP_SEQ, ZD_EDITION_NAME) providing the business-key candidate in 12.2.
• JDR_COMPONENTS_N1 — Nonunique index (COMP_ELEMENT, COMP_DOCID) supporting element-based lookups.
• JDR_COMPONENTS_N2 — Nonunique index (COMP_ID, COMP_DOCID) supporting component-identifier lookups.
• FND.JDR_COMPONENTS — The FND design data definition that seeds and maintains this table.

No additional database objects are documented as being referenced by this table, consistent with its standalone classification.