Search Results cndisl_slice_def_dim_pkg




Overview
Explore in AI Chat

Overview

APPS.CNDISL_SLICE_DEF_DIM_PKG is a PL/SQL package that forms part of the Oracle E-Business Suite (EBS) Contracts Intelligence / Contract Document Intelligence layer that is deployed with the Enterprise Technical Reference Model (ETRM) stack. In EBS 12.1.1 and 12.2.2 this package resides in the APPS schema and carries a VALID status, indicating that it is compiled and available for use at runtime. Its name, combining "SLICE_DEF" (slice definition) and "DIM" (dimension), indicates its role in supporting the definition and population of dimensional slices used by Contracts Intelligence reporting and analytics. Slices are the mechanism by which Contracts Intelligence organizes contract-related fact data across configured dimensions so that downstream reporting, extraction, and analysis can be performed consistently. This package therefore provides the persistence layer for slice definition rows referencing dimension and column mapping metadata. The dependency report confirms that it references only the SYS.STANDARD package directly at the dependency level, while its documented object metadata confirms that it operates against Contracts Intelligence configuration tables through APPS synonyms.

Key Procedures and Functions

The ETRM documentation records four procedures or functions within this package. Their documented purposes are as follows:

  • DEFAULT_ROWS — Responsible for establishing or resetting default slice definition dimension rows, providing the baseline dimensional configuration that subsequent processing relies upon.
  • POPULATE_FIELDS — Populates field values on slice definition dimension records, deriving or copying column-level attributes that define how dimensional slices map to their underlying data.
  • INSERT_ROW — Inserts a new slice definition dimension row, creating the persistent record that describes a dimensional slice configuration.
  • DELETE_ROW — Removes an existing slice definition dimension row, supporting maintenance and cleanup of dimensional slice definitions.

No parameter lists are documented in the ETRM metadata, and none are asserted here. The set of procedures collectively implements a standard create-read-update pattern for slice definition dimension data, with DEFAULT_ROWS and POPULATE_FIELDS handling initialization and attribute derivation while INSERT_ROW and DELETE_ROW handle lifecycle persistence.

Tables Accessed

The documented tables referenced by this package via APPS synonyms are:

  • CN_COLUMN_MAPS — The Contracts Intelligence column map definition table, which defines how source columns map to contract intelligence structures. The package reads and/or writes these records when populating slice dimension fields.
  • CN_COLUMN_MAPS_S — The corresponding secondary (translation or non-translated) table for column maps, accessed where language-dependent or secondary attribute data is required.
  • CN_DIMENSIONS — The dimension definition table that defines the dimensional model used by Contracts Intelligence; slice definitions reference dimension identifiers from this table.
  • CN_OBJECTS_S — The secondary objects table, providing the object-level metadata (such as object identifiers and names) associated with slice definitions.
  • DUAL — The standard Oracle single-row pseudo-table, typically used for validation, sequence value retrieval, or single-row selection constructs within the package's procedures.

Usage Notes

CNDISL_SLICE_DEF_DIM_PKG is an internal utility package within the Contracts Intelligence application and is not exposed as a public API for general customer extension. It is typically invoked by the Contracts Intelligence configuration and administrative layer when slice definitions are created, modified, or refreshed — for example, during setup of dimensional slice definitions that feed Contracts Intelligence extraction and reporting processes. It may be called from EBS forms, concurrent programs, or other PL/SQL packages belonging to the Contracts Intelligence product family. Because the ETRM records show zero packages referencing it directly, callers are most likely forms-based or concurrent-processing components rather than other documented PL/SQL APIs. Any custom code extending Contracts Intelligence should treat this package as internal, invoke it only in accordance with Oracle-supported configuration flows, and avoid direct modification of its underlying CN_ tables outside those flows to preserve data integrity.