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

Syntra Standard Oracle Test Library

Oracle Fusion Correct Receipt Test Cases

Validate that an eligible Oracle Fusion receipt can be corrected within allowed business rules — quantity or other eligible receipt details — while the related purchase order balance updates correctly and the receipt's audit history retains a record of the correction.

Test ID	ORCL.P2P.PROC.RCV.CORRECT
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 18 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a posted Oracle Fusion receipt can be corrected — adjusting the received quantity or other eligible detail — within the business rules and tolerances configured for the receiving transaction, while the related purchase order balance and the receipt's audit history remain accurate.

The scenario should confirm that:

a receipt eligible for correction can be located and opened by an authorized user
the corrected quantity or detail is accepted without unexpected validation errors, when within allowed limits
the corrected quantity is retained on the receipt once the correction is submitted
the related purchase order's open balance is updated to reflect the corrected quantity
a record of the correction is retained in the receipt's audit or transaction history rather than silently overwritten
corrections outside allowed limits or attempted by unauthorized users are correctly prevented

This scenario covers correcting an existing Oracle Fusion receipt within Procurement TEST/UAT environments. It does not cover the original receipt creation, which is covered by the separate Partial Receipt scenario, or returning received goods to a supplier, which is covered by the separate Return to Supplier scenario. Field-level correction variations such as quantity increase, decrease or multi-line correction 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 receipt correction limits and purchase order balance updates for a new Oracle Fusion Procurement implementation
Regression testing of receipt correction behavior after an Oracle quarterly update
UAT sign-off for receiving clerks who routinely correct quantities entered in error
Baseline case referenced by the partial receipt, return and receiving exceptions scenarios within the same receiving process

Where This Test Fits in the Receiving Process

Receive

→

Inspect

→

Correct

→

Return

→

Match

Correct Receipt applies to a receipt transaction that has already been recorded, adjusting the received quantity or other eligible detail rather than creating a new receipt or returning goods to the supplier. Exact correction limits, eligible statuses and required approvals depend on receipt status, downstream matching or accounting activity, and customer configuration.

Preconditions

A receipt exists and is in a status that is eligible for correction.
The corrected quantity or detail entered is valid and within the tolerances configured for the test tenant.
The user performing the correction has the appropriate receiving correction privileges.
The test user has permission to open and correct receipts in Oracle Fusion Procurement.

Exact eligible statuses, quantity tolerances and validation messages may vary by Oracle Fusion implementation, receiving configuration and security setup.

Sample Test Data

Business Unit	${BUSINESS_UNIT}
Receipt Number	${RECEIPT_NUMBER}
PO Number	${PO_NUMBER}
Item	${ITEM}
Original Quantity	${ORIGINAL_QUANTITY}
Corrected Quantity	${CORRECTED_QUANTITY}
Correction Reason	${CORRECTION_REASON}

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

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~18 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion using an authorized Procurement test user.	Oracle Fusion signs the user in successfully and the home page loads.
2	Navigate to the Receipt Navigate to the Receiving work area and search for the receipt eligible for correction. ${RECEIPT_NUMBER} / ${PO_NUMBER} This single business step replaces multiple technical actions such as opening receipt search, entering the receipt number, and selecting the result.	The correct receipt is located and its current quantities and status are displayed.
3	Initiate the Correction Select the option to correct the located receipt.	The receipt correction page opens showing the current received quantity and detail values.
4	Enter the Corrected Quantity Enter the corrected quantity or other eligible detail relevant to this variation. ${CORRECTED_QUANTITY}	The corrected value is accepted without unexpected validation errors.
5	Review Resulting PO Balance Review the purchase order's resulting open balance based on the entered correction before submitting. Reviewing the resulting balance before submitting lets the tester catch an incorrect entry before it is committed.	The projected purchase order balance reflects the correction that is about to be submitted.
6	Submit the Correction Submit and save the receipt correction in the test environment.	Oracle Fusion successfully saves the correction without unexpected errors.
7	Verify Corrected Quantity RetainedBusiness assertion Reopen or refresh the receipt and confirm the corrected quantity is present. This is a primary business assertion for the scenario — a correctly retained quantity is the expected pass condition, not merely a successful save.	The receipt reflects the corrected quantity accurately.
8	Verify Audit History Reflects the CorrectionBusiness assertion Review the receipt's audit or transaction history after the correction is saved.	The audit or transaction history retains a record of both the original and corrected values.

