Search Results igs_ge_invalid_value

Overview

IGS_RU_VAL_RUD is a validation package body in the Oracle E-Business Suite Grants (Oracle Grants Management / IGS) schema, owned by APPS and classified under ETRM as an OTHER API. Its name follows the IGS naming convention for rule validation routines: IGS_RU_VAL_* packages validate the definition of rule objects stored in the IGS_RU (Rules) family of tables. This particular package, RUD, targets the "Rule Description" structure of a rule, validating that the stored rule description text was assembled correctly and consistently with the rule's associated return type and Turing-style evaluation function.

The package is invoked during rule definition and maintenance to validate a newly entered or modified rule description against the prior version (the "old" values), returning a Boolean success indicator and an output message name for error handling by the calling form or API. The business purpose is to prevent invalid or inconsistent rule descriptions from being committed into the grants rule engine, which governs how award, budget, and expenditure rules are evaluated.

Key Procedures and Functions

• RULP_VAL_RUD_DESC — The single documented routine in this package. It validates a new IGS_RU_RULE description by comparing it with the old rule description, old return type, and old Turing function values supplied by the caller. It returns a Boolean indicating validity and populates an OUT message name parameter when validation fails. The routine internally uses a nested helper, breakdown_desc, which decomposes a rule description string into three components: the leading string/token, the action (return type), and the remainder of the description. The hash character (#) delimits the boundary; text following # is matched against IGS_RU_RET_TYPE to determine the action. If the description is NULL or the return-type token cannot be matched, the routine returns FALSE with an error.

The package also declares a PL/SQL table type (t_param_list) and global variables to hold the list of parameter return types used during breakdown and validation, and a comment notes the need to clear rowids saved in a PL/SQL table from a prior commit — a standard EBS pattern for maintaining session-level cached row identifiers.

Tables Accessed

• IGS_RU_DESCRIPTION — The primary rule description table; its rule_description and s_return_type columns are the source and target of the text decomposition performed by breakdown_desc.
• IGS_RU_RET_TYPE — The return type reference table. Matched by s_return_type to resolve the action portion of the description following the # delimiter, ordered descending, with the longest matching return type selected.
• IGS_RU_RULE — The rule header/definition table referenced by the validation (through the description's owning rule).
• IGS_RU_ITEM and IGS_RU_NAMED_RULE — Supporting rule structure tables accessed to resolve items and named rule references that participate in the rule definition validated by this package.

All access is via APPS synonyms, so no schema qualification is required in calls.

Usage Notes

IGS_RU_VAL_RUD is a server-side validation API, not a user-facing form or concurrent program. It is typically invoked from the Grants rule maintenance forms (such as the rule definition window reachable through the Grants setup responsibilities) at the point where a user inserts or updates a rule description. The form passes the pre-image ("old") values alongside the newly captured values so the validation can detect an inconsistency between the description text and the selected return type. Referenced by at least one other package in the IGS schema, it is also called programmatically by the rule setup APIs when rules are loaded or migrated.

The keyword v_action surfaced in user searches corresponds to the action variable used inside the internal breakdown_desc helper and the OUT parameter p_action of that helper — it holds the parsed return type extracted from the #-delimited rule description. Because the package is not a public API, custom code should not call it directly; instead, use the supported rule setup APIs, which in turn invoke this validation. The header indicates a last modification date of 2002, and the package is compatible with both EBS 12.1.1 and 12.2.2 without change.