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

Syntra Standard Oracle Test Library

Oracle Fusion Create Manual Journal Test Cases

Validate that an authorised Oracle Fusion General Ledger user can create a manual journal using valid ledger, accounting period, journal source/category, currency, account combinations, and balanced debit and credit values.

Test ID	ORCL.R2R.GL.JRN.CREATE.MANUAL
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 34 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised Oracle Fusion General Ledger user can create a manual journal using valid ledger, accounting period, journal source, journal category, currency, account combinations, and debit and credit values.

The scenario should confirm that:

the correct Ledger is selected
the Accounting Period is open and valid
the Journal Source and Journal Category are valid and accepted
the journal Currency is handled correctly for the entered amounts
valid Account Combinations are used for each debit and credit line
the journal is balanced, with total Debit equal to total Credit
the journal Description and Reference are captured and retained

This scenario does not claim that the journal is validated, approved, posted or reconciled — those are separate downstream test cases in the journal lifecycle.

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 manual journal entry
Baseline case referenced by validate, approve, post, reverse and inquiry scenarios within the same journal lifecycle

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

Create Journal

→

Validate

→

Approve

→

Post

→

Inquiry / Reconcile

This test covers manual journal creation only, and serves as the entry point for the General Ledger journal lifecycle — a prerequisite for subsequent validation, approval, posting and inquiry/reconciliation scenarios.

Next Stage →

Validate Journal

Preconditions

Oracle Fusion General Ledger is configured and available, and the test user has access.
A valid Ledger is assigned to the test user.
An open Accounting Period exists for the ledger.
A Journal Source and Journal Category are configured.
Valid Account Combinations (with active segment values) are available for the ledger's chart of accounts.
The test user holds the appropriate journal-entry role and security access.

Exact setup, field availability and required permissions may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Ledger	${LEDGER} (active ledger)
Accounting Period	${ACCOUNTING_PERIOD} (open period)
Journal Batch	${JOURNAL_BATCH} — e.g. SYN-GL-BATCH-1001
Journal Name	${JOURNAL_NAME} — e.g. SYN-GL-JRN-1001
Journal Source	${JOURNAL_SOURCE} — e.g. Manual
Journal Category	${JOURNAL_CATEGORY} — e.g. Adjustment
Currency	${CURRENCY} — e.g. USD
Accounting Date	${ACCOUNTING_DATE} (within open period)
Account Combination (debit)	${DEBIT_ACCOUNT} (valid combination)
Account Combination (credit)	${CREDIT_ACCOUNT} (valid combination)
Debit Amount	${AMOUNT}
Credit Amount	${AMOUNT} (equal to Debit Amount)
Description	${DESCRIPTION} — e.g. Syntra Standard GL Journal Test
Reference	${REFERENCE} — e.g. SYN-GL-REF-1001

Sample values are illustrative and parameterised. Replace them with valid ledger, period, source, category, currency and account data from the target Oracle Fusion environment.

Test Steps

12 business-readable steps. SyntraFlow's automation executes ~34 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.	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	Create a Journal Open Tasks and select Create Journal.	The Create Journal page is displayed.
4	Select the Ledger Select the required Ledger for the journal. ${LEDGER}	The Ledger is accepted and journal-entry fields become available.
5	Select Accounting Period Select the Accounting Period for the journal. ${ACCOUNTING_PERIOD}	The selected period is accepted and confirmed as open.
6	Select Journal Source and Category Select the Journal Source and Journal Category for the journal. ${JOURNAL_SOURCE} / ${JOURNAL_CATEGORY} This single business step replaces separate technical actions for opening and selecting each list of values.	Source and category are accepted without unexpected validation errors.
7	Enter Debit Line Enter the debit line, including account combination and debit amount. ${DEBIT_ACCOUNT} / ${AMOUNT}	The debit line is accepted and displayed in the journal lines grid.
8	Enter Credit Line Enter the credit line, including account combination and credit amount. ${CREDIT_ACCOUNT} / ${AMOUNT}	The credit line is accepted and displayed in the journal lines grid.
9	Enter Description and Reference Enter the journal description and reference. ${DESCRIPTION} / ${REFERENCE}	Description and reference are accepted and retained on the journal.
10	Verify Journal Balance Review the journal lines and confirm total debit equals total credit. This step confirms balance ahead of Save; Oracle's own balance check is exercised again as part of the business assertion at Save/Validate.	The journal is balanced, with no unbalanced amount indicated.
11	Save the Journal Select Save.	Oracle Fusion successfully processes the save request without unexpected errors.
12	Validate the Journal and Verify StatusBusiness assertion Run journal validation and confirm the resulting journal status. This is the main business assertion for the scenario — the test does not stop merely because Save was clicked successfully.	The journal validates successfully and is identified by its generated Journal Batch/Name, with a status such as Unposted (Draft), ready for downstream approval and posting.

