Search Results jdr_attributes_trans




Overview
Explore in AI Chat

Overview

JDR_ATTRIBUTES_TRANS is a standalone configuration and metadata table owned by the APPLSYS schema within the FND (Application Object Library) product module. Its name places it in the JDR ("Java Development Runtime" / Oracle Application Framework metadata) family of tables, which store the runtime definitions used by OA Framework pages, regions, and their extensibility (personalization) metadata. The "_TRANS" suffix indicates that the rows carry translated or language-dependent attribute values, allowing attribute metadata to be presented in multiple languages rather than in a single base-language form.

The object belongs to a small, tightly bound metadata family. Its six documented columns describe a composite identity for each attribute record plus the value associated with that attribute. Based on the mined foreign-key structure, the ETRM metadata classifies JDR_ATTRIBUTES_TRANS as a standalone object, meaning it carries no outbound or inbound referential constraints. In Data Vault modeling terms this is not a hub, link, or satellite in the strict sense; the standalone classification is a modeling suggestion that the table can be treated as an independent reference/descriptive store keyed by its own composite business key rather than participating in an enforced dimensional network.

Key Information Stored

The table is relatively narrow (six documented columns). The most important columns and their roles are as follows:

  • ATL_COMP_DOCID — The document identifier of the component whose attribute metadata is being described. It anchors the record to a specific metadata document or component definition.
  • ATL_LANG — The language code for the translated value, distinguishing rows for the same logical attribute across different languages.
  • ATL_COMP_REF — A reference to the component, forming part of the composite identity and identifying which component instance the attribute applies to.
  • ATL_NAME — The attribute name, the semantic label under which the value is stored.
  • ATL_VALUE — The translated or language-dependent value assigned to the named attribute. This is the payload column of primary interest for reporting.
  • ZD_EDITION_NAME — The editioning column present in EBS 12.2.x, supporting the online patching (Edition-Based Redefinition) model introduced with 12.2.

The primary key is defined by JDR_ATTRIBUTES_TRANS_PK over (ATL_COMP_DOCID, ATL_LANG, ATL_COMP_REF, ATL_NAME). A second, unique index JDR_ATTRIBUTES_TRANS_U1 covers the same four columns plus ZD_EDITION_NAME, making that five-column set the effective business-key candidate once editioning is taken into account. The natural key is therefore the composite of document identifier, language, component reference, and attribute name, with the edition name distinguishing copies of the same logical record across editions.

Common Use Cases and Queries

This table is typically queried during investigation and support of OA Framework personalization and metadata translation issues. Typical patterns include retrieving every translated value for a given component and language, checking which attributes exist for a component, and confirming whether a translation row exists for a specific language before assuming a fallback is being applied.

  • Point lookup by composite key: SELECT atl_value FROM jdr_attributes_trans WHERE atl_comp_docid=:1 AND atl_lang=:2 AND atl_comp_ref=:3 AND atl_name=:4;
  • All attributes for a component in a single language: filter by ATL_COMP_DOCID and ATL_LANG and display ATL_NAME with ATL_VALUE.
  • Translation coverage audit: group by ATL_LANG to confirm which languages have rows for a component.
  • Edition-aware queries in 12.2.x should account for ZD_EDITION_NAME when comparing records across patching cycles.

Related Objects

The mined FK structure shows no enforced relationships, so associated objects are those that share the JDR / FND metadata family and reuse the same component-document identity columns (ATL_COMP_DOCID, ATL_COMP_REF). Administrators investigating this table commonly reference the JDR metadata dictionary tables and FND lookup and language tables, using ATL_LANG against FND_LANGUAGES and joining component identifiers back to the corresponding OA Framework metadata definitions. Because the documented relationship data is limited, joins beyond ATL_LANG to FND_LANGUAGES should be validated against the specific component model in use.