Search Results cndisl_slice_attributes_pkg

Overview

The APPS.CNDISL_SLICE_ATTRIBUTES_PKG package body is a component of the Oracle E-Business Suite (EBS) Enterprise Territory Management (ETRM) module, which is delivered under the APPS schema. The package provides the core procedural logic for managing the attributes that define how sales "slices" and their associated fields are resolved and populated during territory definition and assignment processing. In the ETRM data model, a slice represents a logical grouping of dimension attributes and columns used to qualify territories; the CNDISL_SLICE_ATTRIBUTES_PKG automates the creation, population, and maintenance of rows that map these slice attributes to the underlying column metadata.

The package is classified as OTHER in the ETRM API catalog, indicating that it is an internal support package rather than a public, editioned API intended for customer extension. Its object status is VALID, and it is not referenced by any other database object, confirming that it is a leaf-level utility package invoked directly by ETRM application code. This behavior is consistent across both EBS 12.1.1 and 12.2.2 releases, where ETRM continues to rely on a layered set of PL/SQL packages to drive territory and slice configuration. The user search term cn_column_maps_s corresponds directly to one of the primary tables this package depends upon, underscoring the package's role in column-mapping driven attribute resolution.

Key Procedures and Functions

The package exposes four documented procedures. Metadata does not publish explicit parameter signatures, so only purposes are described below.

• DEFAULT_ROWS — Seeds or initializes default slice attribute rows for a given slice or object context. This routine is typically responsible for establishing the baseline set of attribute-to-column mappings so that subsequent population steps have a working template.
• POPULATE_FIELDS — Derives and populates the field-level attribute values for slices by joining slice definitions against the column map and object-column view metadata. It is the principal routine for materializing the fields that territory qualification rules will later evaluate.
• INSERT_ROW — Adds a new slice attribute record, ensuring the composite key relationships to the slice, object, and column mapping are maintained.
• DELETE_ROW — Removes an existing slice attribute record when a slice's configuration changes or when a slice is being rebuilt or purged.

Together, these procedures form a complete create/delete/populate lifecycle for slice attribute records, allowing the ETRM engine to keep slice metadata synchronized with the underlying column map definitions.

Tables Accessed

The package references the following tables and views, resolved through APPS synonyms:

• CN_COLUMN_MAPS — The base table holding column-mapping definitions. It supplies the authoritative list of columns that can participate in territory qualification.
• CN_COLUMN_MAPS_S — The corresponding "_S" (sequential/translations or surrogate-key) companion table, accessed during INSERT and DELETE operations to preserve referential integrity.
• CN_OBJECTS_S — The objects definition table, providing the object context (for example, customer, opportunity, or resource objects) to which slice attributes are attached.
• CN_OBJ_COLUMNS_V — A view that exposes the intersection of objects and their available columns, used by POPULATE_FIELDS to enumerate candidate attributes.
• DUAL — The standard Oracle one-row pseudo-table, used for scalar evaluations and sequence-style lookups within the PL/SQL logic.

Writes are directed at the slice attribute and column-map companion tables, while CN_OBJ_COLUMNS_V and CN_OBJECTS_S are read to drive derivation logic.

Usage Notes

CNDISL_SLICE_ATTRIBUTES_PKG is an internal ETRM package and is not typically invoked directly by customer customizations. It is called by higher-level ETRM slice and territory configuration logic — for example, when a territory administrator defines or modifies a slice in the ETRM administrative forms, or when a concurrent process rebuilds territory qualification structures. Because the package is VALID and referenced by no other database object, its execution is driven exclusively by ETRM application code paths rather than by external dependencies.

Developers troubleshooting slice attribute problems (frequently surfaced by searching for cn_column_maps_s) should verify the integrity of CN_COLUMN_MAPS, CN_COLUMN_MAPS_S, and CN_OBJ_COLUMNS_V for the affected object before assuming a package defect. Direct invocation of INSERT_ROW, DELETE_ROW, DEFAULT_ROWS, or POPULATE_FIELDS from custom code is unsupported, as these routines assume the surrounding ETRM transaction and validation context.