Results for “get_rule_criteria_rec”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.FUN_RULE_CRITERIA_PUB_W is a public Oracle E-Business Suite PL/SQL specification belonging to the Financials (FUN) schema, associated with the Oracle Enterprise Trading and Rule Management (ETRM) module. Its role is to expose the underlying rule criteria entity of the Oracle EBS transaction rules engine as an Application Programming Interface (API). The package header is classified as OTHER within the documented metadata, and the internal header comment ($Header: FUNXTMRULRCTRWS.pls) confirms a 2005 origin consistent with the 11i and R12 code lines. The package is available in both EBS 12.1.1 and 12.2.2.

Rule criteria define the conditional logic that the trading and transaction rules engine evaluates when processing documents such as purchase orders, sales orders, invoices, or other financial transaction flows. Each criterion row captures a field identifier, an operator, comparison values, and related dates and amounts that determine whether a rule action fires. This package provides the sole supported programmatic route for creating, modifying, and retrieving those criteria records outside of the standard forms.

Key Procedures and Functions

The package exposes three documented procedures, all declared in the package specification:

• CREATE_RULE_CRITERIA — Inserts a new rule criteria record into the underlying entity. It accepts the criteria attribute values as positional parameters (internally named p1_a0 through p1_a11), including numeric, VARCHAR2, and DATE arguments, and returns the generated criteria identifier via x_criteria_id along with the standard API return status, message count, and message data outputs.
• UPDATE_RULE_CRITERIA — Modifies an existing rule criteria row. It accepts the same set of criteria attribute parameters as the create procedure, plus an in-out p_object_version_number used for optimistic locking. It returns the standard x_return_status, x_msg_count, and x_msg_data outputs.
• GET_RULE_CRITERIA_REC — Retrieves a single rule criteria record. It is keyed by p_criteria_id and p_rule_detail_id and returns the criteria attributes through output parameters (internally named p3_a0 through p3_a11), together with the standard return status and message outputs.

Tables Accessed

The ETRM metadata does not enumerate the physical tables referenced by this package through APPS synonyms, and no other packages are documented as referencing it. Functionally, the package operates against the rule criteria base table that stores condition rows for the transaction rules engine, reading and writing the columns mapped to the positional p1_a0 through p1_a11 parameters (typically the criterion's field reference, operator, low/high values, effective dates, and numeric qualifiers). Because the specification is a public wrapper, the actual DML is performed in the corresponding body, which resolves the criteria table through APPS synonyms at runtime.

Usage Notes

This API is intended for programmatic and integration use. Typical invocation patterns include custom PL/SQL that seeds or migrates rule criteria during implementation, concurrent programs that bulk-maintain rules, and wrapper code invoked from Oracle Forms or OAF pages in place of direct table manipulation. The standard API conventions apply: a non-success value in x_return_status indicates failure; callers should validate x_msg_count and read x_msg_data, or use FND_MSG_PUB to retrieve the full message stack. The p_init_msg_list parameter controls whether the message list is initialized at entry. Callers must supply p_object_version_number on update to enforce concurrency control, and should never perform direct DML against the rule criteria tables when this supported API is available.