Oracle ERP Testing Tool > Test Library > SCM > Order Management > Returns

Syntra Standard Oracle Test Library

Oracle Fusion Receive Return Test Cases

Validate that returned goods are physically received in Oracle Fusion SCM against an existing return order, with received quantity, condition and disposition correctly driving the resulting inventory update.

Test ID	ORCL.O2C.OM.RET.RECEIVE
Application	Oracle Fusion Cloud
Product	SCM / Order Management
Module	Order Management
Process	Returns
Business Flow	Order-to-Cash
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 20 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that returned goods can be physically received in Oracle Fusion SCM Order Management against an existing, open return order, confirming that the received quantity and condition are captured correctly and that inventory is updated in line with the return order's disposition.

The scenario should confirm that:

the correct open return order is located and selected for receipt
received quantity is captured correctly against the return order line
the disposition (return-to-stock, scrap or inspection-required) drives the correct subinventory routing
the condition code entered is consistent with the disposition
on-hand inventory is updated correctly per the disposition and the return order status reflects the receipt
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 the physical receipt step against an existing, open return order in Oracle Fusion SCM Order Management TEST/UAT environments, assuming the return order itself has already been created. It does not cover creation of the return order or subsequent exception handling, which are covered by the separate Create Return Order and Return Order Exceptions scenarios in the same Returns cluster.

When to Use This Test

Functional testing of return receiving for a new Oracle Fusion SCM Order Management implementation
Regression testing of return receipt and disposition-driven inventory behavior after an Oracle quarterly update
UAT sign-off for warehouse operators who routinely receive customer returns against return orders
Baseline case referenced by the Return Order Exceptions scenario within the same Returns cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during return receipt before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Order-to-Cash Returns Process

Navigate to Returns

→

Locate Return Order

→

Initiate Receive Return

→

Enter Quantity & Condition

→

Confirm Disposition Routing

→

Review

→

Submit

Receive Return is the second scenario in the Returns cluster within Order-to-Cash, following on from Create Return Order once a return order has been created and is open for receipt. Once the return is physically received, unexpected conditions such as quantity mismatches or invalid dispositions are covered by the separate Return Order Exceptions scenario in this same cluster. Exact fields available, subinventory routing rules and tolerances depend on receiving organization configuration, item setup and customer-specific Oracle Fusion configuration.

← Previous Stage

Create Return Order

Next Stage →

Return Order Exceptions

Preconditions

A return order exists in the target Oracle Fusion SCM environment and is open for receipt.
The return order's disposition (return-to-stock, scrap or inspection-required) has been set.
The receiving organization and subinventory locations used for the receipt are configured and active.
The item, quantity and unit of measure on the return order line are valid.
The test user has receiving privileges for the receiving organization.

Exact field availability, subinventory routing rules, tolerances and validation messages may vary by Oracle Fusion implementation, receiving organization configuration, item setup and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Return Order Number	${RETURN_ORDER_NUMBER}
Return Order Line	${RETURN_ORDER_LINE}
Item	${ITEM}
Receive Quantity	${RECEIVE_QUANTITY}
UOM	${UOM}
Disposition	${DISPOSITION}
Subinventory	${SUBINVENTORY}
Condition	${CONDITION}
Receiving Organization	${RECEIVING_ORGANIZATION}

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 receipt — for example, a line already routed to inspection may not require a final sellable subinventory at the point of receipt.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~20 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 authorised warehouse operator test user.	Oracle Fusion opens successfully for the test user.
2	Navigate to Order Management Open the Order Management work area and navigate to the Returns receiving function to begin receiving a return. ${RECEIVING_ORGANIZATION}	The Returns receiving function opens for the correct receiving organization.
3	Locate the Open Return Order Search for and select the open return order eligible for physical receipt. ${RETURN_ORDER_NUMBER} / ${ITEM}	The eligible return order is returned and available for selection.
4	Initiate Receive Return Initiate the receive-return transaction against the selected return order line. ${RETURN_ORDER_LINE} This single business step replaces multiple technical actions such as opening the receipt line list and confirming the return order line detail.	The receive-return transaction opens with the correct return order line detail.
5	Enter Received Quantity and Condition Enter the quantity being received against the return order line and record the item's condition. ${RECEIVE_QUANTITY} / ${UOM} / ${CONDITION}	The received quantity and condition are accepted without unexpected validation errors.
6	Confirm Disposition-Driven Subinventory Routing Confirm or adjust the subinventory the item is routed to, based on the return order's disposition (return-to-stock, scrap or inspection-required). ${DISPOSITION} / ${SUBINVENTORY} This is the step highlighted in the returns receiving process flow, since correctly routing inventory according to disposition is central to this scenario.	The subinventory routing presented is consistent with the return order's disposition.
7	Submit the Receipt Submit the return receipt for processing in the test environment.	Oracle Fusion successfully processes the receipt without unexpected errors.
8	Verify Inventory Impact Matches DispositionBusiness assertion Reopen or refresh the receipt and the source return order and confirm the received quantity, updated on-hand inventory and return order status. This is the primary business assertion for the scenario — inventory correctly updated per disposition is the expected pass condition, not merely a successful submission.	The received quantity matches the entered data, on-hand inventory reflects the disposition (stock, scrap or inspection hold), and the return order status updates to reflect the receipt.

