Oracle ERP Testing Tool > Test Library > SCM > Inventory Management > Cycle Counts

Syntra Standard Oracle Test Library

Oracle Fusion Enter Cycle Count Test Cases

Validate that a physically counted quantity can be entered against a generated cycle count sequence in Oracle Fusion SCM, that the resulting variance against system on-hand quantity is calculated correctly, and that variances outside tolerance are correctly identified.

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

Test Objective

The objective of this test is to validate entry of physically counted quantities against a generated cycle count sequence in Oracle Fusion SCM Inventory Management, and correct identification of variances between the counted quantity and system on-hand quantity.

The scenario should confirm that:

the counted quantity entered against the assigned sequence is recorded accurately
the variance between counted quantity and system on-hand quantity is calculated correctly
a variance within the configured tolerance is correctly identified as such
a variance outside the configured tolerance is correctly flagged and routed for adjustment approval where required
recount and lot/serial-controlled entry are handled correctly where applicable
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 a physically counted quantity against a cycle count sequence that has already been generated and opened for entry. It does not cover generation of the count sequence itself, or approval of the resulting adjustment, which are covered by the separate Generate Count Sequences and Approve Cycle Adjustment scenarios in the same Cycle Counts cluster.

When to Use This Test

Functional testing of cycle count entry for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of variance calculation and tolerance behavior after an Oracle quarterly update
UAT sign-off for warehouse and inventory teams that routinely perform physical cycle counts
Baseline case referenced by the Generate Count Sequences and Approve Cycle Adjustment scenarios within the same Cycle Counts cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and EXPECTED_VALIDATION conditions surfaced during count entry before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Cycle Counts Process

Generate Count Sequences

→

Enter Cycle Count

→

Calculate Variance

→

Recount if Required

→

Route for Approval

→

Approve Cycle Adjustment

Enter Cycle Count is the second stage of the cycle count lifecycle, following generation of count sequences and preceding approval of any resulting adjustment. A count sequence must already exist and be open for entry before this scenario can be executed. Exact tolerance thresholds, approval routing and lot/serial requirements depend on item, subinventory and customer-specific Oracle Fusion configuration.

← Previous Stage

Generate Count Sequences

Next Stage →

Approve Cycle Adjustment

Preconditions

A cycle count sequence has already been generated and is open for entry in the target Oracle Fusion SCM environment.
The test counter has access to the assigned count sequence.
The item, subinventory and locator referenced on the sequence are active and correctly configured.
Tolerance thresholds for the applicable cycle count are configured for the item or item category.
Where the item is lot- or serial-controlled, valid lot or serial data is available for entry.

