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

Syntra Standard Oracle Test Library

Oracle Fusion Miscellaneous Receipt Test Cases

Validate that a miscellaneous receipt is created correctly in Oracle Fusion SCM Inventory Management using a valid organization, item, subinventory, locator, quantity, unit of measure and account.

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

Test Objective

The objective of this test is to validate that a miscellaneous receipt can be created in Oracle Fusion SCM Inventory Management using a valid inventory organization, item, subinventory, locator, quantity, unit of measure and account, and that the resulting transaction correctly updates on-hand inventory.

The scenario should confirm that:

the receipt is created for the correct inventory organization and item
quantity, unit of measure, and lot/serial detail where applicable, are captured correctly
the subinventory and locator used on the transaction are correct
the account charged on the transaction is correct
on-hand inventory quantity is correctly updated by the received quantity
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 creation of a single miscellaneous receipt transaction in Oracle Fusion SCM Inventory Management TEST/UAT environments. It does not cover miscellaneous issues, subinventory transfers, or transaction corrections, which are covered by the separate Miscellaneous Issue, Subinventory Transfer and Inventory Transaction Correction scenarios in the same Item Transactions cluster.

When to Use This Test

Functional testing of miscellaneous receipt creation for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of receipt behavior after an Oracle quarterly update
UAT sign-off for inventory teams that routinely record non-PO-based inventory receipts
Baseline case referenced by the Miscellaneous Issue, Subinventory Transfer and Inventory Transaction Correction scenarios within the same Item Transactions cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during receipt creation before escalating as a possible APPLICATION_ERROR

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

Navigate to Inventory

→

Miscellaneous Receipt

→

Select Organization/Item

→

Select Subinventory/Locator

→

Enter Quantity

→

Select Account

→

Review

Miscellaneous Receipt is the entry point of the Item Transactions cluster within Plan-to-Produce. Once inventory is received, it may subsequently be issued, transferred between subinventories, or corrected — covered by the Miscellaneous Issue, Subinventory Transfer and Inventory Transaction Correction scenarios in this same cluster. Exact fields available and validation depend on inventory organization configuration, item setup and customer-specific Oracle Fusion configuration.

Next Stage →

Miscellaneous Issue

Preconditions

An inventory organization is configured in the target Oracle Fusion SCM environment.
The test item is active and enabled for the inventory organization.
The subinventory, and locator where applicable, used on the receipt are configured and active.
The charge account entered on the receipt is valid and open for the transaction date.

Exact field availability, lot/serial controls, mandatory fields and validation messages may vary by Oracle Fusion implementation, inventory organization configuration, item setup and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Inventory Organization	${INVENTORY_ORGANIZATION}
Item	${ITEM}
Subinventory	${SUBINVENTORY}
Locator	${LOCATOR}
Quantity	${QUANTITY}
UOM	${UOM}
Lot	${LOT}
Serial	${SERIAL}
Account	${ACCOUNT}
Transaction Date	${TRANSACTION_DATE}
Transaction Type	${TRANSACTION_TYPE}
Reason	${REASON}

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- or serial-controlled — not every field applies to every item.

Test Steps

9 business-readable steps. SyntraFlow's automation executes ~20 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	Navigate to Miscellaneous Receipt Open the Miscellaneous Receipt transaction to begin recording an inventory receipt that is not tied to a purchase order or other source document.	The Miscellaneous Receipt entry page opens.
3	Initiate the Miscellaneous Receipt Start a new miscellaneous receipt transaction for the test inventory organization. ${INVENTORY_ORGANIZATION} This single business step replaces multiple technical actions such as opening the transaction type list, selecting Miscellaneous Receipt and confirming the organization.	A new, unsaved miscellaneous receipt is opened for the correct inventory organization.
4	Select Organization and Item Confirm the inventory organization and search for and select the item to be received. ${INVENTORY_ORGANIZATION} / ${ITEM}	The organization and item are accepted and reflected on the transaction line.
5	Select Subinventory and Locator Select the subinventory, and locator where applicable, that the item will be received into. ${SUBINVENTORY} / ${LOCATOR}	The subinventory and locator are accepted without unexpected validation errors.
6	Enter Quantity and UOM Enter the quantity and unit of measure being received, and lot or serial detail where the item is lot- or serial-controlled. ${QUANTITY} / ${UOM} / ${LOT} / ${SERIAL}	Quantity, UOM and lot/serial detail, where applicable, are accepted without unexpected validation errors.
7	Select Account Select the account that the miscellaneous receipt will be charged to. ${ACCOUNT}	The account is accepted and reflected on the transaction line.
8	Review and Submit Review the miscellaneous receipt detail as calculated by Oracle Fusion, then submit the transaction. ${TRANSACTION_DATE} Reviewing the transaction before submission lets the tester catch an incorrect field entry before the receipt is recorded.	Oracle Fusion successfully processes the miscellaneous receipt without unexpected errors.
9	Verify On-Hand Quantity UpdatedBusiness assertion Reopen or refresh on-hand inventory for the item, organization, subinventory and locator, and confirm the transaction and updated on-hand balance. This is the primary business assertion for the scenario — a correctly recorded receipt with an updated on-hand balance is the expected pass condition, not merely a successful save.	The transaction is recorded, on-hand quantity is correctly updated by the received quantity, and the account and subinventory used match the entered data.

