Search Results fun_rule_test_results

Overview

The FUN_RULE_TEST_RESULTS table resides in the FUN schema, which belongs to the Financials Common Modules product family in Oracle E-Business Suite 12.1.1 and 12.2.2. This table stores the outcome records generated when validation rules defined within the Financials Common Modules rule engine are executed against source data during rule testing and validation cycles. It functions as a persistence layer for test evaluation output, capturing the result value produced for each tested rule identifier alongside standard Oracle EBS audit columns.

From a data modeling perspective, the ETRM metadata heuristic classifies this object as standalone, indicating no child tables depend on it through foreign key relationships. In Data Vault terms, this classification suggests treating the table as a satellite-style structure anchored to a business concept (a specific rule test execution), rather than a hub or link. Modeling efforts should therefore focus on the test identifier and result value as descriptive attributes rather than normalizing them into separate entity keys. The single documented foreign key reference from TEST_RESULTS_ID to IGS_AD_TEST_RESULTS implies an association with the IGS (Internet Graphics Server / Application Diagnostics) test results infrastructure, though this linkage is recorded as a column relationship rather than a strict enforced dependency.

Key Information Stored

The table contains nine documented columns. The most significant are:

• TEST_RESULTS_ID — The surrogate primary key and the column referenced in the foreign key relationship to IGS_AD_TEST_RESULTS. It uniquely identifies each result row.
• TEST_ID — The business-key candidate identifying which rule or test definition was executed. This is the primary column for joining back to rule definitions and for filtering results by test.
• RESULT_VALUE — The captured outcome of the test execution, holding the evaluated value produced by the rule engine.
• OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle EBS framework to manage concurrent updates.
• CREATION_DATE / CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and its originating session.

The audit column block conforms to the WHO columns convention applied across Oracle EBS transactional tables, enabling consistent auditing and concurrency control.

Common Use Cases and Queries

Typical usage centers on retrieving, auditing, and reporting rule test outcomes. A common query filters results for a specific test identifier and orders by creation date to review the latest evaluations:

• SELECT test_id, result_value, creation_date FROM fun_rule_test_results WHERE test_id = :test_id ORDER BY creation_date DESC;
• Joining to the referenced diagnostics table to enrich results: SELECT r.test_id, r.result_value, d.* FROM fun_rule_test_results r, igs_ad_test_results d WHERE r.test_results_id = d.test_results_id;
• Reconciliation reporting that counts distinct tests executed and their latest result values per period.
• Data cleanup or archival routines that purge result rows older than a retention threshold, using CREATION_DATE as the cutoff predicate.

Related Objects

The documented relationships and schema context identify the following significant dependent or associated objects:

• IGS_AD_TEST_RESULTS — Referenced through FUN_RULE_TEST_RESULTS.TEST_RESULTS_ID, providing the diagnostics-side result record.
• FUN rule definition tables — Joined via TEST_ID to obtain rule metadata for a given result.
• FND standard audit views — Used to resolve CREATED_BY and LAST_UPDATED_BY into application user names.
• Financials Common Modules rule engine APIs — The runtime components that insert result rows during test execution.

Because the table is classified as standalone, no dependent child tables require cascade handling, simplifying archival and purge operations.