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

Syntra Standard Oracle Test Library

Oracle Fusion Process Physical Inventory Adjustments Test Cases

Validate approval and posting of inventory adjustments resulting from a completed physical inventory count, and correct closure of the physical inventory, using a parameterised approval tolerance rather than a fixed dollar or quantity value.

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

Test Objective

Validate approval and posting of the inventory adjustments generated by a completed physical inventory count, and confirm that the physical inventory can only be closed once every adjustment has been actioned and every tag is accounted for, without assuming any specific hard-coded tolerance value.

The scenario should confirm that:

adjustments generated by the completed physical inventory count route to the appropriate approver based on ${APPROVAL_TOLERANCE} and variance magnitude, not a hard-coded threshold
an approver can approve an adjustment individually within their configured authority
an approver can approve adjustments in bulk across the physical inventory
an approver can override the default account on an adjustment where permitted
multi-level approval routing is enforced where configured
an approved adjustment posts correctly to on-hand quantity and accounting
the physical inventory cannot be closed while unresolved variances or unaccounted tags remain
approval history and audit trail are captured and retained against each adjustment
users without the appropriate role or authority cannot approve adjustments or close the physical inventory

This scenario assumes counts have already been entered through the Enter Physical Inventory Counts scenario and that a variance report has been generated. It does not cover physical inventory definition, tag generation or count entry — those are addressed by earlier scenarios in the Physical Inventory lifecycle. This is the fourth and final page of the Physical Inventory sub-cluster.

When to Use This Test

Functional testing of a new Oracle Fusion Inventory Management physical inventory adjustment approval and closure workflow implementation
Regression testing after an Oracle quarterly update
UAT sign-off for physical inventory adjustment approval routing, posting and closure access control
Final validation case referenced by physical inventory count entry and exception scenarios within the same lifecycle

Where This Test Fits in the Physical Inventory Process

Create Physical Inventory

→

Generate Physical Inventory Tags

→

Enter Physical Inventory Counts

→

Process Physical Inventory Adjustments

This test covers the final stage of the Physical Inventory lifecycle — approving or rejecting the adjustments generated from the completed count, posting them to on-hand and accounting, and closing the physical inventory once every tag has been accounted for.

← Previous Stage

Enter Physical Inventory Counts

Preconditions

Oracle Fusion Inventory Management access is configured and available for the test user.
All tags in scope for the physical inventory have been counted or explicitly marked void.
A variance report has been generated for the completed physical inventory, listing the resulting adjustments.
Approval rules and approver assignments are configured for the applicable organization or item class.
The test user (or approver context) has the appropriate role and access to action physical inventory adjustment approvals and closure.

Approval tolerances, routing rules and approver assignments are configured per organization and item class and vary by Oracle Fusion implementation — this test never assumes a specific dollar or quantity tolerance value.

Sample Test Data

Physical Inventory Name	${PHYSICAL_INVENTORY_NAME}
Item	${ITEM}
Variance Quantity	${VARIANCE_QUANTITY}
Approval Tolerance	${APPROVAL_TOLERANCE} — customer-configured value, not a fixed dollar or quantity threshold
Approver	${APPROVER} — valid approver assigned to the applicable rule and level
Account	${ACCOUNT}
Adjustment Type	Increase / Decrease — scenario-defined
Approval Action	Approve / Reject, where applicable
Tag Status	All Tags Counted or Void — required before the physical inventory can be closed

