Search Results path_docid

Overview

The APPLSYS.JDR_PATHS table is a core repository table within the Oracle E-Business Suite (EBS) architecture, specifically part of the Oracle Application Framework (OAF) and Java-based components. It functions as a metadata registry for defining and managing the hierarchical structure and navigation paths of application objects, such as pages, regions, and items, within the framework. Its primary role is to store the logical relationships and sequences that define how components are assembled and rendered at runtime. As indicated by the warning in the metadata, this table is designated for Oracle Internal Use Only; direct access or modification is not supported outside of standard Oracle Applications programs, and it is critical for the integrity of the application's user interface layer.

Key Information Stored

The table's columns store metadata essential for path definition and versioning. The PATH_NAME column (VARCHAR2(60)) is a mandatory field holding the unique identifier or name of the defined path. PATH_DOCID (NUMBER) and PATH_OWNER_DOCID (NUMBER) are unique identifiers that establish relationships between the path and its constituent document objects within the metadata model. PATH_TYPE (VARCHAR2(30)) categorizes the nature of the path. PATH_SEQ (NUMBER) dictates the order or sequence of elements within the path. The columns PATH_XML_VERSION and PATH_XML_ENCODING track the XML specification details for the path's definition. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) complete the record.

Common Use Cases and Queries

Direct operational use by consultants is rare due to its internal nature; interaction is typically through the OAF development and personalization layers. However, diagnostic or impact analysis queries may be necessary. A fundamental query to retrieve all path definitions is provided in the metadata: SELECT PATH_NAME, PATH_DOCID, PATH_OWNER_DOCID, PATH_TYPE, PATH_SEQ FROM APPLSYS.JDR_PATHS;. A more targeted query to find paths by name, leveraging the non-unique index on PATH_NAME, would be: SELECT * FROM APPLSYS.JDR_PATHS WHERE PATH_NAME LIKE '%<search_string>%';. Reporting might involve joining this table with other JDR_* tables (like JDR_COMPONENTS) to map paths to specific UI components, though such relationships are managed internally by the application.

Related Objects

Based on the provided dependency information, the primary related object is the synonym APPS.JDR_PATHS, which provides the standard access point for the EBS application code to this underlying APPLSYS table. The table's integrity is enforced by two unique indexes: JDR_PATHS_U1 on PATH_DOCID and JDR_PATHS_U2 on the combination of PATH_OWNER_DOCID and PATH_NAME. The non-unique index JDR_PATHS_N1 on PATH_NAME facilitates searches. It logically relates to other metadata tables in the APPLSYS schema, such as JDR_COMPONENTS and JDR_ATTRIBUTES, which store the detailed definitions of the objects referenced by the path identifiers (PATH_DOCID, PATH_OWNER_DOCID).