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

Syntra Standard Oracle Test Library

Oracle Fusion Subinventory Transfer Test Cases

Validate that material can be moved between subinventories within the same Oracle Fusion inventory organization using a valid item, source and target subinventory, locator, quantity, lot and serial detail, and that the total organization on-hand quantity is preserved across the transfer.

Test ID	ORCL.SCM.INV.TXN.SUBINV.TRANSFER
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 9 business-readable test steps; SyntraFlow's automation executes approximately 24 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that material can be transferred between subinventories within the same Oracle Fusion inventory organization using a valid item, source subinventory and locator, target subinventory and locator, quantity, and lot or serial detail where applicable, and that the transfer is reflected correctly on both sides of the movement.

The scenario should confirm that:

the transfer is initiated for the correct inventory organization and item
source subinventory and locator information is captured correctly
target subinventory and locator information is captured correctly
lot and serial detail, where the item is lot- or serial-controlled, is carried correctly to the target subinventory
the total organization on-hand quantity is preserved across the transfer — the source subinventory decreases by exactly the amount the target subinventory increases, so net organization on-hand is unchanged
Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers a subinventory-to-subinventory transfer within a single Oracle Fusion inventory organization in TEST/UAT environments, including locator, lot and serial variations. A core assertion of this scenario is balance conservation: the source subinventory quantity decrease must equal the target subinventory quantity increase, leaving total organization on-hand unchanged. It does not cover transfers between inventory organizations, receiving transactions or standalone corrections, which are covered by separate scenarios in the same Item Transactions cluster.

When to Use This Test

Functional testing of subinventory transfer processing for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of subinventory transfer behavior after an Oracle quarterly update
UAT sign-off for warehouse and inventory personnel who routinely move stock between subinventories
Baseline case referenced by the Miscellaneous Receipt, Miscellaneous Issue and Inventory Transaction Correction scenarios within the same Item Transactions cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during a transfer before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Plan-to-Produce Item Transactions Process

Navigate to Inventory

→

Initiate Transfer

→

Select Item

→

Select Source Sub/Locator

→

Select Target Sub/Locator

→

Enter Quantity

→

Review & Submit

Subinventory Transfer sits within the Item Transactions cluster of the Plan-to-Produce flow, alongside Miscellaneous Receipt, Miscellaneous Issue and Inventory Transaction Correction. It is used whenever material needs to move between subinventories in the same inventory organization — for example between a receiving dock and a staging area, or between a general storage area and a quality-hold location — without changing item ownership or organization. Exact fields available, locator control and validation depend on subinventory and item setup and customer-specific Oracle Fusion configuration.

← Previous Stage

Miscellaneous Issue

Next Stage →

Inventory Transaction Correction

Preconditions

The inventory organization has the source and target subinventories configured and active.
The source subinventory holds sufficient on-hand quantity of the item being transferred.
The target subinventory, and target locator where locator control is enabled, is defined and active for the organization.
The item is active and enabled for the transacting inventory organization.
Where the item is lot- or serial-controlled, valid lot and/or serial numbers exist for the on-hand quantity in the source subinventory.
The test user has access to perform subinventory transfers for the organization.

