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

Syntra Standard Oracle Test Library

Oracle Fusion Create Physical Inventory Test Cases

Validate that a physical inventory definition is created correctly in Oracle Fusion SCM Inventory Management for a full, wall-to-wall count of an inventory organization — including the correct organization, subinventory scope, on-hand snapshot date and transaction freeze configuration — distinct from ongoing, sample-based cycle counting.

Test ID	ORCL.SCM.INV.PI.CREATE
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 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 a physical inventory definition can be created in Oracle Fusion SCM Inventory Management for a full wall-to-wall count of an inventory organization, with the correct organization, subinventory scope, on-hand snapshot date and transaction freeze configuration, and that the resulting definition is available for physical inventory tag generation.

The scenario should confirm that:

the physical inventory definition is created for the correct inventory organization
the subinventory scope, whether organization-wide or restricted, is correctly applied
the on-hand snapshot date is correctly captured and used as the count baseline
the transaction freeze configuration is correctly applied for the count window
the physical inventory definition is distinct from, and does not conflict with, ongoing cycle count activity for the same organization
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 physical inventory definition in Oracle Fusion SCM Inventory Management TEST/UAT environments. It does not cover tag generation, entering physical inventory counts or processing adjustments, which are covered by the separate Generate Physical Inventory Tags, Enter Physical Inventory Counts and Process Physical Inventory Adjustments scenarios in the same Physical Inventory cluster.

When to Use This Test

Functional testing of physical inventory definition creation for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of physical inventory definition behavior after an Oracle quarterly update
UAT sign-off for inventory teams that perform periodic, wall-to-wall physical inventory counts alongside ongoing cycle counting
Baseline case referenced by the Generate Physical Inventory Tags, Enter Physical Inventory Counts and Process Physical Inventory Adjustments scenarios within the same Physical Inventory cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during physical inventory definition creation before escalating as a possible APPLICATION_ERROR

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

Navigate to Inventory

→

Create Physical Inventory Definition

→

Define Scope

→

Set Snapshot Date

→

Configure Freeze Options

→

Review

→

Save

Create Physical Inventory is the entry point of the physical inventory lifecycle within Plan-to-Produce Inventory Management. Once a physical inventory definition is created, tags are typically generated, physical counts entered, and resulting adjustments processed — covered by the Generate Physical Inventory Tags, Enter Physical Inventory Counts and Process Physical Inventory Adjustments scenarios in this same cluster. Physical inventory is a periodic, wall-to-wall count of an organization's inventory and is distinct from the rolling, sample-based approach used by Cycle Counts. Exact fields available, scope options and validation depend on inventory organization configuration and customer-specific Oracle Fusion configuration.

Next Stage →

Generate Physical Inventory Tags

Preconditions

An inventory organization is configured in the target Oracle Fusion SCM environment.
The physical inventory calendar and intended on-hand snapshot date are determined for the organization.
The subinventories to be included in the count scope, whether organization-wide or restricted, are configured and active.
The intended transaction freeze window and freeze approach are planned and communicated to affected teams.
The test user has appropriate access to create physical inventory definitions for the inventory organization.

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

Sample Test Data

Inventory Organization	${INVENTORY_ORGANIZATION}
Physical Inventory Name	${PHYSICAL_INVENTORY_NAME}
Description	${PHYSICAL_INVENTORY_DESCRIPTION}
Snapshot Date	${SNAPSHOT_DATE}
Subinventory Scope	${SUBINVENTORY_SCOPE}
Freeze Transactions Flag	${FREEZE_TRANSACTIONS_FLAG}
Tag Number Prefix	${TAG_NUMBER_PREFIX}
Approval Tolerance	${APPROVAL_TOLERANCE}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field applies to every physical inventory definition — for example, tag numbering fields are typically relevant only once tag generation begins downstream of this scenario.

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 Physical Inventory Open the Physical Inventory page to begin creating a new physical inventory definition. ${INVENTORY_ORGANIZATION}	The physical inventory definition creation page opens for the correct inventory organization.
3	Initiate Create Physical Inventory Initiate a new physical inventory definition and enter a name and description. ${PHYSICAL_INVENTORY_NAME} / ${PHYSICAL_INVENTORY_DESCRIPTION} This single business step replaces multiple technical actions such as opening the create page and confirming the definition name is available.	A new, unsaved physical inventory definition is opened with the entered name.
4	Define Name, Organization and Subinventory Scope Confirm the inventory organization and define the count scope as organization-wide or restricted to selected subinventories. ${INVENTORY_ORGANIZATION} / ${SUBINVENTORY_SCOPE}	The inventory organization and subinventory scope are accepted and reflected on the definition.
5	Set Snapshot Date and Transaction Freeze Options Set the on-hand snapshot date that will serve as the count baseline and configure whether transactions are frozen for the count window. ${SNAPSHOT_DATE} / ${FREEZE_TRANSACTIONS_FLAG} This single business step represents setting both the snapshot date and the freeze configuration, which are evaluated together as part of the same definition.	The snapshot date and transaction freeze configuration are accepted without unexpected validation errors.
6	Review the Physical Inventory Definition Review the physical inventory definition header and configuration as calculated by Oracle Fusion.	The reviewed definition reflects the entered name, organization, scope, snapshot date and freeze configuration.
7	Save the Physical Inventory DefinitionBusiness assertion Save the physical inventory definition for creation in the test environment. This is the primary business assertion for the scenario — a correctly created physical inventory definition with an accurate on-hand snapshot is the expected pass condition, not merely a successful save.	Oracle Fusion successfully creates the physical inventory definition without unexpected errors, and the on-hand snapshot is captured accurately at the defined date.

