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

Syntra Standard Oracle Test Library

Oracle Fusion Return to Supplier Test Cases

Validate return of eligible received goods to the supplier and confirm resulting receipt quantity and return history are correctly reflected.

Test ID	ORCL.P2P.PROC.RCV.RETURN
Application	Oracle Fusion Cloud
Product	SCM / Procurement
Module	Procurement
Process	Receiving
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 verify that an authorised Procurement user can return eligible received goods to the supplier in Oracle Fusion Receiving, and that the resulting receipt quantity and return history correctly reflect the return.

The scenario should confirm that:

the selected receipt has a returnable quantity for the item being returned
the return reason is accepted
the return quantity does not exceed the returnable or received quantity
the receipt's remaining quantity is updated to reflect the return
the return is recorded and visible in the receipt's transaction history
inventory or accounting impact of the return is reflected where applicable
the return remains traceable back to the original receipt and purchase order

This scenario does not claim that every downstream inventory, accounting or supplier-debit configuration is covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test scenarios.

When to Use This Test

Functional testing of Oracle Fusion Receiving return-to-supplier processing
Regression testing after an Oracle quarterly update
UAT sign-off for exception-driven and correction-related receiving events
Baseline case referenced by inspection and receipt correction scenarios that precede a return

Where This Test Fits in the Receiving Process

Goods Received

→

Inspect Receipt

→

Identify Return Need

→

Initiate Return

→

Enter Return Details

→

Submit Return

→

Receipt Quantity Updated

This test covers return of previously received goods to the supplier, and depends on a valid receipt with a returnable quantity already recorded in Oracle Fusion Receiving.

← Previous Stage

Correct Receipt

Preconditions

Oracle Fusion Procurement / Receiving is configured and available.
An eligible receipt exists with a returnable quantity for the item being returned.
Return reason lookup values required for the return are configured.
The test user has permission to process returns to supplier in Oracle Fusion Receiving.

Exact return eligibility rules, return reasons and field availability may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Supplier	${SUPPLIER}
PO Number	${PO_NUMBER}
Receipt Number	${RECEIPT_NUMBER}
Item	${ITEM}
Received Quantity	${RECEIVED_QUANTITY}
Return Quantity	${RETURN_QUANTITY}
Return Reason	${RETURN_REASON}
Return Date	${RETURN_DATE}

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.

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 Sign in to Oracle Fusion Procurement / Receiving as an authorized user.	The user is authenticated and Receiving is accessible.
2	Navigate to the Receipt Navigate to and locate the receipt eligible for return by supplier, PO number and receipt number. ${SUPPLIER} / ${PO_NUMBER} / ${RECEIPT_NUMBER} This single business step replaces multiple technical actions such as opening receipt search, entering search criteria, and opening the located result.	The correct receipt is located and its details, including returnable quantity, are displayed.
3	Initiate Return Initiate the return transaction on the selected receipt.	The return entry page opens for the selected receipt.
4	Select Item and Enter Return Quantity Select the item being returned and enter the return quantity. ${ITEM} / ${RETURN_QUANTITY}	The item and return quantity are accepted without unexpected validation errors.
5	Enter Return Reason Enter or select the return reason. ${RETURN_REASON}	The return reason is accepted.
6	Review Return Details Review the return details, including item, quantity and reason, before submission.	Return details are displayed correctly for review.
7	Submit Return Submit the return.	Oracle Fusion processes the return request without unexpected errors.
8	Verify Receipt Quantity Updated and Return History VisibleBusiness assertion Confirm that the receipt's remaining quantity is updated and that the return appears in the receipt's transaction history. This is the main business assertion for the scenario — the test does not stop merely because Submit was clicked successfully.	The receipt quantity reflects the return, the return is visible in return history, and inventory/accounting effect is correct where applicable.

Expected Results

An eligible return to supplier is processed successfully.
The return is correctly recorded against the originating receipt.
Return quantity and return reason are correctly retained on the transaction.
The receipt's remaining quantity is updated to reflect the return.
The return is visible in the receipt's transaction/return history.
Inventory or accounting impact of the return is reflected where applicable.
No unexpected save errors occur.
The return remains traceable to the original receipt and purchase order for audit purposes.

