Search Results update_dm_binvalues

Overview

AMS_DM_BINVALUES_PVT is a private PL/SQL package in the APPS schema that supports Oracle Marketing (AMS) data-mining bin value definitions. In the Oracle EBS 12.1.1 and 12.2.2 architectures, this package is part of the Advanced Product Catalog and Marketing data-mining infrastructure, which allows marketing users to model customer and prospect data using binned numeric or categorical attributes. A "bin value" is a discrete segment or range defined against a source field — for example, age bands, income ranges, or tenure brackets — used by data-mining and list-generation engines to classify records.

The package is classified as a private (PVT) API, meaning it is an internal implementation layer. It is not intended as a public integration interface; instead it is called by higher-level AMS packages and by the Oracle Forms user interface when users create, modify, or delete bin value definitions. It uses AUTHID CURRENT_USER, so it executes with the privileges of the invoking schema, and it references data through APPS synonyms.

The package defines a PLS record type, dm_binvalues_rec_type, that mirrors all columns of the underlying bin value entity, including audit columns, object_version_number for optimistic locking, and the substantive attributes source_field_id, bucket, bin_value, start_value, and end_value. Attributes default to FND_API "missing" sentinels such as FND_API.G_MISS_NUM and FND_API.G_MISS_CHAR, enabling the standard Oracle API pattern in which absent fields are distinguished from zero or null values. A package constant G_DEFAULT_NUM_REC_FETCH (30) governs record fetching in bulk operations.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions:

• CREATE_DM_BINVALUES — Inserts a new bin value definition, populating audit columns and the object version, based on the passed record. It is the entry point when a user defines a new bin or range against a source field.
• UPDATE_DM_BINVALUES — Modifies an existing bin value. This is the procedure most often associated with the search term "update_dm_binvalues," as it is invoked when a user edits bin boundaries, values, or bucket assignments. It relies on object_version_number to detect concurrent modification.
• DELETE_DM_BINVALUES — Removes a single bin value definition identified by its primary key.
• LOCK_DM_BINVALUES — Acquires a row-level lock on a bin value record, typically as the first step in an update or delete sequence to serialize concurrent transactions.
• VALIDATE_DM_BINVALUES — Performs entity-level validation of a bin value record, checking required attributes and business rules before persistence.
• CHECK_DM_BINVALUES_ITEMS — Verifies dependent items, such as whether child references or related definitions exist, before allowing an operation to proceed.
• VALIDATE_DM_BINVALUES_REC — Applies record-level validation against the supplied dm_binvalues_rec_type structure.
• DELETE_DM_BINVALUES_FOR_FIELD — Bulk-deletes all bin values associated with a given source field, used when a field definition is removed or reorganized.

Tables Accessed

The package reads and writes two documented base tables through APPS synonyms:

• AMS_DM_BIN_VALUES — The primary table holding bin value rows: source field reference, bucket, bin value text, and start/end numeric bounds, plus standard WHO audit columns.
• AMS_DM_BIN_VALUES_S — The corresponding sequence or secondary table used for surrogate key generation and/or localized attributes.
• DUAL — Used for singleton evaluations, such as sequence NEXTVAL retrieval and single-row arithmetic checks.

Usage Notes

Because AMS_DM_BINVALUES_PVT is a PVT package, it should not normally be called directly from customer extensions. It is invoked by the Oracle Marketing forms that maintain bin value definitions, and by two other AMS packages (per the ETRM dependency metadata) that orchestrate data-mining metadata setup. Custom code requiring bin value maintenance should prefer the corresponding public AMS API where one exists; if direct invocation is unavoidable, callers must initialize the record type with FND_API sentinel values, call LOCK_DM_BINVALUES before updating, honor object_version_number for optimistic concurrency, and commit or roll back explicitly. Updates that bypass this package risk corrupting the object version and audit trail, and may leave orphaned bin values if DELETE_DM_BINVALUES_FOR_FIELD is not used when source fields are retired.