Oracle ERP Testing Tool > Test Library > SCM > Inventory Management > Physical Inventory

Syntra Standard Oracle Test Library

Oracle Fusion Enter Physical Inventory Counts Test Cases

Validate that a physically counted quantity can be entered against a generated physical inventory tag in Oracle Fusion SCM, that blank or void tags are correctly recorded as zero, and that the resulting variance against the frozen physical inventory snapshot is calculated correctly.

Test ID	ORCL.SCM.INV.PI.ENTER
Application	Oracle Fusion Cloud
Product	SCM / Inventory Management
Module	Inventory Management
Process	Physical Inventory
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 15 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate entry of physically counted quantities against generated physical inventory tags in Oracle Fusion SCM Inventory Management, and correct identification of variances between the counted quantity and the frozen system snapshot.

The scenario should confirm that:

the counted quantity entered against each tag is recorded accurately
the variance between counted quantity and the frozen physical inventory snapshot quantity is calculated correctly
a blank or void tag is correctly recorded as zero and accounted for
recount entries and lot/serial-controlled tag entry are handled correctly where applicable
every tag within the assigned range is accounted for before entries are considered complete
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 entry of physically counted quantities against physical inventory tags that have already been generated and opened for entry. It does not cover generation of the tags themselves, or processing of the resulting adjustments, which are covered by the separate Generate Physical Inventory Tags and Process Physical Inventory Adjustments scenarios in the same Physical Inventory cluster.

When to Use This Test

Functional testing of physical inventory count entry for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of tag entry and variance calculation after an Oracle quarterly update
UAT sign-off for warehouse and inventory teams that perform periodic physical inventory counts
Baseline case referenced by the Generate Physical Inventory Tags and Process Physical Inventory Adjustments scenarios within the same Physical Inventory cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and EXPECTED_VALIDATION conditions surfaced during tag entry before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Physical Inventory Process

Generate Physical Inventory Tags

→

Enter Physical Inventory Counts

→

Calculate Variance

→

Recount if Required

→

Process Physical Inventory Adjustments

→

Review On-Hand Availability

Enter Physical Inventory Counts is the third stage of the physical inventory lifecycle, following generation of tags and preceding processing of any resulting adjustment. Tags for the assigned range must already exist and be open for entry before this scenario can be executed. Exact tag layout, blank/void handling and lot/serial requirements depend on item, subinventory and customer-specific Oracle Fusion configuration.

← Previous Stage

Generate Physical Inventory Tags

Next Stage →

Process Physical Inventory Adjustments

Preconditions

Physical inventory tags have already been generated and are open for entry in the target Oracle Fusion SCM environment.
The test counter has access to the assigned tag range.
The item, subinventory and locator referenced on each tag are active and correctly configured.
The frozen system snapshot quantity has been captured for the physical inventory being counted.
Where the item is lot- or serial-controlled, valid lot or serial data is available for entry.

Exact field availability, blank/void handling, recount rules and adjustment routing may vary by Oracle Fusion implementation, physical inventory definition and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Physical Inventory Name	${PHYSICAL_INVENTORY_NAME}
Tag Number	${TAG_NUMBER}
Item	${ITEM}
Subinventory	${SUBINVENTORY}
Locator	${LOCATOR}
System Quantity	${SYSTEM_QUANTITY}
Counted Quantity	${COUNTED_QUANTITY}
UOM	${UOM}
Lot/Serial	${LOT_SERIAL}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Lot/serial data applies only where the item is lot- or serial-controlled.

Test Steps

8 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 counter test user and navigate to the Inventory Management work area.	The Inventory Management work area opens successfully.
2	Locate the Assigned Tag Range Open the Physical Inventory task and locate the tag range assigned to the counter for entry. ${PHYSICAL_INVENTORY_NAME} / ${TAG_NUMBER}	The assigned tag range opens for entry, showing the item, subinventory and locator associated with each tag.
3	Review Item and Location Detail Confirm the item, subinventory and locator shown on each tag match the physical count location before entering a count. ${ITEM} / ${SUBINVENTORY} / ${LOCATOR} Confirming location detail before entry reduces the risk of a count being recorded against the wrong item or location.	Item and location detail on the tag match the intended physical count location.
4	Enter the Physically Counted Quantity Enter the physically counted quantity for the tag, including lot or serial detail where the item requires it. ${COUNTED_QUANTITY} / ${UOM} / ${LOT_SERIAL}	The counted quantity is accepted without unexpected validation errors.
5	Mark Blank or Void Tags Where a tag in the assigned range has no physical count because it was unused, mark the tag as blank or void rather than leaving it unrecorded. Marking unused tags as void is what allows the full assigned tag range to reconcile.	The blank or void tag is recorded as zero and accounted for within the tag range.
6	Review the Calculated Variance Review the variance Oracle Fusion calculates between the counted quantity and the frozen system snapshot quantity. ${SYSTEM_QUANTITY}	The displayed variance reflects counted quantity minus the frozen system snapshot quantity.
7	Submit the Count Entries Submit the entered counts for the tag range, triggering a recount instead where the counter is uncertain of a physical count. Recount handling exercises the same entry scenario a second time before a variance is treated as final.	Oracle Fusion successfully records the count entries without unexpected errors.
8	Verify All Tags Are Accounted ForBusiness assertion Reopen or refresh the tag range and confirm every tag, including blank/void tags, has a recorded entry and that the calculated variances are correct. This is the primary business assertion for the scenario — a fully accounted-for tag range with accurately recorded counts and variances is the expected pass condition, not merely a successful submission.	All tags in the assigned range are accounted for, recorded quantities and variances are correct, and entries are available for adjustment processing.

