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

Syntra Standard Oracle Test Library

Oracle Fusion Receive Purchase Order Test Cases

Validate that goods or services are received correctly in Oracle Fusion SCM against an eligible purchase order, using a valid PO line, received quantity, receiving organization and receipt date.

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

Test Objective

The objective of this test is to validate that a purchase order receipt can be created in Oracle Fusion SCM against an eligible, open purchase order, confirming that the correct PO line, received quantity, receiving organization and receipt date are captured and that the resulting receipt and purchase order open quantity are updated correctly.

The scenario should confirm that:

the correct eligible purchase order and line are selected for receipt
received quantity is captured correctly against the PO line
the receiving organization and subinventory location are captured correctly
a system-generated receipt number is assigned and the receipt status is correct
the purchase order's open quantity is updated to reflect the quantity received
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 receipt of goods or services against a single or multi-line purchase order in Oracle Fusion SCM Procurement TEST/UAT environments. It does not cover receipt inspection, receiving exceptions or subsequent correction, which are covered by the separate Inspect Receipt, Receiving Exceptions and related scenarios in the same Receiving cluster.

When to Use This Test

Functional testing of purchase order receiving for a new Oracle Fusion SCM Procurement implementation
Regression testing of receiving behavior after an Oracle quarterly update
UAT sign-off for receiving clerks who routinely receive goods or services against purchase orders
Baseline case referenced by the Partial Receipt, Inspect Receipt and Receiving Exceptions scenarios within the same Receiving cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during receiving before escalating as a possible APPLICATION_ERROR

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

Navigate to Receiving

→

Search Eligible PO

→

Select Lines

→

Enter Received Quantity

→

Select Organization

→

Review

→

Submit

Receive Purchase Order is the entry point of the Receiving scenario family within Procure-to-Pay, following on from the Purchase Orders cluster once a purchase order has been approved and becomes eligible for receipt. Once goods or services are received, the receipt may be inspected, corrected for exceptions, or received across multiple partial transactions — covered by the Partial Receipt, Inspect Receipt and Receiving Exceptions scenarios in this same cluster. Exact fields available, tolerances and validation depend on receiving organization configuration, item setup and customer-specific Oracle Fusion configuration.

Next Stage →

Partial Receipt

Preconditions

The purchase order being received exists in the target Oracle Fusion SCM environment and is in an eligible open status.
The receiving organization used for the receipt is configured and active.
The item, quantity and unit of measure data on the purchase order line are valid.
The test user has receiving privileges for the receiving organization.
The purchase order line has open quantity available to receive.

Exact field availability, tolerances, mandatory fields 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

PO Number	${PO_NUMBER}
PO Line	${PO_LINE}
Supplier	${SUPPLIER}
Item	${ITEM}
Quantity Ordered	${QUANTITY_ORDERED}
Quantity Available	${QUANTITY_AVAILABLE}
UOM	${UOM}
Receipt Date	${RECEIPT_DATE}
Receiving Organization	${RECEIVING_ORGANIZATION}
Subinventory Location	${SUBINVENTORY_LOCATION}

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 service-based purchase order line may not require a subinventory location.

Test Steps

9 business-readable steps. SyntraFlow's automation executes ~22 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 receiving clerk test user.	Oracle Fusion opens successfully for the test user.
2	Navigate to Receiving Open the Receiving work area to begin creating a purchase order receipt. ${RECEIVING_ORGANIZATION}	The Receiving work area opens for the correct receiving organization.
3	Search for the Eligible Purchase Order Search for the purchase order eligible for receipt using the PO number or supplier. ${PO_NUMBER} / ${SUPPLIER}	The eligible purchase order is returned and available for selection.
4	Select the Purchase Order Line(s) Select the purchase order line or lines to be received. ${PO_LINE} / ${ITEM} This single business step replaces multiple technical actions such as opening the line list, selecting each eligible line and confirming its open quantity.	The selected line(s) are added to the receipt with the correct item and open quantity detail.
5	Enter Received Quantity Enter the quantity being received against the selected purchase order line. ${QUANTITY_ORDERED} / ${QUANTITY_AVAILABLE} / ${UOM} This is the step highlighted in the receiving process flow, since correctly capturing the received quantity against the purchase order's open quantity is central to this scenario.	The received quantity is accepted without unexpected validation errors.
6	Select Receiving Organization Select or confirm the receiving organization and subinventory location for the receipt. ${RECEIVING_ORGANIZATION} / ${SUBINVENTORY_LOCATION}	The receiving organization and subinventory location are accepted and reflected on the receipt.
7	Review Receipt Details Review the receipt header and line detail, including PO reference, item, quantity and receipt date, before submitting. ${RECEIPT_DATE} Reviewing the receipt before submission lets the tester catch an incorrect field entry before the receipt is created.	The reviewed receipt reflects the entered PO line, quantity, organization and receipt date.
8	Submit the Receipt Submit the receipt for processing in the test environment.	Oracle Fusion successfully processes the receipt without unexpected errors.
9	Verify Receipt Number and PO Open QuantityBusiness assertion Reopen or refresh the receipt and the source purchase order and confirm the generated receipt number, received quantity and updated PO open quantity. This is the primary business assertion for the scenario — a correctly created receipt with an updated PO open quantity is the expected pass condition, not merely a successful submission.	A receipt number is generated, the received quantity matches the entered data, and the purchase order's open quantity is reduced accordingly.

