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

Syntra Standard Oracle Test Library

Oracle Fusion Create Cycle Count Test Cases

Validate that a cycle count definition is created correctly in Oracle Fusion SCM Inventory Management using an ABC classification-based or schedule-based counting strategy, correct count frequency, subinventory scope where applicable and approval tolerance for an inventory organization.

Test ID	ORCL.SCM.INV.CC.CREATE
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 7 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 that a cycle count definition can be created in Oracle Fusion SCM Inventory Management for an inventory organization, using an ABC classification-based or schedule-based counting strategy, correct count frequency and approval tolerance, and that the resulting definition is available for cycle count sequence generation.

The scenario should confirm that:

the cycle count definition is created for the correct inventory organization
ABC classification or schedule-based counting strategy is correctly applied
count frequency is captured correctly for each ABC class or schedule
approval tolerance values are captured correctly
the subinventory scope, where specified, is correctly applied
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 cycle count definition in Oracle Fusion SCM Inventory Management TEST/UAT environments. It does not cover count sequence generation, entering physical count results or approving count adjustments, which are covered by the separate Generate Count Sequences, Enter Cycle Count and Approve Cycle Adjustment scenarios in the same Cycle Counts cluster.

When to Use This Test

Functional testing of cycle count definition creation for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of cycle count definition behavior after an Oracle quarterly update
UAT sign-off for inventory teams that routinely perform ABC-based or schedule-based cycle counting
Baseline case referenced by the Generate Count Sequences, Enter Cycle Count and Approve Cycle Adjustment scenarios within the same Cycle Counts cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during cycle count definition creation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Plan-to-Produce Cycle Counts Process

Navigate to Inventory

→

Create Cycle Count Definition

→

Select ABC/Schedule Strategy

→

Set Frequency

→

Set Approval Tolerance

→

Review

→

Save

Create Cycle Count is the entry point of the cycle count lifecycle within Plan-to-Produce Inventory Management. Once a cycle count definition is created, count sequences are typically generated, physical counts entered, and resulting adjustments approved — covered by the Generate Count Sequences, Enter Cycle Count and Approve Cycle Adjustment scenarios in this same cluster. Exact fields available, ABC class setup and validation depend on inventory organization configuration, item classification and customer-specific Oracle Fusion configuration.

Next Stage →

Generate Count Sequences

Preconditions

An inventory organization is configured in the target Oracle Fusion SCM environment.
Items are classified into ABC categories where an ABC classification-based counting strategy is used.
A cycle count workday calendar is configured for the inventory organization.
The test user has appropriate access to create cycle count definitions for the inventory organization.
The subinventories to be included in the count scope are configured and active.

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

Sample Test Data

Inventory Organization	${INVENTORY_ORGANIZATION}
Cycle Count Name	${CYCLE_COUNT_NAME}
Description	${COUNT_DEFINITION_DESCRIPTION}
Count Type	${COUNT_TYPE}
ABC Class	${ABC_CLASS}
Count Frequency	${COUNT_FREQUENCY}
Subinventory	${SUBINVENTORY}
Approval Tolerance	${APPROVAL_TOLERANCE}
Workday Calendar	${WORKDAY_CALENDAR}

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 cycle count definition — for example, ABC class fields typically apply to ABC classification-based strategies, while schedule fields typically apply to schedule-based strategies.

Test Steps

