Search Results cn_rate_dimensions_pkg




Overview
Explore in AI Chat

Overview

CN_RATE_DIMENSIONS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is a component of the Oracle Trade Management (formerly Contracts) module, referenced under the CN product short name. The package provides the low-level data access and maintenance layer for rate dimension definitions used by the Trade Management pricing and rate engine. Rate dimensions represent the configurable attributes (such as volume, weight, value, or other qualifiers) against which rate tiers and rate schedules are evaluated during pricing, accrual, and settlement calculations. The package is classified as OTHER in the ETRM API registry rather than as a public or private API, indicating that it is intended principally for internal consumption by the Trade Management data model rather than as a formally published integration interface. Its status is recorded as VALID in ETRM 12.2.2. As a table maintenance package it encapsulates the create, read, update, and delete operations that keep the persistent rate dimension records synchronized with transactional and setup activity in the pricing subsystem.

Key Procedures and Functions

The documented interface consists of four procedures that implement the standard Oracle Forms-style table handler pattern:

  • INSERT_ROW — Creates a new rate dimension record. It is responsible for populating the persistent rate dimension tables with a newly defined dimension, including the associated translated description columns, as part of the save cycle.
  • LOCK_ROW — Acquires and validates a row lock against an existing rate dimension record. It is used to serialize concurrent modifications and to confirm that the row identified by the caller still exists and is eligible for update or deletion.
  • UPDATE_ROW — Applies modifications to an existing rate dimension record, writing changed attribute values and translated description columns back to the underlying tables within the current transaction.
  • DELETE_ROW — Removes an existing rate dimension record, optionally cascading related tier and translated description rows, so that the dimension is no longer available to the pricing and rating engine.

The package contains no other documented procedures or functions in the ETRM metadata. No parameter lists are documented; callers should refer to the package specification in the target release before invoking these procedures directly.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • CN_RATE_DIMENSIONS — The base table holding rate dimension definitions. This is the principal target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW and the subject of LOCK_ROW.
  • CN_RATE_DIMENSIONS_S — The translation (secondary) table holding language-specific description columns for each rate dimension. It is maintained alongside the base table on insert, update, and delete.
  • CN_RATE_DIM_TIERS — The tier table associated with rate dimensions. The package references it to keep tier definitions consistent with their parent dimension, particularly on deletion.
  • DUAL — The standard Oracle single-row utility table, used for lightweight validation queries and default value retrieval within the package logic.

In addition to the tables listed above, the package depends on CN_API for shared Trade Management processing, on FND_GLOBAL for application context such as user and responsibility identifiers, and on the SYS.STANDARD package. The package itself does not appear to modify other functional tables directly.

Usage Notes

CN_RATE_DIMENSIONS_PKG is referenced by one other package, CN_RATE_DIMENSIONS_PVT, which is the private API layer that higher-level Trade Management components call. In typical deployments the package is invoked indirectly: Oracle Forms setup or pricing responsibility forms call the PVT layer, which in turn delegates row-level DML to this package. It is therefore unusual for a form or concurrent program to call CN_RATE_DIMENSIONS_PKG procedures directly. Custom code that does so should respect the same transactional boundaries as the PVT layer, acquiring locks via LOCK_ROW before attempting modification, and should assume that insert, update, and delete operations also maintain the translation and tier tables. Because the package is classified as OTHER rather than a committed public API, Oracle does not guarantee backward compatibility of its signature across patches; customizations should be revalidated after applying Trade Management patch sets or upgrading from 12.1.1 to 12.2.2.