Search Results jdr_paths




Overview
Explore in AI Chat

Overview

The JDR_PATHS table is a core repository object within the Oracle E-Business Suite (EBS) Application Object Library (FND). It is owned by the APPLSYS schema and is integral to the Oracle Application Framework (OA Framework or OAF) architecture. This table functions as a central registry for storing the hierarchical path information of all OA Framework components, such as pages, regions, and items. Its primary role is to manage the internal structure and relationships of these components, enabling the runtime engine to correctly locate, render, and process user interface elements. The existence of a primary key (JDR_PATHS_PK) on PATH_DOCID underscores its critical function in maintaining data integrity for the framework's metadata.

Key Information Stored

Based on the provided metadata and standard OA Framework implementation, the table's structure is designed to map document paths to unique identifiers. The most critical column is PATH_DOCID, which serves as the primary key. This column stores a unique numeric identifier for a specific path entry. While the full column list is not detailed in the excerpt, typical companion columns in such a structure would include a PATH column to store the actual hierarchical path string (e.g., /oracle/apps/fnd/.../MyPG) and potentially a DOCID column referencing the component's definition in the related JDR_ATTRIBUTES or JDR_COMPONENTS tables. The path string itself is a vital piece of metadata used by the framework for component resolution.

Common Use Cases and Queries

This table is primarily accessed by the OA Framework engine and during development or administrative troubleshooting. Common operational scenarios include diagnosing page rendering errors by tracing a component's registered path and performing impact analysis before patching or customizing OA Framework pages. A fundamental query pattern involves joining JDR_PATHS to other JDR_ metadata tables to retrieve a component's full definition. For example, to find the path for a specific document ID, one might execute: SELECT path FROM apps.JDR_PATHS WHERE path_docid = <value>;. Conversely, to find the document ID for a known path: SELECT path_docid FROM apps.JDR_PATHS WHERE path = '<full_path_string>';. Direct reporting or modification by end-users is exceptionally rare.

Related Objects

The JDR_PATHS table is a central node in the OA Framework metadata schema. It has direct relationships with other core JDR_ tables that store component attributes and definitions. The primary key, PATH_DOCID, is almost certainly referenced by foreign keys in tables such as:

  • JDR_ATTRIBUTES: Likely contains a PATH_DOCID column to link attribute values to a specific component path.
  • JDR_COMPONENTS: May use PATH_DOCID to associate a component type and name with its hierarchical location.
  • JDR_PATHS may also self-reference to manage nested path structures. These relationships are essential for the OA Framework to assemble a complete page definition from its constituent metadata parts stored across these interrelated tables.
All access to this table should be performed through the appropriate OA Framework utilities and APIs to preserve metadata consistency.