Oracle ERP Testing Tool > Test Library > SCM > Inventory Management > Item Transactions

Syntra Standard Oracle Test Library

Oracle Fusion Inventory Transaction Correction Test Cases

Validate that an eligible Oracle Fusion inventory transaction can be corrected or reversed, where supported by the transaction type and period status, while the resulting on-hand balance is adjusted correctly and the transaction's history retains a record of the original and corrected values.

Test ID	ORCL.SCM.INV.TXN.CORRECT
Application	Oracle Fusion Cloud
Product	SCM / Inventory Management
Module	Inventory Management
Process	Item Transactions
Business Flow	Plan-to-Produce
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 8 business-readable test steps; SyntraFlow's automation executes approximately 17 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that an Oracle Fusion inventory transaction eligible for correction can be corrected or reversed — where supported by the transaction type, transaction status and accounting period — while the resulting on-hand balance is adjusted correctly and the transaction's history retains an accurate record of the change.

The scenario should confirm that:

an eligible original transaction can be located and opened by an authorized user
correction or reversal is available only for transaction types and statuses that support it
a corrected quantity, lot or serial context is accepted without unexpected validation errors, when within allowed limits
the resulting on-hand balance is adjusted or restored accurately after the correction is submitted
a record of both the original and corrected transaction is retained in transaction history rather than silently overwritten
corrections attempted against ineligible transactions, closed periods or by unauthorized users are correctly prevented

This scenario covers correcting or reversing an inventory transaction that has already been recorded within Oracle Fusion Inventory Management TEST/UAT environments. Not every transaction type is eligible for correction — availability depends on transaction type, status, downstream consumption and customer configuration. It does not cover the original receipt, issue or transfer transactions, which are covered by the separate Miscellaneous Receipt, Miscellaneous Issue and Subinventory Transfer scenarios. Field-level correction variations, such as quantity, lot or serial context, are represented as data-driven variations of this same test rather than as separate published test pages.

When to Use This Test

Functional testing of inventory transaction correction and reversal eligibility for a new Oracle Fusion Inventory Management implementation
Regression testing of correction and reversal behavior after an Oracle quarterly update
UAT sign-off for inventory clerks who routinely correct transactions entered in error
Baseline case referenced by the other item transaction scenarios within the same Inventory Management process

Where This Test Fits in the Item Transactions Process

Receipt

→

Issue

→

Transfer

→

Account Alias

→

Correct

Inventory Transaction Correction applies to a transaction that has already been recorded — such as a receipt, issue, transfer or account alias transaction — adjusting or reversing it rather than creating a new transaction. Exact correction and reversal eligibility depends on transaction type, transaction status, accounting period status and customer configuration.

← Previous Stage

Account Alias Transaction

Preconditions

The original transaction exists and is in a status that is eligible for correction.
The accounting period for the original transaction is open, or correction is otherwise permitted by configuration.
The user performing the correction has the appropriate inventory transaction correction privileges.

Exact eligible transaction types, statuses and validation messages may vary by Oracle Fusion implementation, inventory configuration and security setup.

Sample Test Data

Organization	${ORGANIZATION}
Original Transaction ID	${ORIGINAL_TRANSACTION_ID}
Transaction Type	${TRANSACTION_TYPE}
Item	${ITEM}
Original Quantity	${ORIGINAL_QUANTITY}
Corrected Quantity	${CORRECTED_QUANTITY}
Lot	${LOT}
Serial	${SERIAL}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Lot and serial values apply only when the item and original transaction are lot- or serial-controlled.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~17 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 Oracle Fusion using an authorized Inventory Management test user.	Oracle Fusion signs the user in successfully and the home page loads.
2	Navigate to Inventory Management Navigate to the Inventory Management work area used to review recorded item transactions.	The Inventory Management work area opens and transaction search is available.
3	Locate the Original Transaction Search for and open the original transaction eligible for correction. ${ORIGINAL_TRANSACTION_ID} / ${ITEM} This single business step replaces multiple technical actions such as opening transaction search, entering the transaction identifier, and selecting the result.	The correct transaction is located and its current quantity, lot/serial context and status are displayed.
4	Initiate Correction or Reversal Select the option to correct or reverse the located transaction, as applicable to its transaction type.	The correction or reversal page opens showing the current transaction values.
5	Enter Corrected Values Enter the corrected quantity, lot or serial context relevant to this variation. ${CORRECTED_QUANTITY} / ${LOT} / ${SERIAL}	The corrected values are accepted without unexpected validation errors.
6	Review Resulting On-Hand Impact Review the projected on-hand balance impact of the correction before submitting. Reviewing the resulting on-hand impact before submitting lets the tester catch an incorrect entry before it is committed.	The projected on-hand balance reflects the correction that is about to be submitted.
7	Submit the Correction Submit and save the correction or reversal in the test environment.	Oracle Fusion successfully saves the correction without unexpected errors.
8	Verify On-Hand Adjusted and History RetainedBusiness assertion Reopen or refresh the transaction and on-hand inquiry, and review the transaction history after the correction is saved. This is a primary business assertion for the scenario — an accurately adjusted on-hand balance with a preserved history record is the expected pass condition, not merely a successful save.	The on-hand balance is adjusted or restored correctly, and the transaction history retains a record of both the original and corrected values.

