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

Syntra Standard Oracle Test Library

Oracle Fusion Miscellaneous Issue Test Cases

Validate that a miscellaneous issue correctly removes available on-hand quantity from a source subinventory in Oracle Fusion SCM, using a valid item, subinventory, quantity, unit of measure, lot or serial where controlled, and issue account.

Test ID	ORCL.SCM.INV.TXN.MISC.ISSUE
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 19 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a miscellaneous issue transaction correctly removes available on-hand quantity for an item from a source subinventory in Oracle Fusion SCM Inventory Management, using a valid inventory organization, item, subinventory, quantity, unit of measure, lot or serial control where applicable, and issue account.

The scenario should confirm that:

the miscellaneous issue is recorded against the correct inventory organization, item and source subinventory
the issued quantity and unit of measure are captured correctly
lot and/or serial detail is captured and updated correctly where the item is lot- or serial-controlled
the transaction is recorded against the correct issue account
on-hand quantity in the source subinventory decreases by the issued quantity once the transaction completes
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 issuing available on-hand inventory out of Oracle Fusion SCM using the Miscellaneous Transaction function. It does not cover receiving inventory in (covered by the separate Miscellaneous Receipt scenario), moving stock between subinventories (Subinventory Transfer), or correcting a previously completed transaction (Inventory Transaction Correction) — all in the same Item Transactions cluster.

When to Use This Test

Functional testing of miscellaneous issue transactions for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of on-hand quantity behavior after an Oracle quarterly update
UAT sign-off for warehouse and inventory teams that routinely issue stock for internal consumption, scrap or sampling
Baseline case referenced by the Miscellaneous Receipt, Subinventory Transfer and Inventory Transaction Correction scenarios within the same Item Transactions cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during a miscellaneous issue before escalating as a possible APPLICATION_ERROR

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

Navigate to Inventory

→

Initiate Miscellaneous Issue

→

Select Item/Subinventory

→

Enter Quantity

→

Select Account

→

Review

→

Submit

Miscellaneous Issue is one of the core Item Transactions used to adjust on-hand inventory outside of standard order or work order flows within Plan-to-Produce — for example, issuing material for internal consumption, sampling, scrap or non-order-related usage. It is the counterpart to Miscellaneous Receipt and sits alongside Subinventory Transfer and Inventory Transaction Correction in the same cluster. Exact fields, account defaulting and lot/serial behavior depend on item setup, subinventory configuration and customer-specific Oracle Fusion configuration.

← Previous Stage

Miscellaneous Receipt

Next Stage →

Subinventory Transfer

Preconditions

The inventory organization is configured and active in the target Oracle Fusion SCM environment.
Available on-hand quantity for the item exists in the source subinventory.
The item is active and enabled for the inventory organization.
Where the item is lot- and/or serial-controlled, valid available lot and/or serial values exist for the item.
The issue account entered on the transaction is valid and open for the transaction date.
The test user has appropriate access to perform a miscellaneous issue for the inventory organization.

Exact field availability, mandatory fields, lot/serial control and validation messages may vary by Oracle Fusion implementation, item setup, subinventory configuration and customer-specific configuration. On-hand and readiness requirements vary by implementation.

Sample Test Data

Inventory Organization	${INVENTORY_ORGANIZATION}
Item	${ITEM}
Subinventory	${SUBINVENTORY}
Quantity	${QUANTITY}
UOM	${UOM}
Lot	${LOT}
Serial	${SERIAL}
Account	${ACCOUNT}

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 where the item is lot- and/or serial-controlled; they are not required for a standard uncontrolled item.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~19 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 a Miscellaneous Issue Open the Miscellaneous Transaction function and select Miscellaneous Issue as the transaction type. ${INVENTORY_ORGANIZATION} This single business step replaces multiple technical actions such as opening the transaction page and confirming the inventory organization context.	A new miscellaneous issue transaction is opened for the correct inventory organization.
3	Select Item and Subinventory Select the item to be issued and the source subinventory it will be issued from. ${ITEM} / ${SUBINVENTORY}	The item and source subinventory are accepted and reflected on the transaction line.
4	Enter Quantity and Lot/Serial Enter the quantity and unit of measure to be issued, and enter or select lot and/or serial detail where the item is lot- or serial-controlled. ${QUANTITY} / ${UOM} / ${LOT} / ${SERIAL}	Quantity, UOM and lot/serial detail are accepted without unexpected validation errors.
5	Select Issue Account Select or confirm the account that the issued quantity will be charged to. ${ACCOUNT}	The issue account is accepted and reflected on the transaction line.
6	Review the Transaction Review the transaction header and line detail as entered before submitting. Reviewing the transaction before submission lets the tester catch an incorrect field entry before on-hand quantity is affected.	The reviewed transaction reflects the entered item, subinventory, quantity, lot/serial and account.
7	Submit the Transaction Submit the miscellaneous issue transaction for processing in the test environment.	Oracle Fusion successfully processes the transaction without unexpected errors.
8	Verify On-Hand Quantity DecreasedBusiness assertion Reopen or refresh on-hand availability for the item and subinventory and confirm the quantity decreased by the issued amount. This is the primary business assertion for the scenario — a correctly reduced on-hand balance with accurate transaction detail is the expected pass condition, not merely a successful submission.	On-hand quantity in the source subinventory has decreased by the issued quantity, and the transaction, lot/serial and account detail match the entered data.