Expected Results

A purchase order receipt is created against the eligible, open purchase order.
A system-generated receipt number is assigned.
The received quantity matches the entered data.
The receiving organization and subinventory location on the receipt are correct.
The purchase order's open quantity is updated to reflect the quantity received.
The receipt status correctly reflects a newly created receipt.
The receipt is visible and traceable for the test receiving clerk.

Key Validation Checkpoints

Receipt created.
Received quantity correct.
PO open quantity updated.
Status correct.
Receipt number generated.

Core Business Scenario

Receive Purchase Order

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 Purchase Order business scenario. Jarvis AI can extend this scenario by generating additional item, quantity, organization, 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 item, quantity, organization or purchase order status combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Boundary variations for the customer's environment — including large-quantity receipt cases and receipts attempted against a closed or cancelled purchase order, since correctly enforced validation at the edges of expected values is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Receive Purchase Order business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Purchase Orders, Items, Organizations, Locations and Suppliers.

Jarvis AI

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

Positive + Negative Test Variations

Valid receiving scenarios and edge cases such as closed purchase orders, invalid organizations 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, organization or purchase order status combination, SyntraFlow maintains one core Receive Purchase Order scenario and allows Jarvis AI to generate item, quantity, organization and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Receive Purchase Order 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

Receive the full ordered quantity
Receive a single purchase order line
Receive multiple purchase order lines
Receive purchase orders with different items
Receive purchase orders with different quantities
Receive purchase orders in different receiving organizations
Receive a serial- or lot-controlled item where configured
Receive against a partial open quantity

Negative Scenarios

Attempt to receive against a closed purchase order
Attempt to receive against a cancelled purchase order
Enter a received quantity exceeding the allowed quantity
Attempt to receive an invalid item
Enter an invalid receiving organization
Enter an invalid receipt date
Attempt to submit with missing mandatory data

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

Standard Library Definition

PO Number               ${PO_NUMBER}
PO Line                 ${PO_LINE}
Supplier                ${SUPPLIER}
Item                    ${ITEM}
Quantity Ordered        ${QUANTITY_ORDERED}
Quantity Available      ${QUANTITY_AVAILABLE}
UOM                     ${UOM}
Receipt Date            ${RECEIPT_DATE}
Receiving Organization  ${RECEIVING_ORGANIZATION}
Subinventory Location   ${SUBINVENTORY_LOCATION}

DataVault

Purchase Orders
  Eligible open purchase orders and lines per receiving organization
Items
  Active catalog and serial/lot-controlled item values
Organizations
  Configured receiving organizations and subinventory locations
Suppliers
  Suppliers associated with eligible purchase orders
Quantities
  Ordered and available quantities per purchase order line

Jarvis AI Generates

Scenario 01 — Full Receipt Against Single-Line PO
Scenario 02 — Multi-Line PO Receipt Across Two Items
Scenario 03 — Partial Receipt Against Open Quantity
Scenario 04 — Serial-Controlled Item Receipt
Scenario 05 — Receipt Attempted Against Closed PO
Scenario 06 — Unauthorized User Attempts Receive Purchase Order
...

