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

Syntra Standard Oracle Test Library

Oracle Fusion Create Supplier Site Test Cases

Validate creation of a supplier site in Oracle Fusion Procurement using valid parent supplier, Business Unit, site type, address and payment terms data, and confirm the resulting site record is correctly associated with the supplier and enabled for the right Business Unit(s).

Test ID	ORCL.P2P.PROC.SUPPLIER.SITE.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 8 business-readable test steps; SyntraFlow's automation executes approximately 24 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates that Oracle Fusion Procurement can create a supplier site using a valid parent supplier, Business Unit, site type, address and payment terms.

The scenario should confirm that:

the new site is created against the correct, active parent supplier
the site is enabled for use by the correct Business Unit(s)
the site type (purchasing, pay, or both) is correctly applied
the address and payment terms entered for the site are accepted and retained
Oracle Fusion creates the site record and returns a retrievable site identifier
the resulting site is available for subsequent supplier maintenance, bank account and transaction scenarios

This scenario validates the initial creation of a supplier site tied to an existing supplier. Creating the parent supplier itself, updating an existing site and maintaining a supplier bank account are covered by separate test scenarios.

When to Use This Test

Functional testing of supplier site creation for a new Oracle Fusion Procurement implementation
Regression testing of supplier site creation after an Oracle quarterly update affecting Procurement
UAT sign-off for supplier onboarding and Business Unit assignment controls before go-live
Baseline case referenced by supplier update, bank account and downstream Procure-to-Pay transaction scenarios

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

Create Supplier

→

Create Supplier Site

→

Assign Business Unit Usage

→

Update Supplier

→

Supplier Bank Account

This test covers adding a site to an existing supplier and confirming the resulting site record, supplier association and Business Unit usage. It depends on the parent supplier already existing and is a prerequisite for later site updates, bank account setup and transactions processed against that site.

Preconditions

A parent supplier already exists in Oracle Fusion and is in an active status.
The target Business Unit is configured and available for supplier site usage assignment.
Valid address data (country, address lines, city, postal code) is available for the site.
Payment terms are configured and available for selection where required.
The test user has the appropriate Procurement role and access to maintain supplier sites.

Exact preconditions and field requirements vary by Oracle Fusion implementation, Business Unit configuration and supplier setup rules.

Sample Test Data

Supplier	${SUPPLIER}
Site Name	${SITE_NAME}
Business Unit	${BUSINESS_UNIT}
Site Type	${SITE_TYPE}
Address	${ADDRESS}
Payment Terms	${PAYMENT_TERMS}
Site Purpose (Purchasing / Pay)	${SITE_PURPOSE}
Primary Pay Site Flag	${PRIMARY_PAY_SITE_FLAG}

Sample values are illustrative placeholders only. Replace them with valid supplier, Business Unit and address data from the target Oracle Fusion TEST/UAT environment; not every field applies to every site type or customer configuration, and no real supplier data should be used in non-production testing.

Test Steps

8 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 to Oracle Fusion Sign in to Oracle Fusion Cloud with a user account that has Procurement supplier site maintenance access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Parent Supplier Navigate to the Suppliers work area and open the existing parent supplier record the new site will belong to. ${SUPPLIER}	The parent supplier record opens successfully and is confirmed active.
3	Initiate Add Site Start the Create Site action from within the parent supplier record.	The Create Site flow opens, ready for input.
4	Enter Site Name and Type Enter the site name and select the site type, such as purchasing, pay, or both. ${SITE_NAME} / ${SITE_TYPE}	The site name and type are accepted without validation errors.
5	Select Business Unit Usage Select the Business Unit(s) the site will be enabled for use by. ${BUSINESS_UNIT}	The selected Business Unit usage is accepted and applied to the site.
6	Enter Address Enter the site address details. ${ADDRESS}	The address is accepted without validation errors.
7	Review Site Details Review the entered site name, type, Business Unit usage, address and payment terms before saving. ${PAYMENT_TERMS}	All entered site details display correctly for review.
8	Save and Verify Site CreatedBusiness assertion Save the supplier site and retrieve the resulting site record. This is the main business assertion for the scenario — the test does not stop merely because the save action succeeded; the created site record must be retrievable with the correct supplier association and Business Unit usage.	The supplier site is created successfully, is correctly associated with the parent supplier and selected Business Unit(s), and displays an active status.

Expected Results

A supplier site is created successfully using valid parent supplier, Business Unit, site type, address and payment terms data.
The site is correctly associated with the parent supplier.
The site is correctly enabled for use by the selected Business Unit(s).
The address and payment terms are correctly retained on the site.
The site status reflects successful creation.
The site record is retrievable for subsequent update, bank account and transaction scenarios.

Key Validation Checkpoints

Supplier site created successfully.
Supplier association correct.
Business Unit usage correct.
Site status correct.

