Oracle ERP Testing Tool > Test Library > SCM > Procurement > Suppliers

Syntra Standard Oracle Test Library

Oracle Fusion Create Supplier Test Cases

Validate that a new supplier is created correctly in Oracle Fusion SCM using valid organization, tax registration, address and business relationship data, resulting in a system-generated supplier number and an active status.

Test ID	ORCL.P2P.PROC.SUPPLIER.CREATE
Application	Oracle Fusion Cloud
Product	SCM / Procurement
Module	Procurement
Process	Suppliers
Business Flow	Procure-to-Pay
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 9 business-readable test steps; SyntraFlow's automation executes approximately 26 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a new supplier can be created in Oracle Fusion SCM using valid organization, tax registration, address and business relationship data, and that the resulting supplier record is created with correct header detail and an active status.

The scenario should confirm that:

the supplier is created with the correct organization name and supplier type
tax registration data is captured correctly for the selected country
address data is captured correctly
the business relationship, payment terms and currency are correctly assigned
the supplier receives a system-generated supplier number and correct active status
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 single supplier record in Oracle Fusion SCM Procurement TEST/UAT environments, whether entered directly or through a supplier registration process. It does not cover supplier site creation, subsequent updates, or supplier qualification, which are covered by the separate Create Supplier Site, Update Supplier and Supplier Qualification scenarios in the same Suppliers cluster.

When to Use This Test

Functional testing of supplier creation for a new Oracle Fusion SCM Procurement implementation
Regression testing of supplier creation behavior after an Oracle quarterly update
UAT sign-off for procurement specialists who routinely onboard new suppliers
Baseline case referenced by the Create Supplier Site, Update Supplier and Supplier Qualification scenarios within the same Suppliers cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during supplier creation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Procure-to-Pay Suppliers Process

Navigate to Suppliers

→

Create Supplier

→

Enter Organization/Tax Data

→

Enter Address

→

Enter Business Relationship

→

Review

Create Supplier is the entry point of the Suppliers scenario family within Procure-to-Pay. Once a supplier is created, a supplier site is typically added, and the supplier record may subsequently be updated or qualified — covered by the Create Supplier Site, Update Supplier and Supplier Qualification scenarios in this same cluster. Exact fields available, approval routing and validation depend on supplier registration configuration, tax setup and customer-specific Oracle Fusion configuration.

Next Stage →

Create Supplier Site

Preconditions

The test user has appropriate access and privileges to create a supplier record in the target Oracle Fusion SCM environment.
Tax registration data required for the selected country is available and valid.
Address and country configuration — address styles and geographies — is in place in Oracle Fusion.
The business relationship type(s) applicable to the supplier are configured.
Payment terms and currency to be used on the supplier record are configured and active.

Exact field availability, mandatory fields, tax registration format and validation messages may vary by Oracle Fusion implementation, supplier registration configuration and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Supplier Name	${SUPPLIER_NAME}
Supplier Type	${SUPPLIER_TYPE}
Tax Registration ID	${TAX_ID}
Tax Country	${COUNTRY}
Address Line 1	${ADDRESS}
City	${CITY}
Country	${COUNTRY}
Payment Terms	${PAYMENT_TERMS}
Business Relationship	${BUSINESS_RELATIONSHIP}
Currency	${CURRENCY}

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 supplier — for example, tax registration format and mandatory address fields vary by country.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Procurement Sign in to Oracle Fusion using an authorised procurement test user and navigate to the Procurement work area.	The Procurement work area opens successfully.
2	Navigate to Suppliers Open the Suppliers page to begin creating a new supplier.	The supplier creation page opens.
3	Create New Supplier Initiate a new supplier record for the test organization. ${SUPPLIER_NAME} This single business step replaces multiple technical actions such as opening the create page and confirming the supplier registration mode.	A new, unsaved supplier record is opened.
4	Enter Organization and Tax Details Enter the supplier name, supplier type and tax registration details for the selected country. ${SUPPLIER_NAME} / ${SUPPLIER_TYPE} / ${TAX_ID} / ${COUNTRY}	Organization and tax data are accepted without unexpected validation errors.
5	Enter Address Information Enter the supplier address, including address line, city and country. ${ADDRESS} / ${CITY} / ${COUNTRY}	The address is accepted and reflected on the supplier record.
6	Select Business Relationship Select the business relationship, payment terms and currency applicable to the supplier. ${BUSINESS_RELATIONSHIP} / ${PAYMENT_TERMS} / ${CURRENCY}	The business relationship, payment terms and currency are accepted and reflected on the supplier record.
7	Review Supplier Data Review the organization, tax, address and business relationship data as entered before saving. Reviewing the supplier record before saving lets the tester catch an incorrect field entry before the record is created.	The reviewed supplier record reflects the entered organization, tax, address and business relationship data.
8	Save the Supplier Save the supplier record for creation in the test environment.	Oracle Fusion successfully processes the supplier without unexpected errors.
9	Verify Supplier Number and Active StatusBusiness assertion Reopen or refresh the supplier record and confirm the generated supplier number and active status. This is the primary business assertion for the scenario — a correctly created, active supplier record with accurate organization, tax, address and business relationship data is the expected pass condition, not merely a successful save.	A supplier number is generated, the supplier status is Active, and organization, tax, address and business relationship data match the entered data.