Key Validation Checkpoints

Return processed successfully.
Receipt quantity updated.
Return history visible.
Inventory/accounting effect correct where applicable.

Core Business Scenario

Return to 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 return-to-supplier business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same return test dozens of times simply to cover different combinations of item, quantity, reason and receipt status. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — suppliers, purchase orders, receipts, items and return reasons.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

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 dozens of near-duplicate copies of the same return test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Return to 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 Receiving.

Positive Scenarios

Full return of received quantity
Partial return of received quantity
Return with different return reasons
Return of different items on the same receipt
Return after inspection identifies non-conforming goods
Return processed before the receipt is invoiced, where applicable

Negative Scenarios

Attempt to return a quantity greater than the received quantity
Attempt to return against an invalid receipt
Attempt to return goods already fully returned
Invalid or missing return reason
Return attempted against a closed transaction
Unauthorized user attempts a return

These are representative examples only. Negative scenarios and expected behavior 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 often fails to represent the receipt and purchase order history of a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to create return variations relevant to the customer's actual implementation.

Standard Library Definition

Supplier          ${SUPPLIER}
PO Number         ${PO_NUMBER}
Receipt Number    ${RECEIPT_NUMBER}
Item              ${ITEM}
Received Quantity ${RECEIVED_QUANTITY}
Return Quantity   ${RETURN_QUANTITY}
Return Reason     ${RETURN_REASON}

DataVault

Receipts
  Receipt A — Fully Received, No Prior Return
  Receipt B — Partially Returned
  Receipt C — Already Fully Returned
  Receipt D — Closed Transaction
Items
  Item X, Item Y, Item Z
Return Reasons
  Damaged Goods, Wrong Item Shipped, Quality Rejection, Excess Quantity

Jarvis AI Generates

Scenario 01 — Receipt A + Full Return + Damaged Goods
Scenario 02 — Receipt A + Partial Return + Wrong Item Shipped
Scenario 03 — Receipt B + Additional Partial Return + Quality Rejection
Scenario 04 — Return Quantity Exceeds Received Quantity (Negative)
Scenario 05 — Return Against Already Fully Returned Receipt C (Negative)
Scenario 06 — Return Against Closed Receipt D (Negative)
...

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

Example Test Variations

Representative examples of scenarios 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
VAR-001	Full Return of Received Quantity	Positive	Return quantity equals full received quantity	Syntra Ready
VAR-002	Partial Return of Received Quantity	Positive	Return quantity is less than received quantity	Syntra Ready
VAR-003	Return With Damaged Goods Reason	Positive/Reason	Return reason = Damaged Goods	Syntra Ready
VAR-004	Return With Wrong Item Shipped Reason	Positive/Reason	Return reason = Wrong Item Shipped	Syntra Ready
VAR-005	Return With Quality Rejection Reason	Positive/Reason	Return reason = Quality Rejection	Syntra Ready
VAR-006	Return of a Different Item on Same Receipt	Positive	Second item on the same multi-line receipt returned	Syntra Ready
VAR-007	Return After Inspection	Positive/Timing	Return initiated after a separate inspection step identifies non-conforming goods	Syntra Ready
VAR-008	Return Before Invoice	Positive/Timing	Return processed before the receipt is matched to a supplier invoice, where applicable	Syntra Ready
VAR-009	Additional Partial Return on Already Partially Returned Receipt	Positive/Timing	Second partial return submitted against remaining returnable quantity	Syntra Ready
VAR-010	Return Quantity Exceeds Received Quantity	Negative	Return quantity entered greater than received quantity	Syntra Ready
VAR-011	Return Against Invalid Receipt	Negative	Receipt number does not correspond to a valid, eligible receipt	Syntra Ready
VAR-012	Return Against Already Fully Returned Receipt	Negative/Timing	Receipt has no remaining returnable quantity	Syntra Ready
VAR-013	Invalid or Missing Return Reason	Negative/Reason	Required return reason left blank or set to an invalid value	Syntra Ready
VAR-014	Return Against a Closed Transaction	Negative/Timing	Underlying PO or receipt transaction is closed	Syntra Ready
VAR-015	Unauthorized User Attempts Return	Negative	User lacks return privilege/security	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully return eligible received goods to the supplier.

