Oracle ERP Testing Tool > Test Library > Financials > General Ledger > Journals

Syntra Standard Oracle Test Library

Oracle Fusion Journal Inquiry & Verification Test Cases

Validate that an Oracle Fusion General Ledger user can search for and retrieve journals using key attributes, and that the journal header, line, status and debit/credit total information displayed matches the underlying journal — across unposted, posted and reversed journals, including correctly empty or access-restricted results.

Test ID	ORCL.R2R.GL.JRN.INQUIRY
Application	Oracle Fusion Cloud
Product	Financials
Module	General Ledger
Process	Journals
Business Flow	Record-to-Report
Scenario Type	Positive / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 12 business-readable test steps; SyntraFlow's automation executes approximately 33 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate search, retrieval and verification of journal information across relevant journal attributes and statuses in Oracle Fusion General Ledger.

The scenario should confirm that:

valid search criteria correctly return the matching journal(s)
journal header details displayed match the underlying journal data
journal lines displayed match the underlying journal data
debit and credit totals displayed match the underlying journal and are in balance
journal status — unposted, posted or reversed — is displayed correctly
posting and reversal reference information is displayed correctly
a search with no matching criteria returns a correctly empty result set
a search outside the user's ledger/security access returns a correctly access-restricted result

This scenario does not claim to validate journal creation, approval, posting or reversal processing itself — those are covered by the separate upstream and downstream test cases in the Journal Lifecycle family.

When to Use This Test

Functional testing of a new Oracle Fusion General Ledger implementation
Regression testing after an Oracle quarterly update
UAT sign-off for General Ledger journal search and reporting
Period-close verification that journals of expected status and total exist before close is finalised

Where This Test Fits in the Record-to-Report Process

Journal Creation

→

Validation

→

Approval

→

Posting

→

Inquiry / Reconcile

→

Reversal

→

Period Close

Journal inquiry is not a single terminal step in the Record-to-Report process — it is used throughout the journal lifecycle to verify state, for example confirming a newly created journal exists, checking that a journal has posted, or reviewing a reversal relationship. This test covers search, retrieval and verification of journal information and does not itself create, approve, post or reverse journal entries.

← Previous Stage

Post Journal

Preconditions

Oracle Fusion General Ledger is configured and available, with journal inquiry/view privileges granted to the test user.
Journals of varying status — unposted, posted, reversed and imported — exist in the test environment to search for.
Valid search criteria values (journal batch, name, period, source, category, account) are known for at least one journal of each status.
Relevant accounting periods, including at least one open and one closed period, are available for period-based searches.
The test user's data access/security profile is understood, to support both within-access and outside-access search scenarios.

Exact search fields, available statuses and security restrictions may vary by Oracle Fusion implementation and configuration.

Sample Test Data

Journal Batch	Manual GL Batch – Period Close Adjustments
Journal Name	ACCR-JUL-001
Accounting Period	${ACCOUNTING_PERIOD}
Journal Source	Manual / Spreadsheet / Payables / Receivables
Journal Category	Adjustment / Accrual / Standard
Account Combination	${ACCOUNT}
Expected Journal Status	Unposted / Posted / Reversed
Expected Debit/Credit Totals	10,000.00 / 10,000.00

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.

Test Steps

12 business-readable steps. SyntraFlow's automation executes ~33 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Sign in to Oracle Fusion Sign in to the Oracle Fusion environment using an authorised General Ledger test user with journal inquiry/view privileges.	Oracle Fusion home page is displayed successfully and the user session is established.
2	Navigate to General Ledger > Journals Navigate to the General Ledger Journals work area.	The Journals work area opens successfully.
3	Open Journal Search/Inquiry Open the journal search or inquiry page.	The journal search page is displayed with the available search fields.
4	Enter Search Criteria Enter one or more search criteria — journal batch, name, accounting period, source, category or account. ${ACCOUNTING_PERIOD} / ${ACCOUNT} This single business step covers entering any combination of the available search fields; the specific combination used varies by test variation.	The entered search criteria are accepted without unexpected errors.
5	Execute the Search Execute the search using the entered criteria.	The search is processed and a result list — including a correctly empty result where no journal matches — is returned.
6	Review the Returned Journal(s) Review the list of journals returned by the search.	The returned journal(s), or the correctly empty or access-restricted result, match the entered search criteria and the user's data access.
7	Select a Journal to Review Select a specific journal from the search results.	The selected journal's detail is displayed.
8	Review Journal Header Details Review the journal header — batch, name, period, source, category, currency and description.	Journal header details displayed match the underlying journal data.
9	Review Journal Lines Review the individual journal lines, including account, debit, credit and line description.	Journal lines displayed match the underlying journal data.
10	Review Debit/Credit Totals Review the journal's header-level debit and credit totals.	Debit and credit totals displayed match the underlying journal, agree with the sum of the lines, and are in balance.
11	Review Journal Status and Posting/Reversal Information Review the journal's status — unposted, posted or reversed — and any posting or reversal reference information.	Journal status and posting/reversal reference information displayed match the underlying journal's actual state.
12	Drill Into Journal Details Where AvailableBusiness assertion Where a drill-down path is available, drill from the journal line into the underlying source or subledger detail. This is the main business assertion for the scenario — the test does not stop merely because a search returned results; the retrieved and displayed information must match the underlying journal.	Drill-down detail is consistent with the summary journal information, confirming that the information displayed accurately represents the underlying journal.

