Search Results ams_dmmodel_pub




Overview
Explore in AI Chat

Overview

The APPS.AMS_DMMODEL_PUB package body is a public API within the Oracle E-Business Suite Marketing (AMS) module, responsible for managing the metadata that defines data mining models. In Oracle EBS 12.1.1 and 12.2.2, the Marketing product relies on data mining models to score customers, predict campaign response, and segment audiences. This package provides the programmatic interface through which those model definitions are created, maintained, locked for processing, and removed from the repository. As a public (PUB classification) API, it is designed for external invocation by forms, concurrent programs, or custom code rather than being restricted to internal use.

The object resides in the APPS schema with a status of VALID. The body delegates the majority of its business logic to the private package AMS_DM_MODEL_PVT, which serves as the implementation layer. This separation follows the standard Oracle EBS pattern in which a public wrapper validates inputs, manages the API message stack, and enforces profile options before forwarding work to the private engine.

Key Procedures and Functions

The ETRM metadata documents four public procedures within this package body. Parameter lists are not reproduced here, as the documented metadata does not enumerate them.

  • CREATE_MODEL — Inserts a new data mining model definition into the repository, establishing its identifying attributes and associating it with the appropriate custom setup context.
  • UPDATE_MODEL — Modifies the attributes of an existing data mining model, allowing model metadata to evolve as business requirements change.
  • DELETE_MODEL — Removes a data mining model definition from the repository.
  • LOCK_MODEL — Acquires a lock on a specified model, preventing concurrent modification while another process, such as a build or scoring routine, operates against it. This supports the concurrency control expected in a multi-user EBS environment.

Each procedure is expected to conform to the Oracle Application Object Library API conventions evident in the dependency list, including the use of FND_API, FND_MSG_PUB, and FND_MESSAGE for standardized return statuses and error reporting.

Tables Accessed

The package reads and writes data through APPS synonyms referencing the following base tables:

  • AMS_DM_MODELS_ALL_B — The primary base table holding data mining model definitions. This is the central table manipulated by the create, update, and delete operations.
  • AMS_DM_MODELS_ALL_B_S — The sequence or secondary table associated with the base table, used to generate or manage primary key identifiers for new model records.
  • AMS_CUSTOM_SETUPS_B — Holds custom setup configuration used to validate or contextualize model creation, reflecting the dependency of models on setup data.
  • DUAL — The standard Oracle single-row utility table, typically used for lightweight SQL expressions or validations.

Additional read access is implied through AMS_USER_STATUSES_VL, which likely supplies valid status codes, and AMS_UTILITY_PVT, which provides shared marketing utility logic.

Usage Notes

AMS_DMMODEL_PUB is invoked programmatically rather than executed directly by end users. Typical call sites include the Marketing data mining model setup forms, concurrent programs that batch-maintain model definitions, and custom extensions requiring controlled model lifecycle management. Because the package is not referenced by any other database object, callers interact with it exclusively as top-level API consumers, invoking it from PL/SQL blocks, forms, or concurrent program logic. Callers should supply the standard API parameters, observe the returned message stack via FND_MSG_PUB, and respect the locking semantics of LOCK_MODEL to avoid concurrent modification conflicts with model build or scoring processes.