Search Results ams_content_rules_b_pkg




Overview
Explore in AI Chat

Overview

The APPS.AMS_CONTENT_RULES_B_PKG package body is a core data-access and maintenance component of the Oracle Marketing (AMS) application within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the base-table maintenance layer for the content rules entity, which governs how marketing content is selected, matched, or delivered against defined business criteria in campaign and content management flows. The package encapsulates the standard Oracle EBS multilingual (MLS) CRUD pattern: it provides the transactional row operations on the base table AMS_CONTENT_RULES_B and the corresponding translation rows in AMS_CONTENT_RULES_TL, while delegating common validation, message handling, and exception management to shared utility packages. Its status is VALID in the documented schema, and the API is classified as OTHER, meaning it is an internal technical package rather than a formally published public API. It is not referenced by any other database object, indicating it sits at the top of its own call chain and is invoked by forms or calling code rather than by dependent PL/SQL units.

Key Procedures and Functions

Five documented entry points constitute the package interface:

  • INSERT_ROW — Creates a new content rule definition. It writes the base row into AMS_CONTENT_RULES_B, populates the identifier columns, and inserts the associated translatable (TL) row for the session language, applying standard WHO audit columns.
  • UPDATE_ROW — Modifies an existing content rule. It updates the base row and the corresponding translation row for the current language, preserving other language translations.
  • DELETE_ROW — Removes a content rule by deleting the base record and its dependent translation rows, maintaining referential consistency between the _B and _TL tables.
  • LOCK_ROW — Acquires a row-level lock on a content rule record, typically to serialize concurrent edits made through the Oracle Forms UI and prevent lost updates.
  • ADD_LANGUAGE — Inserts a new translation row in AMS_CONTENT_RULES_TL for a language that does not yet have a translation, using FND_LANGUAGES to validate the language code and enabling the MLS feature for the entity.

Tables Accessed

The package operates against three documented tables, all referenced through APPS synonyms:

  • AMS_CONTENT_RULES_B — The base table holding language-independent content rule attributes. All insert, update, delete, and lock activity targets this table.
  • AMS_CONTENT_RULES_TL — The translation table holding language-specific descriptive columns. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and ADD_LANGUAGE maintain rows here in step with the base table.
  • FND_LANGUAGES — The Oracle Applications language repository, consulted to validate installed languages when adding or resolving translations.

Additional dependencies include AMS_UTILITY_PVT for shared marketing utility routines, FND_API for the standard API error and message framework, FND_MESSAGE for message retrieval, and APP_EXCEPTION for exception handling.

Usage Notes

Because it is not referenced by any other database object, AMS_CONTENT_RULES_B_PKG is normally invoked directly rather than through a higher-level PL/SQL wrapper. In standard EBS operation it is called by the Oracle Marketing setup and administration forms responsible for maintaining content rules, where LOCK_ROW supports the form's row-locking semantics and the CRUD procedures persist user changes. Custom extensions that must create or maintain content rules programmatically should follow the same MLS sequence the package implements: operate on the base row, then manage the translation row, and rely on FND_API and FND_MESSAGE for consistent error reporting. The ADD_LANGUAGE procedure should be used only when introducing translations for a new installed language, and callers should verify the language against FND_LANGUAGES beforehand. Given the package's classification as OTHER, developers should treat it as internal to the AMS product and avoid modifying it; extensions are better implemented as separate custom packages that delegate to these documented procedures.