Exact field availability, locator control, lot/serial control and validation messages may vary by Oracle Fusion implementation, subinventory and item configuration, and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Inventory Organization	${INVENTORY_ORGANIZATION}
Item	${ITEM}
Source Subinventory	${SOURCE_SUBINVENTORY}
Target Subinventory	${TARGET_SUBINVENTORY}
Source Locator	${SOURCE_LOCATOR}
Target Locator	${TARGET_LOCATOR}
Quantity	${QUANTITY}
UOM	${UOM}
Lot	${LOT}
Serial	${SERIAL}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Lot and serial fields apply only when the item being transferred is lot- or serial-controlled; locator fields apply only when the subinventory is locator-controlled.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Inventory Sign in to Oracle Fusion using an authorised inventory test user and navigate to the Inventory Management work area.	The Inventory Management work area opens successfully.
2	Initiate Subinventory Transfer Open the transaction page and initiate a new subinventory transfer for the correct inventory organization. ${INVENTORY_ORGANIZATION}	A new, unsaved subinventory transfer is opened for the correct inventory organization.
3	Select Item Search for and select the item to be transferred. ${ITEM}	The item is accepted and its current on-hand quantity and control attributes are displayed.
4	Select Source Subinventory and Locator Select the source subinventory and, where locator control is enabled, the source locator that the item is being moved from. ${SOURCE_SUBINVENTORY} / ${SOURCE_LOCATOR}	The source subinventory and locator are accepted and the available on-hand quantity is confirmed.
5	Select Target Subinventory and Locator Select the target subinventory and, where locator control is enabled, the target locator that the item is being moved to. ${TARGET_SUBINVENTORY} / ${TARGET_LOCATOR}	The target subinventory and locator are accepted and reflected on the transfer line.
6	Enter Quantity and Lot/Serial Detail Enter the transfer quantity and unit of measure, and select lot and/or serial numbers where the item is lot- or serial-controlled. ${QUANTITY} / ${UOM} / ${LOT} / ${SERIAL} Lot and serial entry only applies when the item's control attributes require it.	Quantity, UOM and any lot/serial detail are accepted without unexpected validation errors.
7	Review Transfer Detail Review the source, target, quantity and lot/serial detail as computed by Oracle Fusion before submitting. Reviewing the transfer before submission lets the tester catch an incorrect field entry before the transaction posts.	The reviewed transfer reflects the entered item, subinventories, locators, quantity and lot/serial detail.
8	Submit the Transfer Submit the subinventory transfer for processing in the test environment.	Oracle Fusion successfully processes the subinventory transfer without unexpected errors.
9	Verify Source Decreased and Target Increased by the Same AmountBusiness assertion Reopen or query on-hand balances for the source and target subinventories and confirm the quantity change on each side. This is the primary business assertion for the scenario — balance conservation across the transfer is the expected pass condition, not merely a successful submission.	The source subinventory quantity has decreased by exactly the transferred amount, the target subinventory quantity has increased by exactly the same amount, and total organization on-hand quantity is unchanged.

Expected Results

The subinventory transfer is created for the correct inventory organization and item.
Source subinventory and locator are correct.
Target subinventory and locator are correct.
Lot and/or serial detail, where applicable, is correctly reflected on the target subinventory.
The source subinventory quantity decrease equals the target subinventory quantity increase.
Total organization on-hand quantity is unchanged after the transfer.
The transfer is visible and traceable in transaction history for the test user.

Key Validation Checkpoints

Total organization quantity preserved across the transfer — source decrease equals target increase.
Source subinventory quantity reduced by the transferred amount.
Target subinventory quantity increased by the transferred amount.
Transfer history recorded.

Core Business Scenario

Subinventory Transfer

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 Subinventory Transfer business scenario. Jarvis AI can extend this scenario by generating additional subinventory, locator, lot/serial and security variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every subinventory, locator, lot or serial combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Control variations for the customer's environment — including transfers of a lot- or serial-controlled item, where correctly carrying lot and serial detail to the target subinventory is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Subinventory Transfer business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Inventory Organizations, Items, Subinventories, Locators, Lots and Serials.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant subinventory, locator, lot/serial and security variations.

Positive + Negative Test Variations

Valid transfer scenarios and edge cases such as insufficient quantity, invalid locators or restricted access.

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 possible subinventory, locator, lot, serial or quantity combination, SyntraFlow maintains one core Subinventory Transfer scenario and allows Jarvis AI to generate subinventory-, locator- and control-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Subinventory Transfer 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

Transfer the full on-hand quantity from source to target subinventory
Transfer a partial quantity, leaving the remainder in the source subinventory
Transfer between specific source and target locators
Transfer a lot-controlled item with lot detail carried to the target subinventory
Transfer a serial-controlled item with serial detail carried to the target subinventory
Transfer between a different pair of valid source and target subinventories

Negative Scenarios

