Search Results ams_rule_group_pub

Overview

APPS.AMS_RULE_GROUP_PUB is a public PL/SQL package in the Oracle E-Business Suite Advanced Marketing (AMS/ETRM) module. It belongs to the API classification PUB, indicating that it exposes a supported, externally callable interface intended for use by Oracle application forms, concurrent programs, and customer-written extensions. The package governs the creation, maintenance, and concurrency control of rule groups, which are the containers that associate marketing rules with a posting and a strategy type. A rule group establishes the execution context for one or more rules, carrying attributes such as posting identifier, strategy type, execution priority, and rule name. Because these records drive how marketing campaigns, offers, and related promotions are evaluated at runtime, the package provides the transactional entry point through which rule group rows are inserted, modified, removed, and locked. Its design follows standard Oracle EBS API conventions: a strongly typed record structure (rule_group_rec_type) mirrors the underlying table columns, missing values are defaulted to FND_API.G_MISS_* sentinels, and a package-level constant G_DEFAULT_NUM_REC_FETCH (set to 30) controls bulk fetch sizing. The header comment identifies the source file as amsprgps.pls, version 120.0, dated 31-May-2005, and confirms the package as a public interface layer over the AMS rule group data model.

Key Procedures and Functions

The package documents four public procedures:

• CREATE_RULE_GROUP — Inserts a new rule group row, accepting the caller-supplied record type that populates the rule group columns (posting, strategy type, execution priority, rule name, description, and standard WHO audit columns).
• UPDATE_RULE_GROUP — Modifies an existing rule group identified by its primary key, applying changed attributes while preserving audit and object version information.
• DELETE_RULE_GROUP — Removes a rule group record, typically invoked when a rule configuration is retired or reorganized.
• LOCK_RULE_GROUP — Acquires a row-level lock on the specified rule group. This is the procedure most directly relevant to the searched term lock_rule_group, and it exists to serialize concurrent modification attempts, preventing two sessions from updating the same rule group simultaneously.

No parameter lists are documented; callers should consult the package specification for exact signatures. Each procedure is expected to honor the standard ETRM error-handling contract, returning API status and message via the FND_API conventions.

Tables Accessed

The metadata does not enumerate the underlying tables explicitly, but the record type maps one-to-one to the rule group base table in the AMS schema (referenced through an APPS synonym). Columns identified in the record definition include row_id, rulegroup_id, posting_id, strategy_type, exec_priority, rule_name, rule_description, and the standard audit columns (last_update_date, last_update_login, created_by, creation_date, last_updated_by, object_version_number). The package reads and writes these columns to persist rule group configuration. It is documented as being referenced by zero other packages, positioning it as a top-of-stack interface rather than an internal utility.

Usage Notes

AMS_RULE_GROUP_PUB is typically invoked from Oracle Forms in the Advanced Marketing setup and administration flows, where users define and maintain rule groupings. Concurrent programs that seed or migrate marketing rules may also call these procedures. Custom integrations should call CREATE, UPDATE, DELETE, and LOCK in this package rather than issuing direct DML against the base table, so that object version numbers and audit columns remain consistent. When programmatic updates are required, LOCK_RULE_GROUP should be called first to guarantee exclusive access; the object version number returned by the record type can then be used for optimistic concurrency validation. Because the header dates to 2005, the interface is stable across 12.1.1 and 12.2.2, with the 12.2 uplift introducing no change to the public signature.