Oracle ERP Testing Tool > Test Library > SCM > Product Management

Syntra Standard Oracle Test Library

Oracle Fusion Create Item Test Cases

Validate that standard, purchased, inventory, customer-orderable, manufacturing, lot-controlled and serial-controlled items can be created in Oracle Fusion SCM Product Management, without assuming a universal item class or template structure, and that the resulting item is correctly available to Procurement, Inventory, Order Management, Manufacturing and Planning.

Test ID	ORCL.SCM.PIM.ITEM.CREATE
Application	Oracle Fusion Cloud
Product	SCM
Module	Product Management
Process	Create Item
Business Flow	Item-to-Order
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 24 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that standard, purchased, inventory, customer-orderable, manufacturing, lot-controlled and serial-controlled items can be created in Oracle Fusion SCM Product Management using a valid item class or template, item number, description, unit of measure and category, without assuming a universal item class or template structure, and that the resulting item is created with correct attributes and controls.

The scenario should confirm that:

the item is created with the correct item class, template and controls as configured
lot and serial control settings are correctly applied where configured, including dual-control items where the configuration supports both
template-based attributes such as category, unit of measure and description are correctly defaulted or entered
the item is available and searchable in Product Management after creation
downstream modules such as Procurement, Inventory, Order Management, Manufacturing and Planning can reference the newly created item
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 items across the item classes and templates configured in the target Oracle Fusion SCM Product Management TEST/UAT environment. It does not cover updating an existing item, assigning an item to additional organizations, or maintaining item attributes after creation, which are covered by the separate Update Item, Item Organization Assignment and Item Attributes scenarios in the same Product Management cluster.

When to Use This Test

Functional testing of item creation for a new Oracle Fusion SCM Product Management implementation
Regression testing of item creation behavior after an Oracle quarterly update
UAT sign-off for product data managers who maintain the item master
Baseline case referenced by the Update Item, Item Organization Assignment and Item Attributes scenarios within the same Product Management cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during item creation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Product Management Item Lifecycle

Navigate to Product Management

→

Select Item Class/Template

→

Create Item

→

Enter Attributes

→

Configure Controls

→

Review

→

Submit

Create Item is the entry point of the Product Management scenario family and of the Item-to-Order business flow. Once an item is created, it is typically assigned to organizations, its attributes are maintained, and it is referenced by Procurement, Inventory, Order Management, Manufacturing and Planning — covered by the Update Item, Item Organization Assignment and Item Attributes scenarios in this same cluster. Exact fields available, defaulting behavior and validation depend on the item class, template and customer-specific Oracle Fusion configuration.

Next Stage →

Update Item

Preconditions

The test user has appropriate Product Data Manager or Item Administrator access to create items.
Required item classes and/or templates are configured and active in the target Oracle Fusion environment.
Required units of measure, categories and item classes referenced in test data are configured and active.
The organization(s) in which the item will be created are configured to allow item creation.
Item numbering configuration — manual or automatic — is understood for the target environment.

Exact field availability, mandatory fields and validation messages may vary by Oracle Fusion implementation, item class, template and customer-specific configuration. No single item class or template structure should be assumed to apply universally.

Sample Test Data

Item Number	${ITEM_NUMBER}
Item Class	${ITEM_CLASS}
Item Template	${ITEM_TEMPLATE}
UOM	${UOM}
Category	${CATEGORY}
Description	${DESCRIPTION}
Effective Date	${EFFECTIVE_DATE}
Lot Control	${LOT_CONTROL}
Serial Control	${SERIAL_CONTROL}

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 item class or template — for example, category may default from the template rather than requiring re-entry.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Product Management Sign in to Oracle Fusion using an authorised Product Management test user and navigate to the Product Management work area.	The Product Management work area opens successfully.
2	Select Item Class or Template Select the item class or item template to be used for the new item. ${ITEM_CLASS} / ${ITEM_TEMPLATE}	The item class or template is selected and its associated attributes are available for entry.
3	Enter Item Number Enter the item number for the new item, or confirm the system-generated number where automatic numbering is configured. ${ITEM_NUMBER}	The item number is accepted and reflected on the new item record.
4	Enter Description, UOM and Category Enter the item description, primary unit of measure and category for the item. ${DESCRIPTION} / ${UOM} / ${CATEGORY}	The description, UOM and category are accepted and reflected on the item record.
5	Configure Lot/Serial Control Where Applicable Where the item class or template supports it, configure lot control and/or serial control for the item. ${LOT_CONTROL} / ${SERIAL_CONTROL} Not every item class or template supports lot or serial control — this step applies only where the configuration allows it.	Lot and/or serial control settings are accepted and reflected on the item record.
6	Submit Item Review the item record and submit it for creation in the test environment. Reviewing the item before submission lets the tester catch an incorrect field entry before the item is created.	Oracle Fusion successfully processes the item without unexpected errors.
7	Verify Item Created and SearchableBusiness assertion Search for the newly created item in Product Management and confirm its attributes. This is the primary business assertion for the scenario — a correctly created and searchable item is the expected pass condition, not merely a successful save.	The item is found by search, and item class, template, controls, UOM and category match the entered data.

