Search Results ams_dm_bin_values_pkg




Overview
Explore in AI Chat

Overview

AMS_DM_BIN_VALUES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Marketing (AMS) module and more specifically the Advanced Product Catalog / Marketing Data Mining (DM) subsystem. In release 12.1.1 and 12.2.2 the package is classified under the generic API classification OTHER, indicating it is a low-level table-handling package rather than a public, interface-oriented API. Its role is to provide the standard insert, update, delete, and lock operations against the AMS_DM_BIN_VALUES table, which stores bin definitions used in data-mining and source-field bucketing logic. Bins allow marketing users to group continuous numeric source-field values into discrete ranges (for example, customer income bands or transaction amount tiers) so that analytical models, campaign selection criteria, and list-generation queries can operate on meaningful segments rather than raw values. The package therefore acts as the persistence layer that keeps these bin definitions consistent within the marketing data model. The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than the definer; concurrent programs and forms that call it therefore require the appropriate grants on the underlying table and on the package itself. The header comment carries a 2002 date and a "noship" designation, reflecting that this is an old-style, internally generated table handler that has remained functionally stable across releases.

Key Procedures and Functions

The documented interface consists of four procedures, all following the conventional generated table-handler pattern used throughout Oracle Applications:

  • Insert_Row — Creates a new bin value record in AMS_DM_BIN_VALUES. It supplies the full column set, including the primary key bin_value_id, the WHO audit columns (last_update_date, last_updated_by, creation_date, created_by, last_update_login), the object_version_number used for optimistic locking, and the functional attributes source_field_id, bucket, bin_value, start_value, and end_value. The primary key and version number are passed as IN OUT NOCOPY parameters so that the procedure can return the generated values to the caller.
  • Update_Row — Modifies an existing bin value record identified by its bin_value_id, writing the same audit, version, and functional columns as Insert_Row. It is the standard mechanism for changing bin boundaries, labels, or their associated source field or bucket assignment.
  • Delete_Row — Removes a single bin value record, identified solely by the BIN_VALUE_ID primary key.
  • Lock_Row — Acquires a row-level lock on the specified bin value record and validates the current column values, including object_version_number, to support optimistic concurrency control. This prevents lost updates when multiple sessions attempt to modify the same bin definition.

Tables Accessed

The package operates exclusively against AMS_DM_BIN_VALUES, referenced through the APPS synonym layer. Insert_Row and Update_Row write the complete row image; Delete_Row removes it by primary key; Lock_Row performs a SELECT ... FOR UPDATE with a version check. The table holds the bin definitions, each linked via source_field_id to the marketing source field it qualifies, organized by bucket, and bounded by start_value and end_value. No other tables are documented as being accessed by this package.

Usage Notes

As a generated, non-shipped (noship) table handler, AMS_DM_BIN_VALUES_PKG is not intended as a public integration API. It is typically invoked by Oracle Marketing forms and concurrent programs that maintain bin definitions, and by one other documented package that depends on it, rather than being called directly from external interfaces. Customizations that need to maintain bins should normally go through the supported Oracle Marketing user interface; where direct PL/SQL access is unavoidable, callers must respect the audit columns, the object_version_number contract, and the Lock_Row pattern to avoid data corruption and concurrency errors. Because the package uses AUTHID CURRENT_USER and carries an old header revision, developers should verify grants and avoid assuming behavior beyond the four documented procedures, since the metadata exposes no additional public functions.