Core Business Scenario

Create Supplier Site

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 Site scenario. Jarvis AI can extend this scenario by generating additional Positive, Negative, Boundary and Security variations across Business Units, site types, addresses and payment terms using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate supplier site test for every Business Unit, site type and address combination. Jarvis uses the standard Create Supplier Site scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Open Supplier Site Setup

The Create Site action is opened from within an existing parent supplier record.

Enter Site Details

Site name, type, address and payment terms are entered.

Assign Business Unit Usage

The site is enabled for use by one or more Business Units.

Create Supplier Site

The transaction is submitted and Oracle Fusion creates the site record.

Confirm Site Record

Supplier association, Business Unit usage and status are confirmed.

Regression Pack

Selected site creation variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Rather than maintaining a separate test for every Business Unit, site type, address and payment terms combination, SyntraFlow maintains one core Create Supplier Site scenario and allows Jarvis AI to generate relevant Positive, Negative, Boundary and Security variations using the customer's available test data.

AI-Generated Test Variations

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

Purchasing site
Pay site
Site created for different Business Units
Multiple sites for the same supplier
Site with different addresses
Site with different payment terms

Negative Scenarios

Inactive parent supplier
Duplicate site
Invalid Business Unit
Invalid address
Missing mandatory site data

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, Business Unit setup and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely reflects the suppliers, Business Units and addresses configured in a real Oracle Fusion Procurement environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct supplier site scenarios relevant to the customer's actual implementation.

Standard Library Definition

Supplier                   ${SUPPLIER}
Site Name                  ${SITE_NAME}
Business Unit               ${BUSINESS_UNIT}
Site Type                   ${SITE_TYPE}
Address                     ${ADDRESS}
Payment Terms                ${PAYMENT_TERMS}
Site Purpose                 ${SITE_PURPOSE}
Primary Pay Site Flag         ${PRIMARY_PAY_SITE_FLAG}

DataVault

Suppliers
  Configured active suppliers eligible for site creation
Business Units
  Configured Business Units and site usage rules
Addresses
  Valid address formats by country
Payment Terms
  Configured payment terms values
Site Types
  Purchasing, pay and combined usage configurations

Jarvis AI Generates

Scenario 01 — Standard Purchasing Site
Scenario 02 — Standard Pay Site
Scenario 03 — Alternate Business Unit
Scenario 04 — Second Site, Same Supplier
Scenario 05 — Invalid Business Unit
Scenario 06 — Inactive Parent Supplier
...

Supplier site test scenarios can involve sensitive procurement data categories such as addresses, payment terms and Business Unit assignments. Where DataVault is connected, this data is masked and access-controlled rather than using real supplier records — see Syntra DataVault (/datavault/) for how customer procurement test data is protected.

Example Test Variations

Representative examples of Create Supplier Site scenarios Jarvis can generate from this business scenario, spanning site type, Business Unit and validation 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	Basic Purchasing Site	Positive/Site Type	Site created with purchasing usage only	Syntra Ready
VAR-002	Basic Pay Site	Positive/Site Type	Site created with pay usage only	Syntra Ready
VAR-003	Site for Alternate Business Unit	Positive/BU	Site created and enabled for an alternate Business Unit	Syntra Ready
VAR-004	Second Business Unit Assignment	Positive/BU	Existing site extended to a second Business Unit usage	Syntra Ready
VAR-005	Multiple Sites for Same Supplier	Positive	A second, independent site created for the same parent supplier	Syntra Ready
VAR-006	Alternate Site Address	Positive	Site created with an alternate valid address	Syntra Ready
VAR-007	Alternate Payment Terms	Positive	Site created with alternate configured payment terms	Syntra Ready
VAR-008	Combined Purchasing and Pay Site	Positive/Site Type	Site created with both purchasing and pay usage enabled	Syntra Ready
VAR-009	Inactive Parent Supplier	Negative	Parent supplier is inactive at the time of site creation	Syntra Ready
VAR-010	Duplicate Site Name	Negative	Site name duplicates an existing site for the same supplier	Syntra Ready
VAR-011	Invalid Business Unit	Negative/BU	Business Unit reference is invalid or not accessible	Syntra Ready
VAR-012	Invalid Address	Negative	Address data is incomplete or fails country-specific formatting rules	Syntra Ready
VAR-013	Missing Mandatory Site Data	Negative	A required site field, such as site name or site type, is left blank	Syntra Ready

Positive and Negative Supplier Site Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion Procurement successfully creates a supplier site when the parent supplier, Business Unit, site type, address and payment terms data are all valid.

Active Supplier + Valid Business Unit/Address → Supplier Site Created Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around supplier status, Business Unit, address and mandatory site data during site creation.

