Search Results ams_dm_scores_all_b_s

Overview

AMS_DM_SCORES_B_PKG is the base-table maintenance package for Oracle Marketing (AMS) scoring data. It encapsulates the DML and translation-handling logic for the AMS_DM_SCORES_ALL entity, which stores the score definitions used by Oracle Marketing's scoring and ranking features for campaigns, leads, and one-to-one marketing list generation. The package belongs to the standard Oracle E-Business Suite public API family: it is defined in the APPS schema, marked VALID in ETRM, and is classified as an "OTHER" API rather than a full multi-org or interface API.

Functionally, the package isolates the base table, the _B (base) table, the _S sequence, and the _TL (translation) table so that callers do not issue direct DML. This ensures that surrogate keys are sourced consistently, that MLS translations are propagated correctly, and that standard EBS error-stack conventions (FND_MSG_PUB, FND_API) are honoured.

Key Procedures and Functions

ETRM documents seven program units in the package body. Their roles are:

• INSERT_ROW — Creates a new score definition row. Generates the primary key from the _S sequence and invokes the language-handling routine to seed translation rows.
• UPDATE_ROW — Modifies an existing score definition. Intended to be called only after LOCK_ROW has confirmed the row is not concurrently modified.
• LOCK_ROW — Issues a SELECT ... FOR UPDATE against the base table to provide optimistic concurrency control before an update or delete.
• DELETE_ROW — Removes a score definition and its dependent translation rows.
• ADD_LANGUAGE — Inserts translation rows in the installed languages for a score definition, keeping the _TL table in step with FND_LANGUAGES.
• TRANSLATE_ROW — Updates the translated name/description columns for an existing _TL row.
• LOAD_ROW — Higher-level convenience routine that combines insert/update behaviour, typically used by seed data and by concurrent/upload processes that must be idempotent.

Tables Accessed

• AMS_DM_SCORES_ALL_B — The base table holding score definitions. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW read and write here.
• AMS_DM_SCORES_ALL_B_S — The sequence supplying primary keys for new rows; referenced by INSERT_ROW and LOAD_ROW.
• AMS_DM_SCORES_ALL_TL — The translation table. ADD_LANGUAGE, TRANSLATE_ROW, and LOAD_ROW read and write here.
• FND_LANGUAGES — Read to determine which languages require translation rows.
• DUAL — Used for sequence and expression evaluation.

Oracle's dependency metadata also lists FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and APP_EXCEPTION as referenced objects, confirming that the package returns standard API status codes and populates the FND message stack on failure.

Usage Notes

The package is not referenced by any other database object in the documented dependency tree, indicating that it is invoked from the application tier rather than from triggers or other PL/SQL units. In practice it is called by the Oracle Marketing scoring setup forms and by the owning entity's own PL/SQL when creating or maintaining score records, and by concurrent/seed programs that use LOAD_ROW for bulk or repeatable loads.

Because the programme units are base-table APIs, callers should expect a standard EBS API contract: a p_commit flag controlling transaction boundaries, an x_return_status of FND_API.G_RET_STS_SUCCESS, ERROR, or UNEXPECTED_ERROR, and message details in FND_MSG_PUB. Custom code should call LOCK_ROW before UPDATE_ROW or DELETE_ROW, and should not insert directly into the base or _TL tables, since doing so bypasses sequence usage and language propagation. This is a 12.1.1 and 12.2.2 compatible object; it is unchanged in respect of the online patching edition, but customisations should be registered against the APPS schema and never modified in place.