Search Results jdr_attributes_n1

Overview

APPLSYS.JDR_ATTRIBUTES is a seed-data table in the Oracle E-Business Suite repository layer. It stores the individual attribute name/value pairs that are attached to JDR (Java Declaration Repository) component documents. In EBS 12.1.1 and 12.2.2, the JDR framework persists metadata describing declarative component definitions — regions, items, properties, and their associated descriptive attributes — and JDR_ATTRIBUTES is the child table that holds those attributes in a normalized, extensible form. Each row associates one attribute with a specific component document instance, allowing the framework to model an arbitrary number of attributes per document without schema changes.

The table is owned by APPLSYS, carries FND design data reference FND.JDR_ATTRIBUTES, resides in the APPS_TS_SEED tablespace (PCTFREE 10), and is flagged VALID. The ETRM metadata includes the standard Oracle warning that the object is for Oracle Internal Use Only and is not supported for direct customer access except through standard Oracle Applications programs.

Based on the documented relationship structure — a composite primary key with no outgoing foreign keys — the heuristic Data Vault classification for this object is standalone. It behaves as an attribute-bearing child rather than as a hub, link, or satellite in its own right; its parent document determines the grain.

Key Information Stored

The physical row is defined by a four-part identity. The first three columns form the documented primary key JDR_ATTRIBUTES_PK (ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ), which establishes the surrogate composite key for the attribute record:

• ATT_COMP_DOCID (NUMBER(10), mandatory) — identifies the owning JDR component document. First component of both the primary key and the unique index.
• ATT_COMP_SEQ (NUMBER, mandatory) — sequence that distinguishes component instances within a document.
• ATT_SEQ (NUMBER, mandatory) — sequence of the individual attribute within the component; together with the two preceding columns it uniquely identifies the row.
• ATT_NAME (VARCHAR2(60), mandatory) — the attribute name. This is the principal business-key candidate along with the document keys; it is the leading column of the non-unique index JDR_ATTRIBUTES_N1 (ATT_NAME, ATT_COMP_DOCID).
• ATT_VALUE (VARCHAR2(4000)) — the attribute value, stored as a large variable-length string; this is the payload of the table and explains the 4000-byte width.
• ZD_EDITION_NAME — the editioning column used by the EBS 12.2 online patching (Edition-Based Redefinition) architecture. It is part of the business-key candidate index JDR_ATTRIBUTES_U1 (ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ, ZD_EDITION_NAME), which appears in 12.2.2 but not in 12.1.1.

The user's search term, JDR_ATTRIBUTES_U1, is precisely this unique index: in 12.1.1 it is unique on (ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ), while in 12.2.2 the editioning column is appended, yielding (ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ, ZD_EDITION_NAME).

Common Use Cases and Queries

JDR_ATTRIBUTES is consumed by the JDR runtime, not by end users. Practical access patterns are diagnostic and investigative — for example, resolving why a personalization, region definition, or declarative page renders unexpectedly, or auditing attribute values loaded by a patch or an OAF component deployment. Because the table is Oracle Internal Use Only, queries should be read-only and used for troubleshooting only.

Typical retrieval pattern:

• Fetch attributes for a known document: SELECT ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ, ATT_NAME, ATT_VALUE FROM APPLSYS.JDR_ATTRIBUTES WHERE ATT_COMP_DOCID = :docid ORDER BY ATT_COMP_SEQ, ATT_SEQ;
• Locate documents containing a given attribute name: SELECT ATT_COMP_DOCID, ATT_COMP_SEQ FROM APPLSYS.JDR_ATTRIBUTES WHERE ATT_NAME = :name; — this uses the JDR_ATTRIBUTES_N1 index with ATT_NAME as the leading column.
• Search attribute values for a literal string (full-table scan; restrict scope): SELECT ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ, ATT_NAME FROM APPLSYS.JDR_ATTRIBUTES WHERE ATT_VALUE LIKE '%' || :pattern || '%';

When running under EBS 12.2, include ZD_EDITION_NAME = 'SET1' (or query through the APPS synonym) to target the correct edition.

Related Objects

The documented dependency block states that JDR_ATTRIBUTES does not reference any database object and is referenced by the APPS synonym JDR_ATTRIBUTES. Its most significant associations are therefore:

• APPS.JDR_ATTRIBUTES — the synonym through which applications code accesses the base table.
• APPLSYS.JDR_ATTRIBUTES — the base table itself, owned in APPLSYS.
• JDR_ATTRIBUTES_PK — primary key on (ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQ).
• JDR_ATTRIBUTES_U1 — unique index; in 12.2.2 includes ZD_EDITION_NAME.
• JDR_ATTRIBUTES_N1 — non-unique index on (ATT_NAME, ATT_COMP_DOCID) supporting name-based lookups.
• FND.JDR_ATTRIBUTES — the FND design-data definition that governs the table's metadata.
• Parent JDR document tables — the component-level tables keyed by the same ATT_COMP_DOCID / ATT_COMP_SEQ values that JDR_ATTRIBUTES resolves against; the FK relationship is implicit through those columns rather than declared.
• JDR runtime APIs and OAF component definitions — the consumers that read attributes to assemble declarative metadata at runtime.