Search Results fun_rule_test_mval_res

Overview

FUN_RULE_TEST_MVAL_RES is a table owned by the FUN schema (Financials Common Modules) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the results of validation tests executed by the Subledger Accounting rule-testing framework, capturing the attribute-level output produced when a rule or condition is evaluated against a set of test values. The object sits within the Financials Common Modules testing infrastructure, alongside the IGS_AD_TEST_RESULTS table that anchors the test result header.

The table is documented as VALID with a physical column count of 24, and it is classified under a heuristic Data Vault model as standalone — meaning it is not treated as a hub, link, or satellite in a strict Data Vault sense, but rather as an independent record container. This classification should be treated as a modeling suggestion rather than a constraint; functionally the table behaves as a detail/result store tied to a parent test result.

Key Information Stored

The table centers on two identifiers. TEST_RESULTS_ID is the primary key and the FK column linking to IGS_AD_TEST_RESULTS. TEST_ID identifies the specific test whose results are being stored, acting as a business-key candidate for grouping and reporting.

The remaining important columns are the attribute flexfield block and the standard audit block:

• TEST_RESULTS_ID — surrogate primary key and FK to the parent test result.
• TEST_ID — business key identifying the test definition.
• ATTRIBUTE_CATEGORY — context (category) descriptor for the descriptive flexfield.
• ATTRIBUTE1 through ATTRIBUTE15 — the Descriptive Flexfield segment values used to store test-specific validation output.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework for concurrent update control.
• CREATION_DATE, CREATED_BY — who created the record and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit trail for the last modification.

Common Use Cases and Queries

This table is typically queried during rule-testing diagnostics, when an implementer needs to inspect which attribute values a validation test produced. A common pattern joins the result detail to its parent header on the shared key:

• SELECT r.* FROM fun_rule_test_mval_res r WHERE r.test_id = :test_id;
• SELECT r.test_results_id, r.attribute_category, r.attribute1, r.attribute2 FROM fun_rule_test_mval_res r JOIN igs_ad_test_results h ON h.test_results_id = r.test_results_id WHERE h.test_id = :test_id;
• Audit reconciliation: filtering on last_update_date to find test results modified after a given date for SOX or change-tracking purposes.
• DBA housekeeping: identifying orphan result rows by left-joining to IGS_AD_TEST_RESULTS and checking for null parents.

Reporting is generally limited to the flexfield segments, which carry the actual validation payload. Because the descriptive columns are generic, meaningful reporting requires knowledge of the ATTRIBUTE_CATEGORY context assigned by the test definition.

Related Objects

• IGS_AD_TEST_RESULTS — the confirmed parent table; joined via FUN_RULE_TEST_MVAL_RES.TEST_RESULTS_ID = IGS_AD_TEST_RESULTS.TEST_RESULTS_ID. This is the only documented foreign key.
• FUN_RULE_TEST_MVAL — companion test-value table within the FUN rule-testing family, sharing the TEST_ID business key context.
• FUN_RULE_TEST_TYPES / rule-test definition tables in the FUN schema — supply the TEST_ID referenced here.
• Subledger Accounting (XLA) rule diagnostic APIs — the framework that populates these results during rule validation.
• Financials Common Modules generic flexfield APIs — used to interpret ATTRIBUTE_CATEGORY and ATTRIBUTE1–15.

Because the table is standalone under the heuristic classification, no downstream link or satellite tables are documented as depending on it; its consumers are primarily diagnostic queries against the FUN and IGS testing schema.