Search Results fnd_irep_class_parent_assigns




Overview
Explore in AI Chat

Overview

FND_IREP_CLASS_PARENT_ASSIGNS is a metadata table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the parent assignments for the Integration Repository, the central catalog that describes every interface, service, API, and business object exposed by EBS components. Specifically, the table records hierarchical relationships between integration repository classes, allowing each class to be linked to its parent class and thereby forming the class inheritance tree that the repository uses for browsing, discovery, and publishing of service definitions.

In Oracle EBS 12.1.1 and 12.2.2 the table is present in the APPLSYS schema and is marked VALID in the ETRM registry. The documented physical schema in 12.2.2 lists three columns, with the primary key FND_CLASS_PARENT_ASSIGNS_PK defined on (CLASS_NAME, PARENT_CLASS_NAME). From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning it does not participate as a hub, link, or satellite in the mined foreign-key structure; it is best treated as a self-contained reference or cross-reference table rather than as a transactional entity. The presence of ZD_EDITION_NAME indicates the table is edition-aware, so class-parent mappings can vary across editions (for example, between 12.1.1 and 12.2.2 or between custom editions).

Key Information Stored

The documented columns in 12.2.2 are limited to three, and each plays a distinct role in the class hierarchy model:

  • CLASS_NAME — The integration repository class being assigned. It identifies the child class in the hierarchy and is the first column of the composite primary key.
  • PARENT_CLASS_NAME — The parent class to which the child class is assigned. It is the second column of the composite primary key, so the combination (CLASS_NAME, PARENT_CLASS_NAME) uniquely identifies each parent-child relationship.
  • ZD_EDITION_NAME — The edition identifier. This column makes the table edition-aware, allowing the same class-parent relationship to exist in multiple editions. It also forms part of the unique index IREP_CLASS_PARENT_ASSIGNS_U1, defined on (CLASS_NAME, ZD_EDITION_NAME), which serves as a business-key candidate.

There is no separate surrogate key column documented; the primary key is composite and business-meaningful. Note that FND_IREP_CLASS_PARENT_ASSIGNS and FND_CLASS_PARENT_ASSIGNS_PK refer to the same object, with the former being the ETRM table name and the latter the constraint name.

Common Use Cases and Queries

Typical uses center on traversing and reporting the Integration Repository class hierarchy. A common query retrieves all immediate children of a given parent class:

  • SELECT CLASS_NAME, PARENT_CLASS_NAME FROM FND_IREP_CLASS_PARENT_ASSIGNS WHERE PARENT_CLASS_NAME = :parent;
  • Determining the parent of a specific class: SELECT PARENT_CLASS_NAME FROM FND_IREP_CLASS_PARENT_ASSIGNS WHERE CLASS_NAME = :child;
  • Filtering by edition: ... WHERE ZD_EDITION_NAME = :edition to isolate mappings for a specific EBS release.

Reporting scenarios include validating that every child class has a defined parent before publishing repository metadata, auditing class hierarchies after patching or upgrading from 12.1.1 to 12.2.2, and generating documentation of the service catalog structure for integration projects. Because the table is standalone and contains no foreign keys, queries are simple joins to the class definition tables on CLASS_NAME and PARENT_CLASS_NAME.

Related Objects

The following objects are most significant in relation to FND_IREP_CLASS_PARENT_ASSIGNS, joined on the documented columns:

  • FND_IREP_CLASSES — Master definition of integration repository classes; join on FND_IREP_CLASS_PARENT_ASSIGNS.CLASS_NAME = FND_IREP_CLASSES.CLASS_NAME and separately on PARENT_CLASS_NAME to resolve both sides of the hierarchy.
  • FND_IREP_CLASS_PARENT_ASSIGNS — Self-referencing traversal, joining PARENT_CLASS_NAME back to CLASS_NAME for multi-level hierarchy queries.
  • FND_IREP_ATTRIBUTES — Attributes belonging to each class; joined via CLASS_NAME.
  • FND_IREP_CLASS_ATTRS — Class-to-attribute mappings, joined on CLASS_NAME.
  • FND_IREP_OPERATIONS / FND_IREP_PARAMETERS — Operations and parameters defined for classes, reached through CLASS_NAME to describe the full service definition.
  • FND_IREP_CLASS_PARENT_ASSIGNS (constraint FND_CLASS_PARENT_ASSIGNS_PK) — The primary key enforces uniqueness of (CLASS_NAME, PARENT_CLASS_NAME) and is the primary integrity mechanism for this table.

Because the ETRM relationship mining classified this table as standalone, no declared foreign keys to other FND tables were documented; joins to the class, attribute, and operation tables are therefore logical rather than enforced by database constraints.