Approval tolerances, routing hierarchies and item-class-specific rules are defined per Oracle Fusion customer implementation. This test intentionally uses ${APPROVAL_TOLERANCE} and ${VARIANCE_THRESHOLD} as placeholders rather than fixed dollar or quantity values — actual tolerance values should be sourced from DataVault or the customer's approval configuration, not hard-coded into the test.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~27 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Sign In as Approver Sign in to Oracle Fusion as the user assigned to approve physical inventory adjustments. ${APPROVER}	The approver signs in successfully and lands on the home page.
2	Navigate to Inventory Management Navigate to the Inventory Management work area used to review the completed physical inventory and its pending adjustments.	The Inventory Management work area opens and physical inventory adjustment functions are available.
3	Review the Variance Report Open the variance report generated for the completed physical inventory and review each resulting adjustment. ${PHYSICAL_INVENTORY_NAME} This single business step replaces multiple technical actions such as opening the report, filtering by physical inventory name and reviewing each variance line.	The variance report lists every adjustment resulting from the count, with variance and tolerance comparison presented accurately, without a fixed dollar or quantity value being assumed by the test.
4	Approve or Reject Each Adjustment Approve or reject each pending adjustment individually or in bulk, as applicable to the scenario. ${ITEM} / ${VARIANCE_QUANTITY}	Each decision is accepted by Oracle Fusion without unexpected errors, and is routed to the correct approver based on ${APPROVAL_TOLERANCE}.
5	Provide Justification Where Required Enter approval or rejection justification if Oracle Fusion requires it for the adjustment.	Justification is accepted where required, or the step is skipped where not required by configuration.
6	Submit the Decisions Submit the approval or rejection decisions for processing.	The decisions are submitted successfully and each adjustment status updates accordingly.
7	Close the Physical Inventory Once all adjustments have been processed and every tag is accounted for, close the physical inventory. ${PHYSICAL_INVENTORY_NAME}	The physical inventory closes successfully only when every tag has been counted or voided and every adjustment has been actioned; closure is blocked otherwise.
8	Verify On-Hand and Accounting ImpactBusiness assertion Confirm the on-hand quantity and accounting impact of the approved adjustments, and confirm the physical inventory status is closed. ${ACCOUNT} This is the main business assertion for the scenario — the test does not stop merely because the approve, submit or close actions were accepted successfully.	Approved adjustments post correctly to on-hand quantity and accounting, and the physical inventory shows a closed status with a complete audit trail.

Expected Results

Adjustments resulting from the completed physical inventory route correctly to the configured approver based on ${APPROVAL_TOLERANCE} and variance magnitude.
An approver within their configured authority can approve adjustments individually or in bulk.
An approver can override the default account on an adjustment where permitted.
Multi-level approval routing is enforced where configured.
An approved adjustment posts correctly to on-hand quantity and accounting.
The physical inventory cannot be closed while unresolved variances or unaccounted tags remain.
Approval history and audit trail are captured and retained against each adjustment.
Users without the appropriate role or authority cannot approve adjustments or close the physical inventory.

Key Validation Checkpoints

Adjustment is correctly routed to the appropriate approver based on ${APPROVAL_TOLERANCE} and variance magnitude, not a hard-coded threshold.
Approved adjustments post to on-hand and accounting correctly.
The physical inventory cannot close until all tags are accounted for.
Approval history and audit trail are recorded against each adjustment.

Core Business Scenario

Process Physical Inventory Adjustments

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 physical inventory adjustment approval and closure business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same approval and closure test dozens of times simply to cover different combinations of variance magnitude, item class, organization and approval level. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's configured approval tolerances — expressed relative to ${APPROVAL_TOLERANCE}, without assuming a fixed dollar or quantity value.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Physical Inventory Names, Items, Variance Quantities, Approval Tolerances, Approvers and Accounts.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, approval-routing and closure scenarios.

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 dozens of near-duplicate copies of the same approval and closure test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available approval configuration — expressed relative to ${APPROVAL_TOLERANCE}, never a hard-coded dollar or quantity value.

AI-Generated Test Variations

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

Approve adjustment within approver's authority
Approve adjustments in bulk across the count
Approve with account override
Close physical inventory after all adjustments processed
Multi-level approval routing where configured

Negative Scenarios

Unauthorized approver attempts approval
Approval attempted before all tags accounted for
Invalid account on adjustment
Attempt to close with unresolved variances
Approval attempted twice on same adjustment
Missing required approval justification

These are representative examples only. Approval rules, approval tolerances and expected behavior depend on the customer's Oracle Fusion configuration — not every Oracle configuration behaves identically, and approval tolerances are never hard-coded; they are sourced from DataVault or the customer's configuration where available.

Generated Using Your DataVault Test Data

