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

Syntra Standard Oracle Test Library

Oracle Fusion Generate Physical Inventory Tags Test Cases

Validate that Oracle Fusion correctly generates physical inventory tags — the system-generated count tags covering all on-hand inventory within the defined scope — from an existing physical inventory definition, at the correct on-hand snapshot point.

Test ID	ORCL.SCM.INV.PI.TAGS
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 16 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that physical inventory tags — the system-generated count tags covering all on-hand inventory within the defined scope — are correctly generated from an existing, active physical inventory definition, at the correct on-hand snapshot point.

The scenario should confirm that:

physical inventory tags are generated only from an active physical inventory definition
the correct items and locations are included in the generated tags based on the defined subinventory scope
the generated tag count matches the expected on-hand item/location combinations at the snapshot point
tag regeneration after a correction produces an accurate, updated tag set
tags correctly cover lot- and serial-controlled items where applicable
the generated tags are available for count entry once produced
Oracle correctly enforces validation when tags already exist, the reference is invalid, no items are in scope, the count window has closed, or the tag numbering configuration is invalid (DATA_ERROR, CONFIGURATION_ERROR, EXPECTED_VALIDATION)

This scenario assumes a physical inventory definition already exists, typically built via the separate Create Physical Inventory scenario. It covers generation of the physical inventory tags only. It does not cover entering physical count quantities against those tags, which is covered by Enter Physical Inventory Counts, or the review and posting of count adjustments, which is covered by Process Physical Inventory Adjustments, both in the same Physical Inventory cluster.

When to Use This Test

Functional testing of physical inventory tag generation for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of tag generation behavior after an Oracle quarterly update
UAT sign-off for inventory teams that rely on periodic or year-end physical inventory counts
Verifying that subinventory scoping and the on-hand snapshot correctly determine which items and locations receive tags
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and EXPECTED_VALIDATION conditions surfaced during tag generation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Inventory Physical Inventory Process

Create Physical Inventory

→

Generate Physical Inventory Tags

→

Enter Physical Inventory Counts

→

Process Physical Inventory Adjustments

Generate Physical Inventory Tags is the second stage of the Physical Inventory cluster within Plan-to-Produce, following creation of the physical inventory definition and preceding count entry. It converts a definition's scope and on-hand snapshot into a concrete set of numbered tags covering every item/location combination due to be counted. Exact tag numbering, snapshot timing and scoping behavior depend on inventory organization configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Create Physical Inventory

Next Stage →

Enter Physical Inventory Counts

Preconditions

An active physical inventory definition exists in the target Oracle Fusion SCM environment.
The on-hand inventory snapshot for the defined scope has been captured.
A tag numbering scheme is configured for the physical inventory definition.
The test user has appropriate access to generate tags for the definition.
Where subinventory scoping is used, the relevant subinventories are configured and active.

Exact snapshot timing, tag numbering behavior and available generation options may vary by Oracle Fusion implementation, inventory organization configuration and customer-specific setup. State and readiness requirements vary by implementation.

Sample Test Data

Physical Inventory Name	${PHYSICAL_INVENTORY_NAME}
Inventory Organization	${INVENTORY_ORGANIZATION}
Subinventory Scope	${SUBINVENTORY_SCOPE}
Tag Prefix	${TAG_PREFIX}
Tag Count	${TAG_COUNT}

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 generation — for example, subinventory scope is only relevant where the physical inventory definition or generation request is limited to specific subinventories.

Test Steps

7 business-readable steps. SyntraFlow's automation executes ~16 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 for the relevant inventory organization. ${INVENTORY_ORGANIZATION}	The Physical Inventory page opens for the correct inventory organization.
3	Locate the Physical Inventory Definition Search for and open the existing, active physical inventory definition that tags will be generated from. ${PHYSICAL_INVENTORY_NAME}	The correct physical inventory definition is opened and confirmed active.
4	Initiate Generate Tags Start the Generate Tags action for the selected physical inventory definition. This single business step replaces multiple technical actions such as opening the generation dialog and confirming the source definition.	The generate tags request is accepted for processing.
5	Review Tag Scope and Count Review the resulting tag scope, checking the subinventory scope, tag prefix and expected tag count before confirming. ${SUBINVENTORY_SCOPE} / ${TAG_PREFIX} / ${TAG_COUNT} Reviewing the scope before confirming lets the tester catch an unexpected scope or count before the tag set is finalized.	The generated tag scope and count reflect the correct items, locations and configured numbering.
6	Confirm Generation Confirm the tag generation request for the physical inventory definition.	Confirmation is accepted without unexpected validation errors.
7	SaveBusiness assertion Save the generated physical inventory tags. This is the primary business assertion for the scenario — a correctly generated tag set with accurate scope and count is the expected pass condition, not merely a successful save.	The tags are saved and become available for count entry, with correct items, locations and tag numbering.

