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

Syntra Standard Oracle Test Library

Oracle Fusion Update Supplier Test Cases

Validate that permitted updates to an active Oracle Fusion supplier's master information — address, contact, tax registration, payment terms, site attributes and communication method — are accepted, correctly applied, and retained without disturbing unrelated supplier data or, where available, the record's change history.

Test ID	ORCL.P2P.PROC.SUPPLIER.UPDATE
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 19 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate permitted updates to supplier master information within Oracle Fusion Procurement — confirming that changes such as address, contact, tax registration, payment terms, site attributes and communication method are accepted, correctly applied, and retained without disturbing unrelated supplier data.

The scenario should confirm that:

an active supplier record can be opened for update by an authorized user
the target attribute or attributes accept a valid new value without unexpected errors
the supplier record reflects the updated values accurately once saved
change history or audit trail is preserved where available in the customer's Oracle Fusion configuration
unrelated supplier data remains unchanged by the update
unauthorized or restricted update attempts are correctly prevented

This scenario covers updating an existing, active supplier record within Oracle Fusion Procurement TEST/UAT environments. It does not cover initial supplier creation, which is covered by the separate Create Supplier scenario, supplier bank account maintenance, covered by the separate Supplier Bank Account scenario, or supplier inactivation, covered by the separate Supplier Inactivation scenario. Individual attribute-level updates such as address, contact or tax info are represented as data-driven variations of this same test rather than as separate published test pages.

When to Use This Test

Functional testing of allowed supplier attribute updates for a new Oracle Fusion Procurement implementation
Regression testing of supplier update and audit-history behavior after an Oracle quarterly update
UAT sign-off for supplier administrators who routinely maintain supplier master data
Baseline case referenced by the create, bank account and inactivation scenarios within the same supplier lifecycle

Where This Test Fits in the Supplier Lifecycle

Create

→

Update

→

Bank Account

→

Inactivate

Update Supplier applies to a supplier record that already exists and is active, adjusting one or more attribute values while keeping the supplier record itself intact. It does not cover initial creation, bank account maintenance or inactivation, which are covered by other stages of the same supplier lifecycle. Exact allowed changes, restricted attributes and audit-history behavior depend on supplier status, customer configuration and security setup.

← Previous Stage

Create Supplier

Next Stage →

Supplier Bank Account

Preconditions

A supplier record exists and is active.
The user performing the update has the appropriate update privileges.
The new attribute values — address, contact, tax info, payment terms, site attributes or communication method — are valid and configured for the test tenant.
The test user has permission to open and edit supplier records in Oracle Fusion Procurement.

Exact updatable attributes, restricted fields and validation messages may vary by Oracle Fusion implementation, supplier configuration and security setup.

Sample Test Data

Supplier	${SUPPLIER}
Supplier Site	${SUPPLIER_SITE}
New Address	${NEW_ADDRESS}
New Contact	${NEW_CONTACT}
New Tax Registration Info	${NEW_TAX_INFO}
New Payment Terms	${NEW_PAYMENT_TERMS}
Communication Method	${COMMUNICATION_METHOD}
Attribute Changed	${ATTRIBUTE_CHANGED}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Only the attribute or attributes relevant to a given variation are typically changed in a single execution.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~19 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 using an authorized Procurement test user.	Oracle Fusion signs the user in successfully and the home page loads.
2	Navigate to the Supplier Record Navigate to the Suppliers work area and search for the active supplier record to be updated. ${SUPPLIER} This single business step replaces multiple technical actions such as opening supplier search, entering the supplier name or number, and selecting the result.	The correct supplier record is located and its current attribute values are displayed.
3	Open the Supplier Record for Edit Select the option to open the located supplier record for edit.	The supplier record opens in an editable state showing its current attribute values.
4	Modify the Target Attribute(s) Update the attribute or attributes relevant to this variation — address, contact, tax info, payment terms, site attributes or communication method. ${NEW_ADDRESS} / ${NEW_CONTACT} / ${NEW_TAX_INFO} / ${NEW_PAYMENT_TERMS} / ${COMMUNICATION_METHOD}	The new value is accepted without unexpected validation errors.
5	Review Changed Values Review the changed attribute values before saving. Reviewing the change before saving lets the tester catch an incorrect value entry before it is committed.	The changed values shown match the intended update for this variation.
6	Save the Updated Supplier Record Submit and save the updated supplier record in the test environment.	Oracle Fusion successfully saves the updated supplier record without unexpected errors.
7	Verify New Values RetainedBusiness assertion Reopen or refresh the supplier record and confirm the updated attribute values are present. This is a primary business assertion for the scenario — retained values with preserved history is the expected pass condition, not merely a successful save.	The supplier record reflects the updated values accurately, and change history is preserved where available.
8	Verify Unrelated Fields UnchangedBusiness assertion Review the remaining supplier attributes that were not part of this update.	Unrelated supplier data remains unchanged by the update.