Generic test data cannot represent a real Oracle Fusion approval configuration. Where connected, Jarvis can use approved test data available through Syntra DataVault — variance magnitude, item class, and account relative to ${APPROVAL_TOLERANCE} — to create variations relevant to the customer's actual implementation, rather than assuming a fixed tolerance value.

Standard Library Definition

Physical Inventory Name  ${PHYSICAL_INVENTORY_NAME}
Item                     ${ITEM}
Variance Quantity        ${VARIANCE_QUANTITY}
Approval Tolerance       ${APPROVAL_TOLERANCE}
Approver                 ${APPROVER}
Account                  ${ACCOUNT}

DataVault

Approval Rules
  Variance-Based
  Item-Class-Based
  Organization-Based
Approval Tolerances
  Per organization and item class (not published)
Approvers
  Approver A (Level 1)
  Approver B (Level 2)
Organizations
  Org A
  Org B
Item Classes
  Class A
  Class B

Jarvis AI Generates

Scenario 01 — Variance Below ${APPROVAL_TOLERANCE} + Single-Level + Approve
Scenario 02 — Variance Above ${APPROVAL_TOLERANCE} + Multi-Level + Approve
Scenario 03 — Bulk Approve Across Count
Scenario 04 — Account Override on Approval
Scenario 05 — Close Physical Inventory After Full Processing
Scenario 06 — Unauthorized Approver Attempt
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Approval configuration — including approval tolerances, routing hierarchies and item-class rules — is customer-specific and, where DataVault is connected, is sourced from DataVault or the customer's own configuration rather than assumed by SyntraFlow.

Example Test Variations

Representative examples of scenarios Jarvis can generate from this business scenario. 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	Approve Adjustment Within Authority	Positive/Approval	Variance within the approver's configured authority relative to ${APPROVAL_TOLERANCE}; adjustment is approved	Syntra Ready
VAR-002	Approve Adjustments in Bulk Across the Count	Positive/Approval	Multiple adjustments across the physical inventory are approved in a single bulk action	Syntra Ready
VAR-003	Approve Adjustment With Account Override	Positive/Approval	Approver overrides the default account on the adjustment before approving, where permitted	Syntra Ready
VAR-004	Multi-Level Approval Routing	Positive/Approval	Variance requires more than one approval level; adjustment routes to the next approver in the hierarchy	Syntra Ready
VAR-005	Close Physical Inventory After All Adjustments Processed	Positive/Closure	Every tag is accounted for and every adjustment has a decision; the physical inventory closes successfully	Syntra Ready
VAR-006	Approve Adjustment Exceeding Approver's Own Tolerance	Positive/Approval	Variance exceeds the acting approver's own configured tolerance; adjustment routes to the next approver or is blocked	Syntra Ready
VAR-007	Unauthorized Approver Attempts Approval	Negative/Approval	A user without approval authority attempts to action an adjustment	Syntra Ready
VAR-008	Approval Attempted Before All Tags Accounted For	Negative/Approval	An approval action is attempted while tags in the physical inventory remain uncounted or unvoided	Syntra Ready
VAR-009	Invalid Account on Adjustment	Negative	The adjustment references an account that fails Oracle account validation	Syntra Ready
VAR-010	Attempt to Close With Unresolved Variances	Negative/Closure	Closure is attempted while one or more adjustments remain undecided; closure is expected to be blocked	Syntra Ready
VAR-011	Approval Attempted Twice on Same Adjustment	Negative/Approval	A second approval action is attempted on an adjustment that already received a decision	Syntra Ready
VAR-012	Missing Required Approval Justification	Negative/Approval	Justification is required by configuration but not provided by the approver	Syntra Ready
VAR-013	Security Restriction — Counter Attempts Approval	Negative/Approval	A user holding only count-entry access, not approval access, attempts to action the adjustment or close the physical inventory	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the physical inventory adjustment approval, posting and closure business process.

Variance Within ${APPROVAL_TOLERANCE} + Single Approver → Approved and Posted Correctly

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's approval validations, routing rules, closure requirements and access controls around physical inventory adjustments.

Unauthorized Approver Attempt → Expected Access Validation
Approval Attempted Before All Tags Accounted For → Expected Validation
Invalid Account on Adjustment → Expected Account Validation
Attempt to Close With Unresolved Variances → Expected Block
Security Restriction → Expected Access Prevented

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