Expected Results

Manual journal is created successfully with the selected Ledger, Accounting Period, Journal Source and Journal Category.
Currency is applied correctly to the debit and credit amounts.
Debit and credit lines use valid Account Combinations.
The journal is balanced — total Debit equals total Credit.
Description and Reference are retained on the journal.
No unexpected save errors occur.
Newly created journal can be identified by its generated Journal Batch/Name.
Journal is saved with the expected status (e.g. Unposted/Draft).
Journal is available for subsequent validation, approval, posting and inquiry scenarios.

Key Validation Checkpoints

Ledger matches the intended test data.
Accounting Period is open and correct.
Journal Source is correct.
Journal Category is correct.
Currency is applied consistently across lines.
Debit line Account Combination is valid.
Credit line Account Combination is valid.
Total Debit equals total Credit.
Description is populated correctly.
Reference is populated correctly.
Save acknowledgement is received.
Journal Batch/Name and status exist after Save.

Core Business Scenario

Create Manual Journal

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 manual journal business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same manual journal test dozens of times simply to cover different combinations of ledger, period, source, category, currency and account configuration. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment — for example a positive Open Period + Valid Account + Balanced Amount scenario, negative Closed Period + Valid Account and Open Period + Disabled Account scenarios, a negative Debit != Credit scenario, a boundary high-value journal, and a configuration-dependent approval-required journal. Not every combination Jarvis generates is executable without validation against the target 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 — Ledgers, Accounting Periods, Currencies, Journal Sources, Journal Categories, Account Combinations, Amounts and other relevant test attributes.

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 manual journal test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Create Manual Journal 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

Balanced single debit/credit line journal
Multi-line journal with multiple balancing segments
Different journal categories
Different currencies
Different accounting dates within the open period
High-value journal
Multiple valid account combinations

Negative Scenarios

Debit and credit out of balance
Invalid account combination
Disabled or inactive account
Missing required field
Closed accounting period
Invalid journal category
Invalid currency
Cross-validation rule violation

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, and not every combination Jarvis generates is executable without further validation.

Generated Using Your DataVault Test Data

Generic test data often fails to represent the ledger structure and chart of accounts of a real Oracle Fusion environment. Where connected, Jarvis can use approved GL test data available through Syntra DataVault to create manual journal variations relevant to the customer's actual implementation.

Standard Library Definition

Ledger              ${LEDGER}
Accounting Period    ${ACCOUNTING_PERIOD}
Journal Source       ${JOURNAL_SOURCE}
Journal Category     ${JOURNAL_CATEGORY}
Currency             ${CURRENCY}
Debit Account        ${DEBIT_ACCOUNT}
Credit Account       ${CREDIT_ACCOUNT}
Amount               ${AMOUNT}

DataVault

Ledgers
  US Primary Ledger
  UK Primary Ledger
Accounting Periods
  Open periods (per ledger)
Journal Sources
  Manual
  Spreadsheet
Journal Categories
  Adjustment
  Accrual
  Reclassification
Currencies
  USD
  GBP
  EUR
Account Combinations
  Valid configured combinations (per ledger)

Jarvis AI Generates

Scenario 01 — US Primary Ledger + Open Period + Valid Account + Balanced Amount
Scenario 02 — UK Primary Ledger + GBP + Adjustment Category
Scenario 03 — Multi-Line + Multiple Balancing Segments
Scenario 04 — Closed Period + Valid Account
Scenario 05 — Open Period + Disabled Account
Scenario 06 — Debit != Credit
...

