Oracle Fusion Inspect Receipt Test Cases
Validate receipt inspection where inspection routing or configuration is enabled — reviewing the received quantity, recording accepted and rejected quantities, capturing inspection notes, and confirming inspection status and downstream inventory or return processing.
| Test ID | ORCL.P2P.PROC.RCV.INSPECT |
| 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 | Medium |
| 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 21 underlying Oracle Fusion UI actions to complete it.
Test Objective
Validate receipt inspection where inspection routing or configuration is enabled for the applicable item or purchase order — including review of the received quantity, recording of accepted and rejected quantities against the inspection, capture of inspection notes or a rejection reason, submission of the inspection decision, and confirmation that inspection status and downstream inventory or return processing reflect the recorded outcome.
The scenario should confirm that:
- a receipt pending inspection can be opened and reviewed by an authorized inspector
- accepted and rejected quantities can be recorded against the inspection and are accepted by Oracle Fusion
- accepted and rejected quantities sum correctly to the received quantity
- inspection notes or a rejection reason can be captured where applicable
- inspection status updates correctly following the inspection decision
- accepted quantity is correctly made available for downstream inventory processing
- rejected quantity is correctly routed to the applicable return path, where configured
- users without appropriate access cannot complete a receipt inspection
This scenario does not claim that every Oracle Fusion customer uses receipt inspection, nor that every inspection routing rule or disposition outcome is exercised — coverage depends on whether inspection routing is implemented and configured for the applicable item or purchase order.
When to Use This Test
- Functional testing of a new Oracle Fusion Procurement inspection routing implementation, where the feature is configured
- Regression testing after an Oracle quarterly update
- UAT sign-off for receiving inspection workflows and access control
- Baseline case referenced by receiving, return-to-supplier and receiving-exception scenarios within the same lifecycle
Where This Test Fits in the Receiving Process
Where inspection routing is configured for an item or purchase order, inspection typically occurs after the receipt is created and before the received quantity is available for putaway or further processing. Not every Oracle Fusion customer configures or requires receipt inspection.
Preconditions
- Oracle Fusion Procurement access is configured and available for the test user.
- The item or purchase order line is configured for inspection routing, where inspection is implemented.
- A receipt exists for the item and is pending inspection.
- An inspector is assigned with appropriate access to complete receipt inspections.
- Inventory and return-to-supplier routing configuration exists for accepted and rejected quantities, where applicable.
Exact inspection routing rules, tolerance levels and return-to-supplier configuration vary by Oracle Fusion implementation. Receipt inspection is not used by every Oracle Fusion customer, and this test applies only where inspection routing is implemented and configured.
Sample Test Data
| Receipt Number | ${RECEIPT_NUMBER} |
| Item | ${ITEM} |
| Received Quantity | ${RECEIVED_QUANTITY} |
| Accepted Quantity | ${ACCEPTED_QUANTITY} |
| Rejected Quantity | ${REJECTED_QUANTITY} |
| Inspector | ${INSPECTOR} — user assigned to complete the inspection |
| Inspection Notes / Reason | ${INSPECTION_NOTES} — required for rejected or partially rejected quantities, where configured |
Inspection routing, tolerance levels and disposition rules are defined per Oracle Fusion customer implementation. This test intentionally uses placeholders such as ${ACCEPTED_QUANTITY} and ${REJECTED_QUANTITY} rather than fixed values — actual values should be sourced from DataVault or the customer's receiving configuration, where receipt inspection is implemented.
Test Steps
8 business-readable steps. SyntraFlow's automation executes ~21 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Sign In Sign in to Oracle Fusion as the user responsible for completing receipt inspections. ${INSPECTOR} | The user signs in successfully and lands on the home page. |
| 2 | Navigate to Pending Inspections Navigate to the Receiving work area and open the list of receipts pending inspection. | The list of receipts pending inspection displays for the applicable inspector. |
| 3 | Open the Receipt Open the specific receipt that is pending inspection. ${RECEIPT_NUMBER} This single business step replaces multiple technical actions such as locating the receipt and opening the inspection entry page. | The receipt opens showing the item and received quantity awaiting inspection. |
| 4 | Review Received Quantity Review the item and received quantity recorded on the receipt. ${ITEM} / ${RECEIVED_QUANTITY} | Item and received quantity details are displayed accurately for inspection. |
| 5 | Enter Accepted and Rejected Quantities Enter the accepted and rejected quantities resulting from the inspection. ${ACCEPTED_QUANTITY} / ${REJECTED_QUANTITY} | Accepted and rejected quantities are accepted by Oracle Fusion without unexpected errors. |
| 6 | Enter Inspection Notes or Reason Enter inspection notes or a rejection reason, where applicable to the inspection outcome. ${INSPECTION_NOTES} | Notes or a rejection reason are recorded against the inspection. |
| 7 | Submit Inspection Submit the completed inspection decision. | The inspection is submitted without unexpected errors. |
| 8 | Verify Accepted/Rejected Quantities and Downstream StatusBusiness assertion Confirm the accepted and rejected quantities, inspection status, and downstream inventory or return-to-supplier processing reflect the recorded inspection outcome. ${ACCEPTED_QUANTITY} / ${REJECTED_QUANTITY} This is the main business assertion for the scenario — the test does not stop merely because the inspection submission was accepted successfully. | Accepted quantity is correctly available for downstream inventory processing and rejected quantity is correctly routed to the applicable return path, with inspection status updated to reflect the decision. |
Expected Results
- Received quantity and item details are correctly displayed for a receipt pending inspection.
- Accepted and rejected quantities can be recorded and sum correctly to the received quantity.
- Inspection notes or a rejection reason are captured where applicable to the outcome.
- The inspection is submitted and inspection status updates accordingly.
- Accepted quantity is correctly made available downstream for inventory processing.
- Rejected quantity is correctly routed to the applicable return-to-supplier path, where configured.
- Users without appropriate access cannot complete a receipt inspection.
Key Validation Checkpoints
- Accepted and rejected quantities are recorded correctly and sum to the received quantity.
- Inspection status updates correctly following the inspection decision.
- Downstream inventory and/or return-to-supplier routing reflects the recorded inspection outcome.
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core receipt inspection business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.
Teams do not need to manually duplicate the same inspection test dozens of times simply to cover different items, quantities and inspection outcomes. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's configured inspection routing, where receipt inspection is implemented.
From Standard Test to Executed Regression Pack
Rather than maintaining dozens of near-duplicate copies of the same inspection test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available receiving configuration — sourced from DataVault or customer configuration, and only where receipt inspection is implemented.
AI-Generated Test Variations
The same Inspect 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.
- Accept all received quantity
- Reject all received quantity
- Partial accept / partial reject
- Different inspection outcomes
- Different items
- Item not eligible for inspection
- Invalid quantity entered
- Inspection quantity exceeds received quantity
- Missing inspection reason
- Unauthorized user attempts inspection
These are representative examples only. Inspection routing, tolerance levels and expected behavior depend on the customer's Oracle Fusion configuration — receipt inspection is not used by every Oracle Fusion customer, and inspection data is never hard-coded; it is sourced from DataVault or the customer's configuration where available.
Generated Using Your DataVault Test Data
Generic test data cannot represent a real Oracle Fusion receiving configuration. Where connected, Jarvis can use approved test data available through Syntra DataVault — item, receipt, quantities and inspector — to create variations relevant to the customer's actual implementation, where receipt inspection is configured.
Standard Library Definition
Receipt Number ${RECEIPT_NUMBER}
Item ${ITEM}
Received Quantity ${RECEIVED_QUANTITY}
Accepted Quantity ${ACCEPTED_QUANTITY}
Rejected Quantity ${REJECTED_QUANTITY}
Inspector ${INSPECTOR}
Inspection Notes / Reason ${INSPECTION_NOTES}
DataVault
Items Item A (Inspection Required) Item B (Inspection Required) Receipts Receipt 1001 Receipt 1002 Inspectors Inspector A Inspector B Inspection Outcomes Accepted Rejected Partial Accept / Reject Pending Review
Jarvis AI Generates
Scenario 01 — Item A + Accept All Scenario 02 — Item A + Reject All Scenario 03 — Item B + Partial Accept/Reject Scenario 04 — Item Not Eligible for Inspection Scenario 05 — Inspection Quantity Exceeds Received Quantity Scenario 06 — Unauthorized User Attempts Inspection ...
Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Receiving configuration — including inspection routing, tolerance levels and return-to-supplier rules — is customer-specific and, where DataVault is connected, is sourced from DataVault or the customer's own configuration rather than assumed by SyntraFlow.
Example Test Variations
Representative examples of scenarios Jarvis can generate from this business scenario. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| VAR-001 | Accept All Received Quantity | Positive/Outcome | Full received quantity accepted; nothing rejected | Syntra Ready |
| VAR-002 | Reject All Received Quantity | Positive/Outcome | Full received quantity rejected; nothing accepted | Syntra Ready |
| VAR-003 | Partial Accept / Partial Reject | Positive/Outcome | Received quantity split between accepted and rejected | Syntra Ready |
| VAR-004 | Inspection Outcome — Pending Review | Positive/Outcome | Inspection recorded but held for further review before final disposition | Syntra Ready |
| VAR-005 | Item — Item A | Positive/Item | Inspection completed against Item A | Syntra Ready |
| VAR-006 | Item — Item B | Positive/Item | Inspection completed against Item B | Syntra Ready |
| VAR-007 | Accepted Quantity Routed to Inventory | Positive/Outcome | Accepted quantity confirmed available in the applicable inventory location | Syntra Ready |
| VAR-008 | Rejected Quantity Routed to Return to Supplier | Positive/Outcome | Rejected quantity confirmed routed to the return-to-supplier path, where configured | Syntra Ready |
| VAR-009 | Item Not Eligible for Inspection | Negative/Item | Inspection attempted against an item not configured for inspection routing | Syntra Ready |
| VAR-010 | Invalid Quantity Entered | Negative | Accepted or rejected quantity entered as a non-numeric or negative value | Syntra Ready |
| VAR-011 | Inspection Quantity Exceeds Received Quantity | Negative/Outcome | Combined accepted and rejected quantity entered greater than the received quantity | Syntra Ready |
| VAR-012 | Missing Inspection Reason | Negative | Rejected quantity submitted without a required inspection reason | Syntra Ready |
| VAR-013 | Unauthorized User Attempts Inspection | Negative | A user without inspector access attempts to complete a receipt inspection | Syntra Ready |
No variations match this filter.
Automatically Expand Positive and Negative Test Coverage
Positive Testing
Jarvis generates scenarios using combinations expected to successfully complete the receipt inspection business process, where inspection routing is enabled.
Receipt + ${ITEM} + Accepted/Rejected Quantities Entered → Inspection Status Updated and Downstream Routing Correct
Negative Testing
Jarvis can generate scenarios designed to exercise Oracle's receiving validations, quantity checks and access controls.
- Item Not Eligible for Inspection → Expected Configuration Validation
- Invalid Quantity Entered → Expected Field Validation
- Inspection Quantity Exceeds Received Quantity → Expected Quantity Validation
- Missing Inspection Reason → Expected Submission Validation
- Unauthorized User Attempts Inspection → Expected Access Validation
A negative receiving scenario passes when Oracle correctly raises the expected validation.
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Valid receipt | Receipt created | PASS |
| Closed PO | PO status validation occurs | PASS |
| Over receipt | Quantity validation occurs | PASS |
| Security restriction | Access prevented | PASS |
| Unexpected application exception | Unexpected failure | FAIL |
Turn AI-Generated Variations into a Regression Pack
Users can select generated scenarios and group them into reusable execution packs.
Inspect Receipt Regression Pack
- Accept All Received Quantity
- Reject All Received Quantity
- Partial Accept / Partial Reject
- Item — Item A
- Item — Item B
- Accepted Quantity Routed to Inventory
- Rejected Quantity Routed to Return to Supplier
- Item Not Eligible for Inspection
- Inspection Quantity Exceeds Received Quantity
- Unauthorized User Attempts Inspection
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected scenarios unattended and records the outcome of each test and business assertion.
| Pack | Inspect 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.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
Security & Persona Variations
SyntraFlow validates receipt inspection access control by confirming that an assigned inspector can complete a receipt inspection, and that an unauthorized user is correctly prevented from completing one.
| Persona | Action | Expected | Syntra Result |
|---|---|---|---|
| Inspector | Complete Inspection | Allowed | PASS |
| Unauthorized User | Attempts Inspection | 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.
From Business Scenario to Execution Evidence
Business teams get readable test documentation; automation teams retain detailed execution traceability.
Meet Jarvis — SyntraFlow's AI Testing Engine
Jarvis extends the Syntra Standard Test Library by analysing the business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment, including Positive, Negative, Boundary and Security variations relative to the customer's configured inspection routing.
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.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
Action Status vs. Business Validation
A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.
| Step | Action Status | Business Validation |
|---|---|---|
| Submit Inspection | Pass | — |
| Confirm Status Update Accepted | Pass | — |
| Verify Accepted/Rejected Quantities and Downstream Status | Pass | Pass |
Related Receiving Tests
Receipt inspection is one stage of the broader receiving lifecycle — explore the related receipt creation, return and exception-handling scenarios below.
Turn This Standard Test into Your Oracle Inspect Receipt Regression Suite
Start with the Syntra Standard receipt inspection test, use DataVault to provide environment-specific item and inspection configuration, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.
Use This Oracle Fusion Test Case
Download Test Case
Excel, CSV or JSON export.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.