Search Results ams_rule_group_pvt




Overview
Explore in AI Chat

Overview

AMS_RULE_GROUP_PVT is a private PL/SQL package in the APPS schema that implements the core business logic for the Oracle E-Business Suite Marketing (AMS) "rule group" entity. Rule groups are the containers used by the Advanced Product Catalog and iStore personalization engine to associate a named set of posting rules, state filters, and state parameters with a marketing artifact. The package follows the standard EBS three-tier API pattern: a private (PVT) layer holding the uncommitted, uncommitted-API-compliant logic, an internal wrapper layer (AMS_RULE_GROUP_PVT_W), and a public facade (AMS_RULE_GROUP_PUB) that exposes the API to external callers. Because it is classified as a PVT package, its procedures are not intended for direct invocation by customer code or by concurrent programs; they are called by the public wrapper and internal code only. The package declares API classification PVT and depends on the standard EBS API foundation packages FND_API and STANDARD for error handling, message stacking, and the standard return-status convention (FND_API.G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR).

Key Procedures and Functions

The documented package body exposes seven procedures and functions, which collectively provide complete create, read, update, delete, and validation coverage for the rule group entity:

  • CREATE_RULE_GROUP — Inserts a new rule group definition, including its translated (TL) descriptive columns and its associated posting-rule assignments, and returns the newly created rule group identifier.
  • UPDATE_RULE_GROUP — Modifies the attributes of an existing rule group and reconciles its child rows (state filters, state parameters, and rule associations) to match the supplied definition.
  • DELETE_RULE_GROUP — Removes a rule group and its dependent child records, respecting the logical-delete conventions used by the AMS schema.
  • LOCK_RULE_GROUP — Acquires an exclusive lock on the rule group row to serialize concurrent modifications and prevent lost updates during a transaction.
  • VALIDATE_RULE_GROUP — Performs the business-rule validation suite on a proposed rule group definition prior to persistence, raising errors through FND_API's message stack.
  • CHECK_RULE_GROUP_ITEMS — Verifies the integrity of the items (rules, filters, and parameters) attached to a rule group, ensuring referential validity against the posting and rules tables.
  • VALIDATE_RULE_GROUP_REC — A record-level validation helper that inspects a single rule group record structure and returns a boolean/status outcome to its caller.

Tables Accessed

The package operates against the following tables, all referenced through APPS synonyms:

  • AMS_IBA_PS_RULEGRPS_B — The base table holding the rule group header definition (primary key, status, and system columns).
  • AMS_IBA_PS_RULEGRPS_B_S — The sequence/primitive surrogate table used to generate primary keys for new rule groups.
  • AMS_IBA_PS_RULEGRPS_TL — The translation table storing language-dependent name and description columns.
  • AMS_IBA_PS_RULES — The posting rules that may be associated with a rule group.
  • AMS_IBA_PS_RL_ST_FLTRS — State filters that constrain when a rule group's rules apply.
  • AMS_IBA_PS_RL_ST_PARAMS — State parameters supplying values to those state filters.
  • AMS_IBA_PS_POSTINGS_B — The posting definitions that consume the rule group at runtime.
  • DUAL — Used for sequence lookup and utility SELECTs.

Usage Notes

AMS_RULE_GROUP_PVT is referenced by two other packages, notably AMS_RULE_GROUP_PUB, which is the supported entry point for all external calls. Customers and integrators should invoke AMS_RULE_GROUP_PUB from forms, concurrent programs, or custom PL/SQL rather than calling AMS_RULE_GROUP_PVT directly, since the PVT layer bypasses the public API's security, logging, and commit semantics. The package is typically executed in the context of the Oracle Marketing and iStore personalization administration forms and the concurrent programs that build and publish the product-catalog rule model.