Attempt a transfer using the same subinventory as both source and target where this is invalid
Attempt a transfer for a quantity greater than the available source on-hand quantity
Enter an invalid or inactive target subinventory
Enter an invalid locator for the source or target subinventory
Attempt a transfer with a lot number that does not match the source subinventory's on-hand lot
Attempt a transfer with a serial number that does not match the source subinventory's on-hand serial
Attempt a transfer of an inactive item

These are representative examples only. Negative-scenario behavior and available field combinations 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 rarely represents every subinventory, locator, lot and serial combination in a real Oracle Fusion inventory organization. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Subinventory Transfer scenarios relevant to the customer's actual implementation.

Standard Library Definition

Inventory Organization  ${INVENTORY_ORGANIZATION}
Item                    ${ITEM}
Source Subinventory     ${SOURCE_SUBINVENTORY}
Target Subinventory     ${TARGET_SUBINVENTORY}
Source Locator          ${SOURCE_LOCATOR}
Target Locator          ${TARGET_LOCATOR}
Quantity                ${QUANTITY}
UOM                     ${UOM}
Lot                     ${LOT}
Serial                  ${SERIAL}

DataVault

Inventory Organizations
  Organizations enabled for subinventory transfer testing
Items
  Active items with lot/serial control attributes
Subinventories / Locators
  Configured source and target subinventories and locators
Lots / Serials
  On-hand lot and serial numbers available for transfer
Security
  Personas eligible to perform subinventory transfers

Jarvis AI Generates

Scenario 01 — Full Quantity Transfer, Subinventory A to B
Scenario 02 — Partial Quantity Transfer, Subinventory A to B
Scenario 03 — Locator-to-Locator Transfer
Scenario 04 — Lot-Controlled Item Transfer
Scenario 05 — Serial-Controlled Item Transfer
Scenario 06 — Unauthorized User Attempts Subinventory Transfer
...

Subinventory Transfer test data can include sensitive inventory categories such as item, location and lot/serial information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific inventory dimensions remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/ for details.

Example Test Variations

Representative examples of Subinventory Transfer scenarios Jarvis can generate from this business scenario, spanning subinventory, locator, lot/serial and security 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	Standard Full Quantity Transfer	Positive	Full on-hand quantity moved from source to target subinventory	Syntra Ready
VAR-002	Partial Quantity Transfer	Positive	Only part of the source on-hand quantity is transferred, remainder stays in source	Syntra Ready
VAR-003	Locator-to-Locator Transfer	Positive/Locator	Transfer specifies both source and target locators within their subinventories	Syntra Ready
VAR-004	Lot-Controlled Transfer	Positive/Lot/Serial	Transfer of a lot-controlled item with lot number carried to target subinventory	Syntra Ready
VAR-005	Serial-Controlled Transfer	Positive/Lot/Serial	Transfer of a serial-controlled item with serial numbers carried to target subinventory	Syntra Ready
VAR-006	Different Source/Target Subinventories	Positive	Transfer executed between an alternate valid subinventory pair	Syntra Ready
VAR-007	Invalid Same Source and Target	Negative	Source and target subinventory entered as the same value where this is invalid	Syntra Ready
VAR-008	Insufficient Source Quantity	Negative	Requested transfer quantity exceeds available source on-hand quantity	Syntra Ready
VAR-009	Invalid Target Subinventory	Negative	Target subinventory entered is invalid or inactive for the organization	Syntra Ready
VAR-010	Invalid Locator	Negative/Locator	Locator entered is invalid for the selected source or target subinventory	Syntra Ready
VAR-011	Lot Mismatch	Negative/Lot/Serial	Lot number entered does not match the source subinventory's on-hand lot	Syntra Ready
VAR-012	Serial Mismatch	Negative/Lot/Serial	Serial number entered does not match the source subinventory's on-hand serial	Syntra Ready
VAR-013	Inactive Item	Negative	Selected item is inactive as of the transfer date	Syntra Ready
VAR-014	Security Restriction — Unauthorized Transfer	Negative	Requesting user lacks access to transfer material for the inventory organization	Syntra Ready

Automatically Expand Positive and Negative Subinventory Transfer Coverage

Positive Testing

Jarvis generates scenarios using item, subinventory, locator, quantity and lot/serial combinations expected to successfully transfer material in Oracle Fusion.