Expected Results

The miscellaneous receipt is created for the correct inventory organization and item.
The received quantity and unit of measure are correct.
On-hand inventory quantity is correctly updated by the received quantity.
The subinventory and locator used are correct.
The account charged is correct.
Lot and serial detail is captured correctly for lot- or serial-controlled items.
The transaction is visible and traceable in transaction history.

Key Validation Checkpoints

Quantity received.
On-hand quantity updated.
Transaction recorded.
Correct account and subinventory used.

Core Business Scenario

Miscellaneous Receipt

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 Receipt business scenario. Jarvis AI can extend this scenario by generating additional item, subinventory, locator, quantity, 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 large-quantity boundary cases and control cases for lot- and serial-controlled items, since correctly enforced validation at the edges of expected values and controlled-item requirements is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Miscellaneous Receipt business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid receipt scenarios and edge cases such as inactive items, invalid accounts 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, locator, quantity or account combination, SyntraFlow maintains one core Miscellaneous Receipt scenario and allows Jarvis AI to generate item, subinventory, quantity, account and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Create a standard miscellaneous receipt
Receive different items
Receive into different subinventories
Receive different quantities
Receive a locator-controlled item
Receive a lot-controlled item
Receive a serial-controlled item
Receive against different accounts
Receive on different transaction dates

Negative Scenarios

Attempt to receive an inactive item
Enter an invalid inventory organization
Enter an invalid subinventory
Enter an invalid locator
Enter a zero or negative quantity
Enter an invalid unit of measure
Attempt to save a lot-controlled item without lot detail
Attempt to save a serial-controlled item without serial detail
Enter an invalid account
Enter an invalid transaction date

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, locator, quantity 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 Receipt scenarios relevant to the customer's actual implementation.

Standard Library Definition

Inventory Organization   ${INVENTORY_ORGANIZATION}
Item                     ${ITEM}
Subinventory             ${SUBINVENTORY}
Locator                  ${LOCATOR}
Quantity                 ${QUANTITY}
UOM                      ${UOM}
Lot                      ${LOT}
Serial                   ${SERIAL}
Account                  ${ACCOUNT}
Transaction Date         ${TRANSACTION_DATE}
Transaction Type         ${TRANSACTION_TYPE}
Reason                   ${REASON}

DataVault

Organizations
  Active inventory organizations
Items
  Active items enabled in the organization, including lot- and serial-controlled items
Subinventories / Locators
  Configured subinventories and locators
Accounts
  Valid, open charge accounts
Transaction Dates
  Valid dates within an open period

Jarvis AI Generates

Scenario 01 — Organization A + Standard Item + Single Receipt
Scenario 02 — Organization A + Lot-Controlled Item
Scenario 03 — Organization B + Serial-Controlled Item
Scenario 04 — Different Subinventory and Locator
Scenario 05 — Inactive Item
Scenario 06 — Unauthorized User Attempts Miscellaneous Receipt
...

