Oracle Fusion Copy Journal Test Cases
Validate copying an existing Oracle Fusion General Ledger journal into a new journal, preserving unchanged attributes and correctly applying intended modifications such as accounting date, description, amount or account changes.
| Test ID | ORCL.R2R.GL.JRN.COPY |
| 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 | Medium |
| 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 verify that an authorised General Ledger user can copy an existing journal into a new journal in Oracle Fusion, correctly preserving unchanged attributes and applying any intended modifications.
The scenario should confirm that:
- the correct source journal is located and eligible to be copied
- the target accounting period is accepted, provided it is open
- the new journal's header and lines are correctly copied from the source
- intended attribute changes (accounting date, description, amount or account) are applied and retained
- unchanged attributes are preserved exactly as copied
- the original source journal remains completely unaffected
- the new journal can be saved successfully
- the new journal is available for subsequent validation and posting
This scenario does not claim that the new journal is automatically validated, approved or posted — those remain separate downstream test cases, exercised optionally as part of this scenario or independently.
When to Use This Test
- Functional testing of Oracle Fusion GL journal-copy functionality
- Regression testing after an Oracle quarterly update
- UAT sign-off for General Ledger journal entry convenience actions
- Supporting scenario referenced across create, validate, post and reversal journal test variations
Where This Test Fits in the Record-to-Report Process
Copy Journal is a supporting, cross-cutting action available at multiple points in the journal lifecycle — for example, copying a prior period's journal as the starting point for a new one. It produces a new draft journal, so it is shown alongside Create Journal above rather than as its own lifecycle stage.
Preconditions
- Oracle Fusion General Ledger is configured and available.
- An existing source journal (posted or unposted) is available to copy.
- The target accounting period is open for the target ledger.
- Valid account combinations are available if attributes are being changed.
- The test user has permission to create and copy General Ledger journals.
Exact setup, copy behavior and field availability may vary by Oracle Fusion implementation and security configuration.
Sample Test Data
| Source Journal | Existing posted or unposted GL journal |
| Target Ledger | ${LEDGER} — usually same as source ledger |
| Target Accounting Period | ${ACCOUNTING_PERIOD} |
| Changed Attributes | ${CHANGED_ATTRIBUTES} — accounting date, description, amount or account (scenario-defined) |
| Currency | Matches source journal unless the scenario specifies otherwise |
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. | Oracle Fusion home page is displayed successfully and the user session is established. |
| 2 | Navigate to General Ledger > Journals Navigate to the Journals work area within General Ledger. | The Journals work area opens successfully. |
| 3 | Locate the Source Journal Search for and open the existing journal to be copied. ${SOURCE_JOURNAL} This single business step replaces multiple technical actions such as opening search, entering journal criteria, clicking Search and selecting the result. | The correct source journal is located and its header and lines are displayed. |
| 4 | Initiate Journal Copy Select the Copy Journal action against the located source journal. | The Copy Journal dialog or page opens, pre-populated from the source journal. |
| 5 | Select the Target Accounting Period Select the accounting period the copied journal should be created in. ${ACCOUNTING_PERIOD} | The target period is accepted, provided it is open for the target ledger. |
| 6 | Review Copied Journal Header and Lines Review the new journal header and lines generated from the source journal. | Header and lines match the source journal prior to any intended changes. |
| 7 | Modify Attributes Where Required Update accounting date, description, amount or account on the copied journal as defined by the scenario. ${CHANGED_ATTRIBUTES} | Intended attribute changes are accepted without unexpected validation errors. |
| 8 | Save the New Journal Select Save. | Oracle Fusion successfully processes the save request and a new journal record is created. |
| 9 | Verify the Original Journal Is Unchanged Return to the original source journal and confirm its header, lines and status are unaffected. | The original journal remains exactly as it was before the copy action, with its own status unchanged. |
| 10 | Validate the New Journal Submit the new journal for validation. | The new journal passes validation, or displays the expected validation message for a negative scenario. |
| 11 | Post the New Journal Where Applicable Post the new journal, where the scenario calls for posting. | The new journal posts successfully, or displays the expected posting message for a negative scenario. |
| 12 | Verify New Journal Lines and StatusBusiness assertion Confirm the generated journal number, review its lines against the intended changes, and verify its final status. This is the main business assertion for the scenario — the test does not stop merely because Save was clicked successfully. | The new journal is successfully created from the source journal, correctly reflects intended attribute changes, and reaches the expected status. |
Expected Results
- A new journal is created from the source journal with header and lines correctly copied.
- Intended attribute changes (accounting date, description, amount or account) are applied and retained on the new journal.
- The original source journal remains completely unaffected by the copy action.
- The new journal can be validated like any other journal when applicable.
- The new journal can be posted like any other journal when applicable.
- The new journal is available for subsequent General Ledger journal lifecycle scenarios.
Key Validation Checkpoints
- Source journal reference is correct and eligible to be copied.
- Target accounting period is correct and open.
- Copied header and lines match the source journal prior to changes.
- Intended attribute changes are applied correctly.
- Unchanged attributes are retained exactly as copied.
- Original journal header, lines and status are unaffected.
- New journal number/identifier is generated.
- Validation outcome matches the scenario's intended result.
- Posting outcome matches the scenario's intended result, where applicable.
- Captured new journal number/identifier can be used by subsequent automated scenarios.
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core journal-copy 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 copy-journal test dozens of times simply to cover different combinations of target period, account, amount and currency. 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
Rather than maintaining dozens of near-duplicate copies of the same journal-copy 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 Copy 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.
- Copy an existing unposted journal
- Copy a posted journal
- Copy a multi-line journal
- Copy into a different accounting period
- Change the accounting date after copy
- Change the description after copy
- Change the amount after copy
- Change the account after copy
- Copy a foreign-currency journal
- Copy into a closed accounting period
- Invalid account combination after copy
- Stale reference data on the source journal
- Invalid accounting date after copy
- Required field left invalid after copy
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 — target period, account, amount and currency dimensions — to create copy-journal variations relevant to the customer's actual implementation.
Standard Library Definition
Source Journal ${SOURCE_JOURNAL}
Target Ledger ${LEDGER}
Target Period ${ACCOUNTING_PERIOD}
Changed Attributes ${CHANGED_ATTRIBUTES}
Currency ${CURRENCY}
DataVault
Ledgers US Primary Ledger UK Primary Ledger Accounting Periods Current open periods per ledger Account Combinations Valid configured combinations Currencies USD GBP EUR Journal Sources Manual Spreadsheet
Jarvis AI Generates
Scenario 01 — Copy Into Next Open Period Scenario 02 — Copy With Changed Account Scenario 03 — Copy Posted Journal, GBP Scenario 04 — Copy With Changed Amount Scenario 05 — Copy Into Closed Period Scenario 06 — Copy With Invalid Account ...
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 ledger, period and account details 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 | Copy Unposted Journal | Positive | Basic copy of an unposted single-ledger journal | Syntra Ready |
| VAR-002 | Copy Posted Journal | Positive | Source journal already posted; copy created as new draft | Syntra Ready |
| VAR-003 | Copy Multi-Line Journal | Positive | Source journal contains multiple lines | Syntra Ready |
| VAR-004 | Copy Into Next Open Period | Positive/Period | Target period differs from source period | Syntra Ready |
| VAR-005 | Copy Within Same Period | Positive/Period | Target period matches source period | Syntra Ready |
| VAR-006 | Change Accounting Date After Copy | Positive/Period | Accounting date updated on the new journal | Syntra Ready |
| VAR-007 | Change Description After Copy | Positive | Description text updated on the new journal | Syntra Ready |
| VAR-008 | Change Line Amount After Copy | Positive/Amount | Line amount updated on the new journal | Syntra Ready |
| VAR-009 | Change Account After Copy | Positive/Account | Account combination updated on a copied line | Syntra Ready |
| VAR-010 | Change Multiple Accounts After Copy | Positive/Account | Multiple line-level accounts updated | Syntra Ready |
| VAR-011 | Copy Foreign-Currency Journal | Positive/Currency | Source journal in a non-functional currency | Syntra Ready |
| VAR-012 | Copy Then Validate | Positive | New journal submitted for validation after copy | Syntra Ready |
| VAR-013 | Copy Then Post | Positive | New journal posted after copy and validation | Syntra Ready |
| VAR-014 | Copy Preserving Original Ledger | Positive | Target ledger matches source ledger | Syntra Ready |
| VAR-015 | Copy With Minimum Amount Change | Positive/Amount | Amount adjusted by a small boundary value | Syntra Ready |
| VAR-016 | Copy Into Closed Period | Negative/Period | Target accounting period is closed | Syntra Ready |
| VAR-017 | Invalid Account After Copy | Negative/Account | Account combination invalid after modification | Syntra Ready |
| VAR-018 | Stale Source Reference | Negative | Source journal changed or deleted before copy completes | Syntra Ready |
| VAR-019 | Invalid Accounting Date After Copy | Negative/Period | Accounting date outside any open period | Syntra Ready |
| VAR-020 | Required Field Invalid After Copy | Negative | Mandatory field left blank or invalid post-copy | Syntra Ready |
| VAR-021 | Invalid Amount After Copy | Negative/Amount | Amount changed to zero or a negative value | Syntra Ready |
| VAR-022 | Currency Mismatch After Copy | Negative/Currency | Currency inconsistent with target ledger configuration | Syntra Ready |
No variations match this filter.
Automatically Expand Positive and Negative Test Coverage
Positive Testing
Jarvis generates scenarios using combinations expected to successfully copy a journal and apply the intended attribute changes.
Valid Source Journal + Open Target Period + Valid Account → New Journal Created
Negative Testing
Jarvis can generate scenarios designed to exercise Oracle's validations, business rules and exception handling around journal copying.
- Copy Into Closed Period → Expected Period Validation
- Invalid Account After Copy → Expected Account Validation
- Invalid Accounting Date After Copy → Expected Date Validation
A negative test should not be marked as failed simply because Oracle rejects the transaction. If the expected Oracle validation occurs, the negative test has passed.
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Valid copy with attribute changes | New journal created correctly | PASS |
| Copy into closed period | Copy/save correctly blocked or flagged | PASS |
| Invalid account after copy | Expected account validation appears on validation | PASS |
| Unexpected 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 Copy Journal Regression Pack
- Copy Unposted Journal
- Copy Posted Journal
- Copy Multi-Line Journal
- Copy Into Next Open Period
- Change Accounting Date After Copy
- Change Line Amount After Copy
- Change Account After Copy
- Copy Foreign-Currency Journal
- Copy Into Closed Period
- Invalid Account After Copy
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.
| Pack | GL Copy Journal 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.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
Understand Why a Test Failed
SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.
From Business Scenario to Execution Evidence
Business teams get readable test documentation; automation teams retain detailed execution traceability.
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.
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.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
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 |
|---|---|---|
| Select Target Accounting Period | Pass | — |
| Click Save | Pass | — |
| Verify New Journal Lines and Status | Pass | Pass |
Related GL Journal Tests
Copying a journal is a convenience action available across the same General Ledger journal lifecycle — explore the related create, validate, post and inquiry scenarios below.
Turn This Standard Test into Your Oracle GL Regression Suite
Start with the Syntra Standard copy-journal test, use DataVault to provide environment-specific test data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.
Use This Oracle Fusion Test Case
Download Test Case
Excel, CSV or JSON export.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.