Search Results delete_rule_object_instance

Overview

APPS.FUN_RULE_OBJECTS_PUB is a public PL/SQL API package belonging to the Oracle E-Business Suite Financials (FUN) application, specifically the Transaction Management / Accounting Rules infrastructure. It provides the programmatic interface for creating, maintaining, and querying "rule objects"—user-customizable constructs that participate in the rule-based processing framework used by Subledger Accounting, transaction validation, and rule test evaluation. The package encapsulates the business logic required to persist rule object definitions, instantiate them for specific organizations, and manage the relationships between rule objects, their attributes, criteria, parameters, and tests. Because it is classified as a PUB API, it is intended for supported external invocation by forms, concurrent programs, and custom extensions rather than internal, private consumption only.

Key Procedures and Functions

The package exposes eleven documented entry points that together form the complete lifecycle management interface for rule objects and their instances:

• CREATE_RULE_OBJECT — Creates a new user-customizable rule object definition.
• CREATE_RULE_OBJECT_INSTANCE — Instantiates an existing rule object definition, typically scoped to a specific organization and instance label. This is the procedure associated with the search term "create_rule_object_instance."
• UPDATE_RULE_OBJECT — Modifies an existing rule object, optionally propagating changes to its instances.
• GET_RULE_OBJECT_REC — Retrieves the persistent record for a rule object, returning its attributes in a record structure.
• DELETE_RULE_OBJECT — Removes a rule object definition.
• DELETE_RULE_OBJECT_INSTANCE — Removes a specific instantiation of a rule object.
• RULE_OBJECT_INSTANCE_EXISTS — Boolean-style check confirming whether a given rule object instance has been defined.
• RULE_OBJECT_INSTANCE_EXISTS_VC — Variant of the existence check returning a VARCHAR2 status code rather than a boolean.
• RULE_OBJECT_USES_PARAMETER — Determines whether a specified parameter is referenced by a rule object, supporting impact analysis before changes.
• CONVERT_USE_INSTANCE — Handles conversion of instance usage semantics, supporting migrations between instance-handling modes.

Tables Accessed

The package reads and writes a consistent family of FUN_RULE_* tables, accessed through APPS synonyms. The base definition tables FUN_RULE_OBJECTS_B and FUN_RULE_OBJECTS_TL hold the object header and its translatable descriptive columns. FUN_RULE_OBJ_ATTRIBUTES stores the attribute definitions belonging to each object. Criteria and their parameters reside in FUN_RULE_CRITERIA, FUN_RULE_CRIT_PARAMS_B, and FUN_RULE_CRIT_PARAMS_TL. Parameter values supplied at runtime are persisted in FUN_RULE_PARAM_VALUES, while FUN_RULE_DETAILS captures detailed configuration rows. The testing and validation side of the framework is supported by FUN_RULE_TESTS, FUN_RULE_TEST_MULTIRULE, FUN_RULE_TEST_MVAL_RES, FUN_RULE_TEST_PARAMS, and FUN_RULE_TEST_RESULTS. These tables collectively allow the API to validate, persist, and later re-evaluate rule object behavior across the application.

Usage Notes

FUN_RULE_OBJECTS_PUB is typically invoked from Oracle Forms maintained within the Financials setup and rule administration responsibilities, from concurrent programs that seed or migrate rule object definitions, and from custom PL/SQL extensions that need to programmatically define rule objects or their instances. Callers should invoke the public procedures rather than the private do_* helpers such as do_create_rule_object and do_create_rule_object_instance, which are declared only for internal use and enforce input validation through FUN_RULE_VALIDATE_PKG. As with all EBS PUB APIs, callers must inspect the x_return_status out parameter after each call and honor the standard FND_API.G_RET_STS_SUCCESS / ERROR / UNEXPECTED_ERROR conventions. The package is referenced by four other packages, confirming it sits at a foundational layer of the rule engine and should be treated as an integration point rather than modified in place.