Receive Purchase Order test data can include sensitive procurement categories such as supplier, item and quantity information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific receiving 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 Purchase Order scenarios Jarvis can generate from this business scenario, spanning item, quantity, organization and PO 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 Receipt	Positive	Receipt created for the full ordered quantity on the purchase order line	Syntra Ready
VAR-002	Single-Line Receipt	Positive	Receipt created against a single purchase order line	Syntra Ready
VAR-003	Multi-Line Receipt	Positive	Receipt created against multiple purchase order lines	Syntra Ready
VAR-004	Different Items	Positive/Item	Receipt created against an alternate active item	Syntra Ready
VAR-005	Different Quantities	Positive/Quantity	Receipt created with a range of valid received quantities	Syntra Ready
VAR-006	Different Receiving Organizations	Positive/Organization	Receipt created against an alternate configured receiving organization	Syntra Ready
VAR-007	Serial/Lot-Controlled Item	Positive/Item	Receipt created for an item configured for serial or lot control	Syntra Ready
VAR-008	Partial Open Quantity Receipt	Positive/Quantity	Receipt created against a purchase order line with remaining open quantity	Syntra Ready
VAR-009	Closed Purchase Order	Negative	Selected purchase order is closed as of the receipt date	Syntra Ready
VAR-010	Cancelled Purchase Order	Negative	Selected purchase order is cancelled	Syntra Ready
VAR-011	Quantity Exceeds Allowed	Negative/Quantity	Received quantity entered exceeds the purchase order line's allowed quantity	Syntra Ready
VAR-012	Invalid Item	Negative/Item	Selected item is invalid or not on the purchase order	Syntra Ready
VAR-013	Invalid Receiving Organization	Negative/Organization	Receiving organization entered is not configured for receipt	Syntra Ready
VAR-014	Invalid Receipt Date	Negative	Receipt date entered is outside a valid processing period	Syntra Ready
VAR-015	Missing Mandatory Data	Negative	A mandatory receipt header or line field is left blank	Syntra Ready

Automatically Expand Positive and Negative Receiving Coverage

Positive Testing

Jarvis generates scenarios using purchase order line, item, quantity, organization and location combinations expected to successfully create a receipt in Oracle Fusion.

Eligible Open PO + Active Item + Valid Quantity + Valid Receiving Organization → Receipt Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around PO status, quantity limits, organization validity and security.

Closed Purchase Order → Expected PO Status Validation
Quantity Exceeds Allowed → Expected Quantity Validation
Invalid Item → Expected Item Validation
Invalid Receiving Organization → Expected Organization Validation
Unauthorized User → Expected Access Restriction

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 Receive Purchase Order scenarios and group them into reusable execution packs.

SCM Procurement Receive Purchase Order Regression Pack

Full Receipt
Single-Line Receipt
Multi-Line Receipt
Different Items
Different Receiving Organizations
Serial/Lot-Controlled Item
Partial Open Quantity Receipt
Closed Purchase Order
Quantity Exceeds Allowed
Security Restriction — Unauthorized Receive

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

Once scheduled, SyntraFlow executes the selected Receive Purchase Order 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 Receive Purchase Order 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 & Approval Variations

Access to receive against a purchase 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 receiving access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Receiving Clerk	Receive Against PO	Allowed	PASS
Unauthorized User	Attempts Receive	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 Purchase Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative and Boundary coverage — including large-quantity receipts and receipts attempted against a closed or cancelled purchase order — 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 Purchase Order, 9 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Search for the Eligible Purchase Order

May internally include

Open PO Search → Enter PO Number/Supplier Criteria → Filter Eligible Lines → Select Purchase Order → Confirm Eligible Status

Business Step

Review Receipt Details

May internally include

Open Receipt Preview → Read PO Reference, Item, Quantity, Organization → Compare Against Entered Values

What SyntraFlow Captures Per Run

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

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the receipt was created correctly — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. When a step fails, SyntraFlow's evidence trail is designed to help a tester classify the likely cause — for example DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Receive Purchase Order failed — Likely category: DATA_ERROR — Evidence: receipt quantity exceeds the PO's open quantity — Recommended action: correct the quantity to the eligible amount and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Received Quantity	Pass	—
Submit the Receipt	Pass	—
Verify Receipt Number and PO Open Quantity	Pass	Pass

Related Receiving Tests

Receive Purchase Order is the entry point of the Receiving cluster — explore the related partial receipt, inspection and exception scenarios below.

Partial Receipt Inspect Receipt Receiving Exceptions

Turn This Standard Test into Your Oracle SCM Receive Purchase Order Regression Suite

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

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

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

Frequently Asked Questions

What does this test validate when receiving a purchase order?

This test validates that a purchase order receipt can be created in Oracle Fusion SCM against an eligible, open purchase order, with the correct PO line, received quantity, receiving organization and receipt date, and that the receipt is assigned a system-generated receipt number while the purchase order's open quantity is updated correctly.

How does this scenario handle serial- or lot-controlled items?

Where an item is configured as serial- or lot-controlled in Oracle Fusion, receiving that item requires entry of the applicable serial numbers or lot detail in addition to received quantity. This scenario includes a serial/lot item variation for environments configured for serial or lot control; behavior otherwise depends on item setup.

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

No. Rather than maintaining a separate public page for every item, quantity, organization or status combination, SyntraFlow maintains this one core Receive Purchase Order scenario and uses Jarvis AI to generate the underlying variations from customer-specific DataVault test data. This page remains the canonical reference for all of them.

How does security testing work for purchase order receiving?

Access to receive against a purchase 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 receiving clerk versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.

Does this test create real receipts or move real inventory in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not create real receiving transactions, move real physical goods or affect real inventory in a production environment.