Search Results genp_get_lookup




Overview
Explore in AI Chat

Overview

APPS.IGS_CO_MAPPING_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the Applications (APPS) schema. It exposes configuration data that maps content items to correspondence/document handling within the Oracle iLearning and content management (IBC) framework. The view resolves internal coded values into human-readable lookup descriptions, presenting an administrator-friendly representation of the IGS_CO_MAPPING base records alongside their associated content item metadata.

The view is of particular relevance to the ibc_query content type, as the first query branch is explicitly filtered on CTYPE_CODE = 'IBC_QUERY' and MAP_CODE = 'LIST'. This makes the view a key source for applications, concurrent programs, and BI Publisher reports that need to surface the mapping between a query-type content item and its live version. Because the view performs language-aware filtering, only content items matching the current session language (USERENV('LANG')) are returned.

Underlying Base Objects

The ETRM metadata indicates that no base objects are formally documented; however, the view text itself references three objects in its defining SELECT statement:

  • IGS_CO_MAPPING CMAP — the primary mapping table holding map codes, document references, enable flags, system letter codes, and scheduling attributes.
  • IBC_CITEMS_V CITM — a content item view supplying names, descriptions, version identifiers, and content type codes for the mapped document.
  • IBC_CONTENT_ITEMS CONITEM — the underlying content item table used to correlate the content item ID with its live content item version (via LIVE_CITEM_VERSION_ID).

The view also invokes the PL/SQL function IGS_GE_GEN_004.GENP_GET_LOOKUP three times to decode MAP_CODE, DOC_CODE, and SYS_LTR_CODE into descriptive lookup values. Because the definition is a UNION ALL of two similarly structured branches, care should be taken when writing queries against it, as row counts may effectively double if both branches qualify.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing correspondence mappings, verifying which query content types are enabled for email/fax/print distribution, and joining content item names to their delivery configuration.

SELECT MAP_ID, MAP_CODE, MAP_TYPE, DOCUMENT_ID,
       NAME, DESCRIPTION, ENABLE_FLAG,
       APPLICATION_NAME, EMAIL, FAX, PRINT
  FROM APPS.IGS_CO_MAPPING_V
 WHERE MAP_CODE = 'LIST'
   AND ENABLE_FLAG = 'Y';

To locate mappings associated with the ibc_query content type specifically:

SELECT MAP_ID, DOCUMENT_ID, NAME, VERSION_ID, DOCUMENT_TYPE
  FROM APPS.IGS_CO_MAPPING_V
 WHERE DOCUMENT_ID IN
       (SELECT CITEM_ID FROM IBC_CITEMS_V WHERE CTYPE_CODE = 'IBC_QUERY');

Because the view performs language filtering and returns only live content item versions, it is well suited for runtime lookups and reporting where accuracy of the active version is essential. When querying, always filter on MAP_CODE or ENABLE_FLAG to limit the UNION ALL branches and improve performance.