Search Results cancel_run_request

Overview

APPS.AMS_DM_SCORE_PVT is a private PL/SQL package belonging to the Oracle Marketing (AMS) module of Oracle E-Business Suite, classified as a PVT (private) API. It encapsulates the business logic that underpins the scoring engine used by Oracle Marketing's data mining and list management functionality. In this context, a "score" is a computed value assigned to customers or prospects based on a data mining model, which is then used to rank, segment, or filter target audiences for campaigns and lists. The package is the internal implementation layer that supports the public wrapper AMS_DM_SCORE_PVT_W, and it exposes the core operations required to create, validate, lock, update, and delete score definitions, as well as to drive the workflow states associated with scoring runs. Because the API is classified as private, it is intended to be invoked by other Oracle Marketing packages rather than directly by end users or external custom code, though its documented procedures are stable enough to be referenced in extensions where the seeded behavior must be augmented.

Key Procedures and Functions

The ETRM metadata documents sixteen procedures and functions within this package. The principal life-cycle operations are CREATE_SCORE, UPDATE_SCORE, and DELETE_SCORE, which manage the persistence of a score definition and its associated records. LOCK_SCORE provides concurrency control so that a score cannot be modified while a run or dependent process is active. Validation is handled by VALIDATE_SCORE and VALIDATE_SCORE_REC, which enforce the business rules for a score record before it is committed. CHECK_SCORE_ITEMS performs item-level validation of the scoring criteria. COPY_SCORE duplicates an existing score definition, supporting the common practice of cloning a model configuration. Workflow-oriented routines include WF_SCORE and WF_CHECKMODELSTATUS, which interact with the Oracle Workflow engine to manage the status of the underlying data mining model, and WF_REVERT, which rolls back a score to a prior workflow state. PROCESS_SCORE_SUCCESS finalizes the outcome of a successful scoring run, while CANCEL_RUN_REQUEST aborts an in-progress run. HANDLE_PREVIEW_REQUEST and HANDLE_DATA_SELECTION_CHANGES support the interactive user experience by processing preview requests and responding to changes in the selected data set.

Tables Accessed

The package reads and writes a focused set of AMS tables via APPS synonyms. Score definition and result data are stored in AMS_DM_SCORES_ALL_B (base), AMS_DM_SCORES_ALL_B_S (sequence/surrogate), and AMS_DM_SCORES_ALL_TL (translatable attributes). Computed outputs are held in AMS_DM_SCORE_RESULTS and its percentile companion AMS_DM_SCORE_PCT_RESULTS. Model information is sourced from AMS_DM_MODELS_ALL_B, while AMS_DM_SOURCE and AMS_DM_TARGETS_B define the source and target populations for scoring. AMS_LIST_SELECT_ACTIONS and AMS_USER_STATUSES_B supply list-action and status lookup data, and AMS_CUSTOM_SETUPS_B provides configuration settings. DUAL is used for singleton queries.

Usage Notes

AMS_DM_SCORE_PVT is invoked indirectly through the public wrapper AMS_DM_SCORE_PVT_W, which is referenced by AMS_ADV_FILTER_PVT, AMS_LISTACTION_PVT, and AMS_WFMOD_PVT. Typical consumers are the Oracle Marketing Scoring and List Management forms and their associated concurrent programs, which call the wrapper during score creation, model status checks, and run cancellation. Because the package depends on FND_API, callers should expect standard EBS API conventions such as message-stack error handling. Direct invocation of the PVT package from custom code is not recommended; extensions should use the public wrapper or the supported UI and concurrent program entry points.