Expected Results

The item is created with the correct item class, template and controls as configured.
A system-generated or manually entered item number is correctly assigned.
Lot and/or serial control settings are correctly applied where configured.
Category, unit of measure and description are correctly captured or defaulted from the template.
Data and configuration validation errors are correctly enforced for invalid or missing input.
The newly created item is available and searchable in Product Management.

Key Validation Checkpoints

Item correctly created with the specified item class and controls.
Lot/serial control correctly applied per item setup.
Template attributes correctly defaulted.
Duplicate item numbers correctly blocked.
Missing or invalid required data correctly blocked.
Unauthorized creation correctly blocked.

Core Business Scenario

Create Item

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 Item business scenario. Jarvis AI can extend this scenario by generating additional item class, template, control 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 class, template or control combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including dual-control items where supported and unauthorized creation attempts, since correctly enforced validation and access control is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Item business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Item Classes, Templates, UOMs and Categories.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant item class, template, control and security variations.

Positive + Negative Test Variations

Valid item creation scenarios and edge cases such as duplicate item numbers, invalid templates 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 class, template, control or attribute combination, SyntraFlow maintains one core Create Item scenario and allows Jarvis AI to generate item class, template, control and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Item 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 Product Management.

Positive Scenarios

Create standard, purchased, inventory and customer-orderable items
Create manufacturing items enabled for production
Create lot-controlled items
Create serial-controlled items
Create dual-control items where the item class or template supports both lot and serial control
Create items using a template with category, unit of measure and description defaulted or entered
Create a future-dated item and create multiple items in a single batch operation

Negative Scenarios

Attempt to create an item with a duplicate item number
Attempt to create an item with a missing item number
Attempt to create an item with an invalid unit of measure
Attempt to create an item using an invalid or inactive template or item class
Attempt to create an item with a missing required attribute
Attempt unauthorized item creation without the required access

These are representative examples only. Negative-scenario behavior and available field combinations can depend on the customer's Oracle Fusion configuration, item classes, templates and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every item class, template, unit of measure and category combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Item scenarios relevant to the customer's actual implementation.

Standard Library Definition

Item Number      ${ITEM_NUMBER}
Item Class       ${ITEM_CLASS}
Item Template    ${ITEM_TEMPLATE}
UOM              ${UOM}
Category         ${CATEGORY}
Description      ${DESCRIPTION}
Effective Date   ${EFFECTIVE_DATE}
Lot Control      ${LOT_CONTROL}
Serial Control   ${SERIAL_CONTROL}

DataVault

Item Classes
  Active item classes and their supported controls
Templates
  Configured item templates and defaulted attributes
UOMs
  Active units of measure by item class
Categories
  Active item categories by catalog
Organizations
  Organizations enabled for item creation

Jarvis AI Generates

Scenario 01 — Standard Item, Item Class A
Scenario 02 — Manufacturing Item, Item Class B
Scenario 03 — Lot-Controlled Item Using Template X
Scenario 04 — Serial-Controlled Item Using Template Y
Scenario 05 — Duplicate Item Number
Scenario 06 — Unauthorized User Attempts Create Item
...

Create Item test data can include item, template and category information tied to product design and supply chain configuration. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific item and template data used in testing remain masked and synthetic within the customer's controlled SyntraFlow environment, protected according to DataVault's data masking policies. See /datavault/data-masking/ for details.

Example Test Variations

