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

Syntra Standard Oracle Test Library

Oracle Fusion Partial Receipt Test Cases

Validate that a partial receipt can be recorded against an eligible purchase order in Oracle Fusion Procurement, and confirm that the resulting remaining open quantity on the purchase order line is calculated and recorded correctly once the receipt is processed.

Test ID	ORCL.P2P.PROC.RCV.PARTIAL
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

This test validates that a partial receipt can be recorded against an eligible purchase order in Oracle Fusion Procurement, and that the resulting remaining open quantity on the purchase order line is calculated as Ordered Quantity minus Received Quantity, and is recorded accurately once the receipt is processed.

The scenario should confirm that:

the purchase order line selected for partial receipt has an open quantity greater than the intended partial receipt amount
the entered partial received quantity is accepted and recorded against the purchase order line without unexpected errors
the resulting Remaining Open Quantity equals Ordered Quantity minus Received Quantity
the receipt is correctly linked to the source purchase order and purchase order line
the purchase order line remains eligible for further receipt where open quantity still remains

This scenario covers a single partial receipt transaction against an eligible purchase order line within Oracle Fusion Procurement TEST/UAT environments. It does not cover receiving the full ordered quantity in one transaction, which is covered by the separate Receive Purchase Order scenario, and it does not cover correcting a previously recorded receipt, which is covered by Correct Receipt. The governing arithmetic relationship for this scenario is: Ordered Quantity − Received Quantity = Remaining Open Quantity. Specific percentages such as 25%, 50% or other partial amounts 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 partial receipt processing for a new Oracle Fusion Procurement implementation
Regression testing of remaining open quantity calculations after an Oracle quarterly update
UAT sign-off for receiving organizations that routinely receive purchase orders across multiple partial receipts
Baseline case referenced by the receive, correct and receiving exceptions scenarios within the same Receiving process

Where This Test Fits in the Receiving Process

Receive Purchase Order

→

Partial Receipt

→

Correct Receipt

→

Receiving Exceptions

Partial Receipt sits alongside full receipt as a way of recording quantity received against an eligible purchase order line, and precedes any later Correct Receipt or Receiving Exceptions handling. It does not cover creating the purchase order itself, which occurs earlier in the Procure-to-Pay process. Exact behavior depends on receiving organization configuration, tolerance settings and customer-specific Oracle Fusion setup.

← Previous Stage

Receive Purchase Order

Next Stage →

Correct Receipt

Preconditions

A purchase order exists with an open quantity greater than the intended partial receipt amount.
The purchase order line is approved and eligible for receiving in Oracle Fusion Procurement.
The receiving organization is configured and the test user has permission to record receipts against it.
The item and unit of measure on the purchase order line are valid for receiving.

Exact setup, field availability and validation messages may vary by Oracle Fusion implementation, receiving organization configuration and security setup.

Sample Test Data

PO Number	${PO_NUMBER}
PO Line	${PO_LINE}
Item	${ITEM}
Ordered Quantity	${ORDERED_QUANTITY}
Partial Received Quantity	${PARTIAL_RECEIVED_QUANTITY}
Remaining Open Quantity (Expected)	${REMAINING_OPEN_QUANTITY}
Unit of Measure	${UNIT_OF_MEASURE}
Receiving Organization	${RECEIVING_ORGANIZATION}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. ${REMAINING_OPEN_QUANTITY} is expected to equal ${ORDERED_QUANTITY} minus ${PARTIAL_RECEIVED_QUANTITY}.

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 and Navigate to Receiving Sign in to Oracle Fusion using an authorised Procurement test user and navigate to the Receiving work area.	The Receiving work area opens successfully.
2	Navigate to the Eligible Purchase Order Search for and open the purchase order and line eligible for partial receipt. ${PO_NUMBER} / ${PO_LINE} This single business step replaces multiple technical actions such as opening receipt search, entering the PO number and line, and selecting the result.	The correct purchase order line is located and its current open quantity is displayed.
3	Initiate the Receipt Select the option to create a receipt against the located purchase order line.	The receipt entry screen opens for the selected purchase order line.
4	Enter Partial Received Quantity Enter a received quantity that is less than the purchase order line's full open quantity. ${PARTIAL_RECEIVED_QUANTITY}	The partial quantity is accepted without unexpected validation errors.
5	Review Resulting Remaining Open Quantity Before Submitting Review the remaining open quantity calculated by Oracle Fusion before submitting the receipt. Reviewing the calculated remaining open quantity before submission lets the tester catch an incorrect quantity entry before the receipt is saved.	The previewed remaining open quantity equals Ordered Quantity minus Partial Received Quantity.
6	Submit and Confirm the Receipt Submit and confirm the partial receipt for processing in the test environment.	Oracle Fusion successfully processes the partial receipt without unexpected errors.
7	Verify Received Quantity RecordedBusiness assertion Reopen or refresh the purchase order line and confirm the received quantity recorded.	The received quantity recorded against the purchase order line matches the entered partial received quantity.
8	Verify Remaining Open Quantity Matches Expected CalculationBusiness assertion Reopen or refresh the purchase order line and confirm the resulting remaining open quantity. This is the primary business assertion for the scenario — a correctly calculated remaining open quantity is the expected pass condition, not merely a successful save.	Ordered Quantity − Received Quantity = Remaining Open Quantity.

