Search Results ams_approvers_pkg




Overview
Explore in AI Chat

Overview

AMS_APPROVERS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM repository as an "OTHER" API object. It belongs to the Oracle Marketing (AMS) product family and provides the low-level data access layer for the AMS_APPROVERS entity — the table that stores approver records used in Oracle Marketing approval workflows (for example, campaign, event, and deliverable approval routing). The package encapsulates the standard insert, update, delete, lock, and load operations for this entity, isolating direct DML on the underlying tables from the calling application logic.

The package is documented as VALID in ETRM 12.2.2 and is part of the standard seeded Objects in the APPS schema. It has no public API classification such as "PL/SQL API" or "Concurrent Program," which indicates it is intended as an internal implementation component rather than a formal callable interface. Its dependencies are limited to the SYS.STANDARD package and the AMS_APPROVERS and AMS_APPROVERS_S tables, plus DUAL, shown through the documented table references.

Key Procedures and Functions

ETRM documents five procedures/functions in this package:

  • INSERT_ROW — Inserts a new approver record into the AMS_APPROVERS table. This is the entry point for creating approval assignments.
  • LOCK_ROW — Acquires a row-level lock on an existing approver record to prevent concurrent modification during an update or delete operation.
  • UPDATE_ROW — Modifies an existing approver record. It is typically called after LOCK_ROW has secured the row.
  • DELETE_ROW — Removes an approver record from the entity, used when an approval assignment is no longer required.
  • LOAD_ROW — Performs a combined load operation (insert-or-update semantics) on an approver record, commonly used in data migration, interface, or seed-data population scenarios.

No parameter lists are documented in the ETRM metadata; the procedures are described here by purpose only. The presence of both INSERT_ROW/UPDATE_ROW/DELETE_ROW and LOAD_ROW is consistent with the standard Oracle EBS "table handler" package pattern, where a companion private package (AMS_APPROVERS_PVT) wraps these primitives with business validation.

Tables Accessed

The package accesses three documented objects:

  • AMS_APPROVERS — The primary transactional table holding approver records. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW perform DML against it.
  • AMS_APPROVERS_S — The "_S" table, which in Oracle EBS usually denotes a sequence or a translated/secure store (depending on product convention). It is referenced when generating or resolving the primary key for new approver rows.
  • DUAL — Used for scalar evaluations and sequence lookups during row processing.

These tables are referenced through APPS synonyms, and the package dependency chain shows AMS_APPROVERS_PKG is referenced by one other package, AMS_APPROVERS_PVT. This confirms the layering: AMS_APPROVERS_PKG handles physical DML while AMS_APPROVERS_PVT applies business logic and is the preferred call target for external code.

Usage Notes

AMS_APPROVERS_PKG is not intended for direct invocation by end users. It is invoked by the AMS_APPROVERS_PVT package, which in turn is called from Oracle Marketing forms, concurrent programs, and approval workflow logic that manage approver assignments. Custom integrations that need to manipulate approver data should call AMS_APPROVERS_PVT rather than this package, to ensure validation and consistency with Oracle Marketing approval semantics.

Direct calls to AMS_APPROVERS_PKG should be reserved for controlled data-fix or migration scripts, and any such use should be performed with the surrounding transaction managed explicitly (locking rows via LOCK_ROW before UPDATE_ROW or DELETE_ROW). Because the package is a seeded APPS object, its signature is dependent on the installed AMS patch level; customization should avoid recompiling or altering it.