Search Results cn_imp_map_fields_n1

Overview

CN.CN_IMP_MAP_FIELDS is a transactional configuration table in the Oracle E-Business Suite Channel Partner (CN) product family. It stores the detailed, column-level mapping definitions between an inbound user data file and the target importing modules that consume that data. Where the parent mapping header defines the overall import context, CN_IMP_MAP_FIELDS decomposes each mapping into discrete field-to-field relationships, specifying which source column in the flat file corresponds to which column in a target database table or object.

Within Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace and is registered as a valid, key Flexfield-enabled object under the CN schema. Its physical design includes standard WHO audit columns, a descriptive flexfield (DFF) via ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15, and an OBJECT_VERSION_NUMBER for optimistic locking, all of which are consistent with a maintained application entity rather than a transient staging object.

The metadata's heuristic Data Vault classification is standalone, meaning the table is not modeled as a strict hub, link, or satellite. From a dimensional modeling perspective, it behaves most like a line-level satellite of the parent import-map header, capturing the descriptive detail rows that belong to a single mapping definition.

Key Information Stored

The row identifier is IMP_MAP_FIELD_ID, a NUMBER(15) surrogate primary key. This column is the sole business-key candidate documented in the physical schema and is enforced by the unique index CN_IMP_MAP_FIELDS_U1, which is the exact object name referenced in the user's search. The unique index is created on the APPS_TS_TX_IDX tablespace.

• IMP_MAP_FIELD_ID — surrogate primary key; uniquely identifies each mapping field row.
• IMP_MAP_ID — foreign key back to the parent import-map header, linking each field definition to its owning mapping.
• SOURCE_COLUMN — the column number or position of the field within the incoming data file.
• SOURCE_USER_COLUMN — the user-facing column name from the data file, used for readable mapping.
• TARGET_TABLE_NAME — the database table the source column is loaded into.
• TARGET_COLUMN_NAME — the destination column in that target table.
• TARGET_TABLE_ID — internal reference to the target table in CN_OBJECTS_ALL.
• TARGET_OBJECT_ID — internal reference to the target object in CN_OBJECTS_ALL.
• OBJECT_VERSION_NUMBER — supports concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for extension.
• SECURITY_GROUP_ID — enforces multi-tenant/operating-unit level access, referencing FND_SECURITY_GROUPS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit trail.

Common Use Cases and Queries

This table is primarily consulted by import and conversion routines to resolve how an uploaded file maps into Oracle tables. Typical scenarios include diagnosing why a column loaded into the wrong target, auditing mapping definitions before a bulk import, and reporting on configured mappings.

A common query pattern reconstructs the full field mapping for a given header:

• SELECT SOURCE_USER_COLUMN, TARGET_TABLE_NAME, TARGET_COLUMN_NAME FROM CN_IMP_MAP_FIELDS WHERE IMP_MAP_ID = :p_map_id ORDER BY SOURCE_COLUMN;
• Lookup by the unique key: SELECT * FROM CN_IMP_MAP_FIELDS WHERE IMP_MAP_FIELD_ID = :p_id;
• Mapping inventory for a target table: SELECT IMP_MAP_ID, TARGET_COLUMN_NAME FROM CN_IMP_MAP_FIELDS WHERE TARGET_TABLE_NAME = :p_table;
• Row count per mapping: SELECT IMP_MAP_ID, COUNT(*) FROM CN_IMP_MAP_FIELDS GROUP BY IMP_MAP_ID;

Related Objects

• CN_IMP_MAP_HEADERS (or the parent mapping header) — joined via IMP_MAP_ID, provides the mapping's name and context.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for access control.
• CN_OBJECTS_ALL — resolves TARGET_TABLE_ID and TARGET_OBJECT_ID to concrete object definitions.
• CN_IMP_MAP_FIELDS_U1 — unique index on IMP_MAP_FIELD_ID, used by application lookups and by the user's original search.
• CN_IMP_MAP_FIELDS_N1 — non-unique index on IMP_MAP_ID, supporting parent-child joins.