Search Results ams_approvers_s

Overview

The APPS.AMS_APPROVERS_PKG package body is a database-side PL/SQL implementation belonging to the Oracle Marketing (AMS) application family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to manage the persistence and lifecycle of approver definitions used in marketing approval workflows — that is, the records that establish which users or roles are authorized to approve marketing objects such as campaigns, events, and collateral.

The package is classified under the ETRM metadata as an "OTHER" API. It is not a public, formally versioned interface API, but rather an internal package that a corresponding specification (AMS_APPROVERS_PKG) exposes to calling code. Within EBS, the _PKG body typically encapsulates the low-level DML for an associated base table plus its audit (_A) and multilingual (_S / _TL) companion objects, shielding callers from direct SQL against those tables.

Key Procedures and Functions

The ETRM documentation records five procedures or functions in the package:

• INSERT_ROW — Inserts a new approver record into the approver base table, populating the standard WHO columns (creation date, created by, and so on) and the primary key.
• LOCK_ROW — Acquires a row-level lock on an existing approver record. It is normally called before UPDATE_ROW or DELETE_ROW to guarantee serialized access and to detect concurrent modifications.
• UPDATE_ROW — Modifies the attributes of an existing approver record, maintaining the WHO "last updated" audit columns.
• DELETE_ROW — Removes an approver record from the base table.
• LOAD_ROW — Performs an idempotent load: inserting the approver when it does not yet exist and updating it when it does. This is the entry point typically used by seed-data loaders, installation routines, or concurrent programs populating approver configuration.

No parameter lists are documented in the ETRM metadata, so the exact signatures (including the standard x_return_status / x_msg_count / x_msg_data out parameters common to this API style) are not reproduced here. Callers should obtain signatures from the package specification.

Tables Accessed

The package references the following objects, resolved through APPS synonyms:

• AMS_APPROVERS — The base transactional table holding approver definitions. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW read and write this table.
• AMS_APPROVERS_S — The "_S" (security / sequence or denormalized snapshot) companion table associated with approvers, also accessed by this package. This is the object most closely matching the user's search term ams_approvers_s.
• DUAL — The standard Oracle utility table, typically used for a single-row select (for example, to validate a key or to return a constant during row-level operations).

In addition, the body depends on APPS.AMS_APPROVERS_PKG (the specification), APP_EXCEPTION and FND_MESSAGE for error handling and translated message text, and SYS.STANDARD.

Usage Notes

This package is an internal implementation object. It is typically invoked by Oracle Marketing forms and by the marketing approval-workflow setup logic whenever approver configuration is created or maintained. The presence of the `_S` companion table suggests the package also participates in maintaining the denormalized or secured view of approver data used by the approval-engine lookups.

ETRM indicates the package is not referenced by any other database object, confirming that it sits at the leaf of the approval dependency chain — it is called by application-layer code rather than by other PL/SQL packages. Customizations should avoid direct DML against AMS_APPROVERS and AMS_APPROVERS_S; instead, call through AMS_APPROVERS_PKG so that WHO audit columns, locking, and error-message propagation remain consistent. Because LOAD_ROW is idempotent, it is the preferred entry point for any data-conversion or setup-loader code, while INSERT_ROW / UPDATE_ROW / DELETE_ROW are appropriate where the caller already knows whether the target row exists.