Expected Results

The physical inventory definition is created for the correct inventory organization.
The subinventory scope, whether organization-wide or restricted, is correctly applied.
The on-hand snapshot date is correctly captured and used as the count baseline.
The transaction freeze configuration is correctly applied for the count window.
The physical inventory definition does not conflict with an existing active physical inventory for the same organization.
The definition is available for physical inventory tag generation.
The physical inventory definition is visible and traceable for the test inventory organization.

Key Validation Checkpoints

Physical inventory definition saved correctly.
On-hand snapshot captured accurately at the defined date.
Definition available for tag generation.

Core Business Scenario

Create Physical Inventory

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 Create Physical Inventory business scenario. Jarvis AI can extend this scenario by generating additional scope, snapshot date, freeze and security variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every subinventory scope, snapshot date or freeze combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Scope variations for the customer's environment — including edge cases such as an overlapping physical inventory already in progress, since correctly enforced validation around active count windows is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Physical Inventory business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Inventory Organizations, Subinventories and Snapshot Calendars.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scope, snapshot date, freeze and security variations.

Positive + Negative Test Variations

Valid physical inventory definitions and edge cases such as an overlapping active physical inventory, invalid snapshot date 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 scope, snapshot date or freeze combination, SyntraFlow maintains one core Create Physical Inventory scenario and allows Jarvis AI to generate scope, snapshot, freeze and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Physical Inventory 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

Create a standard organization-wide physical inventory
Create a physical inventory scoped to selected subinventories
Create a physical inventory with a scheduled snapshot date
Create a physical inventory with transaction freeze enabled
Create a physical inventory with transaction freeze disabled, where permitted

Negative Scenarios

Attempt to create a physical inventory for an invalid inventory organization
Enter an invalid snapshot date
Attempt to create a physical inventory using a duplicate name
Attempt to create a physical inventory that overlaps with an active physical inventory already in progress
Enter an invalid subinventory scope
Attempt to save a definition with missing required freeze configuration

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 inventory organization, subinventory scope and snapshot date combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Physical Inventory scenarios relevant to the customer's actual implementation.

Standard Library Definition

Inventory Organization    ${INVENTORY_ORGANIZATION}
Physical Inventory Name   ${PHYSICAL_INVENTORY_NAME}
Description               ${PHYSICAL_INVENTORY_DESCRIPTION}
Snapshot Date             ${SNAPSHOT_DATE}
Subinventory Scope        ${SUBINVENTORY_SCOPE}
Freeze Transactions Flag  ${FREEZE_TRANSACTIONS_FLAG}
Tag Number Prefix         ${TAG_NUMBER_PREFIX}
Approval Tolerance        ${APPROVAL_TOLERANCE}

DataVault

Inventory Organizations
  Active inventory organizations eligible for physical inventory
Subinventories
  Active subinventories per organization
Snapshot Calendars
  Planned physical inventory snapshot dates
Freeze Windows
  Approved transaction freeze windows by organization
Approval Tolerances
  Approved tolerance ranges by organization

Jarvis AI Generates

Scenario 01 — Org A + Organization-Wide Scope + Freeze Enabled
Scenario 02 — Org A + Subinventory-Scoped Definition
Scenario 03 — Org B + Scheduled Snapshot Date
Scenario 04 — Org A + Freeze Disabled
Scenario 05 — Overlapping Active Physical Inventory
Scenario 06 — Unauthorized User Attempts Create Physical Inventory
...

Create Physical Inventory test data can include sensitive inventory categories such as valuation, location and scheduling 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 Create Physical Inventory scenarios Jarvis can generate from this business scenario, spanning scope, snapshot date and freeze 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 Organization-Wide Physical Inventory	Positive/Scope	Physical inventory definition created covering the full inventory organization	Syntra Ready
VAR-002	Subinventory-Scoped Physical Inventory	Positive/Scope	Definition created with count scope restricted to selected subinventories	Syntra Ready
VAR-003	Scheduled Snapshot Date	Positive	Definition created with a future-dated on-hand snapshot date	Syntra Ready
VAR-004	Transaction Freeze Enabled	Positive/Freeze	Definition created with transaction freeze enabled for the count window	Syntra Ready
VAR-005	Transaction Freeze Disabled	Positive/Freeze	Definition created with transaction freeze disabled, where permitted	Syntra Ready
VAR-006	Invalid Inventory Organization	Negative	Selected inventory organization is invalid or inactive	Syntra Ready
VAR-007	Invalid Snapshot Date	Negative	Snapshot date entered is invalid or outside an acceptable range	Syntra Ready
VAR-008	Duplicate Physical Inventory Name	Negative	Physical inventory name entered already exists for the inventory organization	Syntra Ready
VAR-009	Overlapping Active Physical Inventory	Negative/Scope	An active physical inventory already exists for the selected organization or scope	Syntra Ready
VAR-010	Invalid Subinventory Scope	Negative/Scope	Selected subinventory scope is invalid or inactive	Syntra Ready
VAR-011	Missing Required Freeze Configuration	Negative/Freeze	Definition saved without required transaction freeze configuration	Syntra Ready