Expected Results

Correction or reversal is accepted without unexpected errors, when the transaction type, status and period support it.
The corrected or reversed transaction is reflected accurately once the correction is submitted.
The resulting on-hand balance is adjusted or restored correctly.
A record of the correction is retained in the transaction's history.
Corrections attempted against ineligible transaction types, closed periods or invalid quantities are correctly prevented.
Unauthorized correction attempts are correctly prevented.

Key Validation Checkpoints

Corrected or reversed transaction is reflected accurately.
On-hand balance is adjusted or restored correctly.
Transaction history retains a record of the original and corrected values.

Core Business Scenario

Inventory Transaction Correction

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 inventory transaction correction business scenario. Jarvis AI can extend this scenario by generating additional type, quantity, lot/serial and period variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every transaction type, quantity direction or period condition a correction can involve. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Period variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable inventory transaction correction business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Transactions, Items, Lots, Serials and Accounting Periods.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant type, quantity and period variations.

Positive + Negative + Boundary + Period Test Variations

Valid correction and reversal scenarios alongside edge cases such as ineligible transactions, closed periods and unauthorized users.

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 a separate test page for every transaction type, quantity direction and period condition an inventory transaction can be corrected in, SyntraFlow maintains one core inventory transaction correction scenario and allows Jarvis AI to generate type-driven, quantity and period-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Inventory Transaction Correction 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 SCM Inventory Management Item Transactions.

Positive Scenarios

Correct the quantity recorded on an eligible inventory transaction
Reverse a miscellaneous receipt or issue transaction where reversal is supported
Correct the lot or serial context recorded on an eligible transaction
Correct a transaction within the same accounting period it was originally recorded

Negative Scenarios

Correction attempted on a transaction type that does not support correction or reversal
Correction attempted against a closed accounting period
Invalid or out-of-range quantity entered for the correction
Invalid lot or serial reference entered for the correction
Correction blocked by a downstream dependency, such as a transaction already relieved or consumed

These are representative examples only. Negative-scenario behavior and available correction or reversal types can depend on the customer's Oracle Fusion configuration, transaction type setup and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every transaction, item, lot, serial and period combination in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct inventory transaction correction scenarios relevant to the customer's actual implementation.

Standard Library Definition

Organization             ${ORGANIZATION}
Original Transaction ID  ${ORIGINAL_TRANSACTION_ID}
Transaction Type         ${TRANSACTION_TYPE}
Item                     ${ITEM}
Original Quantity        ${ORIGINAL_QUANTITY}
Corrected Quantity       ${CORRECTED_QUANTITY}
Lot                      ${LOT}
Serial                   ${SERIAL}

DataVault

Transactions
  Recorded transactions eligible for correction or reversal
Items
  Active items with valid quantity ranges and lot/serial control settings
Lots
  Valid lot numbers for lot-controlled items
Serials
  Valid serial numbers for serial-controlled items
Accounting Periods
  Open and closed period configuration per Organization

Jarvis AI Generates

Scenario 01 — TXN-4001 + Correct Quantity
Scenario 02 — TXN-4002 + Reverse Miscellaneous Receipt
Scenario 03 — TXN-4015 + Reverse Miscellaneous Issue
Scenario 04 — TXN-4028 + Correct Lot Context
Scenario 05 — Correction Against Closed Period
Scenario 06 — Unauthorized User Attempts Correction
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific dimensions such as transaction, item, lot and serial remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of inventory transaction correction scenarios Jarvis can generate from this business scenario, spanning transaction type, quantity, lot/serial and period conditions. 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	Correct Transaction Quantity	Positive/Type	Quantity corrected on an eligible transaction within allowed limits	Syntra Ready
VAR-002	Reverse Miscellaneous Receipt	Positive/Type	Miscellaneous receipt reversed where reversal is supported	Syntra Ready
VAR-003	Reverse Miscellaneous Issue	Positive/Type	Miscellaneous issue reversed where reversal is supported	Syntra Ready
VAR-004	Correct Lot Context	Positive/Type	Lot reference corrected on a lot-controlled transaction	Syntra Ready
VAR-005	Correct Serial Context	Positive/Type	Serial reference corrected on a serial-controlled transaction	Syntra Ready
VAR-006	Same-Period Correction	Positive/Period	Correction submitted within the same accounting period as the original transaction	Syntra Ready
VAR-007	Ineligible Transaction Type	Negative/Type	Correction attempted on a transaction type that does not support correction	Syntra Ready
VAR-008	Closed Period Correction	Negative/Period	Correction attempted against a closed accounting period	Syntra Ready
VAR-009	Invalid Quantity Entered	Negative/Type	Corrected quantity entered is not a valid numeric value or exceeds allowed limits	Syntra Ready
VAR-010	Downstream Dependency Blocks Correction	Negative/Type	Correction blocked because the original transaction has already been consumed or relieved downstream	Syntra Ready