Miscellaneous Receipt test data can include sensitive inventory categories such as item, account and location 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 Receipt scenarios Jarvis can generate from this business scenario, spanning item, 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 Miscellaneous Receipt	Positive	Receipt created using a standard, non-controlled item	Syntra Ready
VAR-002	Different Items	Positive	Receipt created using an alternate active item	Syntra Ready
VAR-003	Different Subinventories	Positive/Subinventory	Receipt created into an alternate configured subinventory	Syntra Ready
VAR-004	Different Quantities	Positive	Receipt created with a range of valid received quantities	Syntra Ready
VAR-005	Locator-Controlled Item	Positive/Subinventory	Receipt created into a subinventory requiring locator entry	Syntra Ready
VAR-006	Lot-Controlled Item	Positive/Lot/Serial	Receipt created for an item requiring lot detail	Syntra Ready
VAR-007	Serial-Controlled Item	Positive/Lot/Serial	Receipt created for an item requiring serial detail	Syntra Ready
VAR-008	Different Accounts	Positive/Account	Receipt created against an alternate valid charge account	Syntra Ready
VAR-009	Different Transaction Dates	Positive	Receipt created with a transaction date other than the default	Syntra Ready
VAR-010	Inactive Item	Negative	Selected item is inactive as of the transaction date	Syntra Ready
VAR-011	Invalid Organization	Negative	Selected inventory organization does not exist or is inactive	Syntra Ready
VAR-012	Invalid Subinventory	Negative/Subinventory	Selected subinventory does not exist or is inactive	Syntra Ready
VAR-013	Invalid Locator	Negative/Subinventory	Selected locator is invalid for the chosen subinventory	Syntra Ready
VAR-014	Zero or Negative Quantity	Negative	Quantity entered as zero or a negative value	Syntra Ready
VAR-015	Invalid UOM	Negative	Unit of measure entered does not exist or is invalid for the item	Syntra Ready
VAR-016	Missing Lot Detail	Negative/Lot/Serial	Lot-controlled item saved without required lot detail	Syntra Ready
VAR-017	Missing Serial Detail	Negative/Lot/Serial	Serial-controlled item saved without required serial detail	Syntra Ready
VAR-018	Invalid Account	Negative/Account	Charge account entered is invalid or closed	Syntra Ready
VAR-019	Invalid Transaction Date	Negative	Transaction date entered outside a supported or open period	Syntra Ready

Automatically Expand Positive and Negative Receipt Coverage

Positive Testing

Jarvis generates scenarios using organization, item, subinventory, locator, quantity and account combinations expected to successfully record a miscellaneous receipt in Oracle Fusion.

Valid Organization + Active Item + Valid Subinventory + Valid Account → Receipt Recorded

Negative Testing

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

Inactive Item → Expected Item Validation
Invalid Subinventory → Expected Subinventory Validation
Zero or Negative Quantity → Expected Quantity Validation
Missing Lot Detail → Expected Lot Validation
Invalid Charge 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 Receipt scenarios and group them into reusable execution packs.

SCM Inventory Management Miscellaneous Receipt Regression Pack

Standard Miscellaneous Receipt
Locator-Controlled Item
Lot-Controlled Item
Serial-Controlled Item
Different Subinventories
Different Accounts
Different Transaction Dates
Invalid Account
Missing Lot Detail
Security Restriction — Unauthorized Receipt

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

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

Access to create a miscellaneous receipt 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 receipt-creation 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 Receipt	Allowed	PASS
Unauthorized User	Attempts Receipt	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 Receipt 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 Receipt, 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 Subinventory and Locator

May internally include

Open Subinventory List → Select Subinventory → Check Locator Control → Open Locator List → Select Locator → Confirm

Business Step

Verify On-Hand Quantity Updated

May internally include

Open On-Hand Availability → Query Organization/Item/Subinventory/Locator → Read Quantity → Compare Against Pre-Transaction Balance

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 inventory was received 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 — 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: Miscellaneous Receipt failed — Likely category: DATA_ERROR — Evidence: selected item is inactive in the organization — Recommended action: select an active item and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Quantity and UOM	Pass	—
Review and Submit	Pass	—
Verify On-Hand Quantity Updated	Pass	Pass

Related Item Transaction Tests

Miscellaneous Receipt is the entry point of the Item Transactions cluster — explore the related issue, transfer and correction scenarios below.

Miscellaneous Issue Subinventory Transfer Inventory Transaction Correction

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

Start with the Syntra Standard Miscellaneous Receipt test, use DataVault to provide environment-specific test data, let Jarvis generate additional item, subinventory, lot/serial and account 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 is a miscellaneous receipt used for in Oracle Fusion Inventory Management?

A miscellaneous receipt is used to bring inventory into a subinventory when the receipt isn't tied to a purchase order, sales order return or other standard source document — for example, correcting a physical count discrepancy, receiving samples, or bringing in inventory from a non-integrated source. It is the entry point of the Item Transactions cluster in this test library.

How does lot and serial control affect this test?

When an item is lot- or serial-controlled, Oracle Fusion requires lot and/or serial detail to be entered before the receipt can be completed. This scenario, along with its Jarvis-generated variations, covers both lot-controlled and serial-controlled items and confirms Oracle enforces the required entry.

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

No. Rather than maintaining a separate public page for every item, subinventory, locator, quantity or account combination, SyntraFlow maintains this one core Miscellaneous Receipt 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 miscellaneous receipts?

Access to create a miscellaneous receipt 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 create real inventory movements in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not create real inventory movements, real on-hand balance changes or real transactions in a production environment.