Search Results check_ct_rule_items

Overview

AMS_CT_RULE_PVT_W is a private PL/SQL wrapper package within the Oracle E-Business Suite (EBS) Oracle Marketing (AMS) module. Its name and contents place it squarely in the Content Rules area of marketing campaign management, where "CT" denotes Content Type or Content Template and "RULE" denotes a business rule applied to marketing content. The package provides the service-layer entry points that the Oracle Marketing application uses to create, update, validate, and inspect content rules. In Oracle EBS 12.1.1 and 12.2.2, this object resides in the APPS schema and is classified under the ETRM API classification of OTHER, indicating that it is an internal implementation helper rather than a publicly published, standalone customer API.

The "_W" suffix identifies this as a thin wrapper. The wrapper pattern is used so that the richer underlying private package (AMS_CT_RULE_PVT) can expose strongly typed PL/SQL record and table structures while its procedures remain callable from generated UI and middle-tier code. The two ROSETTA_TABLE_COPY procedures exist specifically to translate between the internal typed collections and the generic JTF_NUMBER_TABLE, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_* collection types that Oracle's Rosetta/Java-based integration layer passes across the PL/SQL-to-Java boundary.

Key Procedures and Functions

The ETRM metadata documents seven procedures in this package:

• ROSETTA_TABLE_COPY_IN_P3 — Copies an incoming set of generic JTF scalar tables into the strongly typed ct_rule_tbl_type collection used internally by the content rule logic.
• ROSETTA_TABLE_COPY_OUT_P3 — Performs the reverse operation, copying the typed ct_rule_tbl_type collection back out into the generic JTF scalar tables.
• CREATE_CT_RULE — Creates a new content rule record. It follows the standard EBS API signature, accepting version, initialization, commit, and validation parameters and returning return status, message count, message data, and the new content_rule_id. It also accepts a block of p7_* parameters corresponding to content rule attributes.
• UPDATE_CT_RULE — Modifies an existing content rule, using the same EBS API calling conventions.
• VALIDATE_CT_RULE — Applies the business validation rules to a content rule before or independently of persistence.
• CHECK_CT_RULE_ITEMS — This is the procedure the user searched for. It inspects the individual items (line-level or membership-level entries) that make up a content rule, performing the existence, completeness, and consistency checks that the rule requires before it can be considered valid. Because the metadata does not expose its full parameter list, no parameter signature is asserted here.
• VALIDATE_CT_RULE_REC — Validates the record-level structure of a single content rule, separate from the item-level checks performed by CHECK_CT_RULE_ITEMS.

Tables Accessed

The ETRM metadata lists PLITBLM as the table referenced by this package through an APPS synonym. PLITBLM is a standard EBS "temporary/global temporary-style" helper table used broadly across Oracle Applications as a scratch area for bulk PL/SQL processing, particularly for passing arrays of values between PL/SQL and calling layers. In this package it supports the Rosetta copy and bulk rule processing logic. The persistent content rule data itself is stored in the AMS content rule base tables, which the underlying AMS_CT_RULE_PVT package maintains.

Usage Notes

AMS_CT_RULE_PVT_W is not intended for direct invocation by customers or implementers. It is invoked by the Oracle Marketing forms and the application's own middle-tier integration code whenever content rules are created or modified through the standard user interface. The metadata records that the package is referenced by zero other packages, confirming its role as a leaf-level wrapper rather than a shared utility.

Custom code should call the corresponding public AMS content rule APIs rather than this wrapper. When troubleshooting, CHECK_CT_RULE_ITEMS and VALIDATE_CT_RULE_REC are the two procedures most relevant to diagnosing why a content rule fails validation. Any modification to this package must be treated as a customization that will be overwritten by patching, and it must be recompiled against the APPS schema in both 12.1.1 and 12.2.2 environments, where the file versions and JTF collection type definitions are consistent.