Results for “cn_column_trg_maps”

44 results




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

Overview

CN_COLUMN_TRG_MAPS is a table residing in the CN schema, which is owned by the Oracle Incentive Compensation (CN) product module. According to the official ETRM documentation metadata for release 12.2.2, the object is marked as VALID but is described as "Not currently used." This status indicates that the table is a legacy or vestigial structure that persists in the data dictionary to maintain schema integrity and backward compatibility, even though the application logic in current Oracle EBS versions (12.1.1 and 12.2.2) does not actively write to or read from it.

The table contains nine documented columns and is defined by the primary key CN_COLUMN_TRG_MAPS_PK, which is a composite key consisting of COLUMN_ID and TRIGGER_ID. The heuristic Data Vault classification, mined from the foreign key structure, identifies this object as "standalone." In a Data Vault modeling context, this suggests the table functions as an independent hub or reference structure without direct link relationships to other hubs within the modeled scope, though it maintains a foreign key reference to FND_SECURITY_GROUPS.

Key Information Stored

The most significant columns within CN_COLUMN_TRG_MAPS define its intended purpose as a mapping mechanism between columns and triggers, likely for dynamic UI or processing logic. The primary key is composite, comprising COLUMN_ID and TRIGGER_ID. These two columns serve as the business-key candidates that uniquely identify a mapping record, preventing duplicate associations between a specific column and its corresponding trigger.

Beyond the composite key, the table includes a surrogate identifier, COLUMN_TRG_MAP_ID, which provides a single-column unique reference for the mapping entry. The table also maintains standard Oracle EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These columns track the user and timestamp for both the initial insertion and any subsequent modifications. Additionally, SECURITY_GROUP_ID is present as a foreign key referencing FND_SECURITY_GROUPS, indicating that the mapping records were intended to be scoped by security group, a common requirement in multi-tenant or multi-org enabled environments. The presence of these columns confirms that the table was designed to be a standard, auditable transactional or setup entity within the EBS framework.

Common Use Cases and Queries

Because the ETRM metadata explicitly states the table is "Not currently used," there are no active application use cases, reporting requirements, or standard queries for this object in a production Oracle EBS environment. It should not be referenced in custom extensions, reports, or integrations, as doing so would rely on data that is neither maintained nor validated by the application.

From a purely investigative or historical perspective, a query might be constructed to inspect the structure and verify the absence of data. For example, a simple SELECT statement against COLUMN_ID and TRIGGER_ID would confirm whether any legacy mapping records remain. However, any such query should be executed only in a non-production or development instance. If historical data exists, joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID would reveal the security context of those entries, but this is strictly for forensic analysis of obsolete configurations.

Related Objects

The primary documented relationship for CN_COLUMN_TRG_MAPS is its foreign key reference to FND_SECURITY_GROUPS, joined on the SECURITY_GROUP_ID column. This dependency indicates that any historical mapping was subject to Oracle EBS security group partitioning.

The composite primary key suggests likely logical relationships to underlying column and trigger definition tables, though specific foreign keys to those parent entities are not documented in the provided metadata. In the broader CN module, related objects would include the trigger and column configuration tables that originally consumed these mappings, as well as the standard audit infrastructure (FND_USER for CREATED_BY and LAST_UPDATED_BY). Given its standalone Data Vault classification and unused status, CN_COLUMN_TRG_MAPS does not serve as a critical dependency for other active CN objects, and its foreign key to FND_SECURITY_GROUPS is the only confirmed structural relationship in the current EBS data model.