Eligible Receipt + Valid Return Quantity + Valid Return Reason → Return Processed

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's return eligibility rules, quantity validations and security around returns to supplier.

Return Quantity Exceeds Received Quantity → Expected Quantity Validation
Invalid Receipt → Expected Eligibility Validation
Already Fully Returned Receipt → Expected Duplicate Return Validation
Missing Return Reason → Expected Required Field Validation
Unauthorized User → Expected Security Validation

A negative receiving scenario passes when Oracle correctly raises the expected validation.

Scenario	Oracle Outcome	Test Result
Valid receipt	Receipt created	PASS
Closed PO	PO status validation occurs	PASS
Over receipt	Quantity 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 scenarios and group them into reusable execution packs.

Receiving Return to Supplier Regression Pack

Full Return of Received Quantity
Partial Return of Received Quantity
Return With Different Return Reasons
Return of a Different Item on Same Receipt
Return After Inspection
Return Before Invoice
Return Quantity Exceeds Received Quantity
Return Against Already Fully Returned Receipt
Missing Return Reason
Unauthorized User Attempts Return

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

Once scheduled, SyntraFlow executes the selected 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	Receiving Return to Supplier Regression Pack
Schedule	Quarterly Update Regression
Tests	15 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

Return to Supplier processing depends on the acting user holding an appropriate Receiving security role. Jarvis can generate persona-based variations to confirm access is correctly granted or restricted.

Persona	Action	Expected	Syntra Result
Receiving Clerk	Process Return	Allowed	PASS
Unauthorized User	Attempts Return	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 business scenario, available DataVault test data and expected business outcomes to generate additional test 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 — Return to Supplier, 8 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

Navigate to the Receipt

May internally include

Open Receiving → Search by Supplier/PO/Receipt → Open Result → Read Returnable Quantity

Business Step

Enter Return Reason

May internally include

Open Return Reason List of Values → Select Reason → Confirm Selection

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
Enter Return Quantity	Pass	—
Click Submit	Pass	—
Verify Receipt Quantity Updated	Pass	Pass

Related Receiving Tests

Return to Supplier is one stage of the same receiving lifecycle — explore the related receipt, correction and inspection scenarios below.

Receive Purchase Order Correct Receipt Inspect Receipt

Turn This Standard Test into Your Oracle Receiving Regression Suite

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

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

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

Frequently Asked Questions

What qualifies received goods for return to supplier in Oracle Fusion?

Goods qualify for return when the originating receipt has a returnable quantity for the item — typically goods that have not already been fully returned, consumed or otherwise closed out. Exact eligibility rules depend on the customer's Oracle Fusion configuration.

What is the difference between a return and a receipt correction?

A return sends previously received goods back to the supplier and reduces the receipt's remaining quantity. A receipt correction adjusts details recorded on the receipt itself, such as quantity entered in error, without necessarily involving the supplier. This scenario is scoped to return to supplier only; receipt correction is covered by a separate test scenario.

Do returns to supplier affect inventory or accounting?

Where the item is inventory-tracked or subject to accounting treatment, a return can update on-hand inventory and related accounting entries. This is covered as a validation checkpoint, worded conditionally since exact impact depends on item setup and customer configuration — SyntraFlow validates the expected outcome in the Oracle Fusion UI as part of automated test execution rather than performing inventory movements itself.

How is security tested for the return-to-supplier scenario?

Security testing verifies that a user with appropriate Receiving privileges, such as a Receiving Clerk, can process a return, while a user without that access is correctly prevented from doing so. Both outcomes are treated as passing test results when Oracle behaves as expected.

Can multiple return reasons and quantities be tested for the same receipt?

Yes — Jarvis AI can generate variations covering full returns, partial returns, different return reasons and different items against the same underlying receipt, using test data available through Syntra DataVault where connected.