Expected Results

The partial received quantity is accepted and recorded against the purchase order line.
Ordered Quantity − Received Quantity = Remaining Open Quantity.
The receipt is correctly linked to the source purchase order and purchase order line.
The purchase order line remains eligible for further receipt where open quantity remains.
Received quantity and remaining open quantity are both visible for review after processing.

Key Validation Checkpoints

Ordered Quantity − Received Quantity = Remaining Open Quantity.
Remaining open quantity is correctly calculated after the partial receipt is processed.
The receipt is linked to the correct purchase order line.
Further receipt against the purchase order line remains possible where open quantity remains eligible.

Core Business Scenario

Partial Receipt

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 partial receipt business scenario. Jarvis AI can extend this scenario by generating additional quantity, sequencing and receiving-organization variations across Positive, Negative, Boundary and Security categories, using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every possible partial-receipt percentage or quantity. Jarvis uses the standard scenario as the foundation and generates relevant quantity-driven and sequential variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable partial receipt business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — purchase orders, items, quantities and receiving organizations.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant quantity, sequencing and receiving-organization variations.

Positive + Negative Test Variations

Valid partial-quantity scenarios and edge cases such as over-receipt, zero quantity or a closed purchase order.

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 partial-receipt percentage or quantity, SyntraFlow maintains one core partial receipt scenario and allows Jarvis AI to generate quantity-driven, sequential and receiving-organization-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Partial Receipt 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

25% receipt of the ordered quantity
50% receipt of the ordered quantity
Multiple partial receipts against the same purchase order line
Partial receipt followed by a final receipt that closes the remaining open quantity
Multi-line partial receipt across several purchase order lines

Negative Scenarios

Received quantity greater than the open quantity
Zero or negative received quantity
Invalid purchase order line
Receipt attempted against a closed purchase order
Invalid receipt date

These are representative examples only. Negative-scenario behavior and available receipt quantities can depend on the customer's Oracle Fusion configuration, tolerances and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every purchase order, item, quantity and receiving-organization combination in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct partial receipt scenarios relevant to the customer's actual implementation.

Standard Library Definition

PO Number               ${PO_NUMBER}
PO Line                 ${PO_LINE}
Item                    ${ITEM}
Ordered Quantity        ${ORDERED_QUANTITY}
Partial Received Qty    ${PARTIAL_RECEIVED_QUANTITY}
Remaining Open Qty      ${REMAINING_OPEN_QUANTITY}
Unit of Measure         ${UNIT_OF_MEASURE}
Receiving Organization  ${RECEIVING_ORGANIZATION}

DataVault

Purchase Orders
  Approved POs with open quantity
Items
  Items valid for receiving
Quantities
  Partial quantity below the PO line's open quantity
Receiving Organizations
  Configured receiving organizations available to the test user

Jarvis AI Generates

Scenario 01 — PO-1001 + Line 1 + 25% Receipt
Scenario 02 — PO-1001 + Line 1 + 50% Receipt
Scenario 03 — PO-2004 + Multiple Sequential Partial Receipts
Scenario 04 — Partial Receipt + Final Receipt
Scenario 05 — Received Quantity Exceeds Open Quantity
Scenario 06 — Closed Purchase Order
...

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 purchase order, item, quantity and receiving organization remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of partial receipt scenarios Jarvis can generate from this business scenario, spanning receipt quantity, sequencing and balance 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	Partial Receipt — 25% of Ordered Quantity	Amount	Received quantity set to 25% of the ordered quantity	Syntra Ready
VAR-002	Partial Receipt — 50% of Ordered Quantity	Amount	Received quantity set to 50% of the ordered quantity	Syntra Ready
VAR-003	Partial Receipt — Other Percentage	Amount	Customer-defined partial quantity entered	Syntra Ready
VAR-004	Partial Receipt — Small Quantity Near Rounding Threshold	Amount/Balance	Small partial quantity used to confirm open-quantity rounding is handled correctly	Syntra Ready
VAR-005	Partial Receipt — Large Percentage (90%)	Amount	Received quantity set close to the full ordered quantity	Syntra Ready
VAR-006	Multiple Partial Receipts Against Same PO Line	Multi-Step	Two or more partial receipts recorded against the same purchase order line over time	Syntra Ready
VAR-007	Partial Receipt Followed by Final Receipt	Multi-Step/Balance	Remaining open quantity closed by a subsequent final receipt	Syntra Ready
VAR-008	Multi-Line Partial Receipt	Multi-Step	Partial receipt recorded across two or more purchase order lines in the same transaction	Syntra Ready
VAR-009	Partial Receipt Leaving Open Quantity for Later Use	Balance	Purchase order line retains open quantity after the partial receipt	Syntra Ready
VAR-010	Partial Receipt — Alternate Receiving Organization	Amount	Receipt processed against a different configured receiving organization	Syntra Ready
VAR-011	Received Quantity Greater Than Open Quantity	Negative/Balance	Entered quantity exceeds the purchase order line's open quantity	Syntra Ready
VAR-012	Zero or Negative Received Quantity	Negative/Amount	Received quantity entered as zero or a negative value	Syntra Ready
VAR-013	Invalid Purchase Order Line	Negative	Receipt attempted against a purchase order line that does not exist or is not eligible	Syntra Ready
VAR-014	Closed Purchase Order	Negative	Purchase order selected for receipt is already closed	Syntra Ready
VAR-015	Invalid Receipt Date	Negative	Receipt date entered falls outside an open or valid receiving period	Syntra Ready