Customer-specific ledger, account and journal test data are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific GL dimensions remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of manual journal creation 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	Basic Balanced Journal	Positive	Single debit/credit line, balanced	Syntra Ready
VAR-002	Multi-Line Journal	Positive	Multiple debit and credit lines	Syntra Ready
VAR-003	Multiple Balancing Segments	Positive/Account	Lines span multiple balancing segments (e.g. cost centers)	Syntra Ready
VAR-004	Accrual Category Journal	Positive	Journal Category = Accrual	Syntra Ready
VAR-005	Adjustment Category Journal	Positive	Journal Category = Adjustment	Syntra Ready
VAR-006	GBP Journal	Positive/Currency	Currency = GBP	Syntra Ready
VAR-007	EUR Journal	Positive/Currency	Currency = EUR	Syntra Ready
VAR-008	Journal on Period Open Date	Positive/Period	Accounting Date = first day of open period	Syntra Ready
VAR-009	Journal on Period Close Date	Positive/Period	Accounting Date = last day of open period	Syntra Ready
VAR-010	High-Value Journal	Positive/Balance	Large debit/credit amount	Syntra Ready
VAR-011	Near-Zero Amount Journal	Positive/Balance	Minimal non-zero debit/credit amount	Syntra Ready
VAR-012	Multiple Account Combinations	Positive/Account	Several distinct valid account combinations used across lines	Syntra Ready
VAR-013	Maximum Practical Line Count	Positive	Journal with a large number of balanced debit/credit lines	Syntra Ready
VAR-014	Custom Description and Reference	Positive	Free-text description and reference populated	Syntra Ready
VAR-015	Statistical Journal	Positive	Non-monetary statistical unit of measure, where configured	Syntra Ready
VAR-016	Debit/Credit Out of Balance	Negative/Balance	Total Debit does not equal total Credit	Syntra Ready
VAR-017	Invalid Account Combination	Negative/Account	Account combination fails cross-validation rules	Syntra Ready
VAR-018	Disabled Account	Negative/Account	Account segment value is inactive/disabled	Syntra Ready
VAR-019	Missing Required Field	Negative	Required field (e.g. Journal Category) left blank	Syntra Ready
VAR-020	Closed Accounting Period	Negative/Period	Accounting Date falls within a closed period	Syntra Ready
VAR-021	Invalid Journal Category	Negative	Unrecognized or unconfigured journal category	Syntra Ready
VAR-022	Invalid Currency	Negative/Currency	Currency not enabled for the ledger	Syntra Ready
VAR-023	Cross-Validation Rule Violation	Negative/Account	Segment combination violates a configured cross-validation rule	Syntra Ready
VAR-024	Invalid Balancing Segment	Negative/Account	Balancing segment value does not balance within itself	Syntra Ready
VAR-025	Approval-Required Journal Category	Positive/Approval	Journal Category configured to require approval prior to posting	Syntra Ready

Positive and Negative Journal Testing

Positive Testing

Jarvis generates scenarios using ledger, period, category, currency and account combinations expected to successfully create a balanced journal.

Open Period + Valid Account + Balanced Amount → Journal Created

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's journal validations, business rules and cross-validation checks.

Debit != Credit → Expected Balance Validation
Closed Period + Valid Account → Expected Period Validation
Open Period + Disabled Account → Expected Account Validation

A negative test PASSES when Oracle produces the expected validation.

Scenario	Oracle Outcome	Test Result
Valid balanced journal	Validation succeeds	PASS
Invalid account	Expected account validation appears	PASS
Closed period	Expected period validation appears	PASS
Unexpected server 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 Manual Journal Creation Regression Pack

Basic Balanced Journal
Multi-Line Journal
Multiple Balancing Segments
Accrual Category Journal
GBP Journal
EUR Journal
High-Value Journal
Debit/Credit Out of Balance
Invalid Account Combination
Closed Accounting Period

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 releasePeriod-close testingAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	GL Manual Journal Creation Regression Pack
Schedule	Period-Close Regression
Tests	25 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 — Create Manual Journal, 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

Select Journal Source and Category

May internally include

Open Source LOV → Select Source → Open Category LOV → Select Category → Confirm

Business Step

Enter Debit Line

May internally include

Open Journal Lines Grid → Add Line → Open Account Combination Search → Enter Segments → Select Combination → Enter Debit Amount

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 UI interaction does not automatically prove the business outcome — 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 Debit Line	Pass	—
Click Save	Pass	—
Verify Journal Balanced and Saved	Pass	Pass

Related GL Journal Tests

Manual journal creation is the entry point of the same General Ledger journal lifecycle — explore the related validation, approval, posting, reversal and inquiry scenarios below.

Validate Journal Journal Approval Post Journal Reverse Journal Journal Inquiry

Turn This Standard Test into Your Oracle GL Regression Suite

Start with the Syntra Standard manual journal test, use DataVault to provide environment-specific ledger, period, currency and account data, let Jarvis generate additional positive and negative 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 Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What does the Create Manual Journal test validate in Oracle Fusion General Ledger?

It validates that a manual journal can be created using a valid ledger, open accounting period, journal source and category, currency, and valid account combinations — and that the journal is balanced and saved with the expected status.

What happens if debit does not equal credit?

Oracle Fusion is expected to prevent the journal from being saved or validated as balanced. This is treated as a negative scenario that passes when the expected balance validation is displayed, not when the journal saves unbalanced.

Can this test run across different ledgers and currencies?

Yes. The ledger, accounting period, currency, journal source and category are parameterised, so the same standard scenario can be run for different ledgers, currencies and journal categories using DataVault-driven test data.

How are the many journal creation test variations generated?

Jarvis AI uses this standard manual journal scenario together with available DataVault test data and configuration to generate relevant positive, negative and boundary variations for the customer's environment.

Does approval affect this test?

No. This scenario covers journal creation only. Whether a saved journal subsequently requires approval before posting depends on the customer's approval configuration and is covered by a separate Journal Approval test.

Can this be scheduled as part of a regression pack?

Yes. Selected manual journal creation variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution — for example nightly, before release, or during period-close testing.