Search Results fnd_irep_classes_n1

Overview

APPLSYS.FND_IREP_CLASSES is an Oracle E-Business Suite seed data table that stores Integration Repository metadata describing executable interfaces registered in the EBS instance. In the EBS architecture, the Integration Repository provides a catalog of interfaces — PL/SQL APIs, Java classes, concurrent programs, and web services — exposed by Oracle applications. Each row in FND_IREP_CLASSES represents a single interface class, identified by both a surrogate numeric key and a fully qualified name. The table resides in the APPS_TS_SEED tablespace, consistent with its role as seed data maintained by Oracle rather than by end users. Under the ETRM 12.2.2 documented schema the table contains 37 columns, and the design data object is registered as FND.FND_IREP_CLASSES. The table is classified heuristically as standalone within a Data Vault model, meaning it does not participate as a link or satellite in a mined foreign-key mesh; it can be treated as a reference or catalog hub keyed on CLASS_ID, with CLASS_NAME acting as the natural business key.

Key Information Stored

The primary key is CLASS_ID (NUMBER(15)), enforced by FND_IREP_CLASSES_PK. Two unique indexes are documented as business-key candidates: FND_IREP_CLASSES_U1 (CLASS_ID, ZD_EDITION_NAME) and FND_IREP_CLASSES_U2 (CLASS_NAME, ZD_EDITION_NAME) — the latter is the index most commonly referenced when users search for fnd_irep_classes_u2, since it enforces uniqueness of the interface class name within an edition. Among the most significant columns:

• CLASS_ID — surrogate primary key for the interface class.
• CLASS_NAME — the unique qualified name of the interface, and the driver of the U2 index.
• IREP_NAME — the native (internal) name of the interface.
• CLASS_TYPE — the type or owning product classification of the interface.
• PRODUCT_CODE — the product that owns the interface; indexed by the non-unique FND_IREP_CLASSES_N1 index.
• IMPLEMENTATION_NAME — the Java implementation name invoked at runtime.
• DEPLOYED_FLAG, GENERATED_FLAG, COMPATIBILITY_FLAG — status flags indicating deployment, generation, and compatibility state.
• ASSOC_CLASS_ID — a pointer to the base class, supporting interface inheritance.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, scoping visibility of the interface.
• SCOPE_TYPE and LIFECYCLE_MODE — scope and lifecycle metadata for the interface.
• SOURCE_FILE_PRODUCT, SOURCE_FILE_PATH, SOURCE_FILE_NAME, SOURCE_FILE_VERSION — provenance of the source artifact.
• DESCRIPTION and XML_DESCRIPTION — CLOB columns holding the description and the WSDL or schema definition.
• STANDARD_TYPE, STANDARD_VERSION, STANDARD_SPEC — standard compliance metadata.
• LOAD_ERR and LOAD_ERR_MSGS — loader diagnostics.
• ACTIVE_FLAG and ZD_EDITION_NAME — record activity and edition (AD/Zd) qualifier included in the unique indexes.

Common Use Cases and Queries

The table is typically queried when investigating registered interfaces, diagnosing deployment or loading errors, or determining which product owns a given interface. A typical lookup by business key uses the U2 index:

SELECT class_id, class_name, irep_name, product_code, deployed_flag FROM fnd_irep_classes WHERE class_name = :p_name AND zd_edition_name = 'SET1';

Reporting by product or load status is also common:

SELECT product_code, class_type, COUNT(*) FROM fnd_irep_classes WHERE active_flag = 'Y' GROUP BY product_code, class_type;

Diagnostics for failed loads filter on LOAD_ERR, and interface discovery joins on SECURITY_GROUP_ID to constrain results to a security group. Queries against FND_IREP_CLASSES should generally restrict on ZD_EDITION_NAME to the active edition so that AD edition rows are excluded.

Related Objects

The principal related objects, based on documented relationships, include:

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID (foreign key), controlling interface visibility.
• FND_IREP_CLASSES (self-referencing) — via ASSOC_CLASS_ID for base-class inheritance chains.
• FND_IREP_PARAMETERS — holds parameter definitions for each CLASS_ID, joined by CLASS_ID.
• FND_IREP_INTERFACES — interface instances referencing class definitions.
• FND_IREP_CLASS_TYPES — lookup supporting CLASS_TYPE values.
• FND_IREP_PRODUCTS — product registration referenced through PRODUCT_CODE.
• FND_IREP_LICENSES — licensing metadata for registered interfaces.
• FND_IREP_GEN_* API/loader packages — used to load and generate interface metadata rows.

These objects together comprise the Integration Repository seed tables, with FND_IREP_CLASSES serving as the central catalog of executable interfaces for the instance.