Search Results ams_dm_binvalues_pvt




Overview
Explore in AI Chat

Overview

APPS.AMS_DM_BINVALUES_PVT is a private (PVT) PL/SQL package body belonging to the Oracle E-Business Suite Marketing (AMS) module, specifically the Oracle Marketing or Advanced Product Catalog / Segmentation component that handles "bin values" used by the data-mining and direct-marketing list build logic. Within AMS, a "bin" represents a value bucket associated with a profile or scoring attribute in a data-mining model; the corresponding bin values define the discrete value ranges or coded values that are grouped into that bin. The package therefore serves as the internal implementation layer for the maintenance of these bin value definitions, providing the create, update, delete, lock, and validation routines that the public AMS_DM_BIN_VALUES_PKG wrapper exposes to the application. It is classified as a PVT API, meaning it is not intended for direct invocation by external consumers and is instead called by the AMS data-mining setup screens and the parent package.

Its status is recorded as VALID, and it resides in the APPS schema alongside the majority of EBS PL/SQL APIs, using the standard EBS API infrastructure for error handling and message resolution.

Key Procedures and Functions

The ETRM documentation lists eight documented program units within the package:

  • CREATE_DM_BINVALUES — Inserts a new bin value record into the AMS data-mining bin values repository, establishing the association between a bin and its underlying value.
  • UPDATE_DM_BINVALUES — Modifies an existing bin value record, typically when a bin's definition or display attributes change.
  • DELETE_DM_BINVALUES — Removes a bin value record from the repository.
  • LOCK_DM_BINVALUES — Obtains a row-level lock on the bin value record to serialize concurrent modifications during an update or delete operation.
  • VALIDATE_DM_BINVALUES — Performs business-rule validation on bin value data before it is persisted, checking required attributes and internal consistency.
  • CHECK_DM_BINVALUES_ITEMS — Evaluates whether specific items or dependent records exist for a bin value, effectively a referential-integrity precondition check.
  • VALIDATE_DM_BINVALUES_REC — Validates an individual bin value record, generally used as a reusable helper invoked from the main validation routine.
  • DELETE_DM_BINVALUES_FOR_FIELD — Deletes all bin value records associated with a particular field, supporting bulk cleanup when a field definition is removed or restructured.

The metadata does not document parameter lists, so signatures must be confirmed by inspecting the package specification in the target environment.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • AMS_DM_BIN_VALUES — The primary transactional table storing the bin value records created, updated, and deleted by the package.
  • AMS_DM_BIN_VALUES_S — The sequence used to generate unique primary keys for new bin value rows.
  • DUAL — Used for scalar evaluations and single-row queries common in validation routines.

The package also references AMS_DM_BIN_VALUES_PKG (the public wrapper), AMS_UTILITY_PVT, FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and JTF_PLSQL_API, reflecting adherence to the standard EBS API error-handling and message-framework conventions.

Usage Notes

As a PVT package, AMS_DM_BINVALUES_PVT is not intended to be called directly by external code. It is invoked by the public AMS_DM_BIN_VALUES_PKG, which in turn is called from the AMS data-mining setup forms and from concurrent or batch processes that populate or refresh bin definitions. The metadata states the package is referenced by two other packages, consistent with this layered design. Developers performing customizations or data migrations involving bin values should call the public wrapper (AMS_DM_BIN_VALUES_PKG) rather than this private body, and should use the FND message stack to retrieve errors raised through FND_MSG_PUB. Because the package writes to AMS_DM_BIN_VALUES, any direct manipulation should respect the same validation and locking sequence the API enforces.