Expected Results

The supplier is created with the correct organization name and supplier type.
A system-generated supplier number is assigned.
Tax registration data is correct for the selected country.
Address data is correct.
Business relationship, payment terms and currency are correct.
The supplier status correctly reflects a newly created, active supplier record.
The supplier is visible and traceable for the test procurement specialist.

Key Validation Checkpoints

Supplier created.
Supplier number generated.
Status active.
Core data retained.

Core Business Scenario

Create Supplier

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 Supplier business scenario. Jarvis AI can extend this scenario by generating additional supplier type, country, tax, address, business relationship 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 supplier type, country, tax or business relationship combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment, since correctly enforced validation around duplicate suppliers, tax formats and restricted access is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Supplier business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Supplier Types, Countries, Tax Registrations, Addresses and Business Relationships.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant supplier type, country, tax and security variations.

Positive + Negative Test Variations

Valid supplier scenarios and edge cases such as duplicate suppliers, invalid tax IDs 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 supplier type, country, tax detail, address or business relationship combination, SyntraFlow maintains one core Create Supplier scenario and allows Jarvis AI to generate type, country, tax and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Supplier 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 Procurement Suppliers.

Positive Scenarios

Create a standard supplier with complete organization, tax and address data
Create suppliers with different supplier types
Create suppliers in different countries
Create suppliers with different tax registration details
Create suppliers with different payment terms
Create a supplier with multiple addresses
Create suppliers with different business relationships

Negative Scenarios

Attempt to create a duplicate supplier
Attempt to save without a supplier name
Enter an invalid tax registration ID
Enter an invalid country or address combination
Attempt to save with missing required attributes
Attempt creation under a security restriction preventing access

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 supplier type, country, tax registration, address and business relationship combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Supplier scenarios relevant to the customer's actual implementation.

Standard Library Definition

Supplier Name          ${SUPPLIER_NAME}
Supplier Type           ${SUPPLIER_TYPE}
Tax Registration ID     ${TAX_ID}
Tax Country             ${COUNTRY}
Address Line 1          ${ADDRESS}
City                    ${CITY}
Country                 ${COUNTRY}
Payment Terms           ${PAYMENT_TERMS}
Business Relationship   ${BUSINESS_RELATIONSHIP}
Currency                ${CURRENCY}

DataVault

Supplier Types
  Configured supplier type values
Countries / Tax Registrations
  Valid country and tax ID formats
Addresses
  Configured address styles and geographies
Payment Terms
  Configured payment terms codes
Business Relationships
  Configured business relationship types
Currencies
  Configured transaction currencies

Jarvis AI Generates

Scenario 01 — Standard Supplier + Spend Authorized
Scenario 02 — Different Supplier Type + Prospective Relationship
Scenario 03 — Different Country + Tax Registration
Scenario 04 — Supplier with Multiple Addresses
Scenario 05 — Duplicate Supplier Attempt
Scenario 06 — Unauthorized User Attempts Create Supplier
...

