Oracle ERP Testing Tool > Test Library > SCM > Inventory Management > On-Hand

Syntra Standard Oracle Test Library

Oracle Fusion Review On-Hand Availability Test Cases

Validate that on-hand quantity and available-to-promise inquiries in Oracle Fusion SCM Inventory Management return accurate, correctly scoped results across organizations, subinventories and lot/serial dimensions, without creating or modifying any inventory.

Test ID	ORCL.SCM.INV.ONHAND.REVIEW
Application	Oracle Fusion Cloud
Product	SCM / Inventory Management
Module	Inventory Management
Process	On-Hand
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 7 business-readable test steps; SyntraFlow's automation executes approximately 15 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that on-hand quantity and available-to-promise (ATP) inquiries in Oracle Fusion SCM Inventory Management return accurate, correctly scoped results when filtered by inventory organization, item, subinventory, locator, lot and serial, and that available-to-promise quantity correctly nets out active reservations and allocations against on-hand quantity. This is a read-only inquiry — the test verifies displayed data only and does not create, modify or move any inventory.

The scenario should confirm that:

the displayed on-hand quantity matches the expected value for the selected item, organization, subinventory, locator, lot or serial
available-to-promise quantity correctly nets out active reservations and allocations from on-hand quantity
results are correctly scoped to the selected organization, item and subinventory filters
results remain consistent across repeated inquiries when no intervening transaction has occurred
an over-restrictive filter combination correctly returns an empty result set rather than an error
Oracle correctly enforces validation and access restrictions when search criteria are invalid or when a user lacks access to a requested inventory organization (DATA_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers read-only inquiry into on-hand and available-to-promise quantity in Oracle Fusion SCM Inventory Management TEST/UAT environments. No inventory is created, modified, moved or adjusted by this test — it only reads and verifies displayed on-hand and availability data. Transactions that change on-hand quantity, such as receipts, issues, transfers and physical inventory adjustments, are covered by the separate scenarios in the Item Transactions, Transfers, Cycle Counts and Physical Inventory clusters.

When to Use This Test

Functional testing of on-hand and available-to-promise inquiry for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of on-hand availability inquiry behavior after an Oracle quarterly update
UAT sign-off for planning, warehouse and customer service teams that routinely check on-hand and available-to-promise quantity
Diagnosing DATA_ERROR and SECURITY_ERROR conditions surfaced during on-hand research before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Plan-to-Produce Inventory Management Process

Item Transactions

→

Transfers

→

Cycle Counts

→

Physical Inventory

→

On-Hand

On-Hand is a read-only inquiry process rather than a transactional stage in the Inventory Management lifecycle — it is used throughout to verify the on-hand and available-to-promise position resulting from item transactions, transfers, cycle counts and physical inventory adjustments. This test does not itself create, modify or move any inventory; it validates that the quantities displayed by the inquiry are accurate. Exact fields available and access depend on inventory organization configuration, item attributes, lot/serial control and customer-specific Oracle Fusion configuration.

← Previous Stage

Process Physical Inventory Adjustments

Preconditions

On-hand inventory data exists across multiple inventory organizations and subinventories in the target Oracle Fusion SCM environment.
Reservations and/or allocations exist against at least some items, so that on-hand and available-to-promise quantity can be verified as distinct values.
The test user has view/inquiry access to on-hand availability for the relevant inventory organization(s).
Lot and/or serial-controlled items with recorded on-hand quantity are available where lot/serial-scoped inquiry is being verified.

Exact fields available, filter options and access depend on Oracle Fusion implementation, inventory organization configuration, item attributes, lot/serial control, security profile and customer-specific configuration. Data availability requirements vary by implementation.

Sample Test Data

Inventory Organization	${INVENTORY_ORGANIZATION}
Secondary Inventory Organization	${INVENTORY_ORGANIZATION_2}
Item	${ITEM}
Subinventory	${SUBINVENTORY}
Locator	${LOCATOR}
Lot	${LOT}
Serial	${SERIAL}
As-Of Date	${AS_OF_DATE}
Reservation Quantity	${RESERVATION_QUANTITY}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field needs to be populated for every inquiry — item and organization are typically sufficient, while subinventory, locator, lot and serial narrow a broader inquiry.

Test Steps

7 business-readable steps. SyntraFlow's automation executes ~15 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 the On-Hand Availability Inquiry Open the on-hand availability inquiry page for the relevant inventory organization. ${INVENTORY_ORGANIZATION}	The on-hand availability inquiry page opens for the correct inventory organization.
3	Apply Organization, Item and Subinventory Filters Enter filters such as inventory organization, item, subinventory, locator, lot or serial to scope the inquiry. ${INVENTORY_ORGANIZATION} / ${ITEM} / ${SUBINVENTORY} / ${LOCATOR} / ${LOT} / ${SERIAL}	The filters are accepted without unexpected errors.
4	Execute the Inquiry Submit the inquiry and review the results returned as of the selected date. ${AS_OF_DATE} This single business step replaces multiple technical actions such as submitting the search and reading the results grid.	Results matching the entered filters are displayed, or a correctly empty result set is returned for an over-restrictive filter combination.
5	Review Displayed On-Hand and Available-to-Promise Quantities Review the on-hand quantity and available-to-promise quantity displayed for the selected item, organization, subinventory, locator, lot or serial. ${RESERVATION_QUANTITY}	On-hand quantity is displayed correctly, and available-to-promise quantity correctly nets out any active reservations or allocations.
6	Cross-Check Against Expected Values Cross-check the displayed on-hand and available-to-promise quantities against expected reference values for the selected scope.	Displayed quantities match the expected reference values.
7	Verify Results Are Correctly ScopedBusiness assertion Confirm that the returned results are correctly scoped to the selected organization, item, subinventory, locator, lot and serial filters, and remain consistent on a repeated inquiry. This is the primary business assertion for the scenario — accurate, correctly scoped on-hand and available-to-promise quantities are the expected pass condition, not merely a successful search.	Results are correctly scoped to the selected filters and remain consistent across repeated inquiries with no drift when no intervening transaction has occurred.

Expected Results

The displayed on-hand quantity matches the expected value for the selected scope.
Available-to-promise quantity correctly nets out active reservations and allocations.
Results are correctly scoped to the selected organization, item, subinventory, locator, lot and serial filters.
Results remain consistent across repeated inquiries when no intervening transaction has occurred.
An over-restrictive filter combination correctly returns an empty result set rather than an error.
An unauthorized organization inquiry is correctly access-restricted.
No inventory is created, modified or moved by this inquiry.

Key Validation Checkpoints

Displayed on-hand quantity matches expected value.
Available-to-promise correctly nets out reservations/allocations.
Results correctly scoped to the selected filters.
Results consistent across repeated inquiries (no drift without an intervening transaction).

Core Business Scenario

Review On-Hand Availability

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 Review On-Hand Availability business scenario. Jarvis AI can extend this scenario by generating additional organization, subinventory, lot/serial, reservation 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 organization, subinventory or lot/serial combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Scope variations for the customer's environment — including zero on-hand boundary cases, since correctly handling items with no on-hand quantity is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Review On-Hand Availability 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 organization, subinventory, lot/serial and security variations.

Positive + Negative Test Variations

Valid on-hand and available-to-promise inquiries and edge cases such as zero on-hand, invalid filters 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 inventory organization, item, subinventory, locator, lot or serial combination, SyntraFlow maintains one core Review On-Hand Availability scenario and allows Jarvis AI to generate organization, scope and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Review On-Hand Availability 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 On-Hand.

Positive Scenarios

Single-organization inquiry
Multi-organization inquiry
Subinventory-scoped inquiry
Lot/serial-scoped inquiry
Item with active reservations (on-hand vs. available differ correctly)
Item with zero on-hand

Negative Scenarios

Invalid organization filter
Invalid item filter
Invalid date filter
Over-restrictive filter combination correctly returns no results
Unauthorized organization access attempted
Invalid subinventory filter

These are representative examples only. Negative-scenario behavior and available search fields 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 inventory organization, item, subinventory, locator, lot and serial combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Review On-Hand Availability scenarios relevant to the customer's actual implementation.

Standard Library Definition

Inventory Organization    ${INVENTORY_ORGANIZATION}
Secondary Organization    ${INVENTORY_ORGANIZATION_2}
Item                      ${ITEM}
Subinventory               ${SUBINVENTORY}
Locator                    ${LOCATOR}
Lot                        ${LOT}
Serial                     ${SERIAL}
As-Of Date                 ${AS_OF_DATE}
Reservation Quantity       ${RESERVATION_QUANTITY}

DataVault

Inventory Organizations
  Active organizations with on-hand data across a representative range of scopes
Items
  Items with on-hand quantity, including some with zero on-hand
Subinventories / Locators
  Configured subinventories and locators per organization
Lots / Serials
  Lot- and serial-controlled items with recorded on-hand quantity
Reservations / Allocations
  Items with active reservations or allocations against on-hand quantity

Jarvis AI Generates

Scenario 01 — Single-Organization Inquiry
Scenario 02 — Multi-Organization Inquiry
Scenario 03 — Subinventory-Scoped Inquiry
Scenario 04 — Lot/Serial-Scoped Inquiry
Scenario 05 — Item With Active Reservations
Scenario 06 — Item With Zero On-Hand
Scenario 07 — Invalid Organization Filter
Scenario 08 — Unauthorized Organization Access Attempted
...

On-hand and available-to-promise test data can include sensitive supply-chain categories such as item, location and quantity 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 Review On-Hand Availability scenarios Jarvis can generate from this business scenario, spanning organization, subinventory, lot/serial and availability 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	Single-Organization Inquiry	Positive/Scope	Inquiry scoped to a single inventory organization	Syntra Ready
VAR-002	Multi-Organization Inquiry	Positive/Scope	Inquiry spans multiple inventory organizations	Syntra Ready
VAR-003	Subinventory-Scoped Inquiry	Positive/Scope	Inquiry filtered to a specific subinventory	Syntra Ready
VAR-004	Locator-Scoped Inquiry	Positive/Scope	Inquiry filtered to a specific locator within a subinventory	Syntra Ready
VAR-005	Lot-Scoped Inquiry	Positive/Scope	Inquiry filtered to a specific lot	Syntra Ready
VAR-006	Serial-Scoped Inquiry	Positive/Scope	Inquiry filtered to a specific serial number	Syntra Ready
VAR-007	Item With Active Reservations	Positive/Availability	On-hand and available-to-promise quantity correctly differ due to active reservations	Syntra Ready
VAR-008	Item With Active Allocations	Positive/Availability	Available-to-promise quantity correctly nets out active allocations	Syntra Ready
VAR-009	Item With Zero On-Hand	Positive/Availability	Item correctly displays zero on-hand and zero available-to-promise quantity	Syntra Ready
VAR-010	Invalid Organization Filter	Negative	Inquiry submitted with an invalid inventory organization	Syntra Ready
VAR-011	Invalid Item Filter	Negative	Inquiry submitted with an invalid or non-existent item	Syntra Ready
VAR-012	Over-Restrictive Filter Combination	Negative	Filter combination correctly returns an empty result set, not an error	Syntra Ready
VAR-013	Unauthorized Organization Access	Negative	User without organization access attempts the inquiry	Syntra Ready

Automatically Expand Positive and Negative On-Hand Availability Coverage

Positive Testing

Jarvis generates scenarios using inventory organization, item, subinventory, locator, lot and serial combinations expected to successfully return accurate on-hand and available-to-promise results in Oracle Fusion.

Valid Item + Organization + Active Reservation → On-Hand and Available-to-Promise Correctly Differ

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around inquiry filters, result sets and security.

Invalid Organization Filter → Expected Validation Message
Invalid Item Filter → Expected Validation Message
Invalid Date Filter → Expected Validation Message
Over-Restrictive Filter Combination → Expected Empty Result Set
Unauthorized Organization Access → Expected Access Restriction

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

Scenario	Oracle Outcome	Test Result
Valid physical inventory	Definition created	PASS
Invalid snapshot date	Validation occurs	PASS
Overlapping definition	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 Review On-Hand Availability scenarios and group them into reusable execution packs.

SCM Inventory Management On-Hand Availability Regression Pack

Single-Organization Inquiry
Multi-Organization Inquiry
Subinventory-Scoped Inquiry
Lot/Serial-Scoped Inquiry
Item With Active Reservations
Item With Zero On-Hand
Invalid Organization Filter
Invalid Item Filter
Over-Restrictive Filter Combination
Unauthorized Organization Access

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

Once scheduled, SyntraFlow executes the selected Review On-Hand Availability 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 On-Hand Availability 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 & Access Variations

Access to view on-hand and available-to-promise quantity 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 on-hand availability inquiry access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Viewer	View On-Hand Availability	Allowed	PASS
Unauthorized User	Attempts Cross-Organization Inquiry	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 Review On-Hand Availability scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Scope 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 — Review On-Hand Availability, 7 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

Apply Organization, Item and Subinventory Filters

May internally include

Open Filter Panel → Enter Organization/Item/Subinventory/Locator/Lot/Serial Fields → Submit Inquiry → Wait for Results Grid

Business Step

Review Displayed On-Hand and Available-to-Promise Quantities

May internally include

Open Item Availability Detail → Read On-Hand Quantity → Read Reserved/Allocated Quantity → Read Available-to-Promise Quantity → Compare Against Expected Value

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 that displayed on-hand and available-to-promise quantities are accurate — 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: Review On-Hand Availability failed — Likely category: DATA_ERROR — Evidence: displayed available-to-promise does not net out an active reservation — Recommended action: verify reservation data and re-run the inquiry with supporting evidence before escalating. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Apply Organization, Item and Subinventory Filters	Pass	—
Execute the Inquiry	Pass	—
Verify Results Are Correctly Scoped	Pass	Pass

Related Inventory Management Tests

Review On-Hand Availability is the read and verification counterpart to the transactional scenarios that create and move inventory — explore related Inventory Management scenarios below.

Miscellaneous Receipt Subinventory Transfer Process Physical Inventory Adjustments

Turn This Standard Test into Your Oracle SCM On-Hand Availability Regression Suite

Start with the Syntra Standard Review On-Hand Availability test, use DataVault to provide environment-specific test data, let Jarvis generate additional organization, subinventory, lot/serial and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Inventory Management On-Hand 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 On-Hand Test Library Syntra DataVault

Frequently Asked Questions

What is the difference between on-hand quantity and available-to-promise quantity?

On-hand quantity is the physical quantity of an item recorded in inventory for a given organization, subinventory, locator, lot or serial. Available-to-promise (ATP) quantity is the on-hand quantity net of active reservations and allocations — in other words, the quantity that is actually free to be committed to a new demand. This test validates that both figures are displayed accurately and that ATP correctly nets out reservations and allocations from on-hand.

How do reservations and allocations affect available-to-promise quantity?

A reservation or allocation commits a portion of on-hand quantity to a specific order, work order or other demand, without physically moving the inventory. When reservations or allocations exist, available-to-promise quantity should be lower than on-hand quantity by the reserved or allocated amount. This scenario specifically tests items with active reservations to confirm on-hand and available-to-promise are displayed as correctly distinct values.

Does this test create, modify or move any inventory?

No. Review On-Hand Availability is a read-only inquiry scenario — it does not create, modify or move any inventory. It only reads and verifies the on-hand and available-to-promise quantities displayed by Oracle Fusion for the selected organization, item, subinventory, locator, lot or serial.

How does security testing work for on-hand availability inquiry?

Access to view on-hand and available-to-promise quantity 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 authorized inventory viewer versus an unauthorized user attempting a cross-organization inquiry — to confirm that inquiry access behaves as expected, without asserting a single universal Oracle security model.

Why might the same item show different on-hand quantity in different organizations or subinventories?

On-hand quantity is tracked separately by inventory organization, and further by subinventory, locator, lot and serial within an organization. An item can have different on-hand and available-to-promise quantities in each of these scopes. This test includes single-organization, multi-organization and subinventory-scoped variations to confirm results are correctly scoped to the filters applied.