Search Results insert_criteria

Overview

The APPS.AD_PA_CREATE_ADVISOR_CRITERIA package body is an internal Oracle EBS Application DBA (AD) utility used by the Patching and Advisor framework. Its business function is to seed and maintain the advisor criteria records that drive the "Patch Advisor" / "Patch Recommendations" capability available in Oracle Applications Manager (OAM). These records define which products, product families, and patch attributes the advisor evaluates when generating recommendations for an E-Business Suite environment. The package is classified as an OTHER API under the APPS schema and is not a public, customer-facing interface; it exists to support internal maintenance of advisor configuration data, particularly during pre-seeding and installation or upgrade operations.

The package is unusually small‑scope: it exposes only two documented procedures, both of which are narrowly focused on inserting rows into the advisor criteria tables. The header indicates an early-2000s vintage ($Header: adpaincb.pls 115.3 2002/10/14), and the code style is consistent with that era, using inline anonymous blocks with local exception handlers rather than a shared error-handling utility. Because it is owned by APPS and depends only on APPS-synonym tables, it can be invoked from SQL*Plus or from concurrent/installation drivers without additional grants.

Key Procedures and Functions

• INSERT_CRITERIA — The primary documented procedure. It inserts a single row into AD_PA_CRITERIA, populating the advisor criteria identifier, the human-readable criteria description, the pre-seeded flag, and standard audit columns (creation date, last updated by, created by, last update date). Its notable defensive behavior is degradation of a null p_last_updated_by to the value 1, and trapping of DUP_VAL_ON_INDEX to raise application error -20001 with a message that echoes the duplicate advisor_criteria_id and pre_seeded_flag. This makes the procedure effectively "insert-only-if-absent" from the caller's perspective, since duplicates surface as a returned Oracle error rather than a silent no-op.
• INSERT_CRITERIA_PROD — The companion procedure. It inserts a row into AD_PA_CRITERIA_PRODUCTS, associating an advisor criteria identifier with a product abbreviation and product family abbreviation, plus flags controlling whether a family pack, mini-pack, or high-priority patch is required for the criteria to be satisfied. Like its sibling, it applies the same null-user substitution and duplicates-on-index handling pattern. Together the two procedures form a two-level seeding operation: one call defines the criteria header, and one or more calls define the products governed by that criteria.

Tables Accessed

The package writes to two documented tables:

• AD_PA_CRITERIA — Holds the advisor criteria master records, including the identity, description, and pre-seeded indicator of each criterion. Written exclusively by INSERT_CRITERIA.
• AD_PA_CRITERIA_PRODUCTS — Holds the product-level detail rows that qualify a criteria record, including family pack, mini-pack, and high-priority requirements. Written exclusively by INSERT_CRITERIA_PROD.

No other tables, views, or sequences appear in the documented metadata. There are no reads in the visible source; the package is purely an insert path for advisor configuration data.

Usage Notes

Because the metadata records zero dependent packages and the procedures are narrowly scoped insert helpers, invocation is expected from internal AD-level drivers: patch application scripts, AutoPatch-related seeding steps, or installation/upgrade programs that populate the advisor criteria tables before OAM presents patch recommendations. Custom code should treat this package as unsupported internal infrastructure rather than a stable public API; the documented metadata explicitly classifies it as OTHER, and its procedures accept positional parameters with no default values shown. Callers should be prepared for the -20001 duplicate-key error, which is the package's only documented error contract, and should supply a valid created-by and last-updated-by user identifier to avoid the silent fallback to user 1. The ETRM excerpt is truncated at the exception block of INSERT_CRITERIA_PROD, so the remainder of that handler, along with any private helpers below the documented procedures, is not represented in the supplied metadata and should be verified directly from the package source in the target environment.