Expected Results

The corrected quantity or detail is accepted without unexpected errors, when within allowed limits.
The receipt reflects the corrected quantity accurately once the correction is submitted.
The related purchase order's open balance is updated to reflect the corrected quantity.
A record of the correction is retained in the receipt's audit or transaction history.
Corrections that exceed the purchase order's ordered quantity or violate configured tolerances are correctly prevented.
Unauthorized correction attempts are correctly prevented.

Key Validation Checkpoints

Corrected quantity is retained on the receipt.
Purchase order balance is updated to reflect the correction.
Audit or transaction history retains a record of the correction.

Core Business Scenario

Correct 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 correct-receipt business scenario. Jarvis AI can extend this scenario by generating additional quantity, 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 direction a receipt quantity can be corrected, or for every status and permission combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable correct-receipt business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative + Boundary + Security Test Variations

Valid correction scenarios alongside edge cases such as over-tolerance corrections, ineligible receipts and unauthorized users.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

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

Results + Evidence + Exceptions

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

Rather than maintaining a separate test page for every direction and context a receipt quantity can be corrected in, SyntraFlow maintains one core correct-receipt scenario and allows Jarvis AI to generate quantity-driven, status and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Increase the received quantity on a receipt
Decrease the received quantity on a receipt
Correct a partial receipt
Correct a multi-line receipt

Negative Scenarios

Invalid quantity entered for the correction
Correction exceeds the purchase order's ordered quantity
Receipt not eligible for correction
Invalid correction date or receipt status
Unauthorized user attempts a correction

These are representative examples only. Negative-scenario behavior and available correction types 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 receipt, purchase order, item and tolerance combination in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct correct-receipt scenarios relevant to the customer's actual implementation.

Standard Library Definition

Business Unit        ${BUSINESS_UNIT}
Receipt Number        ${RECEIPT_NUMBER}
PO Number             ${PO_NUMBER}
Item                  ${ITEM}
Original Quantity     ${ORIGINAL_QUANTITY}
Corrected Quantity    ${CORRECTED_QUANTITY}
Correction Reason     ${CORRECTION_REASON}

DataVault

Receipts
  Posted receipts eligible for correction
Purchase Orders
  Open purchase orders with remaining balance
Items
  Active items with valid quantity ranges
Suppliers
  Active suppliers eligible for assignment
Receiving Tolerances
  Configured quantity tolerance rules per Business Unit

Jarvis AI Generates

Scenario 01 — RCPT-2001 + Increase Quantity
Scenario 02 — RCPT-2001 + Decrease Quantity
Scenario 03 — RCPT-2044 + Correct Partial Receipt
Scenario 04 — RCPT-2077 + Correct Multi-Line Receipt
Scenario 05 — Correction Exceeds PO Quantity
Scenario 06 — Unauthorized User Attempts Correction
...

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

Example Test Variations

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

ID	Variation	Type	Key Difference	Execution
VAR-001	Increase Receipt Quantity	Positive/Direction	Quantity corrected upward within the purchase order's ordered quantity	Syntra Ready
VAR-002	Decrease Receipt Quantity	Positive/Direction	Quantity corrected downward to match the physical count	Syntra Ready
VAR-003	Correct Partial Receipt	Positive/Status	Correction applied to a receipt recorded across multiple partial deliveries	Syntra Ready
VAR-004	Correct Multi-Line Receipt	Positive/Status	Correction applied across more than one receipt line	Syntra Ready
VAR-005	Correct Receipt Item Detail	Positive/Direction	An eligible non-quantity detail corrected on the receipt line	Syntra Ready
VAR-006	Correct Receipt Unit of Measure	Positive/Direction	Unit of measure corrected on the receipt line	Syntra Ready
VAR-007	Invalid Quantity Entered	Negative/Direction	Corrected quantity entered is not a valid numeric value	Syntra Ready
VAR-008	Correction Exceeds PO Quantity	Negative/Status	Corrected quantity entered exceeds the purchase order's ordered quantity	Syntra Ready
VAR-009	Receipt Not Eligible for Correction	Negative/Status	Correction attempted on a receipt outside the eligible correction window	Syntra Ready
VAR-010	Invalid Correction Date	Negative/Status	Correction attempted using a date outside a valid or open period	Syntra Ready
VAR-011	Receipt Already Matched	Negative/Status	Correction attempted on a receipt already matched or accounted	Syntra Ready
VAR-012	Unauthorized Correction Attempt	Negative/Status	A user without correction privileges attempts to correct the receipt	Syntra Ready
VAR-013	Invalid Item on Corrected Line	Negative/Direction	Corrected line references an item that is inactive or not configured	Syntra Ready

