Search Results fnd_irep_uses_maps_u1

Overview

APPLSYS.FND_IREP_USES_MAPS is a transactional configuration table in the Oracle E-Business Suite APPLSYS schema that stores "Uses Maps" information for iRep, the Oracle EBS diagnostic and business-flow reporting subsystem. Each row associates an iRep class with a map that the class consumes, and records the sequence in which that map is displayed. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is registered in FND design data as FND.FND_IREP_USES_MAPS.

The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema comprises four columns. Under the heuristic Data Vault classification derived from its foreign-key structure, the object is treated as standalone; no FK relationships to parent entities are documented, so a Data Vault modeler would not be obligated to promote it into a hub or link construct. Its primary key, FND_IREP_USES_MAPS_PK, is defined on (MAP_USED, CLASS_ID).

Key Information Stored

The table holds four documented columns. The most significant are:

• CLASS_ID — NUMBER(15). The identifier of the iRep class whose map usage is being defined. This column participates in the composite primary key and in the unique index FND_IREP_USES_MAPS_U1.
• MAP_USED — VARCHAR2(255). The name or identifier of the map consumed by the class. It is the leading column of the composite primary key.
• DISPLAY_SEQ — NUMBER(15). Governs the order in which the associated map is presented in iRep output.
• ZD_EDITION_NAME — VARCHAR2(30). The edition designator used by the EBS online patching and editioning framework. It is the second column of the unique index FND_IREP_USES_MAPS_U1.

The primary key (MAP_USED, CLASS_ID) is the surrogate row identifier, while FND_IREP_USES_MAPS_U1 on (CLASS_ID, ZD_EDITION_NAME) functions as the documented business-key candidate. The unique index FND_IREP_USES_MAPS_U1 is created in the APPS_TS_TX_IDX tablespace and is the index most commonly probed when the user search term "fnd_irep_uses_maps_u1" is encountered.

Common Use Cases and Queries

Typical usage centers on inspecting or auditing how iRep classes consume maps, validating display ordering, and confirming edition-scoped uniqueness. A straightforward query returns the full row set:

• SELECT CLASS_ID, MAP_USED, DISPLAY_SEQ, ZD_EDITION_NAME FROM APPLSYS.FND_IREP_USES_MAPS;
• Filter by class to list all maps used by a class, ordered by DISPLAY_SEQ.
• Join to the edition column to isolate rows belonging to a specific edition during patching or upgrade analysis.
• Verify that FND_IREP_USES_MAPS_U1 enforces one map entry per class per edition.

Because the table is standalone with no documented outbound references, reporting typically presents it as a lookup joined externally on CLASS_ID or MAP_USED rather than through enforced foreign keys.

Related Objects

The documented dependency data indicates that APPLSYS.FND_IREP_USES_MAPS does not reference any database object, but it is referenced by APPLSYS.FND_IREP_USES_MAPS#, the editioning infrastructure object associated with the base table. Beyond this, related objects are inferred from the shared iRep configuration domain:

• APPLSYS.FND_IREP_USES_MAPS# — the editioning view/object associated with the base table.
• Index FND_IREP_USES_MAPS_U1 (APPS_TS_TX_IDX) on (CLASS_ID, ZD_EDITION_NAME).
• Index FND_IREP_USES_MAPS_PK (APPS_TS_TX_IDX) on (MAP_USED, CLASS_ID).
• iRep class and map definition tables sharing the CLASS_ID and MAP_USED domains.

These objects should be joined on CLASS_ID and MAP_USED when assembling iRep diagnostic and flow reports.