Inactive Supplier → Expected Supplier Status Validation
Duplicate Site → Expected Duplicate Validation
Invalid Business Unit → Expected Business Unit Validation
Missing Mandatory Data → Expected Required-Field Validation

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

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

Once scheduled, SyntraFlow executes the selected supplier site creation 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 Site Regression Pack
Schedule	Nightly Regression
Tests	13 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

Security & Persona Variations

Jarvis can generate the same Create Supplier Site transaction attempted by different personas to confirm that Oracle Fusion's role-based and data security correctly allows or restricts the action. Exact behavior depends on the customer's own security configuration.

Persona	Action	Expected	Syntra Result
Procurement Specialist	Create Supplier Site	Allowed	PASS
Unauthorized User	Attempts Create Site	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 Site 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, Negative, Boundary and Security 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 Site, 8 Business Steps

↓

DataVault — Customer-Specific Supplier/Site 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

Select Business Unit Usage

May internally include

Open Business Unit LOV → Select Business Unit → Confirm Usage → Apply

Business Step

Save and Verify Site Created

May internally include

Validate Form → Save Site → Poll Confirmation → Capture Site Identifier

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

Step	Action Status	Business Validation
Save Supplier Site	Pass	—
Enter Site Address	Pass	—
Verify Site Created and Associated to Supplier	Pass	Pass

Related Supplier Tests

Creating a supplier site depends on the parent supplier and feeds into later supplier maintenance and payment setup — explore the related supplier scenarios below.

Create Supplier Update Supplier Supplier Bank Account

Turn This Standard Test into Your Oracle Procurement Supplier Regression Suite

Start with the Syntra Standard Create Supplier Site test, use DataVault to provide environment-specific supplier, Business Unit and address data, let Jarvis generate additional Positive, Negative, Boundary and Security variations, and execute the resulting regression pack automatically with SyntraFlow.

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

Frequently Asked Questions

What is a supplier site, and how is it different from the supplier itself?

The supplier record represents the business entity Oracle Fusion transacts with, while a supplier site represents a specific location, address and Business Unit usage — for example a purchasing address or a remit-to address. A single supplier can have one or more sites, each independently enabled for purchasing, pay, or both.

What is the difference between a purchasing site and a pay site?

A purchasing site is enabled to receive purchase orders for a given Business Unit, while a pay site is enabled to receive payments and hold payment-related attributes such as payment terms and bank account references. A site can be configured as purchasing only, pay only, or both, depending on the customer's Oracle Fusion setup.

Can a single supplier have multiple sites in Oracle Fusion?

Yes. Oracle Fusion supports multiple sites per supplier, commonly used to represent different Business Units, addresses, or purchasing versus pay locations. This test covers creating one site; Jarvis can generate variations covering additional sites for the same supplier.

How does security testing work for this scenario?

Jarvis can generate variations that attempt the same site creation transaction as different personas — for example an authorized Procurement Specialist versus an unauthorized user — to confirm that Oracle Fusion's role-based and data security correctly allows or restricts the action. Results depend on the customer's own security configuration.

How does SyntraFlow help identify why a Create Supplier Site test failed?

SyntraFlow's execution evidence is organized into categories such as data, configuration, security, automation, application, environment and expected-validation issues, so a failure like "Create Supplier Site failed — Likely category: DATA_ERROR — Evidence: parent supplier is inactive — Recommended action: activate the parent supplier or select a different one" points a tester toward the likely cause. This is a diagnostic aid, not a conclusion — a failure should not be labeled an Oracle defect without supporting evidence from the execution trace.

Oracle Fusion Create Supplier Site Test Cases

Test Objective

When to Use This Test

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

Preconditions

Sample Test Data

Test Steps

Expected Results

Key Validation Checkpoints

Go Beyond the Standard Test with Jarvis AI

From Standard Test to Executed Regression Pack

AI-Generated Test Variations

Generated Using Your DataVault Test Data

Standard Library Definition

DataVault

Jarvis AI Generates

Example Test Variations

Positive and Negative Supplier Site Testing

Positive Testing

Negative Testing

Turn AI-Generated Variations into a Regression Pack

SCM Procurement Create Supplier Site Regression Pack

Run On-Demand or Schedule Automated Batch Execution

Review Results Across the Entire Test Pack

Security & Persona Variations

Understand Why a Test Failed

From Business Scenario to Execution Evidence

Meet Jarvis — SyntraFlow's AI Testing Engine

How SyntraFlow Automates This Test

Business Step → Underlying UI Actions

What SyntraFlow Captures Per Run

Action Status vs. Business Validation

Related Supplier Tests

Turn This Standard Test into Your Oracle Procurement Supplier Regression Suite

Use This Oracle Fusion Test Case

Download Test Case

Automate with SyntraFlow

Related Oracle Testing Resources

Frequently Asked Questions