Results for “rulp_get_rule”

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

Overview

IGS_PS_UNIT_VER_RU_V is a seeded Oracle E-Business Suite view owned by the APPS schema within the IGS (Student System) product family. It presents the association between program unit versions and the rules that govern them, resolving rule call definitions and rule descriptions into a single denormalised result set. In EBS 12.1.1 and 12.2.2 the view is delivered as a VALID database object and forms part of the rules engine infrastructure used by Student System configuration, enrollment eligibility, and curriculum validation processes.

The view's principal architectural role is to answer the question of which rules apply to a given unit version and, conversely, which rule calls exist that a unit version has not yet been assigned. This dual perspective makes it useful both for administrative reporting on configured rules and for data integrity checks during implementation.

Underlying Base Objects

The view is defined over three documented base tables: IGS_RU_DESCRIPTION, IGS_RU_CALL, and IGS_PS_UNIT_VER_RU, with IGS_PS_UNIT_VER participating through a NOT EXISTS sub-query in the second branch of the UNION. The rule description and rule call tables provide the catalogue of available rules, while IGS_PS_UNIT_VER_RU stores the actual assignment of a rule call to a specific unit and version.

The view text is a UNION of two branches. The first joins IGS_PS_UNIT_VER_RU to IGS_RU_CALL on S_RULE_CALL_CD and to IGS_RU_DESCRIPTION on RUD_SEQUENCE_NUMBER, filtering on S_RULE_TYPE_CD = 'UNIT'. The second branch drives from the rule call catalogue and returns every UNIT-type rule call for every unit version in IGS_PS_UNIT_VER for which no matching assignment row exists, producing a placeholder row with DEFINED_LAMP set to 'UNDEFINED'. The call to IGS_RU_GEN_003.RULP_GET_RULE(UVR.RUL_SEQUENCE_NUMBER) resolves the rule text for the assigned branch; the undefined branch returns a null RULE_TEXT.

Key Columns

• UNIT_CD / VERSION_NUMBER — identify the program unit and its version, forming the key with the rule call code.
• S_RULE_CALL_CD — the rule call code linking to the rule definition catalogue.
• RUL_SEQUENCE_NUMBER — the assigned rule sequence; null in the undefined branch.
• RUD_SEQUENCE_NUMBER / SELECT_GROUP — the rule description sequence and select group from IGS_RU_DESCRIPTION.
• S_RETURN_TYPE / RULE_DESCRIPTION — the return type and descriptive text of the rule.
• RULE_TEXT — the resolved rule text returned by the IGS_RU_GEN_003 API.
• DEFINED_LAMP — set to 'UNDEFINED' for unit versions with no rule assignment; null where a rule is assigned.
• Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Reporting on rule coverage for unit versions is the primary use case, particularly identifying units where a rule call remains undefined.

SELECT unit_cd, version_number, s_rule_call_cd, rule_description FROM igs_ps_unit_ver_ru_v WHERE defined_lamp = 'UNDEFINED';

To inspect the resolved rule text for a specific unit version:

SELECT unit_cd, version_number, s_rule_call_cd, rule_text FROM igs_ps_unit_ver_ru_v WHERE unit_cd = :unit_cd AND version_number = :version_number;

Because the view invokes IGS_RU_GEN_003.RULP_GET_RULE per row, queries returning RULE_TEXT should be restricted with predicates to avoid full-table scans and repeated PL/SQL calls. The view is also commonly used as a validation source in concurrent programs and personalisations that enforce rules engine completeness before enrollment processing.