Exact field availability, tolerance thresholds, recount rules and approval routing may vary by Oracle Fusion implementation, cycle count definition and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Cycle Count Name	${CYCLE_COUNT_NAME}
Sequence Number	${SEQUENCE_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 ~17 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 Count Sequence Open the Cycle Counts task and locate the count sequence assigned to the counter for entry. ${CYCLE_COUNT_NAME} / ${SEQUENCE_NUMBER}	The assigned count sequence opens for entry, showing the item, subinventory and locator to be counted.
3	Review Item and Location Detail Confirm the item, subinventory and locator shown on the sequence 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 sequence match the intended physical count location.
4	Enter the Physically Counted Quantity Enter the physically counted quantity, 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	Review the Calculated Variance Review the variance Oracle Fusion calculates between the counted quantity and the system on-hand quantity. ${SYSTEM_QUANTITY}	The displayed variance reflects counted quantity minus system quantity.
6	Confirm Entry or Trigger Recount Where the variance appears unexpectedly large or the counter is uncertain of the physical count, trigger a recount instead of confirming the entry. Recount handling exercises the same entry scenario a second time before a variance is treated as final.	The count entry is either confirmed as final or flagged for recount, as appropriate.
7	Submit the Count Entry Submit the entered count for the sequence.	Oracle Fusion successfully records the count entry without unexpected errors.
8	Verify Variance Status and RoutingBusiness assertion Reopen or refresh the count sequence and confirm the recorded counted quantity, the calculated variance, and whether the entry is within tolerance or has been routed for adjustment approval. This is the primary business assertion for the scenario — an accurately recorded count with a correctly calculated and classified variance is the expected pass condition, not merely a successful submission.	The recorded counted quantity, variance and tolerance status are correct, and entries outside tolerance are routed for approval.

Expected Results

The counted quantity is recorded accurately against the assigned sequence.
The variance between counted quantity and system on-hand quantity is calculated correctly.
A variance within configured tolerance is correctly identified as within tolerance.
A variance outside configured tolerance is correctly flagged and routed for approval where required.
Recount entries are correctly captured where triggered.
Lot/serial detail is correctly recorded where the item requires it.
The count entry is visible and traceable for the assigned counter.

Key Validation Checkpoints

Entered quantity recorded accurately.
Variance calculated correctly (counted minus system).
Variance within/outside tolerance correctly flagged.
Entry routed for approval where required.

Core Business Scenario

Enter Cycle Count

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 Cycle Count business scenario. Jarvis AI can extend this scenario by generating additional item, quantity, variance, tolerance 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 tolerance combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Control variations for the customer's environment — including variance-at-tolerance-boundary cases, since correctly enforced validation at the edge of a configured tolerance is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Enter Cycle Count business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid count-entry scenarios and edge cases such as invalid sequences, out-of-tolerance variances 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 tolerance combination, SyntraFlow maintains one core Enter Cycle Count scenario and allows Jarvis AI to generate quantity, variance, tolerance and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Enter Cycle Count 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 Cycle Counts.

Positive Scenarios

Enter a counted quantity that matches the system on-hand quantity exactly (zero variance)
Enter a counted quantity that differs from system quantity but remains within configured tolerance
Enter a counted quantity that differs from system quantity beyond configured tolerance, with the variance correctly flagged
Enter a recount against a sequence flagged for recount
Enter a counted quantity for a lot- or serial-controlled item

Negative Scenarios

Attempt to enter a count against an invalid or unassigned sequence reference
Enter a negative counted quantity
Submit a sequence without a required counted quantity entered
Attempt count entry as a counter not authorized for the sequence
Attempt a duplicate entry against a sequence already submitted
Attempt count entry after the cycle 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 tolerance combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Enter Cycle Count scenarios relevant to the customer's actual implementation.

Standard Library Definition

Cycle Count Name    ${CYCLE_COUNT_NAME}
Sequence Number     ${SEQUENCE_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 cycle counting
Subinventories / Locators
  Configured count locations
System Quantities
  Current on-hand quantities as of the count date
Tolerance Rules
  Configured tolerance thresholds by item/category
Lot/Serial
  Active lot and serial values for controlled items

Jarvis AI Generates

Scenario 01 — Item A + Zero Variance
Scenario 02 — Item B + Variance Within Tolerance
Scenario 03 — Item C + Variance Outside Tolerance
Scenario 04 — Item D + Recount Entry
Scenario 05 — Lot-Controlled Item + Lot Entry
Scenario 06 — Unauthorized User Attempts Count Entry
...

Enter Cycle Count 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 Cycle Count scenarios Jarvis can generate from this business scenario, spanning quantity, variance, tolerance 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 on-hand quantity exactly	Syntra Ready
VAR-002	Variance Within Tolerance	Positive/Tolerance	Counted quantity differs from system quantity but stays within configured tolerance	Syntra Ready
VAR-003	Variance Outside Tolerance	Positive/Variance/Tolerance	Counted quantity differs from system quantity beyond configured tolerance and is correctly flagged	Syntra Ready
VAR-004	Recount Entry	Positive	A second count entered against the same sequence after a recount is triggered	Syntra Ready
VAR-005	Lot-Controlled Entry	Positive	Counted quantity entered against a specific lot number	Syntra Ready
VAR-006	Serial-Controlled Entry	Positive	Counted quantity entered against specific serial numbers	Syntra Ready
VAR-007	Invalid Sequence Reference	Negative	Entry attempted against a sequence number that does not exist or is not assigned to the counter	Syntra Ready
VAR-008	Negative Counted Quantity	Negative	Counted quantity entered as a negative value	Syntra Ready
VAR-009	Missing Required Count Entry	Negative	Sequence submitted without a counted quantity entered	Syntra Ready
VAR-010	Unauthorized Counter	Negative	Entry attempted by a user not assigned to the count sequence	Syntra Ready
VAR-011	Duplicate Entry for Same Sequence	Negative	A second count entry attempted against a sequence already submitted	Syntra Ready
VAR-012	Entry After Count Window Closed	Negative	Entry attempted after the cycle count window has closed	Syntra Ready
VAR-013	Variance at Tolerance Boundary	Positive/Variance/Tolerance	Counted quantity produces a variance exactly at the configured tolerance boundary	Syntra Ready

Automatically Expand Positive and Negative Cycle Count Coverage

Positive Testing

Jarvis generates scenarios using item, quantity, variance and tolerance combinations expected to successfully record a cycle count entry and correctly classify the resulting variance in Oracle Fusion.

Valid Sequence + Counted Quantity + Correct Variance Calculation → Entry Recorded

Negative Testing

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

Invalid Sequence → Expected Sequence 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 cycle count	Count definition created	PASS
Invalid classification	Validation occurs	PASS
Invalid tolerance	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 Cycle Count scenarios and group them into reusable execution packs.

SCM Inventory Management Enter Cycle Count Regression Pack

Zero Variance Entry
Variance Within Tolerance
Variance Outside Tolerance
Recount Entry
Lot-Controlled Entry
Serial-Controlled Entry
Invalid Sequence Reference
Negative Counted Quantity
Duplicate Entry for Same Sequence
Unauthorized Counter

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

Once scheduled, SyntraFlow executes the selected Enter Cycle Count 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 Cycle Count 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 sequence 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 Cycle Count	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 Cycle Count scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Control 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 Cycle Count, 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 Sequence 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 System Quantity → Read Calculated Variance → Compare Against Configured Tolerance

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 Cycle Count failed — Likely category: EXPECTED_VALIDATION — Evidence: counted quantity variance exceeds configured tolerance — Recommended action: this is expected behavior; the entry correctly routes for adjustment approval. 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 Entry	Pass	—
Verify Variance Status and Routing	Pass	Pass

Related Cycle Count Tests

Enter Cycle Count is the second stage of the Cycle Counts cluster — explore the related sequence-generation, adjustment-approval and exception scenarios below.

Generate Count Sequences Approve Cycle Adjustment Cycle Count Exceptions

Turn This Standard Test into Your Oracle SCM Enter Cycle Count Regression Suite

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

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

Frequently Asked Questions

How is the variance calculated on an entered cycle count?

The variance is the difference between the physically counted quantity entered by the counter and the system on-hand quantity recorded in Oracle Fusion at the time of the count, calculated as counted quantity minus system quantity. This test validates that the displayed variance is calculated correctly for a range of counted-quantity scenarios.

What happens when a counted variance exceeds the configured tolerance?

When the variance falls outside the tolerance configured for the item or item category, Oracle Fusion flags the entry so that it can be routed for adjustment approval rather than being accepted automatically. This is expected, correctly enforced behavior, not a defect — the outcome this test confirms passes when that routing occurs correctly.

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 before the variance is treated as final. Exact recount rules depend on the customer's cycle count configuration.

How does security testing work for cycle count entry?

Access to enter a count against a given sequence 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 cycle 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.