Representative examples of 22 individual Create Item test scenarios spanning item class variations, lot/serial control, templates and negative/security item-creation testing that 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
PIM-ITEM-001	Create Standard Item	Positive	Item created using item class ${ITEM_CLASS} with standard attributes and no special controls.	SyntraFlow Ready
PIM-ITEM-002	Create Purchased Item	Positive	Item ${ITEM_NUMBER} created as a purchased item enabled for procurement.	SyntraFlow Ready
PIM-ITEM-003	Create Inventory Item	Positive	Item ${ITEM_NUMBER} created as an inventory-enabled item for stock tracking.	SyntraFlow Ready
PIM-ITEM-004	Create Customer Orderable Item	Positive	Item ${ITEM_NUMBER} created and enabled as customer orderable for Order Management.	SyntraFlow Ready
PIM-ITEM-005	Create Manufacturing Item	Positive	Item ${ITEM_NUMBER} created as a manufacturing item enabled for production.	SyntraFlow Ready
PIM-ITEM-006	Create Lot-Controlled Item	Positive	Item ${ITEM_NUMBER} created with lot control set to ${LOT_CONTROL}.	SyntraFlow Ready
PIM-ITEM-007	Create Serial-Controlled Item	Positive	Item ${ITEM_NUMBER} created with serial control set to ${SERIAL_CONTROL}.	SyntraFlow Ready
PIM-ITEM-008	Create Dual-Control Item Where Supported	Positive	Item ${ITEM_NUMBER} created with both lot control ${LOT_CONTROL} and serial control ${SERIAL_CONTROL}, where the item class supports dual control.	SyntraFlow Ready
PIM-ITEM-009	Create Item Using Template	Positive	Item ${ITEM_NUMBER} created using item template ${ITEM_TEMPLATE}, with attributes defaulted from the template.	SyntraFlow Ready
PIM-ITEM-010	Create Item with Category	Positive	Item ${ITEM_NUMBER} created and assigned to category ${CATEGORY}.	SyntraFlow Ready
PIM-ITEM-011	Create Item with UOM	Positive	Item ${ITEM_NUMBER} created with primary unit of measure ${UOM}.	SyntraFlow Ready
PIM-ITEM-012	Create Item with Description	Positive	Item ${ITEM_NUMBER} created with description ${DESCRIPTION}.	SyntraFlow Ready
PIM-ITEM-013	Create Future-Dated Item	Positive	Item ${ITEM_NUMBER} created with an effective date of ${EFFECTIVE_DATE} in the future.	SyntraFlow Ready
PIM-ITEM-014	Create Multiple Items	Positive	Multiple items, including ${ITEM_NUMBER}, are created in a single batch operation.	SyntraFlow Ready
PIM-ITEM-015	Duplicate Item Number	Negative	Item creation is attempted using item number ${ITEM_NUMBER} that already exists in the item master.	SyntraFlow Ready
PIM-ITEM-016	Missing Item Number	Negative	Item creation is attempted without entering a value for ${ITEM_NUMBER}.	SyntraFlow Ready
PIM-ITEM-017	Invalid UOM	Negative	Item creation is attempted using a unit of measure ${UOM} that is not valid or configured.	SyntraFlow Ready
PIM-ITEM-018	Invalid Template	Negative	Item creation is attempted using item template ${ITEM_TEMPLATE} that does not exist or is inactive.	SyntraFlow Ready
PIM-ITEM-019	Invalid Item Class	Negative	Item creation is attempted using item class ${ITEM_CLASS} that is not valid or configured.	SyntraFlow Ready
PIM-ITEM-020	Missing Required Attribute	Negative	Item creation is attempted with a required attribute left blank on item ${ITEM_NUMBER}.	SyntraFlow Ready
PIM-ITEM-021	Unauthorized Item Creation	Negative/Security	An unauthorized user attempts to create item ${ITEM_NUMBER} without the required Product Data Manager access.	SyntraFlow Ready
PIM-ITEM-022	Verify Created Item Searchability	Positive	Previously created item ${ITEM_NUMBER} is searched for in Product Management to confirm it is correctly indexed and searchable.	SyntraFlow Ready

Automatically Expand Positive and Negative Item Creation Coverage

Positive Testing

Jarvis generates scenarios using item class, template, control, unit of measure and category combinations expected to successfully create an item in Oracle Fusion.

Valid Item Number + Valid Item Class + Valid UOM → Item Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around item number uniqueness, required attributes, configuration and security.