Automatically Expand Positive and Negative Physical Inventory Coverage

Positive Testing

Jarvis generates scenarios using inventory organization, scope, snapshot date and freeze combinations expected to successfully create a physical inventory definition in Oracle Fusion.

Valid Organization + Valid Scope + Valid Snapshot Date + Valid Freeze Configuration → Physical Inventory Definition Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around snapshot date, scope, overlapping definitions and security.

Invalid Snapshot Date → Expected Date Validation
Invalid Subinventory Scope → Expected Scope Validation
Duplicate Physical Inventory Name → Expected Uniqueness Validation
Overlapping Active Physical Inventory → Expected Overlap Validation
Unauthorized User → Expected Access Restriction

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

Scenario	Oracle Outcome	Test Result
Valid 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 Create Physical Inventory scenarios and group them into reusable execution packs.

SCM Inventory Management Create Physical Inventory Regression Pack

Standard Organization-Wide Physical Inventory
Subinventory-Scoped Physical Inventory
Scheduled Snapshot Date
Transaction Freeze Enabled
Transaction Freeze Disabled
Invalid Inventory Organization
Invalid Snapshot Date
Overlapping Active Physical Inventory
Invalid Subinventory Scope
Security Restriction — Unauthorized Create Physical Inventory

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

Once scheduled, SyntraFlow executes the selected Create Physical Inventory 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 Create Physical Inventory Regression Pack
Schedule	Quarterly Update Regression
Tests	11 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 create a physical inventory definition 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 physical inventory definition creation access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Manager	Create Physical Inventory Definition	Allowed	PASS
Unauthorized User	Attempts Definition Creation	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 Create Physical Inventory 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 — Create Physical Inventory, 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

Set Snapshot Date and Transaction Freeze Options

May internally include

Open Snapshot Selector → Enter Snapshot Date → Toggle Freeze Transactions → Confirm Freeze Scope → Confirm

Business Step

Review the Physical Inventory Definition

May internally include

Open Definition Preview → Read Calculated Header/Scope Fields → Compare Against Entered Values → Save

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 physical inventory definition was created 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: Create Physical Inventory failed — Likely category: DATA_ERROR — Evidence: an active physical inventory already exists for the selected organization — Recommended action: complete or cancel the existing physical inventory before creating a new one. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Set Snapshot Date and Transaction Freeze Options	Pass	—
Review the Physical Inventory Definition	Pass	—
Save the Physical Inventory Definition	Pass	Pass

Related Physical Inventory Tests

Create Physical Inventory is the entry point of the Physical Inventory cluster — explore the related tag generation, count entry and adjustment processing scenarios below.

Generate Physical Inventory Tags Enter Physical Inventory Counts Process Physical Inventory Adjustments

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

Start with the Syntra Standard Create Physical Inventory test, use DataVault to provide environment-specific test data, let Jarvis generate additional scope, snapshot date, freeze 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

What is the difference between a physical inventory and a cycle count?

A physical inventory is a full, typically periodic wall-to-wall count of all — or a defined scope of — an inventory organization's on-hand quantities, often performed once or twice a year and frequently combined with a transaction freeze for the count window. Cycle counts, by contrast, are ongoing and sample-based, counting a rotating subset of items on a recurring schedule using an ABC classification or schedule-based strategy. This scenario covers creation of the physical inventory definition specifically, not cycle counting, which is covered separately in the Cycle Counts cluster.

What does a transaction freeze mean for a physical inventory?

A transaction freeze restricts or blocks certain inventory transactions for the affected organization or subinventories during the physical inventory count window, so that on-hand quantities remain stable while the count is performed. Whether a freeze is enabled, and how strictly it is enforced, depends on the physical inventory definition and the customer's Oracle Fusion configuration. This test validates that the freeze configuration entered on the definition is correctly captured.

Why does the snapshot date matter for a physical inventory?

The snapshot date determines the on-hand quantity baseline that the physical count will be compared against. An inaccurate or mismatched snapshot date can cause count variances that do not reflect real inventory discrepancies. This test validates that the snapshot date entered on the definition is correctly captured and used as the count baseline.

How does security testing work for physical inventory definition creation?

Access to create a physical inventory definition 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 manager versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.

Does this test perform a real physical inventory count or real inventory movements in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not perform a real wall-to-wall count, freeze real transactions or produce real inventory movements in a production environment.