Search Results cn_imp_maps




Overview
Explore in AI Chat

Overview

CN_IMP_MAPS is a transactional configuration table within the Oracle Incentive Compensation (CN) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. The table stores mapping definitions that associate user-supplied import data files with the corresponding Incentive Compensation import modules. In practical terms, it is the repository that tells the import engine which columns of an inbound flat file or staging source align with which target attributes during a compensation data load. This mapping metadata is essential for repeatable, template-driven imports of participant, transaction, and credit data into Incentive Compensation.

From a Data Vault modeling perspective, the metadata classifies CN_IMP_MAPS as standalone. This heuristic classification suggests that, in a derived analytical model, the table is best treated as a descriptive reference entity rather than a link or satellite. It carries its own surrogate identifier and a natural business key, and it does not participate in a hub-to-hub relationship pattern. Its single foreign key to FND_SECURITY_GROUPS introduces a security dimension rather than a transactional association, further reinforcing the standalone interpretation.

Key Information Stored

The table contains 26 documented columns. The most significant are summarized below.

  • IMP_MAP_ID — the surrogate primary key, enforced by the unique index CN_IMP_MAPS_U1. It uniquely identifies each mapping definition.
  • NAME — the natural business-key candidate, enforced by the unique index CN_IMP_MAPS_U2. It provides the human-readable identifier by which an administrator selects a mapping.
  • IMPORT_TYPE_CODE — indicates which import module or import category the mapping serves, driving which loading logic consumes the mapping.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, controlling which security group owns or may access the mapping.
  • OBJECT_VERSION_NUMBER — supports optimistic locking and change detection during concurrent maintenance.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexfield attribute set, available for descriptive or extensible use.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified each mapping row and when.

The distinction between IMP_MAP_ID and NAME is important: the surrogate key is used for internal referential integrity, whereas NAME is the business-facing identifier that users and import processes reference.

Common Use Cases and Queries

Administrators and implementers typically query CN_IMP_MAPS to inventory the mappings configured for each import type, to verify that a mapping exists before running an import, and to audit the security group and audit trail of each definition.

  • Listing all mappings for a given import module: SELECT imp_map_id, name FROM cn_imp_maps WHERE import_type_code = :p_type;
  • Retrieving a specific mapping by business key: SELECT * FROM cn_imp_maps WHERE name = :p_name;
  • Auditing recent changes: SELECT name, last_update_date, last_updated_by FROM cn_imp_maps ORDER BY last_update_date DESC;
  • Reporting mappings by security group, joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID.

These queries support configuration baselines, migration verification between environments, and troubleshooting when an import fails to locate an expected mapping.

Related Objects

The principal documented relationship is the foreign key from SECURITY_GROUP_ID to FND_SECURITY_GROUPS, which governs access to mapping definitions. Because the metadata classifies the table as standalone, no other foreign keys are documented. In practice, CN_IMP_MAPS is referenced conceptually by the Incentive Compensation import processes and by the staging interfaces that consume its definitions at run time. Administrators should therefore treat FND_SECURITY_GROUPS as the primary join partner and consult the CN import module documentation for the runtime processes that read these mappings.