Search Results fnd_irep_classes

Overview

The FND_IREP_CLASSES table is an Application Object Library (FND) repository table that stores Integration Repository metadata describing executable interfaces within Oracle E-Business Suite. The Integration Repository is the underlying catalog that drives the Interface Designer, exposing deployable interface classes, their source definitions, mapping information, and lifecycle state. Each row in this table represents a single interface class definition registered in the repository, identified by a surrogate primary key.

The table resides in the APPLSYS schema and is present in both Oracle EBS 12.1.1 and 12.2.2. Under the documented physical schema for 12.2.2, it contains 37 columns. It carries the ZD_EDITION_NAME column, indicating that the object participates in the Editioning model introduced with Online Patching in Release 12.2; the same logical definition may therefore exist in multiple editions, with the ZD_EDITION_NAME differentiating rows.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. This suggests the table functions primarily as a reference or lookup entity rather than as a classic hub, link, or satellite. The single documented foreign key (SECURITY_GROUP_ID to FND_SECURITY_GROUPS) reinforces the view that most relationships are enforced functionally rather than through an extensive constraint network.

Key Information Stored

The table's identity is anchored by the surrogate primary key CLASS_ID, defined through the FND_IREP_CLASSES_PK constraint. Overlaid on top of this is the edition-aware structure typical of 12.2.2 objects.

• CLASS_ID — surrogate primary key uniquely identifying each interface class record.
• CLASS_NAME — the logical name of the interface class; part of the unique business key FND_IREP_CLASSES_U2 (along with ZD_EDITION_NAME).
• ZD_EDITION_NAME — edition discriminator. It appears in both unique indexes (FND_IREP_CLASSES_U1 on CLASS_ID+ZD_EDITION_NAME and FND_IREP_CLASSES_U2 on CLASS_NAME+ZD_EDITION_NAME).
• IREP_NAME — the Integration Repository display name for the class.
• CLASS_TYPE — categorization of the interface class.
• PRODUCT_CODE — owning product/module short code (e.g., FND, INV).
• IMPLEMENTATION_NAME — the implementing Java or PL/SQL class.
• SECURITY_GROUP_ID — the foreign key referencing FND_SECURITY_GROUPS, controlling visibility/data segregation.
• DEPLOYED_FLAG, GENERATED_FLAG, COMPATIBILITY_FLAG, ACTIVE_FLAG, OPEN_INTERFACE_FLAG — status and control flags governing deployment and interface usability.
• SOURCE_FILE_PRODUCT, SOURCE_FILE_PATH, SOURCE_FILE_NAME, SOURCE_FILE_VERSION — describe the artifact from which the interface definition was loaded.
• DESCRIPTION and XML_DESCRIPTION — human-readable and structured XML descriptions.
• STANDARD_TYPE, STANDARD_VERSION, STANDARD_SPEC — standard conformance metadata.
• LOAD_ERR, LOAD_ERR_MSGS — load diagnostics captured during interface registration or generation.
• MAP_CODE, INTERFACE_CLASS, IREP_HIDE_SCHEMA, IREP_LDR_PP_FLAG, IREP_LDR_INTERNAL_FLAG, LIFECYCLE_MODE, SCOPE_TYPE — control and configuration metadata used by the loader and runtime.

Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Administrators and technical consultants query FND_IREP_CLASSES primarily when diagnosing Integration Repository content, auditing which interfaces are deployed for a given product, or troubleshooting load errors.

• Inventory deployed interfaces for a product:

  SELECT class_name, irep_name, product_code, deployed_flag FROM fnd_irep_classes WHERE product_code = 'INV' AND deployed_flag = 'Y';

• Locate interfaces with load errors:

  SELECT class_id, class_name, load_err, load_err_msgs FROM fnd_irep_classes WHERE load_err IS NOT NULL;

• Trace the source artifact for an interface:

  SELECT class_name, source_file_product, source_file_name, source_file_version FROM fnd_irep_classes WHERE class_name = :class_name;

• Join to the security group to resolve ownership:

  SELECT c.class_name, s.security_group_name FROM fnd_irep_classes c, fnd_security_groups s WHERE c.security_group_id = s.security_group_id;

• Reporting on standard conformance (STANDARD_TYPE, STANDARD_VERSION) for compliance reviews, and filtering on ACTIVE_FLAG to surface only live interfaces.

Because the table is editioned in 12.2.2, queries should typically constrain or expect the ZD_EDITION_NAME column to avoid returning multiple edition rows for the same logical interface.

Related Objects

Relationships are defined functionally rather than through an extensive documented FK graph, but the following objects are most significant when working with FND_IREP_CLASSES:

• FND_SECURITY_GROUPS — referenced via FND_IREP_CLASSES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; controls visibility and ownership of each class.
• FND_IREP_ATTRIBUTES — holds attribute-level detail for each interface class, joined by CLASS_ID.
• FND_IREP_PARAMETERS — parameter definitions associated with a class.
• FND_IREP_CLASS_ATTRS / interface attribute mapping tables — carry generated interface metadata used by the Interface Designer.
• FND_IREP_OBJECTS — object-level Integration Repository definitions related to the interface class.
• The FND Interface Designer forms and the Integration Repository loader program — functional consumers that populate, generate, and validate rows in this table.

These related objects form the broader Integration Repository data model, within which FND_IREP_CLASSES serves as the header or catalog layer for executable interfaces across the E-Business Suite.