Search Results check_rule_group_items

Overview

AMS_RULE_GROUP_PVT_W is a private PL/SQL wrapper package belonging to the Oracle Marketing (AMS) application module of Oracle E-Business Suite. Its header signature (amswrgps.pls 120.0) places it in the application's rule-group processing layer, which supports the definition and evaluation of marketing rule groups — logical containers that bind a set of rules to a campaign, event, or list source so that targeting and qualification logic can be executed consistently at runtime.

The package is classified by ETRM as API category "OTHER", meaning it is not published as a supported public interface but is instead a generated wrapper used internally by the Marketing rule engine and by the PL/SQL layer that exposes rule-group maintenance to forms and concurrent processes. The "_PVT_W" suffix indicates a private packaged wrapper whose body follows the standard Oracle Marketing private-API conventions: bulk table handlers generated by the Rosetta code generator, followed by Create, Update, Validate, and Check procedures layered over the underlying business logic in AMS_RULE_GROUP_PVT.

Key Procedures and Functions

ETRM documents seven procedures in this package:

• ROSETTA_TABLE_COPY_IN_P3 — Transfers a set of parallel JTF indexed tables (number, varchar2, and date arrays) into a single PL/SQL record collection of type ams_rule_group_pvt.rule_group_tbl_type. It is the standard inbound bulk-conversion hook generated by Rosetta.
• ROSETTA_TABLE_COPY_OUT_P3 — Performs the reverse operation, unpacking a rule_group_tbl_type collection back into the parallel JTF number, varchar2, and date tables for consumption by forms, OAF pages, or Java callers.
• CREATE_RULE_GROUP — Creates a new rule-group header. It accepts the standard API parameter block (API version, message list initialization, commit flag, validation level) and returns standard return status, message count, and message data along with the newly generated rule-group identifier. The trailing p7_a0 through p7_a11 parameters correspond to the generated attribute columns of the rule-group entity, with defaults using fnd_api.g_miss_* sentinels.
• UPDATE_RULE_GROUP — Updates an existing rule-group record using the same API parameter conventions, allowing header attributes to be modified while preserving the standard validation and message handling framework.
• VALIDATE_RULE_GROUP — Performs validation logic for a rule-group entity, ensuring that mandatory attributes and referential rules are satisfied before a create or update is committed.
• CHECK_RULE_GROUP_ITEMS — The procedure of interest in the user's search. It checks the line-level items (rule-group members/rule assignments) associated with a rule group, returning status information about whether the group's constituent items are valid, complete, or consistent. This is typically the gatekeeper invoked before rule-group submission or evaluation.
• VALIDATE_RULE_GROUP_REC — A record-level validation entry point that accepts a rule-group record structure and applies the same business validation rules used by the check procedures.

Tables Accessed

The only table referenced via APPS synonym in the documented metadata is PLITBLM. PLITBLM is a standard Oracle Applications "PL/SQL Interface Table, Blob/Message" structure used by the Rosetta-generated bulk handlers to stage indexed table data in and out of the PL/SQL layer. No direct DML against the AMS rule-group base tables is documented at this wrapper level; those inserts and updates are performed by the underlying AMS_RULE_GROUP_PVT body, with this wrapper serving as the table-array conversion and API façade.

Usage Notes

Because this is a private wrapper, it is not intended to be called directly from customer extensions or third-party integrations. The supported entry point for rule-group maintenance is the underlying AMS_RULE_GROUP_PVT public package, whose procedures follow the same name-and-parameter pattern documented here. The CHECK_RULE_GROUP_ITEMS procedure is invoked internally by Marketing forms (for example, the rule-group setup UI) when the user saves or submits a rule group, and by concurrent processes that evaluate rule groups for campaign execution.

Callers within the application typically rely on the standard fnd_api.g_miss_* sentinel values for optional attributes and must pass a valid API version number, commit flag, and validation level. Return values should always be inspected through x_return_status, with diagnostics retrieved from x_msg_data. The package header is source-version 120.0 and is marked noship, indicating that it ships only as a stub with the compiled body supplied by the AMS product installation on the application tier.