Expected Results

A receipt is recorded against the open return order.
The received quantity matches the entered data.
On-hand inventory is updated correctly according to the return order's disposition.
Items received with a scrap disposition are excluded from sellable on-hand.
Items received with an inspection-required disposition are held pending inspection rather than posted to sellable stock.
The return order status updates to reflect the receipt.
A receipt history / audit trail entry is recorded for the transaction.

Key Validation Checkpoints

Received quantity correctly recorded against the return order.
On-hand updated correctly based on disposition (stock vs scrap vs inspection hold).
Return order status updates to reflect receipt.
Receipt history/audit trail recorded.

Core Business Scenario

Receive Return

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 Receive Return business scenario. Jarvis AI can extend this scenario by generating additional item, quantity, disposition, condition and security variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every item, quantity, disposition or condition combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Boundary variations for the customer's environment — including receipts attempted against a closed or cancelled return order and condition codes inconsistent with the stated disposition, since correctly enforced validation at these edges is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Receive Return business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Return Orders, Items, Organizations, Subinventories and Dispositions.

Jarvis AI

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

Positive + Negative Test Variations

Valid return receiving scenarios and edge cases such as closed return orders, invalid subinventories or restricted access.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

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

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining a separate test page for every possible item, quantity, disposition or condition combination, SyntraFlow maintains one core Receive Return scenario and allows Jarvis AI to generate quantity, disposition and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Receive Return 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 Order Management Returns.

Positive Scenarios

Full-quantity receipt to stock
Partial-quantity receipt
Receipt with disposition scrap (excluded from sellable on-hand)
Receipt requiring inspection before disposition
Receipt of multiple lines on the same return order

Negative Scenarios

Receive quantity exceeds return order quantity
Receipt attempted on a closed/cancelled return order
Invalid subinventory for disposition
Unauthorized user attempts receipt
Duplicate receipt against the same return line
Condition code inconsistent with disposition

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 return order, item, quantity, disposition and condition combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Receive Return scenarios relevant to the customer's actual implementation.

Standard Library Definition

Return Order Number     ${RETURN_ORDER_NUMBER}
Return Order Line       ${RETURN_ORDER_LINE}
Item                    ${ITEM}
Receive Quantity        ${RECEIVE_QUANTITY}
UOM                     ${UOM}
Disposition             ${DISPOSITION}
Subinventory            ${SUBINVENTORY}
Condition               ${CONDITION}
Receiving Organization  ${RECEIVING_ORGANIZATION}

DataVault

Return Orders
  Open return orders and lines per receiving organization
Items
  Active catalog and condition-tracked item values
Organizations
  Configured receiving organizations and subinventory locations
Dispositions
  Return-to-stock, scrap and inspection-required routing rules
Quantities
  Shipped and remaining open quantities per return order line

Jarvis AI Generates

Scenario 01 — Full-Quantity Receipt to Stock
Scenario 02 — Partial-Quantity Receipt
Scenario 03 — Scrap Disposition Receipt
Scenario 04 — Inspection-Required Disposition Receipt
Scenario 05 — Receipt Attempted on Cancelled Return Order
Scenario 06 — Unauthorized User Attempts Receive Return
...

Receive Return test data can include sensitive customer and item categories such as return order, item and quantity information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific returns 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 Receive Return scenarios Jarvis can generate from this business scenario, spanning quantity, disposition and return order status 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	Full-Quantity Receipt to Stock	Positive	Receipt created for the full return order quantity, routed to a sellable subinventory	Syntra Ready
VAR-002	Partial-Quantity Receipt	Positive/Quantity	Receipt created for less than the full return order quantity	Syntra Ready
VAR-003	Disposition Scrap Receipt	Positive/Disposition	Receipt created against a scrap disposition, excluded from sellable on-hand	Syntra Ready
VAR-004	Inspection-Required Receipt	Positive/Disposition	Receipt created and held pending inspection before final disposition	Syntra Ready
VAR-005	Multiple Lines on Same Return Order	Positive	Receipt created against multiple lines on the same return order	Syntra Ready
VAR-006	Quantity Exceeds Return Order	Negative/Quantity	Received quantity entered exceeds the return order's authorized quantity	Syntra Ready
VAR-007	Closed/Cancelled Return Order	Negative	Receipt attempted against a closed or cancelled return order	Syntra Ready
VAR-008	Invalid Subinventory for Disposition	Negative/Disposition	Selected subinventory is not valid for the return order's disposition	Syntra Ready
VAR-009	Unauthorized User Attempts Receipt	Negative	Test user lacks receiving privileges for the receiving organization	Syntra Ready
VAR-010	Duplicate Receipt Against Same Line	Negative	A second receipt is attempted against an already-received return order line	Syntra Ready
VAR-011	Condition Code Inconsistent with Disposition	Negative/Disposition	Condition code entered does not align with the return order's disposition	Syntra Ready