Expected Results

Search criteria correctly return the matching journal(s), including a correctly empty result set where no journal matches.
Journal header details displayed match the underlying journal data.
Journal lines displayed match the underlying journal data.
Debit and credit totals displayed match the underlying journal and are in balance.
Journal status — unposted, posted or reversed — displayed matches the underlying journal.
Posting and reversal reference information displayed matches the underlying journal.
A search outside the user's ledger/security access returns a correctly access-restricted result.
Drill-down journal detail, where available, is consistent with the summary information.
No unexpected search or retrieval errors occur.

Key Validation Checkpoints

Search criteria are accepted without unexpected errors.
Returned journal(s) match the entered search criteria.
A search with no matching criteria returns a correctly empty result set.
A search outside the user's security access returns a correctly access-restricted result.
Journal header details displayed match the underlying journal.
Journal lines displayed match the underlying journal.
Debit and credit totals displayed match the underlying journal and are in balance.
Journal status displayed matches the underlying journal.
Posting and reversal reference information displayed matches the underlying journal.
Drill-down detail is consistent with the summary journal information.
Imported journal source/category information is displayed correctly.
Accounting date/period displayed matches the underlying journal.

Core Business Scenario

Journal Inquiry

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core journal inquiry business scenario. Jarvis AI can extend this scenario by generating additional search and verification variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same inquiry test dozens of times simply to cover different combinations of batch, period, source, category, account and status. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Journal Batches, Journal Names, Accounting Periods, Journal Sources, Journal Categories, Account Combinations and Expected Statuses.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining dozens of near-duplicate copies of the same journal inquiry test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant search and verification variations using the customer's available test data.

AI-Generated Test Variations

The same Journal Inquiry business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to General Ledger Journals.

Positive Scenarios

Search by journal batch
Search by journal name
Search by accounting period
Search by journal source
Search by journal category
Search by account combination
Search for a posted journal
Search for an unposted journal
Review journal lines
Review journal status
Review debit/credit totals
Review accounting date
Review reversal relationship
Review imported journal

Negative Scenarios

Search with no matching criteria
Invalid or malformed search criteria
Search outside the user's ledger/security access
Search across a closed period with no matching data
Search using a nonexistent journal batch or name

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, controls and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data often fails to represent the configuration of a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to create journal inquiry variations relevant to the customer's actual implementation.

Standard Library Definition

Journal Batch     ${JOURNAL_BATCH}
Journal Name      ${JOURNAL_NAME}
Accounting Period ${ACCOUNTING_PERIOD}
Journal Source    ${JOURNAL_SOURCE}
Journal Category  ${JOURNAL_CATEGORY}
Account           ${ACCOUNT}
Expected Status   ${EXPECTED_STATUS}

DataVault

Journal Batches
  Manual GL Batch – Period Close Adjustments
  Spreadsheet Import Batch
Accounting Periods
  Jul-2026 (Open)
  Jun-2026 (Closed)
Journal Sources
  Manual
  Spreadsheet
  Payables
Journal Categories
  Adjustment
  Accrual
  Standard
Expected Statuses
  Unposted
  Posted
  Reversed

Jarvis AI Generates

Scenario 01 — Batch Search + Posted Status
Scenario 02 — Period Search + Closed Period + Reversed Status
Scenario 03 — Source Search + Spreadsheet Import
Scenario 04 — Category Search + Accrual
Scenario 05 — No Matching Criteria
Scenario 06 — Search Outside Security Access
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific data such as journal batches, names and account combinations remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of scenarios Jarvis can generate from this business scenario. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Search by Journal Batch	Batch	Batch name used as primary search criterion	Syntra Ready
VAR-002	Search by Journal Name	Batch	Journal name used as primary search criterion	Syntra Ready
VAR-003	Search by Accounting Period	Period	Search restricted to a specific accounting period	Syntra Ready
VAR-004	Search by Journal Source	Source	Search filtered by journal source, e.g. Manual or Spreadsheet	Syntra Ready
VAR-005	Search by Journal Category	Category	Search filtered by journal category, e.g. Adjustment or Accrual	Syntra Ready
VAR-006	Search by Account Combination	Account	Search filtered by a specific account combination	Syntra Ready
VAR-007	Search for a Posted Journal	Status	Search criteria return a journal with Posted status	Syntra Ready
VAR-008	Search for an Unposted Journal	Status	Search criteria return a journal with Unposted status	Syntra Ready
VAR-009	Search for a Reversed Journal	Status/Reversal	Search criteria return a journal with Reversed status	Syntra Ready
VAR-010	Review Journal Lines	Account	Line-level account, debit and credit detail reviewed	Syntra Ready
VAR-011	Review Journal Status	Status	Displayed status reviewed against expected value	Syntra Ready
VAR-012	Review Debit/Credit Totals	Account	Header totals reviewed against line-level sum	Syntra Ready
VAR-013	Review Accounting Date	Period	Accounting date reviewed against expected period	Syntra Ready
VAR-014	Review Reversal Relationship	Reversal	Original and reversal journal cross-reference reviewed	Syntra Ready
VAR-015	Review Imported Journal	Source	Journal imported from a subledger or spreadsheet source reviewed	Syntra Ready
VAR-016	Drill Into Journal Details	Account/Status	Drill-down from journal line to underlying source/subledger detail	Syntra Ready
VAR-017	Search Combining Period and Source	Period/Source	Multiple criteria combined in a single search	Syntra Ready
VAR-018	Search Combining Category and Account	Category/Account	Multiple criteria combined in a single search	Syntra Ready
VAR-019	Search With No Matching Criteria	Batch	No journal matches the entered criteria	Syntra Ready
VAR-020	Invalid or Malformed Search Criteria	Batch	Criteria entered in an unsupported or malformed format	Syntra Ready
VAR-021	Search Outside Security Access	Status	Search targets a journal outside the user's data access	Syntra Ready
VAR-022	Search Across Closed Period With No Data	Period	Closed-period search criteria return no results	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using valid search criteria expected to correctly retrieve and display journal information.