Valid Item + Sufficient Source Quantity + Valid Target Subinventory/Locator → Transfer Completed, Balances Preserved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around quantity, subinventory, locator, lot/serial and security.

Insufficient Source Quantity → Expected Quantity Validation
Invalid Target Subinventory → Expected Subinventory Validation
Invalid Locator → Expected Locator Validation
Lot/Serial Mismatch → Expected Lot/Serial Validation
Unauthorized User → Expected Access Restriction

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 Subinventory Transfer scenarios and group them into reusable execution packs.

SCM Inventory Management Subinventory Transfer Regression Pack

Standard Full Quantity Transfer
Partial Quantity Transfer
Locator-to-Locator Transfer
Lot-Controlled Transfer
Serial-Controlled Transfer
Different Source/Target Subinventories
Insufficient Source Quantity
Invalid Locator
Lot Mismatch
Security Restriction — Unauthorized Transfer

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

Once scheduled, SyntraFlow executes the selected Subinventory Transfer 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	SCM Inventory Management Subinventory Transfer Regression Pack
Schedule	Quarterly Update Regression
Tests	14 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

Access to transfer material between subinventories for a given inventory organization is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that transfer access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Clerk	Transfer Between Subinventories	Allowed	PASS
Unauthorized User	Attempts Transfer	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 Subinventory Transfer scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Control coverage — including transfers of a lot- or serial-controlled item — 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 — Subinventory Transfer, 9 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 Source Subinventory and Locator

May internally include

Open Subinventory LOV → Select Source Subinventory → Open Locator LOV → Select Source Locator → Confirm Available Quantity

Business Step

Verify Source Decreased and Target Increased by the Same Amount

May internally include

Open On-hand Balances → Query Source Subinventory → Query Target Subinventory → Compare Pre/Post Quantities → Confirm Organization Total Unchanged

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 transfer moved the correct quantity — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. When a step fails, SyntraFlow's evidence trail is designed to help a tester classify the likely cause — for example DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Subinventory Transfer failed — Likely category: DATA_ERROR — Evidence: target locator is invalid for the item — Recommended action: select a valid locator and retry. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Quantity and Lot/Serial Detail	Pass	—
Submit the Transfer	Pass	—
Verify Source Decreased and Target Increased by the Same Amount	Pass	Pass

Related Item Transaction Tests

Subinventory Transfer sits alongside the other core item transaction scenarios — explore the related receipt, issue and correction scenarios below.

Miscellaneous Receipt Miscellaneous Issue Inventory Transaction Correction

Turn This Standard Test into Your Oracle SCM Subinventory Transfer Regression Suite

Start with the Syntra Standard Subinventory Transfer test, use DataVault to provide environment-specific test data, let Jarvis generate additional subinventory, locator and lot/serial variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Inventory Management 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

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

Frequently Asked Questions

What does a subinventory transfer test validate?

This test validates that material can be moved from one subinventory to another within the same Oracle Fusion inventory organization, using a valid item, source and target subinventory, locator, quantity, and lot or serial detail where the item requires it, and that the transfer is reflected correctly on both sides of the movement.

How is quantity conservation verified for a subinventory transfer?

SyntraFlow queries on-hand balances for both the source and target subinventories before and after the transfer. The scenario's core business assertion confirms that the source quantity decrease exactly equals the target quantity increase, so total organization on-hand quantity is unchanged by the movement.

How are locator-to-locator transfers handled?

Where a subinventory is locator-controlled, the transfer also captures source and target locator detail. SyntraFlow's generated variations include locator-to-locator transfers so that locator-level movement, not just subinventory-level movement, is exercised.

Do all the listed positive and negative variations need separate test library pages?

No. Rather than maintaining a separate public page for every subinventory, locator, lot or serial combination, SyntraFlow maintains this one core Subinventory Transfer scenario and uses Jarvis AI to generate the underlying variations from customer-specific DataVault test data. This page remains the canonical reference for all of them.

How does security testing work for subinventory transfers?

Access to transfer material between subinventories in a given inventory organization is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an authorised inventory clerk versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.