Search Results delete_rule_criteria

Overview

APPS.FUN_RULE_CRITERIA_PUB is a public PL/SQL API package in the Oracle E-Business Suite Financials (FUN) module that governs the creation, maintenance, and retrieval of rule criteria records used by Oracle Treasury and the Enterprise Transaction Management (ETRM) rule engine. Rule criteria define the specific conditions or line-item attributes that a transaction must satisfy for an associated rule to fire; each criteria row is linked to a parent rule detail through the RULE_DETAIL_ID foreign key. The package body carries the standard EBS API architecture: thin public entry points that delegate work to private procedures, an input-validation layer, and a table-handler package that performs the actual DML. The header revision ($Header: FUNXTMRULRCTPUB.pls 120.0 2005/06/20) confirms the package originated in the Treasury (XTM) development stream and remains the supported interface for programmatic manipulation of criteria definitions in releases 12.1.1 and 12.2.2.

Key Procedures and Functions

• CREATE_RULE_CRITERIA — Validates an incoming criteria record and inserts a new row into the criteria table, returning the generated criteria identifier and the standard API return status. It is the primary entry point for adding conditions to an existing rule detail.
• UPDATE_RULE_CRITERIA — Modifies the attributes of an existing criteria record. The operation uses the object version number for optimistic concurrency control, so callers must supply the current version and expect it to be incremented on success.
• GET_RULE_CRITERIA_REC — Retrieves a single criteria record, typically by criteria identifier, populating a RULE_CRITERIA_REC_TYPE structure for the caller. It is the standard read interface used before performing an update or for display purposes.
• DELETE_RULE_CRITERIA — Removes a criteria definition from the rule configuration, ensuring that orphaned criteria do not remain attached to a rule detail.

The private workers do_create_rule_criteria and do_update_rule_criteria perform the substantive logic. The create path first calls FUN_RULE_VALIDATE_PKG.validate_rule_criteria with an action code of 'C'; if the validator raises the standard error status, the procedure raises fnd_api.g_exc_error and aborts. On successful validation it invokes FUN_RULE_CRITERIA_PKG.Insert_Row, passing ROWID, CRITERIA_ID, RULE_DETAIL_ID, and the remaining record attributes as the X_ arguments. The update path follows the same validate-then-delegate pattern. All public procedures observe the FND_API conventions: NOCOPY parameters, an IN OUT x_return_status, and use of the shared error-handling exception.

Tables Accessed

The package operates on a single base table, FUN_RULE_CRITERIA, accessed through its APPS synonym. All reads and writes flow through the FUN_RULE_CRITERIA_PKG table handler rather than issuing SQL directly, which preserves the EBS layering standard and centralizes row-level DML. The table stores the criteria identifier, the owning rule detail identifier, the object version number, and the WHO audit columns maintained by the handler.

Usage Notes

FUN_RULE_CRITERIA_PUB is invoked whenever rule criteria are configured or maintained — for example, from the Treasury rules setup forms, from concurrent programs that migrate or copy rule definitions between environments, and from custom extensions that build rule sets programmatically. The package is a PUB-classified API, so it is the supported integration surface; custom code should call these procedures rather than writing to FUN_RULE_CRITERIA directly. Because the metadata records it as referenced by two other packages, it functions as a shared dependency within the rule framework and should be treated as an interface contract. Callers must always initialize and inspect x_return_status, and must pass the correct object version number on updates to avoid concurrent-modification errors.