Expected Results

The counted quantity is recorded accurately against each tag.
The variance between counted quantity and the frozen system snapshot is calculated correctly.
Blank or void tags are correctly recorded as zero.
Recount entries are correctly captured where triggered.
Lot/serial detail is correctly recorded where the item requires it.
Every tag within the assigned range is accounted for.
Completed entries are available for adjustment processing.

Key Validation Checkpoints

Entered quantity recorded accurately.
Variance calculated correctly against the frozen snapshot.
All tags accounted for, including blank/void tags.
Entry available for adjustment processing.

Core Business Scenario

Enter Physical Inventory Counts

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 Enter Physical Inventory Counts business scenario. Jarvis AI can extend this scenario by generating additional item, quantity, variance, tag-status 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 tag combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Tag Status variations for the customer's environment — including blank/void tag handling, since correctly recording an unused tag as zero and accounting for it within the assigned range is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Enter Physical Inventory Counts business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Items, Subinventories, Locators, Tags and System Quantities.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant quantity, variance, tag-status and security variations.

Positive + Negative Test Variations

Valid count-entry scenarios and edge cases such as invalid tags, blank/void tags 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, quantity, variance or tag-status combination, SyntraFlow maintains one core Enter Physical Inventory Counts scenario and allows Jarvis AI to generate quantity, variance, tag-status and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Enter Physical Inventory Counts 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 Physical Inventory.

Positive Scenarios

Enter a counted quantity that matches the system quantity exactly (zero variance)
Enter a counted quantity that differs from the system quantity, with the variance correctly identified
Enter a recount against a tag flagged for recount
Record a blank or void tag correctly as zero
Enter a counted quantity for a lot- or serial-controlled tag

Negative Scenarios

Attempt to enter a count against an invalid tag reference
Enter a negative counted quantity
Submit a tag without a required counted quantity entered
Attempt count entry as a counter not authorized for the assigned tag range
Attempt a duplicate entry against a tag already submitted
Attempt count entry after the count window has closed

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, quantity and tag combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Enter Physical Inventory Counts scenarios relevant to the customer's actual implementation.

Standard Library Definition

Physical Inventory Name    ${PHYSICAL_INVENTORY_NAME}
Tag Number                 ${TAG_NUMBER}
Item                       ${ITEM}
Subinventory               ${SUBINVENTORY}
Locator                    ${LOCATOR}
System Quantity            ${SYSTEM_QUANTITY}
Counted Quantity           ${COUNTED_QUANTITY}
UOM                        ${UOM}
Lot/Serial                 ${LOT_SERIAL}

DataVault

Items
  Active items configured for physical inventory
Subinventories / Locators
  Configured count locations
Tags
  Generated tag numbers for the physical inventory
System Quantities
  Frozen snapshot quantities as of the count date
Lot/Serial
  Active lot and serial values for controlled items

Jarvis AI Generates

Scenario 01 — Item A + Zero Variance
Scenario 02 — Item B + Variance Correctly Identified
Scenario 03 — Item C + Recount Entry
Scenario 04 — Blank/Void Tag + Zero Recorded
Scenario 05 — Lot-Controlled Item + Lot Entry
Scenario 06 — Unauthorized User Attempts Count Entry
...

Enter Physical Inventory Counts test data can include sensitive inventory dimensions such as on-hand quantity, location and item cost 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 Enter Physical Inventory Counts scenarios Jarvis can generate from this business scenario, spanning quantity, variance, tag-status 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	Zero Variance Entry	Positive	Counted quantity matches system quantity exactly	Syntra Ready
VAR-002	Variance Correctly Identified	Positive/Variance	Counted quantity differs from system quantity and the resulting variance is correctly identified	Syntra Ready
VAR-003	Recount Entry	Positive	A second count entered against the same tag after a recount is triggered	Syntra Ready
VAR-004	Blank/Void Tag Entry	Positive/Tag Status	Tag correctly recorded as zero when no physical count exists	Syntra Ready
VAR-005	Lot-Controlled Tag Entry	Positive	Counted quantity entered against a specific lot number	Syntra Ready
VAR-006	Serial-Controlled Tag Entry	Positive	Counted quantity entered against specific serial numbers	Syntra Ready
VAR-007	Invalid Tag Reference	Negative	Entry attempted against a tag number that does not exist or is outside the assigned range	Syntra Ready
VAR-008	Negative Counted Quantity	Negative	Counted quantity entered as a negative value	Syntra Ready
VAR-009	Missing Required Count Entry	Negative	Tag submitted without a counted quantity entered	Syntra Ready
VAR-010	Unauthorized Counter	Negative	Entry attempted by a user not assigned to the tag range	Syntra Ready
VAR-011	Duplicate Entry for Same Tag	Negative	A second count entry attempted against a tag already submitted	Syntra Ready
VAR-012	Entry After Count Window Closed	Negative	Entry attempted after the physical inventory count window has closed	Syntra Ready
VAR-013	Unaccounted Tag in Range	Negative/Tag Status	A tag within the assigned range left with no entry and not marked void	Syntra Ready

