Search Results validate_source_rec

Overview

AMS_DMSource_PVT is a private PL/SQL package in the Oracle Marketing (AMS) application, owned by APPS and classified as a PVT (private) API within Oracle E-Business Suite 12.1.1 and 12.2.2. The package supports Oracle Marketing's data-mining infrastructure, providing the programmatic foundation for creating, validating, and maintaining "source" definitions that feed predictive scoring models. A source represents the input data set — typically derived from customers, prospects, parties, or list entries — against which a data-mining model is applied. The package encapsulates the private business logic used to manage the AMS_DM_SOURCE entity and its related staging, scoring, and target-association records. Because it is classified private, its procedures are not intended as a public integration surface; instead they are called by sibling packages within the AMS data-mining stack. The package body is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, and its record definitions lean on the FND_API layer (G_MISS_NUM, G_MISS_DATE, G_MISS_CHAR) to distinguish null from "not supplied" values during API processing.

Key Procedures and Functions

The documented API surface comprises eleven procedures and functions:

• CHECK_SOURCE_ITEMS — Verifies the integrity and completeness of source items associated with a source definition prior to processing.
• LOCK_SOURCE — Obtains a row-level lock on a source record to serialize concurrent modifications.
• CREATE_SOURCE — Creates a new source record in the AMS_DM_SOURCE table, applying defaults and validation.
• UPDATE_SOURCE — Modifies an existing source record, honoring FND_API "miss" semantics for optional attributes.
• DELETE_SOURCE — Removes a source definition and its dependent rows.
• VALIDATE_SOURCE_REC — Validates a single in-memory source record structure (Source_Rec_Type) before it is persisted.
• VALIDATE_SOURCE — Performs full validation of a source including its related associations and targets.
• BIN_PROBABILITY — Assigns or computes a probability bin for scoring output; introduced in the July 2001 revision alongside the decile/percentile scoring enhancements.
• PROCESS_SCORES — Processes and persists model scores (score result, target value, confidence, continuous score, decile, percentile) against source records.
• GENERATE_ODM_INPUT_VIEWS — Builds the input views consumed by Oracle Data Mining (ODM) from the source and target definitions.
• CLEANUP_ODM_INPUT_VIEWS — Drops or resets the generated ODM input views after scoring completes.

Tables Accessed

Access is performed through APPS synonyms. The package reads and writes AMS_DM_SOURCE and its security/child table AMS_DM_SOURCE_S, which store the source header and associated attributes. Model metadata is drawn from AMS_DM_MODELS_ALL_B, while score output is written to AMS_DM_SCORES_ALL_B. Target definitions and their linkage to sources are held in AMS_DM_TARGETS_B and AMS_DM_TARGET_SOURCES. List-source configuration is read from AMS_LIST_SRC_FIELDS, AMS_LIST_SRC_TYPES, and AMS_LIST_SRC_TYPE_ASSOCS. A global temporary table, AMS_DM_APPLY_STG_GT, serves as staging for score application. DBMS_RANDOM and DUAL are used for sampling and single-row expression evaluation, and V$DATABASE is queried to detect database-level environment characteristics affecting ODM view generation.

Usage Notes

As a PVT package, AMS_DMSource_PVT is not invoked directly from Oracle Forms or exposed as a concurrent program entry point; the metadata records that it is referenced by one other package, which orchestrates source lifecycle and scoring operations on its behalf. Its procedures are called during model build and apply cycles — for example, when the marketing data-mining concurrent processes build ODM input views, execute scoring, and then clean up those views. Custom code that attempts to build or score a data-mining model should invoke the public AMS data-mining APIs rather than this private package, since its signatures and internal record types (Source_Rec_Type) are not guaranteed stable across patches. Where BIN_PROBABILITY or PROCESS_SCORES behavior must be extended, the supported approach is to wrap the public API layer and use profile options or model configuration, preserving upgrade safety within 12.1.1 and 12.2.2.