Expected Results

Physical inventory tags are generated only from an active physical inventory definition.
The correct items and locations are included based on the defined subinventory scope.
The generated tag count matches the expected on-hand item/location combinations.
The generated tags are available for count entry.
Regeneration after a correction produces an accurate, updated tag set.
Oracle correctly rejects duplicate generation, an invalid reference, or generation with no items in scope.

Key Validation Checkpoints

Correct items and locations included in the generated tags.
Tag count matches expected on-hand item/location combinations.
Tags available for count entry.

Core Business Scenario

Generate Physical Inventory Tags

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 Generate Physical Inventory Tags business scenario. Jarvis AI can extend this scenario by generating additional scope, regeneration and boundary 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 or regeneration scenario. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Scope variations for the customer's environment — including cases such as duplicate generation attempts and zero-item-in-scope conditions, since correctly enforced behavior at these edges is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Generate Physical Inventory Tags business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Physical Inventory Names, Inventory Organizations, Subinventory Scopes and Tag Prefixes.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scope, regeneration and boundary variations.

Positive + Negative Test Variations

Valid generation scenarios and edge cases such as duplicate generation, no items in scope or an invalid physical inventory reference.

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 subinventory scope, tag prefix or regeneration combination, SyntraFlow maintains one core Generate Physical Inventory Tags scenario and allows Jarvis AI to generate scope- and regeneration-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Generate a standard set of tags covering the full defined scope
Generate tags scoped to a specific subinventory
Regenerate tags after correcting the physical inventory definition
Generate tags covering lot- and serial-controlled items

Negative Scenarios

Attempt tag generation when tags have already been generated (duplicate generation)
Attempt generation against an invalid physical inventory reference
Attempt generation when no on-hand items exist in scope
Attempt generation after the count window has closed
Attempt generation with an invalid tag numbering configuration

These are representative examples only. Negative-scenario behavior and available generation options can depend on the customer's Oracle Fusion configuration, inventory organization setup and count window rules — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every subinventory scope, tag numbering scheme and regeneration path in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Generate Physical Inventory Tags scenarios relevant to the customer's actual implementation.

Standard Library Definition

Physical Inventory Name  ${PHYSICAL_INVENTORY_NAME}
Inventory Organization   ${INVENTORY_ORGANIZATION}
Subinventory Scope       ${SUBINVENTORY_SCOPE}
Tag Prefix               ${TAG_PREFIX}
Tag Count                ${TAG_COUNT}

DataVault

Physical Inventory Definitions
  Active definitions eligible for tag generation
Inventory Organizations
  Configured organizations with on-hand snapshots
Subinventories
  Configured, active subinventories per organization
Tag Numbering Schemes
  Configured prefixes and numbering ranges
Count Windows
  Valid open count windows per definition

Jarvis AI Generates

Scenario 01 — Standard Tag Generation, Full Scope
Scenario 02 — Subinventory-Scoped Tag Generation
Scenario 03 — Regeneration After Correction
Scenario 04 — Lot/Serial-Controlled Item Tags
Scenario 05 — Duplicate Generation Attempted
Scenario 06 — Invalid Physical Inventory Reference
...

Generate Physical Inventory Tags test data can include operational inventory dimensions such as organization, subinventory and on-hand item detail. 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 Generate Physical Inventory Tags scenarios Jarvis can generate from this business scenario, spanning scope, regeneration and boundary 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 Tag Generation, Full Scope	Positive	Tags generated from an active definition covering the full defined scope	Syntra Ready
VAR-002	Subinventory-Scoped Tag Generation	Positive/Scope	Generation limited to a specific subinventory rather than the full organization	Syntra Ready
VAR-003	Regeneration After Correction	Positive/Regeneration	Tags regenerated for the same definition after a scope or configuration correction	Syntra Ready
VAR-004	Lot/Serial-Controlled Item Tags	Positive	Generated tags correctly cover lot- and serial-controlled items in scope	Syntra Ready
VAR-005	Duplicate Generation Attempted	Negative/Regeneration	Generation attempted against a definition that already has an active tag set	Syntra Ready
VAR-006	Invalid Physical Inventory Reference	Negative	Generation attempted against a physical inventory definition that does not exist	Syntra Ready
VAR-007	No On-Hand Items in Scope	Negative/Scope	No on-hand items exist within the defined subinventory scope at generation time	Syntra Ready
VAR-008	Generation After Count Window Closed	Negative	Generation attempted after the physical inventory count window has closed	Syntra Ready
VAR-009	Invalid Tag Numbering Configuration	Negative	Generation attempted with an invalid or incomplete tag numbering scheme	Syntra Ready