Valid Batch + Valid Period + Valid Account → Correct Journal Returned With Matching Header, Lines and Totals

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's search handling, empty-result behaviour and security-restricted access around journal inquiry.

No Matching Search Criteria → Expected Empty Result Set
Search Outside Ledger/Security Access → Expected Access-Restricted Result
Invalid or Malformed Search Criteria → Expected Search Validation

A search test should not be marked as failed simply because it returns no records or an access-restricted result. If the search correctly returns the expected outcome — including a correctly empty result set or a correctly access-restricted result — the inquiry test has passed.

Scenario	Oracle Outcome	Test Result
Valid search criteria	Correct journal returned with matching header, line and total detail	PASS
Search with no matching criteria	Correctly empty result set	PASS
Search outside security access	Correctly access-restricted result	PASS
Unexpected search/processor error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated scenarios and group them into reusable execution packs.

GL Journal Inquiry Regression Pack

Search by Journal Batch
Search by Accounting Period
Search by Account Combination
Search for a Posted Journal
Search for a Reversed Journal
Review Debit/Credit Totals
Review Reversal Relationship
Review Imported Journal
Search With No Matching Criteria
Search Outside Security Access

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	GL Journal Inquiry Regression Pack
Schedule	Quarterly Update Regression
Tests	22 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

Journal Lifecycle

Not every journal moves through every stage, and approval depends on customer configuration. Stages link to the corresponding test scenario family.

Create / Import→Validate→Approve→Post→

Inquiry

→Reverse

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Library — Journal Inquiry, 12 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Enter Search Criteria

May internally include

Open Search Panel → Focus Criteria Field → Enter Value → Apply Criteria → Repeat for Additional Fields

Business Step

Drill Into Journal Details Where Available

May internally include

Open Journal Line → Open Drill-Down Link → Navigate to Source/Subledger Detail → Return to Journal

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful search action does not automatically prove the retrieved data is correct — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

Step	Action Status	Business Validation
Enter Search Criteria	Pass	—
Execute Search	Pass	—
Verify Journal Detail Matches Underlying Data	Pass	Pass

Related GL Journal Tests

Journal inquiry is used to verify journal state throughout the same General Ledger journal lifecycle — explore the related creation, approval, posting and reversal scenarios below.

Create Manual Journal Post Journal Reverse Journal Journal Approval

Turn This Standard Test into Your Oracle GL Regression Suite

Start with the Syntra Standard journal inquiry test, use DataVault to provide environment-specific test data, let Jarvis generate additional search and verification variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore GL Journals Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

General Ledger Journals General Ledger Oracle GL Testing Tool Prebuilt Oracle Test Library Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What can be searched for in Oracle Fusion journal inquiry?

Journals can typically be searched by journal batch, journal name, accounting period, journal source, journal category or account combination, depending on what is enabled in the target Oracle Fusion environment.

Does this test cover reversed and imported journals?

Yes. Journal inquiry variations cover searching for and reviewing journals across unposted, posted, reversed and imported statuses, including reviewing the relationship between an original journal and its reversal.

What happens if a search returns no results?

A search that correctly returns no results for criteria with no matching journal is treated as a pass, not a failure — the test verifies that the empty result is the expected outcome for the given criteria.

How are the many journal inquiry test variations generated?

Jarvis AI uses this standard journal inquiry scenario together with available DataVault test data — batches, periods, sources, categories, accounts and expected statuses — to generate relevant search and verification variations for the customer's environment.

Can this journal inquiry test be scheduled?

Yes. Selected journal inquiry variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution.

Does journal inquiry modify any journal data?

No. This scenario is a search and verification test only — it does not create, approve, post or reverse journal entries. Those actions are covered by the separate test cases in the Journal Lifecycle family.