Search Results irep_class_parent_assigns_u1

Overview

APPLSYS.FND_IREP_CLASS_PARENT_ASSIGNS is a seed data table in the Oracle E-Business Suite Integration Repository (IREP) schema. It records the parent-child hierarchy between integration repository classes, defining how a given child class inherits metadata and behavior from one or more parent classes. The Integration Repository is the metadata backbone behind interfaces such as the Interface Repository browser, the Web Services provider, and the Business Event System's class registry, and this table supplies the class inheritance graph those facilities traverse at runtime.

Physically the table resides in the APPS_TS_SEED tablespace with PCTFREE 10, consistent with reference and seed data that is populated at installation and patched, rather than transactionally appended at runtime. From a Data Vault modeling perspective, this object is standalone with no foreign key dependencies to or from other tables in the documented schema, and its natural structure of two related class identifiers suggests it functions as a link table, joining a child class to its designated parent class. That classification is a heuristic modeling suggestion; in practice the table should be treated as a reference hierarchy maintained through patching and concurrent program execution rather than as a transactional entity.

Key Information Stored

The documented physical schema exposes three columns, and these are the columns of analytical interest:

• CLASS_NAME (VARCHAR2(430), mandatory) — the name of the child class. This is the class that inherits from the parent identified in the adjacent column.
• PARENT_CLASS_NAME (VARCHAR2(430), mandatory) — the name of the parent class from which CLASS_NAME inherits. Together with CLASS_NAME, this forms the declared primary key FND_CLASS_PARENT_ASSIGNS_PK.
• ZD_EDITION_NAME (VARCHAR2(30)) — the edition tag introduced by the Online Patching (Edition-Based Redefinition) infrastructure in Oracle EBS 12.2.x, used to scope records to a specific edition during patching cycles.

The composite primary key (CLASS_NAME, PARENT_CLASS_NAME) is the true business key for the hierarchy: each child-to-parent relationship appears exactly once. The unique index IREP_CLASS_PARENT_ASSIGNS_U1 (CLASS_NAME, ZD_EDITION_NAME) enforces the additional constraint that, within any single edition, a child class may have at most one parent assignment recorded. That index is the object referenced by the search term "irep_class_parent_assigns_u1". There is no synthetic surrogate key column; the identity of a row is derived entirely from the pair of class name columns.

Common Use Cases and Queries

The table is most often queried to resolve class inheritance for a given interface or service, and to trace the full ancestry chain of a repository class. A direct lookup for a child class is straightforward:

• SELECT CLASS_NAME, PARENT_CLASS_NAME, ZD_EDITION_NAME FROM APPLSYS.FND_IREP_CLASS_PARENT_ASSIGNS WHERE CLASS_NAME = :child_class;
• Reverse lookup to find all children of a parent class: SELECT CLASS_NAME FROM APPLSYS.FND_IREP_CLASS_PARENT_ASSIGNS WHERE PARENT_CLASS_NAME = :parent_class;
• Edition-aware queries filtering on ZD_EDITION_NAME when investigating behavior differences between patched editions.

Reporting scenarios include auditing the hierarchy for orphaned or duplicate parent assignments, verifying that an upgrade or patch did not alter expected inheritance, and generating an interface dependency report for integration architects. Because the table is seed data in the APPS schema, queries should be run as a user with read privileges on APPLSYS rather than from a custom schema.

Related Objects

The metadata notes that FND_IREP_CLASS_PARENT_ASSIGNS is referenced only by APPLSYS.FND_IREP_CLASS_PARENT_ASSIGNS#, the editioning or stub counterpart object used by the Online Patching framework. No other downstream database objects are documented as depending on it. In functional terms, the significant related objects are the other Integration Repository seed tables that share the class registry:

• FND_IREP_CLASSES — the master list of class names that CLASS_NAME and PARENT_CLASS_NAME reference by name.
• FND_IREP_ATTRIBUTES — attributes attached to repository classes.
• FND_IREP_PARAMETERS — parameters defined for class methods.
• FND_IREP_OBJS and FND_IREP_INTERFACES — interface and object definitions built on the class hierarchy.
• FND_IREP_CLASS_PARENT_ASSIGNS# — the APPS-schema editioning counterpart object.

These tables are joined on the class name columns rather than through declared foreign keys, so consistency between them is maintained by the EBS patching and seed data load processes.