Automatically Expand Positive and Negative Correct Receipt Coverage

Positive Testing

Jarvis generates scenarios using quantities and statuses expected to successfully correct an eligible receipt while keeping the purchase order balance and audit history accurate.

Eligible Receipt + Valid Corrected Quantity + Within PO Balance → Correction Accepted and History Preserved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around receipt status, quantity limits and user authorization.

Invalid Quantity Entered → Expected Quantity Validation
Correction Exceeds PO Quantity → Expected Quantity Validation
Receipt Not Eligible for Correction → Expected Status Validation
Invalid Correction Date or Status → Expected Status 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 correct-receipt scenarios and group them into reusable execution packs.

Correct Receipt Regression Pack

Increase Receipt Quantity
Decrease Receipt Quantity
Correct Partial Receipt
Correct Multi-Line Receipt
Correct Receipt Unit of Measure
Correction Exceeds PO Quantity
Receipt Not Eligible for Correction
Receipt Already Matched
Unauthorized Correction Attempt

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

Once scheduled, SyntraFlow executes the selected correct-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	Correct Receipt Regression Pack
Schedule	Quarterly Update Regression
Tests	13 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

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

Persona	Action	Expected	Syntra Result
Receiving Clerk	Correct Own Receipt	Allowed	PASS
Unauthorized User	Attempts Correct 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 correct-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, Negative, Boundary and Security variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Library — Correct 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 Receipt

May internally include

Open Receipt Search → Enter Receipt Number → Search → Select Receipt → Confirm

Business Step

Verify Audit History Reflects the Correction

May internally include

Open Receipt Transaction History → Read Prior Value → Read Corrected Value → Compare Against Expected Change

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 corrected quantity was retained or the purchase order balance updated — 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 the Corrected Quantity	Pass	—
Submit the Correction	Pass	—
Verify Corrected Quantity Retained	Pass	Pass

Related Receiving Tests

Correct Receipt applies to a receipt that already exists within the same receiving process — explore the related partial receipt, return and exceptions scenarios below.

Partial Receipt Return to Supplier Receiving Exceptions

Turn This Standard Test into Your Oracle Receiving Regression Suite

Start with the Syntra Standard correct-receipt test, use DataVault to provide environment-specific test data, let Jarvis generate additional quantity, status and security 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 Test Library Syntra DataVault

Frequently Asked Questions

What corrections are typically allowed to an existing Oracle Fusion receipt?

Depending on receipt status and customer configuration, allowed corrections commonly include adjusting the received quantity upward or downward within configured tolerances, and correcting certain line-level details. Availability of each correction type depends on the customer's Oracle Fusion setup and whether the receipt has already been matched or accounted.

What is the difference between correcting a receipt and returning it to the supplier?

A correction adjusts a receipt entry error, such as a quantity keyed incorrectly, without physically moving goods. A return to supplier reflects goods being physically sent back and is covered by the separate Return to Supplier scenario. This test focuses only on the correction path.

What happens to the purchase order balance after a receipt correction?

Where the correction is accepted, the related purchase order's open balance is updated to reflect the corrected quantity, so downstream matching and remaining-quantity calculations stay consistent with the corrected receipt.

How is security testing approached for receipt corrections?

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