Search Results ams_ct_rule_pub




Overview
Explore in AI Chat

Overview

AMS_CT_RULE_PUB is the public API package for managing content rules within Oracle E-Business Suite's Advanced Marketing (AMS) module, specifically the content targeting (CT) rule framework. Content rules define the conditional logic by which marketing content is matched, prioritized, or presented to specific audiences, segments, or channels. This package exposes the supported public entry points through which forms, concurrent programs, and custom integrations create, modify, remove, and reserve content rule definitions, while delegating the substantive business logic to the corresponding private package, AMS_CT_RULE_PVT.

The package body follows the standard Oracle EBS PL/SQL API architecture. The single documented public procedure, Create_Ct_Rule, carries a header comment identifying the file as amspctrb.pls (version 120.1, dated 2006/02/22) and declares the formal API signature. Every procedure is built around the FND_API framework: it opens a savepoint, calls FND_API.Compatible_API_Call to verify the caller's API version, optionally initializes the message stack via FND_MSG_PUB, sets the return status to FND_API.G_RET_STS_SUCCESS, and delegates the actual database work to the private layer. This structure guarantees consistent error handling, message propagation, and transactional integrity across the AMS public APIs.

Key Procedures and Functions

  • CREATE_CT_RULE — Creates a new content rule. It accepts the caller's API version and initialization/commit controls, a content rule record, and returns the generated content rule identifier along with the standard return status, message count, and message data outputs. Internally it validates API compatibility, initializes the message list when requested, and invokes the corresponding private procedure AMS_Ct_Rule_PVT.Create_Ct_Rule, returning the primary key of the newly created rule.
  • UPDATE_CT_RULE — Modifies an existing content rule, applying changes to the rule record supplied by the caller while preserving the same standard API conventions for version checking, messaging, and commit control.
  • DELETE_CT_RULE — Removes a content rule identified by its key. The operation is executed under the package's savepoint discipline so that failures can be rolled back cleanly.
  • LOCK_CT_RULE — Acquires a logical lock on a content rule record, typically used to serialize concurrent maintenance before an update or delete. It is the standard concurrency-control companion to UPDATE_CT_RULE and DELETE_CT_RULE.

Tables Accessed

The supplied metadata does not enumerate the base tables referenced through APPS synonyms. Given the object's purpose and the AMS content targeting schema, the package operates on the content rule definition tables (the AMS_CT_RULE family) that store rule headers, their associated conditions, and rule-to-content associations. The public package body performs no direct SQL of its own; all inserts, updates, deletes, and lock operations are issued by AMS_CT_RULE_PVT against these underlying tables.

Usage Notes

Create_Ct_Rule and its companion procedures are invoked whenever a content rule must be defined or maintained programmatically. Typical callers include the AMS content targeting setup forms, concurrent programs that seed or migrate rule definitions, and customer extensions that build content rules as part of a larger marketing workflow. Because the API classification is PUB, these procedures are the sanctioned integration surface; direct DML against the content rule tables is unsupported.

Callers should always pass an accurate p_api_version_number, honor the p_init_msg_list and p_commit flags, check x_return_status after every call, and drain the message stack via FND_MSG_PUB when errors occur. The package body source inspected is version 120.1, consistent with the 12.1.1 and 12.2.2 code lines; no downstream packages reference it, so its consumers are external callers rather than other PL/SQL APIs.