Automatically Expand Positive and Negative Inventory Transaction Correction Coverage

Positive Testing

Jarvis generates scenarios using transaction types, quantities and periods expected to successfully correct or reverse an eligible transaction while keeping on-hand balances and history accurate.

Eligible Transaction + Valid Corrected Quantity + Open Period → Correction Accepted and History Preserved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around transaction eligibility, period status and quantity limits.

Ineligible Transaction Type → Expected Validation
Closed Period → Expected Period Validation
Invalid Quantity Entered → Expected Quantity Validation
Unauthorized User → Expected Security Validation

A negative scenario passes when Oracle correctly enforces the expected business rule or validation

Scenario	Oracle Outcome	Test Result
Valid receipt	Inventory received	PASS
Inactive item	Item validation occurs	PASS
Invalid account	Account validation occurs	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Inventory Transaction Correction Regression Pack

Correct Transaction Quantity
Reverse Miscellaneous Receipt
Reverse Miscellaneous Issue
Correct Lot Context
Correct Serial Context
Same-Period Correction
Ineligible Transaction Type
Closed Period Correction
Invalid Quantity Entered

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 inventory transaction correction scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected inventory transaction correction 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	Inventory Transaction Correction Regression Pack
Schedule	Quarterly Update Regression
Tests	10 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

Security & Persona Variations

Correction privileges for an existing inventory transaction are typically restricted by role. Jarvis can generate persona-based variations to confirm that only authorized users can correct or reverse a transaction, and that unauthorized attempts are correctly prevented rather than silently allowed.

Persona	Action	Expected	Syntra Result
Inventory Clerk	Correct Own Transaction	Allowed	PASS
Unauthorized User	Attempts Correction	Access prevented	PASS

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 inventory transaction correction scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Period coverage for the customer's environment.

Generate

Positive, Negative, Boundary and Period 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 — Inventory Transaction Correction, 8 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative + Boundary + Period 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

Locate the Original Transaction

May internally include

Open Transaction Search → Enter Transaction ID → Search → Select Transaction → Confirm

Business Step

Verify On-Hand Adjusted and History Retained

May internally include

Open On-Hand Inquiry → Read Balance → Open Transaction History → Compare Original vs Corrected Values

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 corrected transaction was retained, the on-hand balance adjusted, or history preserved — 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 Corrected Values	Pass	—
Submit the Correction	Pass	—
Verify On-Hand Adjusted and History Retained	Pass	Pass

Related Item Transaction Tests

Inventory Transaction Correction is the fifth and final scenario in the Item Transactions cluster, applying to transactions already recorded through the related receipt, issue and transfer scenarios below.

Miscellaneous Receipt Miscellaneous Issue Subinventory Transfer

Turn This Standard Test into Your Oracle Inventory Correction Regression Suite

Start with the Syntra Standard inventory transaction correction test, use DataVault to provide environment-specific test data, let Jarvis generate additional type, quantity, lot/serial and period variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Item Transactions 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

Item Transactions Test Library Inventory Management Test Library SCM Test Library Oracle ERP Testing Tool Test Library Syntra DataVault

Frequently Asked Questions

What inventory transaction types are typically eligible for correction?

Depending on transaction status and customer configuration, eligible transaction types commonly include miscellaneous receipts and issues, and certain other item transactions, corrected or reversed within configured tolerances. Availability depends on the customer's Oracle Fusion setup and whether the transaction has already been relieved or consumed downstream — not every transaction type is correctable.

What happens when the accounting period for the original transaction is closed?

Where the period is closed, correction is typically prevented or requires an alternate adjustment path, depending on customer configuration. Jarvis can generate a negative scenario confirming that Oracle correctly enforces this period-status validation rather than allowing the correction.

Is the original transaction history preserved after a correction?

Yes. A record of both the original and corrected values is expected to be retained in the transaction's history rather than silently overwritten, so downstream reviewers can see what changed.

How is security testing approached for inventory transaction corrections?

Jarvis AI can generate a security variation where a user without correction privileges attempts to correct or reverse a transaction. The expected outcome is that Oracle Fusion correctly prevents the correction, which counts as a passed negative test — see the Security & Persona Variations table on this page.

Does SyntraFlow perform the actual inventory correction in Oracle Fusion?

SyntraFlow automates the test steps against the target Oracle Fusion TEST/UAT environment using environment-specific test data and credentials. It is a test automation tool — it does not perform inventory movements or corrections outside of the environment and test scenario being executed.