Process Physical Inventory Adjustments Regression Pack

Approve Adjustment Within Authority
Approve Adjustments in Bulk Across the Count
Approve Adjustment With Account Override
Multi-Level Approval Routing
Close Physical Inventory After All Adjustments Processed
Approve Adjustment Exceeding Approver's Own Tolerance
Unauthorized Approver Attempts Approval
Approval Attempted Before All Tags Accounted For
Attempt to Close With Unresolved Variances
Missing Required Approval Justification

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

Once scheduled, SyntraFlow executes the selected 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	Process Physical Inventory Adjustments 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 & Persona Variations

SyntraFlow validates physical inventory adjustment approval and closure access control by confirming that approvers can only action adjustments within their configured authority, and that users without approval access are correctly prevented from approving adjustments or closing the physical inventory.

Persona	Action	Expected	Syntra Result
Inventory Manager (within approval tolerance)	Approve Adjustment	Allowed	PASS
Inventory Manager (exceeds own tolerance)	Approve Adjustment	Routes to next approver or blocked	PASS
Inventory Counter	Attempts Approval	Access prevented	PASS
Unauthorized User	Attempts Approval	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 business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment, including Positive, Negative, Approval Routing and Closure variations relative to ${APPROVAL_TOLERANCE}.

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 — Process Physical Inventory Adjustments, 8 Business Steps

↓

DataVault — Customer-Specific Approval Configuration

↓

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

Review the Variance Report

May internally include

Open Variance Report → Filter by Physical Inventory Name → Review Variance Lines → Confirm Tolerance Comparison

Business Step

Approve or Reject Each Adjustment

May internally include

Open Decision Menu → Select Individual or Bulk Approve/Reject → Enter Justification (optional) → Confirm Action

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 business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

Step	Action Status	Business Validation
Approve or Reject Each Adjustment	Pass	—
Close the Physical Inventory	Pass	—
Verify On-Hand and Accounting Impact	Pass	Pass

Related Physical Inventory Tests

This is the fourth and final page in the Physical Inventory sub-cluster — approval and closure follow count creation, tag generation and count entry in the same lifecycle. Explore the related scenarios below.

Enter Physical Inventory Counts Create Physical Inventory Review On-Hand Availability

Turn This Standard Test into Your Oracle Physical Inventory Adjustment Regression Suite

Start with the Syntra Standard physical inventory adjustment approval and closure test, use DataVault to provide environment-specific approval configuration, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore 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

Physical Inventory Test Library Inventory Management Test Library SCM Test Library Oracle Fusion Test Library Oracle ERP Testing Tool Syntra DataVault

Frequently Asked Questions

What does the Process Physical Inventory Adjustments test validate in Oracle Fusion?

It validates that adjustments resulting from a completed physical inventory count route to the correct approver, that approval and posting update on-hand quantity and accounting correctly, and that the physical inventory can only be closed once every tag has been accounted for.

How are approval tolerances configured for this test?

Approval tolerances are configured per organization and item class within the customer's Oracle Fusion implementation. This test always uses ${APPROVAL_TOLERANCE} and ${VARIANCE_THRESHOLD} as placeholders rather than a hard-coded dollar or quantity value — actual values are sourced from DataVault or the customer's own configuration.

What happens if variances remain unresolved when trying to close the physical inventory?

Oracle Fusion is expected to block closure while unresolved variances or unaccounted tags remain. This scenario includes a negative variation that confirms closure is correctly prevented until every adjustment has been actioned.

What are the requirements for closing a physical inventory?

Every tag in scope must be counted or explicitly marked void, and every resulting adjustment must have received an approval decision, before the physical inventory can be closed. This scenario validates both the successful closure path and the blocked path when requirements are not met.

How is security tested as part of this scenario?

SyntraFlow includes variations that confirm an authorized approver can action adjustments within their configured tolerance, that an adjustment exceeding an approver's own authority routes onward or is blocked, and that unauthorized users are correctly prevented from approving or closing — see the Security & Persona Variations section below.