Results for “order_flag”

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

Overview

CN_COLUMN_IND_MAPS is a table owned by the CN schema within the Oracle E-Business Suite Incentive Compensation module. The ETRM documentation for both release 12.1.1 and 12.2.2 explicitly describes this object as "Not currently used." It exists within the physical schema as a valid, deployed table with eleven documented columns, but Oracle does not populate or reference it through any active application logic. Its presence in the database is therefore vestigial — retained for schema consistency and potential backward compatibility rather than for operational functionality.

Based on the foreign key structure and the heuristic Data Vault classification mined from the metadata, this object is best modeled as a standalone entity rather than a hub, link, or satellite. The classification reflects the absence of inbound referential relationships: the table references other objects but is not itself referenced, which is consistent with an unused or deprecated structure. Administrators and developers should treat CN_COLUMN_IND_MAPS as non-authoritative and avoid building dependencies upon it, since Oracle may remove or alter it without notice in future releases.

Key Information Stored

The documented physical schema contains eleven columns. The most significant structural elements are:

• COLUMN_IND_MAP_ID — A surrogate identifier column present in the physical schema. Although it is not part of the declared primary key, it functions as a unique row identifier in practice.
• COLUMN_ID and INDEX_ID — The composite business-key columns forming the primary key CN_COLUMN_IND_MAPS_PK. Together they define the uniqueness constraint on the table, suggesting the object was originally intended to associate an index definition with one of its constituent columns.
• ORDER_FLAG and COLUMN_POSITION — Positional and ordering attributes, indicating the table was designed to record the sequence in which columns participate within an index.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, providing the standard multi-tenant data isolation used throughout EBS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard Oracle EBS audit trail columns present on nearly all transactional and setup tables.

The distinction between the surrogate identifier (COLUMN_IND_MAP_ID) and the documented composite primary key (COLUMN_ID, INDEX_ID) indicates the table was modeled for index-column mapping purposes, though no active code path exercises this design.

Common Use Cases and Queries

Because the object is documented as unused, there are no supported business scenarios that query it. Any exploration should be confined to diagnostic or migration-audit contexts, such as determining whether legacy data remains from an earlier release or verifying that no custom code references the table. The following patterns are representative:

• Row-count and data-presence checks: SELECT COUNT(*) FROM CN.CN_COLUMN_IND_MAPS;
• Audit-trail inspection to identify any historical inserts: SELECT CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM CN.CN_COLUMN_IND_MAPS ORDER BY CREATION_DATE;
• Dependency analysis before decommissioning, confirming that no custom objects or views reference the table.

Reporting use cases do not exist for this object, and no seeded concurrent programs or Oracle-delivered reports depend on it.

Related Objects

The only documented referential relationship is the foreign key from SECURITY_GROUP_ID to FND_SECURITY_GROUPS, which anchors the table within the standard EBS security-group framework. Beyond this, the most relevant related objects are structural rather than functional:

• FND_SECURITY_GROUPS — Referenced via CN_COLUMN_IND_MAPS.SECURITY_GROUP_ID; supplies the security group context for any rows.
• CN_COLUMN_IND_MAPS_PK — The primary key constraint enforcing uniqueness on COLUMN_ID and INDEX_ID.

No other CN incentive compensation tables, views, or public APIs are documented as referencing CN_COLUMN_IND_MAPS. Given its unused status and standalone classification, the table should be treated as isolated metadata with no operational dependencies.