Search Results path_name




Overview
Explore in AI Chat

Overview

APPLSYS.JDR_PATHS is a seed data table in the Oracle E-Business Suite Applications schema, registered in FND Design Data as FND.JDR_PATHS. The acronym "JDR" refers to the Java Development Runtime metadata layer, and this table stores path definitions used by the Oracle Applications XML/Java framework — specifically the logical navigation and document path entries consumed by runtime components that resolve XML documents and application path structures. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_SEED tablespace with PCTFREE 10, indicating that it holds relatively static, shipped configuration data rather than high-churn transactional content.

The ETRM metadata classifies this object heuristically as standalone under a Data Vault modelling lens, meaning no foreign-key relationships to other tables are documented. It can therefore be modelled most simply as a hub-like reference entity keyed on PATH_DOCID, with descriptive attributes (path type, sequence, XML version/encoding) treated as satellite-style descriptive columns rather than link-based relationships. That classification is a modelling suggestion only; the physical design is the conventional EBS seed-table pattern with audit columns.

Key Information Stored

The table contains thirteen documented columns. The most important are:

  • PATH_DOCID — Number(10) surrogate primary key. It is the single-column primary key JDR_PATHS_PK and also the leading column of unique index JDR_PATHS_U1 (PATH_DOCID, ZD_EDITION_NAME).
  • PATH_NAME — Varchar2(60). The human-readable path identifier. It is the second column of unique business-key index JDR_PATHS_U2 (PATH_OWNER_DOCID, PATH_NAME, ZD_EDITION_NAME) and is independently indexed by non-unique index JDR_PATHS_N1 for lookup performance.
  • PATH_OWNER_DOCID — Number(10). Identifies the owning document or owner context that the path belongs to; combined with PATH_NAME it forms the business-key candidate.
  • PATH_TYPE — Varchar2(30). Classifies the path (for example the kind of navigation or document path being defined).
  • PATH_SEQ — Number. Ordinal sequencing used to order paths within an owner or document grouping.
  • PATH_XML_VERSION — Varchar2(10). XML version declared for the path's document content.
  • PATH_XML_ENCODING — Varchar2(10). Character encoding declared for the associated XML document.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns recording insert and update identity and timestamps.
  • ZD_EDITION_NAME — The editioning column introduced with EBS 12.2 online patching, present in the physical schema and included in both unique indexes.

Common Use Cases and Queries

Because the table stores framework seed definitions, typical usage is diagnostic and reference-oriented: verifying that a path definition shipped correctly, auditing path sequencing for an owner, or confirming XML version/encoding metadata during integration troubleshooting. A direct query is straightforward:

  • Resolve a path by name: SELECT PATH_DOCID, PATH_OWNER_DOCID, PATH_TYPE, PATH_SEQ FROM APPLSYS.JDR_PATHS WHERE PATH_NAME = :name;
  • List all paths for an owner in order: SELECT PATH_NAME, PATH_SEQ FROM APPLSYS.JDR_PATHS WHERE PATH_OWNER_DOCID = :docid ORDER BY PATH_SEQ;
  • Audit configuration: select CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE to identify whether a path definition deviates from the shipped seed set.

Note the Oracle internal-use warning: the object should be accessed only through standard Oracle Applications programs, not modified directly.

Related Objects

The documented dependency data states that APPLSYS.JDR_PATHS does not reference any other database object, and that it is referenced only by the APPS synonym JDR_PATHS, which applications code uses in place of the APPLSYS-qualified name. Consequently, no FK-based joins to sibling tables are documented in the ETRM metadata. In practice, joins occur within the JDR framework family through the shared document identifier, correlating PATH_DOCID and PATH_OWNER_DOCID with document-oriented JDR tables, while PATH_NAME is the principal business lookup key exposed to reporting and diagnostic queries. All access should be treated as read-only reference inspection.