Results for “delete_rule_detail”

10 results




Overview
Explore in AI Chat

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

Overview

APPS.FUN_RULE_DETAILS_PUB is a public PL/SQL package belonging to the Rules Framework within the Oracle E-Business Suite Financials product family (product code FUN). It exposes the public APIs for the definition and maintenance of a set of rules, as documented under the display name "Rules Framework: Set of Rules Defintion." The package is classified as a PUB API layer, meaning it is intended to be called by external consumers—forms, concurrent programs, or custom code—rather than being invoked directly as an internal implementation detail.

The package operates under AUTHID CURRENT_USER and is scoped to the business entity FUN_rule_details. Its header, dated 2006, is carried forward into both the 12.1.1 and 12.2.2 releases as part of the Rules Framework infrastructure used by products such as Financials Common Modules (FUN). The record type rule_details_rec_type encapsulates the full column structure of the underlying rule detail entity, including the rule detail identifier, the owning rule object, the rule name, sequence, operator, enabled flag, result application and value, standard audit columns (creation and update metadata), and the created_by_module attribute used for provenance tracking.

Key Procedures and Functions

  • CREATE_RULE_DETAIL — Creates a rule and its related information, inserting a new record into the FUN_RULE_DETAILS table. It raises the Oracle business event oracle.apps.fun.rules.server.HACustomizableObjectEO.create upon execution, reflecting the entity object behind the Rules Framework. The routine accepts an initialization flag for the message stack (p_init_msg_list), a rule detail record (p_rule_detail_rec), and an out parameter conveying the created identifier.
  • UPDATE_RULE_DETAIL — Modifies an existing rule detail record, allowing changes to attributes such as sequence, operator, enabled flag, and result value. Standard audit columns are maintained by the framework.
  • GET_RULE_DETAIL_REC — Retrieves an existing rule detail into the rule_details_rec_type structure, providing read access for validation, display, or downstream processing without altering persisted data.
  • DELETE_RULE_DETAIL — Removes a rule detail entry from the FUN_RULE_DETAILS table, completing the lifecycle management quartet exposed by the package.

All four documented routines share the FUN_RULE_DETAILS business entity and the same record abstraction, ensuring consistent validation and auditing behavior across create, read, update, and delete operations.

Tables Accessed

The package reads and writes a single documented table, FUN_RULE_DETAILS, accessed through its APPS synonym. FUN_RULE_DETAILS stores the individual rules that make up a rule set, keyed by RULE_DETAIL_ID and linked to a parent rule object through RULE_OBJECT_ID. Each row carries the rule name, evaluation sequence, operator, enablement status, and the result application and value returned when the rule evaluates true. Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and CREATED_BY_MODULE support standard EBS tracking and diagnostics.

Usage Notes

FUN_RULE_DETAILS_PUB is the supported entry point for programmatic rule definition within the Rules Framework, and is referenced by two other packages in the ETRM repository. Typical invocation scenarios include:

  • Forms and framework components — Rules Framework maintenance screens call these APIs to persist user-defined rules rather than performing direct DML.
  • Custom code and extensions — Because the package is AUTHID CURRENT_USER and classified PUB, customers and integrators may call it from custom PL/SQL to seed or migrate rule definitions, honoring the documented initialize-message-stack flag to control error handling via the FND message stack.
  • Concurrent programs — Batch processes that generate or copy rule configurations may invoke these routines iteratively, validating inputs through the out parameters before committing.

Callers should rely exclusively on the public signatures, avoid direct manipulation of FUN_RULE_DETAILS, and check the message stack after each call, since the package follows standard EBS API error-handling conventions.