Automatically Expand Positive and Negative Physical Inventory Count Coverage

Positive Testing

Jarvis generates scenarios using item, quantity, variance and tag-status combinations expected to successfully record a physical inventory count entry and correctly identify the resulting variance in Oracle Fusion.

Valid Tag + Counted Quantity + Correct Variance Identification → Entry Recorded

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around tag status, entry authorization and mandatory data.

Invalid Tag → Expected Tag Validation
Negative Quantity → Expected Quantity Validation
Missing Counted Quantity → Expected Mandatory Field Validation
Unauthorized Counter → Expected Access Restriction
Duplicate Entry → Expected Duplicate Validation

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 Enter Physical Inventory Counts scenarios and group them into reusable execution packs.

SCM Inventory Management Enter Physical Inventory Counts Regression Pack

Zero Variance Entry
Variance Correctly Identified
Recount Entry
Blank/Void Tag Entry
Lot-Controlled Tag Entry
Serial-Controlled Tag Entry
Invalid Tag Reference
Negative Counted Quantity
Duplicate Entry for Same Tag
Unaccounted Tag in Range

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

Once scheduled, SyntraFlow executes the selected Enter Physical Inventory Counts 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 Enter Physical Inventory Counts 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 enter a physical count against a given tag range is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that count-entry access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Counter	Enter Physical Inventory Counts	Allowed	PASS
Unauthorized User	Attempts Count Entry	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 Enter Physical Inventory Counts scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Tag Status 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 — Enter Physical Inventory Counts, 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 the Physically Counted Quantity

May internally include

Open Tag Entry → Enter Counted Quantity → Enter UOM → Enter Lot/Serial Where Required → Confirm Field Entry

Business Step

Review the Calculated Variance

May internally include

Open Variance Display → Read Frozen Snapshot Quantity → Read Calculated Variance → Compare Against Counted 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 counted quantity and variance were recorded 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: Enter Physical Inventory Counts failed — Likely category: DATA_ERROR — Evidence: a tag in the assigned range was left blank without being marked void — Recommended action: mark unused tags as void so the full tag range reconciles. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter the Physically Counted Quantity	Pass	—
Submit the Count Entries	Pass	—
Verify All Tags Are Accounted For	Pass	Pass

Related Physical Inventory Tests

Enter Physical Inventory Counts is the third stage of the Physical Inventory cluster — explore the related tag-generation, adjustment-processing and on-hand availability scenarios below.

Generate Physical Inventory Tags Process Physical Inventory Adjustments Review On-Hand Availability

Turn This Standard Test into Your Oracle SCM Enter Physical Inventory Counts Regression Suite

Start with the Syntra Standard Enter Physical Inventory Counts test, use DataVault to provide environment-specific test data, let Jarvis generate additional quantity, variance, tag-status and security variations, and execute the resulting regression pack automatically with SyntraFlow.

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

Frequently Asked Questions

How is the variance calculated on an entered physical inventory count?

The variance is the difference between the physically counted quantity entered against a tag and the frozen system snapshot quantity captured in Oracle Fusion when the physical inventory was taken, calculated as counted quantity minus the frozen snapshot quantity. This test validates that the displayed variance is calculated correctly for a range of counted-quantity scenarios.

What happens to blank or void tags during entry?

A tag generated for a location or item where no physical stock is found should be marked as blank or void rather than left with no entry. This test confirms that a blank or void tag is correctly recorded as zero and that it is still accounted for when the full tag range is reconciled.

How does this test handle recounts?

Where a counted quantity produces an unexpected or large variance, or the counter is uncertain of the physical count, this scenario covers triggering a recount and re-entering the quantity against the same tag before the variance is treated as final. Exact recount rules depend on the customer's physical inventory configuration.

How does security testing work for physical inventory count entry?

Access to enter a count against a given tag range is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an assigned inventory counter versus an unauthorized user — to confirm that count-entry access behaves as expected, without asserting a single universal Oracle security model.

Does entering a physical inventory count in this test perform a real inventory movement?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not perform real inventory movements, real stock adjustments or affect production on-hand quantities.