Search Results xml_description

Overview

FND_IREP_CLASSES_VL is a bilingual (MLS) validation view owned by the APPS schema in Oracle E-Business Suite, residing in the FND — Application Object Library product. It presents the translation-aware, language-specific definition records for iRep (integrated repository) classes. An iRep class defines the metadata, source, lifecycle, and deployment characteristics of a repository object that participates in Oracle EBS's integrated repository framework. The "_VL" suffix denotes a view that joins a base table (FND_IREP_CLASSES) with its translation table (FND_IREP_CLASSES_TL), returning translatable descriptive columns (DISPLAY_NAME, SHORT_DESCRIPTION) in the session's current language while retaining all non-translated technical attributes from the base table.

Because the view filters translations using USERENV('LANG'), it returns exactly one row per CLASS_ID for the active language, making it the standard reporting and integration surface for repository class definitions rather than the underlying translated table. It is documented as VALID and is used by both Oracle Application Object Library internals and customer-facing queries examining deployed iRep classes.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

• FND_IREP_CLASSES — the base table (aliased B) holding the primary, non-translated attributes of each iRep class, keyed by CLASS_ID.
• FND_IREP_CLASSES_TL — the translation table (aliased T) holding language-specific DISPLAY_NAME and SHORT_DESCRIPTION, joined on CLASS_ID.

The join predicate is B.CLASS_ID = T.CLASS_ID AND T.LANGUAGE = USERENV('LANG'), which constrains output to the single row matching the session language. All other columns are projected directly from the base table. The view also exposes ROW_ID derived from the base table's ROWID, and WHERE clauses in ETRM references consistently place both source tables in the FROM list with this language-restricted join, confirming the view is intended as a language-filtered read layer.

Key Columns

• CLASS_ID — primary identifier of the repository class; join key across both base objects.
• CLASS_NAME / IREP_NAME — the internal class identifier and the iRep repository object name.
• CLASS_TYPE — categorizes the class within the iRep framework.
• PRODUCT_CODE — owning Oracle product (application short name).
• IMPLEMENTATION_NAME — the implementing object or routine.
• DEPLOYED_FLAG, GENERATED_FLAG, ACTIVE_FLAG, COMPATIBILITY_FLAG — lifecycle/status indicators for the class.
• ASSOC_CLASS_ID, SCOPE_TYPE, LIFECYCLE_MODE — association and scoping attributes controlling class behavior.
• SOURCE_FILE_PRODUCT, SOURCE_FILE_PATH, SOURCE_FILE_NAME, SOURCE_FILE_VERSION — provenance of the generating source file.
• DESCRIPTION / XML_DESCRIPTION — non-translated profile text and its XML form; DISPLAY_NAME and SHORT_DESCRIPTION are the translated display values.
• STANDARD_TYPE, STANDARD_VERSION, STANDARD_SPEC — standards-conformance metadata.
• LOAD_ERR, LOAD_ERR_MSGS — load failure state and diagnostic messages.
• OPEN_INTERFACE_FLAG, MAP_CODE, INTERFACE_CLASS — interface-related attributes.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID) — standard EBS audit and multi-org security tracking.

Common Use Cases and Queries

A typical reporting query lists all deployed, active classes for a product. The USERENV('LANG') predicate is applied automatically, so translations appear in the session language.

• Locate a class by name:
  SELECT class_id, class_name, irop_name, product_code, deployed_flag
FROM fnd_irep_classes_vl
WHERE class_name = :name;
• List active classes for a product:
  SELECT class_id, class_name, display_name, implementation_name
FROM fnd_irep_classes_vl
WHERE product_code = :prod AND active_flag = 'Y';
• Diagnose load errors:
  SELECT class_name, load_err, load_err_msgs
FROM fnd_irep_classes_vl
WHERE load_err IS NOT NULL;

Because the view enforces a single-language row, it is preferred for interface and reporting queries over the raw TL table, where callers must otherwise add their own LANGUAGE predicate.