Search Results create_dm_binvalues

Overview

AMS_DM_BINVALUES_PVT is a private PL/SQL package within the Oracle E-Business Suite (EBS) Oracle Marketing (AMS) module. It is declared with AUTHID CURRENT_USER and functions as the lowest-level API layer for managing the AMS_DM_BIN_VALUES entity. In the marketing data-mining model, a "bin value" represents the numeric range binning definition applied to a source field so that continuous values can be grouped into discrete buckets for analytical processing. The package provides the core insert, update, delete, lock, and validation logic that higher-level (public) marketing APIs and internal consumers rely upon.

The package header identifies the record structure dm_binvalues_rec_type, which mirrors the AMS_DM_BIN_VALUES table columns: bin_value_id, the standard WHO audit columns (last_update_date, last_updated_by, creation_date, created_by, last_update_login), object_version_number, source_field_id, bucket, bin_value, start_value, and end_value. All attributes are initialized to the corresponding FND_API.G_MISS_* sentinel values, which allows the lower-level components to distinguish between "no value supplied" and an actual value. A package-level constant, G_DEFAULT_NUM_REC_FETCH, is set to 30 and controls the default number of records fetched per call.

Key Procedures and Functions

The documented API surface consists of eight components:

• CREATE_DM_BINVALUES — Inserts a new bin value definition row for a given source field, applying the record structure and assigning identifiers as required.
• UPDATE_DM_BINVALUES — Modifies an existing bin value definition, typically the bucket, bin_value, start_value, end_value, or source_field_id attributes.
• DELETE_DM_BINVALUES — Removes a single bin value definition identified by its primary key.
• DELETE_DM_BINVALUES_FOR_FIELD — Deletes all bin value rows associated with a particular source field, supporting cleanup when a field's binning scheme is redefined or removed.
• LOCK_DM_BINVALUES — Acquires a row-level lock to prevent concurrent modification while a transaction processes the record.
• VALIDATE_DM_BINVALUES — Performs entity-level validation on supplied column values before they are persisted.
• VALIDATE_DM_BINVALUES_REC — Validates the entire dm_binvalues_rec_type record, allowing the record to be checked before any DML is initiated.
• CHECK_DM_BINVALUES_ITEMS — Validates individual attribute values, providing granular checks that support the higher-level validation routines.

Tables Accessed

The package operates against three objects referenced through APPS synonyms:

• AMS_DM_BIN_VALUES — The primary table storing bin value definitions. CREATE, UPDATE, DELETE, and LOCK operations target this table, and it is the read source for validation and fetch logic.
• AMS_DM_BIN_VALUES_S — The secondary/sequence-support table typically maintained alongside the base table in EBS, used to obtain or verify the surrogate primary key for new rows.
• DUAL — Used for single-row evaluations, such as sequence lookups or simple value checks.

Usage Notes

Because this is a PVT (private) API, it is not intended for direct invocation by external custom code. It is referenced by two other packages in the AMS schema, which act as the public entry points; the marketing data-mining forms and concurrent programs that maintain binning definitions ultimately delegate to these procedures through that public layer. In release 12.1.1 and 12.2.2, the package remains unchanged in its documented interface except for the OAF-based user interface migration in 12.2, which does not alter the API contract. Developers extending marketing functionality should call the public wrapper rather than AMS_DM_BINVALUES_PVT, and should ensure the standard WHO audit columns and object_version_number are populated, as the validation routines depend on them. The G_MISS sentinels in dm_binvalues_rec_type should be preserved unless a value is intentionally supplied.