Automatically Expand Positive and Negative Return Receipt Coverage

Positive Testing

Jarvis generates scenarios using return order, item, quantity, disposition and condition combinations expected to successfully record a receipt in Oracle Fusion.

Open Return Order + Valid Quantity + Valid Disposition + Valid Subinventory → Receipt Recorded

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around return order status, quantity limits, disposition/subinventory validity and security.

Quantity Exceeds Return Order → Expected Quantity Validation
Closed/Cancelled Return Order → Expected Status Validation
Invalid Subinventory for Disposition → Expected Configuration Validation
Duplicate Receipt Against Same Line → Expected Duplicate 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 return order	Return created	PASS
Quantity exceeds shipped	Validation occurs	PASS
Item not return-eligible	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 Receive Return scenarios and group them into reusable execution packs.

SCM Order Management Receive Return Regression Pack

Full-Quantity Receipt to Stock
Partial-Quantity Receipt
Disposition Scrap Receipt
Inspection-Required Receipt
Multiple Lines on Same Return Order
Quantity Exceeds Return Order
Closed/Cancelled Return Order
Invalid Subinventory for Disposition
Duplicate Receipt Against Same Line
Security Restriction — Unauthorized Receipt

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

Once scheduled, SyntraFlow executes the selected Receive Return 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 Order Management Receive Return Regression Pack
Schedule	Quarterly Update Regression
Tests	11 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

Access to receive against a return order for a given receiving organization is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that return receiving access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Warehouse Operator	Receive Return	Allowed	PASS
Unauthorized User	Attempts Return Receipt	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 Receive Return scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative and Boundary coverage — including receipts attempted against a closed or cancelled return order and quantities exceeding the authorized amount — 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 — Receive Return, 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

Locate the Open Return Order

May internally include

Open Return Order Search → Enter Return Order Number/Customer Criteria → Filter Open Return Orders → Select Return Order → Confirm Eligible Status

Business Step

Confirm Disposition-Driven Subinventory Routing

May internally include

Read Return Order Disposition → Resolve Target Subinventory → Validate Subinventory Is Valid for Disposition → Apply Routing to Receipt Line

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 receipt was recorded 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: Receive Return failed — Likely category: DATA_ERROR — Evidence: received quantity exceeds the quantity authorized on the return order — Recommended action: verify the return order quantity and correct the receipt entry. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Received Quantity and Condition	Pass	—
Submit the Receipt	Pass	—
Verify Inventory Impact Matches Disposition	Pass	Pass

Related Returns Tests

Receive Return follows on from Create Return Order in the Returns cluster — explore the related creation, exception and inventory receipt scenarios below.

Create Return Order Return Order Exceptions Miscellaneous Receipt

Turn This Standard Test into Your Oracle SCM Receive Return Regression Suite

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

Automate with SyntraFlow Explore Order Management Returns 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 Order Management Test Library Returns Test Library Syntra DataVault

Frequently Asked Questions

What does this test validate when receiving a return?

This test validates that returned goods can be physically received in Oracle Fusion SCM against an existing, open return order, with the correct received quantity and condition captured, and that the resulting inventory update and return order status match the return order's disposition.

How does disposition drive inventory routing during return receipt?

The return order's disposition determines where the received item is routed. A return-to-stock disposition routes the item to a sellable subinventory, a scrap disposition excludes it from sellable on-hand, and an inspection-required disposition holds it in a non-sellable location pending inspection. This scenario confirms the correct routing occurs for each disposition.

What happens when a return is received with a scrap disposition?

Items received against a scrap disposition are recorded as received but are excluded from sellable on-hand inventory. This scenario confirms that scrap receipts do not incorrectly inflate available-to-promise or sellable stock.

How does this scenario handle partial receipt against a return order?

A return order line can be received in full or in part. This scenario includes a partial-quantity receipt variation, confirming that the received quantity is recorded correctly and that the return order line remains open for the remaining quantity where applicable.

How does security testing work for return receiving?

Access to receive against a return order for a given receiving organization is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an authorised warehouse operator versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.