Automatically Expand Positive and Negative Partial Receipt Coverage

Positive Testing

Jarvis generates scenarios using received quantities and sequencing expected to successfully record a partial receipt against an eligible purchase order line while leaving Oracle Fusion's remaining open quantity calculation accurate.

Valid Purchase Order + Valid Line + 50% Received Quantity → Receipt Processed and Remaining Open Quantity Correctly Calculated

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around received quantity, purchase order status, line eligibility and receipt date.

Quantity Exceeds Open Quantity → Expected Over-Receipt Validation
Zero or Negative Quantity → Expected Quantity Validation
Invalid Purchase Order Line → Expected Line Eligibility Validation
Closed Purchase Order → Expected PO Status Validation
Invalid Receipt Date → Expected Period 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 partial-receipt scenarios and group them into reusable execution packs.

Procurement Partial Receipt Regression Pack

Partial Receipt — 25% of Ordered Quantity
Partial Receipt — 50% of Ordered Quantity
Partial Receipt — Other Percentage
Multiple Partial Receipts Against Same PO Line
Partial Receipt Followed by Final Receipt
Multi-Line Partial Receipt
Received Quantity Greater Than Open Quantity
Zero or Negative Received Quantity
Closed Purchase Order
Invalid Receipt Date

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

Once scheduled, SyntraFlow executes the selected partial-receipt 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	Procurement Partial Receipt 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

Access to receiving functions in Oracle Fusion Procurement is governed by job-role and duty-role security. Jarvis can generate persona-based variations confirming that only appropriately provisioned users can record a partial receipt.

Persona	Action	Expected	Syntra Result
Receiving Clerk	Receive Partial Quantity	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 partial receipt 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 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 — Partial Receipt, 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 Eligible Purchase Order

May internally include

Open Receipt Search → Enter PO Number → Enter PO Line → Search → Select Purchase Order Line → Confirm

Business Step

Review Resulting Remaining Open Quantity Before Submitting

May internally include

Open Receipt Preview → Read Calculated Remaining Open Quantity → Compare Against Expected Value

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 remaining open quantity was calculated correctly — 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 Partial Received Quantity	Pass	—
Submit and Confirm the Receipt	Pass	—
Verify Remaining Open Quantity Matches Expected Calculation	Pass	Pass

Related Receiving Tests

Partial Receipt is one way of recording quantity received within the same Receiving process — explore the related receive, correct and exception-handling scenarios below.

Receive Purchase Order Correct Receipt Receiving Exceptions

Turn This Standard Test into Your Oracle Procurement Receiving Regression Suite

Start with the Syntra Standard partial receipt test, use DataVault to provide environment-specific test data, let Jarvis generate additional quantity, sequencing and receiving-organization 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

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

Frequently Asked Questions

What does this Oracle Fusion Partial Receipt test validate?

It validates that a partial receipt can be recorded against an eligible purchase order line in Oracle Fusion Procurement, and that the resulting remaining open quantity is calculated and recorded correctly after the receipt is processed.

How are 25%, 50% and other percentage variations 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. This keeps a single canonical URL for all partial-receipt percentage variations while still exercising each distinct amount.

Are multiple partial receipts against the same purchase order line supported?

Yes. Jarvis AI can generate variations covering multiple sequential partial receipts, including a scenario where a partial receipt is followed by a further receipt that fully consumes the remaining open quantity.

How is the remaining open quantity calculated?

Remaining Open Quantity equals Ordered Quantity minus Received Quantity. The test verifies this value as recorded by Oracle Fusion Procurement after the receipt is processed, not merely as entered inputs.

Does this test use real customer data?

The public Syntra Standard Test Library uses illustrative test data. Where DataVault is connected, customer-specific dimensions such as purchase order, item, quantity and receiving organization can be used, protected according to DataVault's data policies.