Search Results fnd_irep_uses_maps




Overview
Explore in AI Chat

Overview

FND_IREP_USES_MAPS is a repository table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. Its documented purpose is to store "Uses Maps Information for iRep," meaning it records the association between iRep (integrated reporting) class definitions and the maps they reference. In the EBS 12.1.1 and 12.2.2 file systems, iRep components underpin the XML Publisher and Oracle Reports publishing infrastructure, and this table captures which map entities are consumed by which reporting class.

The table is documented as VALID and consists of four columns. Under the heuristic Data Vault classification supplied with the metadata, FND_IREP_USES_MAPS is identified as standalone, which suggests it is best modeled as a reference or lookup table rather than a hub, link, or satellite. This is consistent with a configuration-style association table whose rows are not participating in a broader FK-linked Data Vault topology.

Key Information Stored

Only four physical columns are documented for FND_IREP_USES_MAPS in the ETRM 12.2.2 schema, and each contributes directly to the table's semantics:

  • CLASS_ID — Identifier of the iRep class to which the map usage applies. It participates in the composite primary key and is the leading column of the unique index.
  • MAP_USED — Identifier of the map that the referenced class consumes. It is the second component of the composite primary key.
  • DISPLAY_SEQ — Sequence number controlling the ordering in which map usage entries are presented, typically for deterministic rendering in iRep configuration and maintenance screens.
  • ZD_EDITION_NAME — Editioning column introduced for the EBS 12.2 online patching (adop) architecture, isolating data by edition so that runtime and patch editions can coexist.

The surrogate/business key structure is fully documented:

  • Primary key: FND_IREP_USES_MAPS_PK, comprising (MAP_USED, CLASS_ID). This is the row's unique identity.
  • Unique index (business-key candidate): FND_IREP_USES_MAPS_U1, comprising (CLASS_ID, ZD_EDITION_NAME). This alternate uniqueness constraint ties each class to a single edition, reinforcing that CLASS_ID combined with the edition column is a meaningful business identifier.

Common Use Cases and Queries

Because the table is small and configuration-oriented, it is primarily queried to audit or troubleshoot iRep map-to-class assignments. Typical scenarios include determining which maps a given iRep class uses, verifying that map usage rows were correctly replicated across editions after an online patch, and validating display ordering in custom iRep metadata screens.

A representative query listing map usage for a specific class might read:

  • SELECT map_used, display_seq FROM applsys.fnd_irep_uses_maps WHERE class_id = :class_id ORDER BY display_seq;

To confirm edition coverage in a 12.2 environment:

  • SELECT class_id, map_used, zd_edition_name FROM applsys.fnd_irep_uses_maps WHERE zd_edition_name = 'RUN' ORDER BY class_id, display_seq;

Reporting use cases are limited largely to administrative dashboards and support diagnostics. The table is not transactional, so it is rarely referenced in high-volume reporting or ETL flows. When cloning or comparing environments, it can be joined against the corresponding class definition table to detect configuration drift between source and target instances.

Related Objects

The metadata classifies FND_IREP_USES_MAPS as standalone in the heuristic FK structure, meaning no referenced or referencing foreign keys were mined. The most significant related objects are therefore inferred from the class/map semantics encoded in CLASS_ID and MAP_USED:

  • FND_IREP_CLASSES (or the analogous iRep class repository) — joins on CLASS_ID to resolve class names and attributes.
  • FND_IREP_MAPS (or the corresponding map repository) — joins on MAP_USED to resolve map definitions.
  • FND_IREP_USES_MAPS editions — the ZD_EDITION_NAME column aligns this table with the 12.2 editioning model used across FND configuration tables.
  • AD_ZD_EDITION-related views and online patching utilities — consume ZD_EDITION_NAME to manage edition-aware data.
  • XML Publisher / Oracle Reports iRep configuration screens — read and write rows in this table through the standard FND application layer.

Because no FK relationships are documented, joins to the class and map repositories should be validated against the specific EBS instance, since naming of the companion iRep tables can vary by patch level.