Create Supplier test data can include sensitive procurement categories such as tax registration and organization information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific supplier 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 Supplier scenarios Jarvis can generate from this business scenario, spanning supplier type, country, tax and terms 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 Supplier	Positive	Supplier created with complete organization, tax and address data	Syntra Ready
VAR-002	Different Supplier Types	Positive	Supplier created using an alternate configured supplier type	Syntra Ready
VAR-003	Different Countries	Positive/Country	Supplier created for a country other than the default	Syntra Ready
VAR-004	Different Tax Registration Details	Positive/Tax	Supplier created with an alternate valid tax registration number and format	Syntra Ready
VAR-005	Different Payment Terms	Positive/Terms	Supplier created with an alternate configured payment terms code	Syntra Ready
VAR-006	Multiple Addresses	Positive	Supplier created with more than one address	Syntra Ready
VAR-007	Different Business Relationships	Positive	Supplier created with an alternate business relationship, e.g. spend authorized vs. prospective	Syntra Ready
VAR-008	Different Currency	Positive	Supplier created with an alternate configured transaction currency	Syntra Ready
VAR-009	Foreign Supplier with VAT-Style Registration	Positive/Country/Tax	Supplier created for a country requiring VAT-style tax registration	Syntra Ready
VAR-010	Prospective Supplier	Positive	Supplier created with a Prospective business relationship pending qualification	Syntra Ready
VAR-011	Duplicate Supplier	Negative	Attempt to create a supplier that duplicates an existing active supplier	Syntra Ready
VAR-012	Missing Supplier Name	Negative	Attempt to save the supplier without a supplier name	Syntra Ready
VAR-013	Invalid Tax ID	Negative/Tax	Tax registration ID entered in an invalid format for the selected country	Syntra Ready
VAR-014	Invalid Country/Address	Negative/Country	Address entered with an invalid country or unsupported address combination	Syntra Ready
VAR-015	Missing Required Attributes	Negative	Supplier saved with one or more mandatory organization or business attributes blank	Syntra Ready
VAR-016	Invalid Payment Terms	Negative/Terms	Payment terms code entered is not configured for the environment	Syntra Ready
VAR-017	Security Restriction — Unauthorized Create Supplier	Negative	Requesting user lacks access to create a supplier record	Syntra Ready

Automatically Expand Positive and Negative Supplier Coverage

Positive Testing

Jarvis generates scenarios using supplier type, country, tax, address and business relationship combinations expected to successfully create a supplier in Oracle Fusion.

Valid Supplier Name + Valid Tax Registration + Valid Address + Active Business Relationship → Supplier Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around duplicate suppliers, tax ID format, address/country combinations and security.

Duplicate Supplier → Expected Duplicate Validation
Missing Supplier Name → Expected Mandatory Field Validation
Invalid Tax ID → Expected Tax Validation
Invalid Country/Address → Expected Address 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 supplier	Supplier created	PASS
Duplicate supplier	Duplicate validation occurs	PASS
Invalid tax ID	Tax 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 Supplier scenarios and group them into reusable execution packs.

SCM Procurement Create Supplier Regression Pack

Standard Supplier
Different Supplier Types
Different Countries
Different Tax Registration Details
Different Payment Terms
Multiple Addresses
Different Business Relationships
Duplicate Supplier
Invalid Tax ID
Security Restriction — Unauthorized Create Supplier

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

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

Persona	Action	Expected	Syntra Result
Procurement Specialist	Create Supplier	Allowed	PASS
Unauthorized User	Attempts Create Supplier	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 Supplier scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary 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 Supplier, 9 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 Organization and Tax Details

May internally include

Open Organization Tab → Enter Supplier Type → Enter Tax Registration Number → Select Tax Country → Validate Tax Format → Confirm Organization Details

Business Step

Review Supplier Data

May internally include

Open Supplier Preview → Read Organization/Tax/Address/Business Relationship Data → Compare Against Entered Values

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 supplier 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 Supplier failed — Likely category: DATA_ERROR — Evidence: tax ID format is invalid for the selected country — Recommended action: correct the tax ID format and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Address Information	Pass	—
Save the Supplier	Pass	—
Verify Supplier Number and Active Status	Pass	Pass

Related Supplier Tests

Create Supplier is the entry point of the Suppliers cluster — explore the related site, update and qualification scenarios below.

Create Supplier Site Update Supplier Supplier Qualification

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

Start with the Syntra Standard Create Supplier test, use DataVault to provide environment-specific test data, let Jarvis generate additional type, country, tax and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Procurement Suppliers 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 Procurement Test Library Suppliers Test Library Syntra DataVault

Frequently Asked Questions

What does this test validate when creating a supplier?

This test validates that a supplier can be created in Oracle Fusion SCM with correct organization data, supplier type, tax registration details, address and business relationship, and that the supplier is assigned a system-generated supplier number with an active status.

How does this test guard against duplicate suppliers?

One of the negative variations Jarvis can generate attempts to create a supplier that duplicates an existing active supplier, confirming that Oracle Fusion's duplicate-supplier validation is correctly enforced rather than allowing a second record to be created.

Do tax registration requirements vary by country?

Yes. Tax registration ID format and mandatory tax fields vary by the country selected on the supplier record and by customer-specific tax configuration. This scenario is designed to be exercised across different countries using DataVault test data rather than a single fixed tax format.

Do all the listed positive and negative variations need separate test library pages?

No. Rather than maintaining a separate public page for every supplier type, country, tax detail or business relationship combination, SyntraFlow maintains this one core Create Supplier scenario and uses Jarvis AI to generate the underlying variations from customer-specific DataVault test data. This page remains the canonical reference for all of them.

Does this test create real suppliers or real spend in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not create real suppliers, real supplier onboarding transactions or real spend in a production environment.