Results for “select_row”

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

Overview

The APPS.CN_COLUMN_IND_MAPS_PKG package body is a component of the Oracle E-Business Suite Channel Revenue Management (CN) module, specifically within the territory and quota management subsystem that governs how sales credit and incentive compensation are calculated and allocated across channels, columns, and territories. The package functions as a low-level data access utility that encapsulates the DML operations for the CN_COLUMN_IND_MAPS table, which stores the mapping relationships between columns and industry or segment classifications used in the channel management and territory assignment model.

Its operational role is to provide a controlled, reusable interface for inserting and retrieving column mapping records, shielding callers from direct manipulation of the underlying base tables. In the 12.1.1 and 12.2.2 releases this package is documented with API classification OTHER, indicating that it is an internal implementation object rather than a public, downward-compatible integration API intended for external development.

Key Procedures and Functions

The ETRM metadata documents two procedures on this package body:

• INSERT_ROW — Creates a new record in the column indicator mapping table. This procedure is the designated mechanism for establishing a mapping between a channel management column and its associated indicator, populating the CN_COLUMN_IND_MAPS entity with the required key and attribute values supplied by the calling process.
• SELECT_ROW — Retrieves a single mapping record from the same table. This procedure returns the attributes of a specified column indicator mapping so that dependent logic can resolve which indicator applies to a given column configuration.

No parameter lists are published in the available metadata, and no additional procedures or functions are documented beyond these two. Consumers should treat both as internal entry points invoked by higher-level channel management logic rather than as a stable public interface.

Tables Accessed

The package operates against the following tables, resolved through APPS synonyms:

• CN_COLUMN_IND_MAPS — The primary table read and written by INSERT_ROW and SELECT_ROW. It holds the column-to-indicator mapping definitions that drive territory and channel classification logic.
• CN_COLUMN_TRG_MAPS — A related mapping table referenced as part of the package's dependency set, supporting column-to-target associations used together with indicator mappings.
• CN_OBJECTS_S — The Channel Revenue Management object sequence, referenced as a dependency. This is the object most commonly associated with the user's search term and supplies unique identifier generation for CN entities. Note that in Oracle EBS, sequences are conventionally named with an _S suffix; the presence of CN_OBJECTS_S in the dependency list indicates the package obtains surrogate keys during insert operations.
• DUAL — The standard Oracle single-row utility table, used for scalar evaluation and sequence access within the package body.

Oracle's standard package STANDARD under the SYS schema is also listed as a dependency, reflecting normal PL/SQL runtime linkage. The package does not reference or depend on any application-level tables outside the CN schema.

Usage Notes

CN_COLUMN_IND_MAPS_PKG is not referenced by any other database object, according to the documented dependency analysis. Its callers are therefore not exposed through the object dependency view, which commonly indicates invocation from external or dynamically compiled code paths — notably Oracle Forms user exits, concurrent program PL/SQL blocks, or server-side triggers that reference the procedures by name at runtime rather than through compiled dependencies.

The package is typically invoked during channel management setup and maintenance activities, when administrators define or adjust the column indicator mappings that feed territory assignment and incentive calculation. Because it is classified as OTHER rather than a public API, it should not be called directly from customer extensions; instead, use the supported Channel Revenue Management setup forms and concurrent programs. Any modification to the package should be treated as a patch-level change applied through standard EBS patching, and the package body should be recompiled following Oracle's documented recompilation procedures to preserve VALID status in both 12.1.1 and 12.2.2 environments.