Expected Results

The target attribute or attributes accept the new value without unexpected errors.
The supplier record is updated and the revised values are reflected accurately once saved.
Change history or audit trail is preserved where available in the customer's Oracle Fusion configuration.
Unrelated supplier data remains unchanged by the update.
Restricted attribute changes are correctly prevented where configured.
Unauthorized update attempts are correctly prevented.

Key Validation Checkpoints

New values are retained on the supplier record.
History or audit trail is preserved where available.
Unrelated supplier data is unchanged.

Core Business Scenario

Update 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 update-supplier business scenario. Jarvis AI can extend this scenario by generating additional field, status 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 attribute a supplier record can change, or for every status and permission combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable update-supplier business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Suppliers, Addresses, Contacts, Tax Registrations and Payment Terms.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant field, status and security variations.

Positive + Negative + Boundary + Security Test Variations

Valid attribute-change scenarios alongside edge cases such as inactive suppliers, invalid values and unauthorized users.

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 attribute a supplier record can change, SyntraFlow maintains one core update-supplier scenario and allows Jarvis AI to generate field-driven and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Update supplier address
Update supplier contact
Update supplier tax info
Update supplier payment terms
Update supplier site attributes
Update supplier communication method

Negative Scenarios

Unauthorized user attempts update
Invalid tax data entered
Invalid address entered
Inactive supplier
Restricted attribute change attempted

These are representative examples only. Negative-scenario behavior and available attribute updates 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, address, contact and tax configuration in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct update-supplier scenarios relevant to the customer's actual implementation.

Standard Library Definition

Supplier                  ${SUPPLIER}
Supplier Site              ${SUPPLIER_SITE}
New Address                ${NEW_ADDRESS}
New Contact                ${NEW_CONTACT}
New Tax Registration Info  ${NEW_TAX_INFO}
New Payment Terms          ${NEW_PAYMENT_TERMS}
Communication Method       ${COMMUNICATION_METHOD}
Attribute Changed          ${ATTRIBUTE_CHANGED}

DataVault

Suppliers
  Active suppliers eligible for update
Addresses
  Valid address formats per country
Contacts
  Configured contact roles per supplier
Tax Registrations
  Valid tax registration formats per jurisdiction
Payment Terms
  Valid term codes per supplier agreement
Security Roles
  Update privileges by persona

Jarvis AI Generates

Scenario 01 — SUPP-2001 + Update Address
Scenario 02 — SUPP-2001 + Update Payment Terms
Scenario 03 — SUPP-3002 + Update Tax Registration Info
Scenario 04 — SUPP-3002 + Update Communication Method
Scenario 05 — Invalid Tax Data Entered
Scenario 06 — Unauthorized User Attempts Update
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific dimensions such as supplier, address, contact and tax data remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of update-supplier scenarios Jarvis can generate from this business scenario, spanning field and security conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Update Supplier Address	Positive/Field	Address updated to a new valid value	Syntra Ready
VAR-002	Update Supplier Contact	Positive/Field	Contact updated to a new valid value	Syntra Ready
VAR-003	Update Supplier Tax Registration Info	Positive/Field	Tax registration info updated to a new valid value	Syntra Ready
VAR-004	Update Supplier Payment Terms	Positive/Field	Payment terms updated to a new valid term code	Syntra Ready
VAR-005	Update Supplier Site Attributes	Positive/Field	Site-level attributes updated to new valid values	Syntra Ready
VAR-006	Update Supplier Communication Method	Positive/Field	Communication method updated to a new valid option	Syntra Ready
VAR-007	Update Multiple Attributes in a Single Change	Positive/Field	Two or more attributes updated together in one save	Syntra Ready
VAR-008	Update Supplier Site Address Independently	Positive/Field	Site address updated without changing the supplier-level address	Syntra Ready
VAR-009	Unauthorized User Attempts Update	Negative/Security	A user without update privileges attempts to modify the supplier record	Syntra Ready
VAR-010	Invalid Tax Data Entered	Negative/Field	New tax registration value entered is not a valid format	Syntra Ready
VAR-011	Invalid Address Entered	Negative/Field	New address value entered is incomplete or invalid	Syntra Ready
VAR-012	Inactive Supplier	Negative/Field	Update attempted on a supplier record that is not active	Syntra Ready
VAR-013	Restricted Attribute Change Attempted	Negative/Security	A user attempts to change an attribute restricted to a different role	Syntra Ready
VAR-014	Duplicate Tax Registration Number Entered	Negative/Field	New tax registration number duplicates an existing supplier's registration	Syntra Ready