Expected Results

The miscellaneous issue is recorded for the correct inventory organization, item and subinventory.
On-hand quantity in the source subinventory decreases by the issued quantity.
Quantity and UOM on the transaction are correct.
Lot and/or serial detail is correct where the item is lot- or serial-controlled.
The issue account on the transaction is correct.
The transaction is visible and traceable in the inventory transaction history.
No on-hand quantity is issued beyond what was available at the time of the transaction.

Key Validation Checkpoints

On-hand decreases correctly.
Issue transaction exists.
Lot/serial updated.
Accounting context correct.

Core Business Scenario

Miscellaneous Issue

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 Miscellaneous Issue business scenario. Jarvis AI can extend this scenario by generating additional item, subinventory, quantity, lot/serial, account 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 item, subinventory, quantity or account combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Control variations for the customer's environment — including quantity-at-the-edge-of-available boundary cases and lot/serial control checks, since correctly enforced validation at the edges of expected values is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Miscellaneous Issue business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid issue scenarios and edge cases such as insufficient on-hand, invalid subinventories 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 item, subinventory, quantity, lot/serial or account combination, SyntraFlow maintains one core Miscellaneous Issue scenario and allows Jarvis AI to generate item, subinventory, quantity, lot/serial and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Miscellaneous Issue 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

Standard miscellaneous issue of an uncontrolled item
Issue with multiple quantities across separate lines
Issue from different subinventories
Issue of a lot- and/or serial-controlled item
Issue against different accounts

Negative Scenarios

Attempt to issue a quantity greater than available on-hand
Attempt to issue an inactive or invalid item
Enter an invalid or inactive subinventory
Attempt to select a lot with no available on-hand quantity
Attempt to select a serial that is unavailable or already issued
Enter an invalid unit of measure
Enter an invalid or closed issue account
Attempt to issue an exact quantity beyond the available on-hand boundary

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 item, subinventory, lot/serial and account combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Miscellaneous Issue scenarios relevant to the customer's actual implementation.

Standard Library Definition

Inventory Organization  ${INVENTORY_ORGANIZATION}
Item                    ${ITEM}
Subinventory            ${SUBINVENTORY}
Quantity                ${QUANTITY}
UOM                     ${UOM}
Lot                     ${LOT}
Serial                  ${SERIAL}
Account                 ${ACCOUNT}

DataVault

Items
  Active items with current on-hand quantity by subinventory
Subinventories
  Configured, active subinventories per inventory organization
Lots / Serials
  Available lot and serial numbers for lot/serial-controlled items
Accounts
  Valid, open issue accounts

Jarvis AI Generates

Scenario 01 — Standard Issue of Uncontrolled Item
Scenario 02 — Multiple Quantities Across Lines
Scenario 03 — Issue From Alternate Subinventory
Scenario 04 — Lot-Controlled Item Issue
Scenario 05 — Serial-Controlled Item Issue
Scenario 06 — Quantity Exceeds Available On-Hand
Scenario 07 — Unauthorized User Attempts Issue
...

Miscellaneous Issue test data can include sensitive inventory categories such as item, quantity and account 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 Miscellaneous Issue scenarios Jarvis can generate from this business scenario, spanning quantity, subinventory, lot/serial and account 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 Issue — Uncontrolled Item	Positive	Miscellaneous issue completed for a standard, uncontrolled item	Syntra Ready
VAR-002	Multiple Quantities	Positive	Issue transaction created with multiple line quantities	Syntra Ready
VAR-003	Different Subinventories	Positive	Issue completed from an alternate active source subinventory	Syntra Ready
VAR-004	Lot-Controlled Issue	Positive/Lot/Serial	Issue completed against a valid available lot number	Syntra Ready
VAR-005	Serial-Controlled Issue	Positive/Lot/Serial	Issue completed against a valid available serial number	Syntra Ready
VAR-006	Different Accounts	Positive/Account	Issue transaction recorded against an alternate valid issue account	Syntra Ready
VAR-007	Insufficient On-Hand	Negative	Requested quantity exceeds available on-hand in the source subinventory	Syntra Ready
VAR-008	Invalid Item	Negative	Selected item is inactive or invalid for the inventory organization	Syntra Ready
VAR-009	Invalid Subinventory	Negative	Selected subinventory is invalid or inactive	Syntra Ready
VAR-010	Lot Unavailable	Negative/Lot/Serial	Selected lot has no available on-hand quantity	Syntra Ready
VAR-011	Serial Unavailable	Negative/Lot/Serial	Selected serial is unavailable or already issued	Syntra Ready
VAR-012	Invalid UOM	Negative	Unit of measure entered does not exist or is invalid for the item	Syntra Ready
VAR-013	Invalid Account	Negative/Account	Issue account entered is invalid or closed	Syntra Ready