Automatically Expand Positive and Negative Tag Generation Coverage

Positive Testing

Jarvis generates scenarios using physical inventory definition, subinventory scope and tag numbering combinations expected to successfully generate tags in Oracle Fusion.

Active Definition + Valid Scope + Valid Tag Numbering → Physical Inventory Tags Generated

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around duplicate generation, reference validity, scope eligibility and count window timing.

Tags Already Generated → Expected Duplicate Generation Validation
Invalid Physical Inventory Reference → Expected Reference Validation
No Items in Scope → Expected Empty Result
Count Window Closed → Expected Timing 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 Generate Physical Inventory Tags scenarios and group them into reusable execution packs.

SCM Inventory Generate Physical Inventory Tags Regression Pack

Standard Tag Generation, Full Scope
Subinventory-Scoped Tag Generation
Regeneration After Correction
Lot/Serial-Controlled Item Tags
Duplicate Generation Attempted
Invalid Physical Inventory Reference
No On-Hand Items in Scope
Generation After Count Window Closed
Invalid Tag Numbering Configuration

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

Once scheduled, SyntraFlow executes the selected Generate Physical Inventory Tags 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 Generate Physical Inventory Tags Regression Pack
Schedule	Quarterly Update Regression
Tests	9 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 generate physical inventory tags for a given definition is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that generation access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Manager	Generate Physical Inventory Tags	Allowed	PASS
Unauthorized User	Attempts Tag Generation	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 Generate Physical Inventory Tags 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 — Generate Physical Inventory Tags, 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

Initiate Generate Tags

May internally include

Open Physical Inventory Definition → Select Generate Tags Action → Open Generation Dialog → Confirm Source Definition

Business Step

Review Tag Scope and Count

May internally include

Open Generated Tag Preview → Read Subinventory/Item/Location Columns → Compare Against Expected On-Hand Snapshot

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 tags were generated 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: Generate Physical Inventory Tags failed — Likely category: EXPECTED_VALIDATION — Evidence: tags have already been generated for this physical inventory — Recommended action: this is expected behavior; use the existing tag set or cancel and recreate the definition. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Initiate Generate Tags	Pass	—
Confirm Generation	Pass	—
Review Tag Scope and Count	Pass	Pass

Related Physical Inventory Tests

Generate Physical Inventory Tags sits between definition and physical count entry in the Physical Inventory cluster — explore the related create, count entry and adjustment scenarios below.

Create Physical Inventory Enter Physical Inventory Counts Process Physical Inventory Adjustments

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

Start with the Syntra Standard Generate Physical Inventory Tags test, use DataVault to provide environment-specific test data, let Jarvis generate additional scope, regeneration and boundary 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 a physical inventory tag in Oracle Fusion?

A physical inventory tag is a system-generated count tag covering an item/location combination within the scope of a physical inventory definition. Tags are produced from the on-hand inventory snapshot at the point of generation and are numbered according to the configured tag numbering scheme, ready for count entry.

How is the scope of generated tags determined?

Scope is driven by the physical inventory definition's inventory organization and subinventory configuration, together with the on-hand snapshot captured at generation time. Where the definition or generation request is scoped to specific subinventories, only items and locations within that scope receive tags. Exact behavior depends on the customer's Oracle Fusion configuration.

What happens if physical inventory tags need to be regenerated?

Where a correction is required — for example after fixing scope or configuration issues — tags can typically be regenerated for the same physical inventory definition. Oracle Fusion is expected to prevent duplicate generation against a definition that already has an active tag set, surfacing this as an expected validation (EXPECTED_VALIDATION) rather than an application defect.

How does security testing work for physical inventory tag generation?

Access to generate tags for a given physical inventory definition 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 move real inventory or affect real stock counts in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It generates physical inventory tags for testing purposes and does not perform real inventory movements or affect production stock records.