Automatically Expand Positive and Negative Update Supplier Coverage

Positive Testing

Jarvis generates scenarios using attribute values and supplier status expected to successfully update an active supplier record while preserving unrelated data and change history where available.

Active Supplier + Valid New Payment Terms → Update Saved and Values Retained

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around supplier status, attribute values and user authorization.

Unauthorized User → Expected Security Validation
Invalid Tax Data → Expected Tax Validation
Invalid Address → Expected Address Validation
Inactive Supplier → Expected Status 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 update-supplier scenarios and group them into reusable execution packs.

Update Supplier Regression Pack

Update Supplier Address
Update Supplier Contact
Update Supplier Tax Registration Info
Update Supplier Payment Terms
Update Supplier Site Attributes
Update Supplier Communication Method
Update Multiple Attributes in a Single Change
Invalid Tax Data Entered
Inactive Supplier
Unauthorized User Attempts Update

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

Once scheduled, SyntraFlow executes the selected update-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	Update Supplier Regression Pack
Schedule	Quarterly Update Regression
Tests	14 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

Update privileges for an existing supplier record are typically restricted by role. Jarvis can generate persona-based variations to confirm that only authorized users can update a supplier, and that unauthorized attempts are correctly prevented rather than silently allowed.

Persona	Action	Expected	Syntra Result
Procurement Specialist	Update Supplier	Allowed	PASS
Unauthorized User	Attempts Update	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 update-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, 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 — Update Supplier, 8 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

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

Navigate to the Supplier Record

May internally include

Open Supplier Search → Enter Supplier Name/Number → Search → Select Supplier → Confirm

Business Step

Verify New Values Retained

May internally include

Reopen Supplier Record → Read Updated Attribute → Compare Against Expected Value → Check Change History

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 updated values were retained or that unrelated data was left unchanged — 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
Modify the Target Attribute(s)	Pass	—
Save the Updated Supplier Record	Pass	—
Verify New Values Retained	Pass	Pass

Related Supplier Tests

Update Supplier applies to a supplier record that already exists within the same supplier lifecycle — explore the related create, bank account and inactivation scenarios below.

Create Supplier Supplier Bank Account Supplier Inactivation

Turn This Standard Test into Your Oracle Supplier Regression Suite

Start with the Syntra Standard update-supplier test, use DataVault to provide environment-specific test data, let Jarvis generate additional field and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore 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

Suppliers Test Library Procurement Test Library SCM Test Library Oracle ERP Testing Tool Test Library Syntra DataVault

Frequently Asked Questions

What supplier attributes are typically updatable in Oracle Fusion?

Depending on customer configuration and security setup, commonly updatable attributes include address, contact details, tax registration information, payment terms, site attributes and communication method. Availability of each attribute depends on the customer's Oracle Fusion setup and the supplier's current status.

Is change history or an audit trail preserved when a supplier is updated?

Where the customer's Oracle Fusion configuration supports it, prior values may be retained in change history or audit logs. This test verifies that history is preserved where available, without assuming every environment retains the same level of detail.

Are some supplier attribute changes restricted?

Yes, certain attributes — such as tax registration or bank-related information — may be restricted to specific roles or governed by additional controls, depending on customer configuration. This test includes a variation for a restricted attribute change to confirm the restriction is correctly enforced.

How is unauthorized-user testing approached for supplier updates?

Jarvis AI can generate a security variation where a user without update privileges attempts to modify a supplier record. The expected outcome is that Oracle Fusion correctly prevents the change, which counts as a passed negative test — see the Security & Persona Variations table on this page.

How are individual attribute-level updates such as address or tax info handled?

They are represented as data-driven rows in the Example Test Variations table on this same page rather than as separate published test pages, keeping a single canonical URL for all update-supplier variations.