Search Results delete_dm_binvalues

Overview

APPS.AMS_DM_BINVALUES_PVT is a private (PVT) PL/SQL package belonging to the Oracle Marketing (AMS) module of Oracle E-Business Suite. It supports the Oracle Marketing data-mining and binning infrastructure, specifically the maintenance of "bin values" — the discrete ranges or categorical buckets used to segment numeric or character data into bins for analytical processing, predictive modeling, and target-group selection. The package encapsulates the business logic that governs the lifecycle of rows in the binning configuration store.

The package is declared with AUTHID CURRENT_USER, and the header comment indicates that the package and its record type definitions were, in part, automatically generated from the underlying table definition. The record type dm_binvalues_rec_type mirrors the columns of the base bin-values entity, including identifiers (bin_value_id, source_field_id), audit columns (creation_date, created_by, last_update_date, last_updated_by, last_update_login, object_version_number), and the binning attributes (bucket, bin_value, start_value, end_value). Each attribute is initialized to the corresponding FND_API.G_MISS_* sentinel, the standard Oracle EBS convention that allows the API layer to distinguish "attribute not supplied" from "attribute explicitly set." The package constant G_DEFAULT_NUM_REC_FETCH is set to 30, reflecting the default bulk-fetch size used by the internal cursor logic.

Key Procedures and Functions

The ETRM metadata documents eight public program units. The user search term "delete_dm_binvalues" maps directly to the DELETE_DM_BINVALUES procedure, which is the primary maintenance routine for removing bin-value rows. Its companion, DELETE_DM_BINVALUES_FOR_FIELD, performs a mass removal of all bin values associated with a given source field.

The remaining documented procedures are:

• CREATE_DM_BINVALUES — Creates a new bin-value record from a populated dm_binvalues_rec_type, validating required attributes and applying audit defaults before insertion.
• UPDATE_DM_BINVALUES — Modifies an existing bin-value record; the G_MISS_* sentinel pattern ensures only supplied attributes are overwritten.
• DELETE_DM_BINVALUES — Deletes a specific bin-value record, typically by primary key, and enforces referential and concurrency checks.
• LOCK_DM_BINVALUES — Acquires a row-level lock on a bin-value record to prevent concurrent modification, supporting the optimistic locking model implied by object_version_number.
• VALIDATE_DM_BINVALUES — Performs entity-level validation of the bin-value record, checking required fields and attribute consistency.
• CHECK_DM_BINVALUES_ITEMS — Verifies that dependent child items exist and are consistent, guarding against orphaned references.
• VALIDATE_DM_BINVALUES_REC — A record-level validation routine that operates on the full dm_binvalues_rec_type structure rather than individual attribute values.

No parameter lists are documented in the ETRM metadata, and none are reproduced here.

Tables Accessed

The package references three objects through APPS synonyms:

• AMS_DM_BIN_VALUES — The base table holding bin-value definitions. All create, update, delete, and validation logic targets this entity.
• AMS_DM_BIN_VALUES_S — The corresponding sequence (or alternate key) object used to generate surrogate primary keys for new bin_value_id values.
• DUAL — Used for single-row computations and sequence next-value retrieval.

The presence of AMS_DM_BIN_VALUES_S confirms that CREATE_DM_BINVALUES obtains its key from a sequence rather than from MAX()+1 logic, consistent with standard EBS design.

Usage Notes

As a PVT package, AMS_DM_BINVALUES_PVT is not intended for direct invocation by external or customer code. It is called by the public wrapper package or API in the same product family, consistent with the metadata note that it is "referenced by 2 other packages." Typical invocation paths are Oracle Forms or OAF-based marketing configuration screens that let users define number ranges and list buckets, and Oracle Marketing concurrent programs or data-mining setup routines that generate bin definitions programmatically. Customers who need to manipulate bin values should invoke the public API layer, which in turn delegates to this private package; calling the PVT package directly bypasses no validation but is unsupported and may break in a future patch set. The AUTHID CURRENT_USER declaration means privileges are evaluated against the invoking schema, so grants on the underlying AMS tables must be in place for any caller. Because the package dates from 2002 (per the $Header comment) and remains present in both 12.1.1 and 12.2.2, its behavior is stable across releases and safe to inspect for diagnostic purposes; however, the delete routines should always be exercised through the supported public API to ensure that dependent marketing objects are not left inconsistent.