Duplicate Item Number → Expected Uniqueness Validation
Missing Item Number → Expected Required Field Validation
Invalid UOM → Expected UOM Validation
Invalid Template → Expected Template Validation
Invalid Item Class → Expected Item Class Validation
Unauthorized User → Expected Access Restriction

A negative product management scenario passes when Oracle correctly enforces the expected data, configuration or security rule

Scenario	Oracle Outcome	Test Result
Valid item data	Item created	PASS
Duplicate or missing item number	Validation occurs	PASS
Invalid attribute or template	Validation occurs	PASS
Unauthorized user	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Create Item scenarios and group them into reusable execution packs.

SCM Product Management Create Item Regression Pack

Create Standard Item
Create Manufacturing Item
Create Lot-Controlled Item
Create Serial-Controlled Item
Create Item Using Template
Create Future-Dated Item
Duplicate Item Number
Missing Item Number
Invalid Item Class
Security Restriction — Unauthorized Item Creation

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

Once scheduled, SyntraFlow executes the selected Create Item 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 Product Management Create Item Regression Pack
Schedule	Quarterly Update Regression
Tests	22 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 items is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that item-creation access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Product Data Manager	Create Item	Allowed	PASS
Item Administrator	Create Item Using Template	Allowed	PASS
Unauthorized User	Attempts to Create Item	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 Item scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative and Security 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 Item, 7 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative + Security 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

Select Item Class or Template

May internally include

Open Item Class Search → Enter Search Criteria → Select Item Class → Select Template → Confirm Template Attributes → Apply to New Item

Business Step

Configure Lot/Serial Control Where Applicable

May internally include

Open Item Attributes Tab → Navigate to Inventory Controls → Set Lot Control Flag → Set Serial Control Flag → Confirm Control Settings → Save Attributes

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 item 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: Item Creation Failed — Likely category: DATA_ERROR — Evidence: Item number ${ITEM_NUMBER} already exists — Recommendation: Use a unique item number or verify existing item record. A failure should never be labeled as an Oracle defect without eliminating data, configuration, security, automation and integration causes first.

Step	Action Status	Business Validation
Enter Item Number, Description, UOM and Category	Pass	—
Submit Item	Pass	—
Verify Item Created and Searchable	Pass	Pass

Related Product Management Tests

Create Item is the entry point of the Product Management cluster — explore the related item maintenance, organization assignment and attribute scenarios below.

Update Item Item Organization Assignment Item Attributes

Turn This Standard Test into Your Oracle SCM Create Item Regression Suite

Start with the Syntra Standard Create Item test, use DataVault to provide environment-specific test data, let Jarvis generate additional item class, template and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore SCM Product Management 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 Product Management Test Library Syntra DataVault DataVault Data Masking

Frequently Asked Questions

Is there a single universal item class or template used across all Oracle Fusion implementations?

No. Item classes, templates and the attributes they expose vary by Oracle Fusion Product Management configuration and customer setup. This scenario is designed to validate item creation as configured in the target environment rather than assuming a single universal item class or template structure.

How is lot and serial control tested for created items?

Where an item class or template supports lot and/or serial control, SyntraFlow can validate that the control settings — such as ${LOT_CONTROL} and ${SERIAL_CONTROL} — are correctly applied at item creation, including dual-control items where the configuration supports both.

Why does item master data matter to modules outside Product Management?

Item master data created here is referenced by Procurement, Inventory, Order Management, Manufacturing and Planning. An incorrectly created item — for example missing a required attribute or an incorrect unit of measure — can propagate downstream, so validating creation accuracy at the source reduces the risk of downstream data issues.

How is searchability of a newly created item validated?

Scenario PIM-ITEM-022 searches Product Management for the previously created item to confirm it is correctly indexed and returned by search, in addition to confirming the item record itself was saved with the expected attributes.

What do the failure intelligence categories mean when an item creation test fails?

SyntraFlow's evidence trail is designed to help classify a failure as DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — for example a duplicate item number is a DATA_ERROR. A failure should never be labeled as an Oracle defect without first eliminating data, configuration, security, automation and integration causes.

How is security tested for item creation?

Access to create items is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as a Product Data Manager, an Item Administrator and an unauthorized user — to confirm that item-creation access behaves as expected, without asserting a single universal Oracle security model.