7 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 test user and navigate to the Inventory Management work area.	The Inventory Management work area opens successfully.
2	Navigate to Cycle Counts Open the Cycle Counts page to begin creating a new cycle count definition. ${INVENTORY_ORGANIZATION}	The cycle count definition creation page opens for the correct inventory organization.
3	Initiate Create Cycle Count Definition Initiate a new cycle count definition and enter a name and description. ${CYCLE_COUNT_NAME} / ${COUNT_DEFINITION_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 cycle count definition is opened with the entered name.
4	Define Organization and Scope Confirm the inventory organization and, where applicable, restrict the count scope to selected subinventories. ${INVENTORY_ORGANIZATION} / ${SUBINVENTORY}	The inventory organization and subinventory scope are accepted and reflected on the definition.
5	Configure ABC Classes or Schedule Strategy Select an ABC classification-based strategy and assign ABC classes and count frequencies, or select a schedule-based strategy and configure the count schedule and frequency. ${COUNT_TYPE} / ${ABC_CLASS} / ${COUNT_FREQUENCY} This single business step represents configuring either an ABC-based or schedule-based counting strategy, depending on the value selected for Count Type.	The ABC/schedule strategy, classes and frequencies are accepted without unexpected validation errors.
6	Set Approval Tolerances Enter the approval tolerance values that determine when a count variance requires approval. ${APPROVAL_TOLERANCE}	The approval tolerance values are accepted and reflected on the definition.
7	Review and Save the Cycle Count DefinitionBusiness assertion Review the cycle count definition header and configuration as calculated by Oracle Fusion, then save the definition for creation in the test environment. This is the primary business assertion for the scenario — a correctly created cycle count definition with accurate configuration is the expected pass condition, not merely a successful save.	Oracle Fusion successfully creates the cycle count definition without unexpected errors, and the reviewed definition reflects the entered name, organization, scope, ABC/schedule strategy, frequency and approval tolerance.

Expected Results

The cycle count definition is created for the correct inventory organization.
The ABC classification or schedule-based counting strategy is correctly applied.
Count frequency is correctly captured for each ABC class or schedule.
Approval tolerance values are correctly captured.
The subinventory scope, where specified, is correctly applied.
The definition is available for cycle count sequence generation.
The cycle count definition is visible and traceable for the test inventory organization.

Key Validation Checkpoints

Cycle count definition saved correctly.
ABC/schedule strategy correctly applied.
Definition available for sequence generation.

Core Business Scenario

Create 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 Create Cycle Count business scenario. Jarvis AI can extend this scenario by generating additional ABC classification, schedule, frequency, 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 ABC class, frequency, subinventory or tolerance combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Configuration variations for the customer's environment — including edge-case tolerance values, since correctly enforced validation at the edges of expected values is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Cycle Count business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid cycle count definitions and edge cases such as missing ABC classification, invalid frequency 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 ABC class, frequency, subinventory or tolerance combination, SyntraFlow maintains one core Create Cycle Count scenario and allows Jarvis AI to generate strategy, frequency, tolerance and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Create a standard ABC classification-based cycle count definition
Create a schedule-based cycle count definition
Create a cycle count definition with different count frequencies per ABC class
Create a cycle count definition scoped to a specific subinventory
Create a cycle count definition with configured approval tolerances

Negative Scenarios

Attempt to create a cycle count definition for an invalid inventory organization
Attempt to save an ABC-based definition without ABC classification assigned
Enter an invalid count frequency
Enter an invalid approval tolerance value
Attempt to create a cycle count definition using a duplicate name
Enter an invalid subinventory

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, ABC class, subinventory and tolerance combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Cycle Count scenarios relevant to the customer's actual implementation.

Standard Library Definition

Inventory Organization  ${INVENTORY_ORGANIZATION}
Cycle Count Name        ${CYCLE_COUNT_NAME}
Description             ${COUNT_DEFINITION_DESCRIPTION}
Count Type              ${COUNT_TYPE}
ABC Class               ${ABC_CLASS}
Count Frequency         ${COUNT_FREQUENCY}
Subinventory            ${SUBINVENTORY}
Approval Tolerance      ${APPROVAL_TOLERANCE}
Workday Calendar        ${WORKDAY_CALENDAR}

DataVault

Inventory Organizations
  Active inventory organizations eligible for cycle counting
ABC Classes
  Item ABC classification assignments
Subinventories
  Active subinventories per organization
Workday Calendars
  Configured cycle count workday calendars
Approval Tolerances
  Approved tolerance ranges by organization or class

Jarvis AI Generates

Scenario 01 — Org A + ABC-Based Strategy + Standard Frequencies
Scenario 02 — Org A + Schedule-Based Strategy
Scenario 03 — Org B + Subinventory-Scoped Definition
Scenario 04 — Org A + Tight Approval Tolerance
Scenario 05 — Missing ABC Classification
Scenario 06 — Unauthorized User Attempts Create Cycle Count
...

Create Cycle Count test data can include sensitive inventory categories such as item classification, valuation and location 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 Cycle Count scenarios Jarvis can generate from this business scenario, spanning strategy, frequency, subinventory and tolerance 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 ABC-Based Definition	Positive/Strategy	Cycle count definition created using an ABC classification-based strategy	Syntra Ready
VAR-002	Schedule-Based Definition	Positive/Strategy	Cycle count definition created using a schedule-based strategy	Syntra Ready
VAR-003	Different Frequencies per Class	Positive/Strategy	Definition created with distinct count frequencies assigned per ABC class	Syntra Ready
VAR-004	Subinventory-Scoped Definition	Positive	Definition created with count scope restricted to a specific subinventory	Syntra Ready
VAR-005	Approval Tolerance Configuration	Positive/Tolerance	Definition created with configured approval tolerance values	Syntra Ready
VAR-006	Invalid Inventory Organization	Negative	Selected inventory organization is invalid or inactive	Syntra Ready
VAR-007	Missing ABC Classification	Negative/Strategy	ABC-based definition attempted without ABC classification assigned to items	Syntra Ready
VAR-008	Invalid Count Frequency	Negative/Strategy	Count frequency entered does not exist or is invalid for the strategy	Syntra Ready
VAR-009	Invalid Approval Tolerance	Negative/Tolerance	Approval tolerance value entered is outside a valid range	Syntra Ready
VAR-010	Duplicate Cycle Count Name	Negative	Cycle count name entered already exists for the inventory organization	Syntra Ready
VAR-011	Invalid Subinventory	Negative	Selected subinventory is invalid or inactive	Syntra Ready

Automatically Expand Positive and Negative Cycle Count Coverage

Positive Testing

Jarvis generates scenarios using inventory organization, ABC class, frequency, subinventory and tolerance combinations expected to successfully create a cycle count definition in Oracle Fusion.

Valid Organization + ABC Classification Assigned + Valid Frequency + Valid Tolerance → Cycle Count Definition Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around ABC classification, frequency, tolerance and security.

Missing ABC Classification → Expected Classification Validation
Invalid Count Frequency → Expected Frequency Validation
Invalid Approval Tolerance → Expected Tolerance Validation
Duplicate Cycle Count Name → Expected Uniqueness 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 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 Create Cycle Count scenarios and group them into reusable execution packs.

SCM Inventory Management Create Cycle Count Regression Pack

Standard ABC-Based Definition
Schedule-Based Definition
Different Frequencies per Class
Subinventory-Scoped Definition
Approval Tolerance Configuration
Invalid Inventory Organization
Missing ABC Classification
Invalid Approval Tolerance
Duplicate Cycle Count Name
Security Restriction — Unauthorized Create Cycle Count

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

Once scheduled, SyntraFlow executes the selected Create 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 Create Cycle Count 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 cycle count 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 cycle count 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 Cycle Count 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 Cycle Count scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Configuration 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 Cycle Count, 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

Configure ABC Classes or Schedule Strategy

May internally include

Open Strategy Selector → Choose ABC-based or Schedule-based → Assign Classes/Schedule → Enter Frequency per Class → Confirm

Business Step

Review and Save the Cycle Count Definition

May internally include

Open Definition Preview → Read Calculated Header/Strategy 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 cycle count 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 Cycle Count failed — Likely category: CONFIGURATION_ERROR — Evidence: items in the selected subinventory lack ABC classification — Recommended action: complete ABC classification or switch to a schedule-based strategy. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Configure ABC Classes or Schedule Strategy	Pass	—
Set Approval Tolerances	Pass	—
Review and Save the Cycle Count Definition	Pass	Pass

Related Cycle Count Tests

Create Cycle Count is the entry point of the Cycle Counts cluster — explore the related sequence generation, count entry and adjustment approval scenarios below.

Generate Count Sequences Enter Cycle Count Approve Cycle Adjustment

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

Start with the Syntra Standard Create Cycle Count test, use DataVault to provide environment-specific test data, let Jarvis generate additional strategy, frequency, 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

What does ABC classification mean for cycle counting?

ABC classification groups inventory items into classes — typically A, B and C — based on value, usage or another significance criterion, so that higher-value or higher-usage items can be counted more frequently than lower-value items. This test validates that ABC classes and their associated count frequencies are correctly captured on the cycle count definition.

What is the difference between schedule-based and ABC-based cycle counting?

An ABC classification-based strategy counts items according to their assigned ABC class and a frequency set per class, so higher-value classes are counted more often. A schedule-based strategy instead counts items according to a defined calendar schedule independent of ABC class. This scenario covers both strategies where supported by the customer's Oracle Fusion configuration.

How do approval tolerances work on a cycle count definition?

Approval tolerance values determine the acceptable variance between the system on-hand quantity and the physical count result before an adjustment requires approval. This test validates that the tolerance values entered on the definition are correctly captured; the downstream approval behavior itself is covered by the Approve Cycle Adjustment scenario.

How does security testing work for cycle count definition creation?

Access to create a cycle count 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 real inventory counts or real inventory movements in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not perform real physical inventory counts, create real inventory adjustments or produce real inventory movements in a production environment.