Automatically Expand Positive and Negative Issue Coverage

Positive Testing

Jarvis generates scenarios using item, subinventory, quantity, lot/serial and account combinations expected to successfully complete a miscellaneous issue in Oracle Fusion.

Available On-Hand + Active Item + Valid Subinventory + Valid Account → On-Hand Decreases Correctly

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around available quantity, item/subinventory status, lot/serial availability and account validity.

Quantity Exceeds Available On-Hand → Expected Quantity Validation
Invalid Item → Expected Item Validation
Invalid Subinventory → Expected Subinventory Validation
Lot/Serial Unavailable → Expected Lot/Serial Validation
Invalid Account → Expected Account 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 Miscellaneous Issue scenarios and group them into reusable execution packs.

SCM Inventory Management Miscellaneous Issue Regression Pack

Standard Issue — Uncontrolled Item
Multiple Quantities
Different Subinventories
Lot-Controlled Issue
Serial-Controlled Issue
Different Accounts
Insufficient On-Hand
Invalid Account
Lot Unavailable
Security Restriction — Unauthorized Issue

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

Once scheduled, SyntraFlow executes the selected Miscellaneous Issue 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 Miscellaneous Issue Regression Pack
Schedule	Quarterly Update Regression
Tests	13 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 & Approval Variations

Access to perform a miscellaneous issue 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 issue-transaction access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Clerk	Create Miscellaneous Issue	Allowed	PASS
Unauthorized User	Attempts Issue	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 Miscellaneous Issue scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Control 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 — Miscellaneous Issue, 8 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Enter Quantity and Lot/Serial

May internally include

Open Quantity Field → Enter Quantity/UOM → Open Lot/Serial Picker (if controlled) → Select Available Lot/Serial → Confirm → Add Line

Business Step

Verify On-Hand Quantity Decreased

May internally include

Open On-Hand Availability Inquiry → Enter Item/Subinventory → Read Current Quantity → Compare Against Pre-Transaction Quantity Minus Issued Quantity

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 on-hand quantity was reduced correctly — 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 across eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Miscellaneous Issue failed — Likely category: EXPECTED_VALIDATION — Evidence: issue quantity exceeds available on-hand — Recommended action: this is expected behavior; reduce the issue quantity to the available amount and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Quantity and Lot/Serial	Pass	—
Submit the Transaction	Pass	—
Verify On-Hand Quantity Decreased	Pass	Pass

Related Item Transaction Tests

Miscellaneous Issue is the counterpart to Miscellaneous Receipt within the Item Transactions cluster — explore the related receipt, transfer and correction scenarios below.

Miscellaneous Receipt Subinventory Transfer Inventory Transaction Correction

Turn This Standard Test into Your Oracle SCM Miscellaneous Issue Regression Suite

Start with the Syntra Standard Miscellaneous Issue test, use DataVault to provide environment-specific test data, let Jarvis generate additional quantity, lot/serial, account and security 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

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

Frequently Asked Questions

What is a miscellaneous issue used for in Oracle Fusion?

A miscellaneous issue is used to remove available on-hand inventory from a subinventory for reasons outside standard order or work order flows — for example, internal consumption, sampling, scrap or non-order-related usage. It reduces on-hand quantity and records the transaction against a specified issue account.

What happens when a user attempts to issue more than the available on-hand quantity?

Oracle Fusion is expected to reject or otherwise prevent an issue transaction where the requested quantity exceeds the available on-hand balance in the source subinventory. This scenario tests that the validation is correctly enforced rather than allowing on-hand quantity to go negative.

How is lot and serial control handled during a miscellaneous issue?

Where an item is lot- and/or serial-controlled, the transaction requires selection of a valid available lot and/or serial value at the time of issue, and Oracle Fusion is expected to update the corresponding lot/serial on-hand balances once the transaction completes. This scenario includes lot/serial-specific positive and negative variations.

How does security testing work for miscellaneous issue transactions?

Access to perform a miscellaneous issue for 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.

Does this test perform real inventory movements in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not perform real inventory movements, real on-hand adjustments or real cost impact in a production environment.