Results for “cn_imp_map_fields”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CN_IMP_MAP_FIELDS is a table owned by the CN schema within the Oracle Incentive Compensation module of Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). Its documented purpose is to store the detailed information describing mappings between a user-supplied data file and the importing modules that consume that data. In practical terms, this is the metadata layer that tells the Incentive Compensation import engine which source column in a user's flat file corresponds to which target column in which target table during a load or conversion.

The table is documented as having 31 columns and a single unique index, CN_IMP_MAP_FIELDS_U1, defined on IMP_MAP_FIELD_ID. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning no natural parent-child dependency chains were detected through foreign keys. As a modeling suggestion, this object is best treated as a reference or configuration artifact rather than a true Data Vault hub, link, or satellite; if modeled, it would most plausibly be a satellite-like descriptive record keyed by the surrogate identifier. Its role is administrative and structural: it governs how inbound incentive data is interpreted, not the incentive results themselves.

Key Information Stored

The columns below are the most significant of the 31 documented attributes:

• IMP_MAP_FIELD_ID — the surrogate primary key and the sole documented unique business-key candidate via index CN_IMP_MAP_FIELDS_U1.
• IMP_MAP_ID — the parent mapping identifier linking this field-level definition to its owning import mapping header.
• SOURCE_COLUMN and SOURCE_USER_COLUMN — the source-side column name and the user-facing label as it appears in the incoming data file.
• TARGET_TABLE_NAME and TARGET_COLUMN_NAME — the destination table and column receiving the mapped value.
• TARGET_TABLE_ID and TARGET_OBJECT_ID — surrogate references to the target table and object metadata, used for internal resolution.
• OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) column set for extensible mapping attributes.
• SECURITY_GROUP_ID — the multi-tenant security grouping key; this is the only foreign key on the table, referencing FND_SECURITY_GROUPS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-column audit set.

Common Use Cases and Queries

Typical usage centers on diagnosing and auditing import configurations. Administrators investigate why a column failed to load, confirm that a target column is mapped, or replicate a working mapping across environments.

• List all mappings for a given import mapping header: SELECT source_column, target_table_name, target_column_name FROM cn.cn_imp_map_fields WHERE imp_map_id = :p_map_id ORDER BY imp_map_field_id;
• Locate where a specific target column is populated: SELECT imp_map_id, source_column FROM cn.cn_imp_map_fields WHERE target_table_name = :p_table AND target_column_name = :p_column;
• Audit recent configuration changes using the who-columns: SELECT imp_map_field_id, last_updated_by, last_update_date FROM cn.cn_imp_map_fields WHERE last_update_date > SYSDATE - 30;
• Query DFF extensions: filter on attribute_category to surface mappings carrying custom descriptive attributes.

Report consumers should note that this table is configuration metadata; it should be joined to mapping headers by IMP_MAP_ID rather than treated as transactional incentive data.

Related Objects

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; join cn_imp_map_fields.security_group_id = fnd_security_groups.security_group_id to resolve security grouping.
• CN_IMP_MAP (import mapping header) — the logical parent, joined on IMP_MAP_ID.
• CN_IMP_MAP_FIELDS unique index CN_IMP_MAP_FIELDS_U1 — enforces the surrogate key.
• CN import APIs and concurrent programs in the Incentive Compensation module that read these mappings during data-file loading.
• FND_OBJECTS / target object metadata — referenced conceptually through TARGET_OBJECT_ID and TARGET_TABLE_ID for target resolution.
• FND_TABLES — resolves TARGET_TABLE_NAME and TARGET_TABLE_ID to physical table definitions.

Because the documented FK structure is standalone, joins to header-level tables are maintained through application logic and the IMP_MAP_ID column rather than enforced referential constraints.