Oracle ERP Testing Tool > Test Library > SCM > Procurement > Purchase Orders

Syntra Standard Oracle Test Library

Oracle Fusion Close Purchase Order Test Cases

Validate manual or business-driven closure of an eligible purchase order or purchase order line in Oracle Fusion Procurement, and confirm the resulting status change and downstream processing impact.

Test ID	ORCL.P2P.PROC.PO.CLOSE
Application	Oracle Fusion Cloud
Product	SCM / Procurement
Module	Procurement
Process	Purchase Orders
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 7 business-readable test steps; SyntraFlow's automation executes approximately 16 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorized Procurement user can manually close an eligible purchase order, or a specific line within it, in Oracle Fusion, and confirm the resulting status and downstream impact — separately from the business-driven closure that Oracle can apply automatically once a line is fully fulfilled.

The scenario should confirm that:

the selected purchase order or purchase order line is eligible for closure
a full purchase order can be closed, and a single line can be closed independently on a multi-line purchase order
closure can be applied for receiving, for invoicing, or for both, where the customer's configuration supports it
the purchase order or line status correctly updates to Closed
a closed purchase order or line is no longer available for further receiving or invoicing where that restriction is expected
the closure is retained in purchase order history rather than removing the record

This scenario does not claim that every downstream receiving, invoicing or budgetary-control interaction is covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test scenarios.

When to Use This Test

Functional testing of Oracle Fusion Procurement close-purchase-order processing for a new implementation
Regression testing of closure eligibility, status and security validations after an Oracle quarterly update
UAT sign-off for purchase order controls that must correctly restrict and record closures
Closing scenario referenced alongside cancel, inquiry and change scenarios within the same purchase order lifecycle

Where This Test Fits in the Purchase Order Lifecycle

Create Purchase Order

→

Approve Purchase Order

→

Receive / Invoice

→

Change (Optional)

→

Close Eligible Purchase Order

→

Purchase Order Closed

This test covers manual or business-driven closure of a purchase order or purchase order line that has reached an eligible status, and represents one of the terminal actions available once fulfillment activity has reached an acceptable point. Exact eligibility rules and downstream impact depend on the customer's Oracle Fusion configuration.

← Previous Stage

Create Purchase Order

Preconditions

Oracle Fusion Procurement Purchase Orders is configured and available to the test user.
An existing purchase order exists, with at least one line in a status eligible for closure.
No blocking open obligations remain against the purchase order or line, such as an outstanding receipt or unmatched invoice, where the customer's configuration treats these as blocking.
The purchase order or line has not already been closed.
The test user has the appropriate security/privilege to close purchase orders.

Exact closure eligibility rules and security privileges may vary by Oracle Fusion implementation and configuration.

Sample Test Data

Purchase Order Number	${PO_NUMBER}
Line Number	${LINE_NUMBER}
PO/Line Status	Open / Partially Received / Fully Received / Invoiced — eligible for closure
Closure Scope	Full Purchase Order or Specific Line
Close Reason	${CLOSE_REASON}
Buyer	${BUYER}

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.

Test Steps

7 business-readable steps. SyntraFlow's automation executes ~16 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 Cloud with a user that holds purchase order closure privileges. ${BUYER}	The user successfully signs in and lands on the Oracle Fusion home page.
2	Navigate to the Purchase Order Navigate to the Purchase Orders work area and search for the target purchase order. ${PO_NUMBER} This single business step replaces multiple technical actions such as opening search, entering the purchase order number, clicking Search and selecting the result.	The correct purchase order is located and its current status and lines are displayed.
3	Verify Eligibility for Closure Review the purchase order or line status and any open obligations to confirm it is eligible for closure. ${LINE_NUMBER}	The purchase order or line is confirmed as eligible for closure, with no unresolved blocking obligations.
4	Select Close (Full Purchase Order or Line) Select the Close action for the full purchase order, or for a specific line where only a line-level closure is required, and enter a close reason where applicable. ${CLOSE_REASON}	The Close Purchase Order (or Close Line) page or dialog opens for the selected scope and accepts the close reason without unexpected validation errors.
5	Confirm Closure Confirm and submit the closure.	Oracle Fusion successfully processes the closure request without unexpected errors.
6	Verify Status UpdatedBusiness assertion Confirm the purchase order's or line's status following the closure.	Purchase order or line status updates to Closed, with the close reason correctly recorded where applicable.
7	Verify Downstream Behavior Is CorrectBusiness assertion Confirm that the closed purchase order or line correctly restricts further receiving and/or invoicing as expected for the closure scope selected, while remaining visible in purchase order history. ${PO_NUMBER} This is the main business assertion for the scenario — a purchase order closure must be enforced downstream and must not silently remove purchase order history.	The closed purchase order or line correctly blocks the expected downstream activity — such as further receiving or invoicing — and remains traceable in history rather than being removed.

Expected Results

An eligible purchase order or purchase order line closes successfully.
Purchase order or line status updates correctly to Closed.
Close reason is correctly recorded where applicable.
A closed full purchase order and a closed single line both behave correctly and independently of other lines.
The closed purchase order or line correctly restricts further receiving and/or invoicing where that restriction is expected.
The closure remains traceable in purchase order history.
No unexpected save errors occur.
The closed purchase order or line does not silently disappear from history or reporting.

Key Validation Checkpoints

Purchase order or line closure status is correct.
Downstream receiving/invoicing behavior is correct.
Closure is retained in purchase order history.

Core Business Scenario

Close 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 close-purchase-order 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 close-purchase-order test dozens of times simply to cover different combinations of closure scope, fulfillment state and reason. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — purchase orders, buyers, line items and other relevant test attributes.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

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 dozens of near-duplicate copies of the same close-purchase-order test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Close 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 Purchase Orders.

Positive Scenarios

Close a completed purchase order
Close a single purchase order line
Close for receiving where the line is fully received
Close for invoicing where applicable and the line is fully invoiced
Close purchase orders across different fulfillment states

Negative Scenarios

Attempt to close a purchase order or line while open obligations remain
Attempt to close a purchase order or line in an invalid status
Closure attempted without the appropriate security/privilege
Attempt to close an already-closed purchase order or line
Attempt to close a purchase order or line with a pending transaction in progress

These are representative examples only. Negative scenarios and expected behavior 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 the full range of purchase order statuses, lines and buyers in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct close-purchase-order variations relevant to the customer's actual implementation.

Standard Library Definition

Purchase Order Number   ${PO_NUMBER}
Line Number              ${LINE_NUMBER}
Close Reason             ${CLOSE_REASON}
Buyer                    ${BUYER}

DataVault

Purchase Orders
  Open / Partially Received / Fully Received / Invoiced / Closed
Lines
  Single-Line, Multi-Line
Buyers
  Buyer A, Buyer B, Buyer C
Close Reasons
  Fully Received, Fully Invoiced, No Further Activity Expected, Business Closure

Jarvis AI Generates

Scenario 01 — Full Purchase Order Closure, Reason = Fully Received
Scenario 02 — Single-Line Closure on Multi-Line Purchase Order
Scenario 03 — Close for Receiving Only
Scenario 04 — Close for Invoicing Only
Scenario 05 — Already-Closed Purchase Order (Negative)
Scenario 06 — Open Obligation Closure Attempt (Negative)
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific data such as purchase order, buyer and line details remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of close-purchase-order 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	Close Fully Received Purchase Order	Positive/Fulfillment State	Entire purchase order closed after full receipt	Syntra Ready
VAR-002	Close Single Purchase Order Line	Positive	Only one line of a multi-line purchase order closed	Syntra Ready
VAR-003	Close for Receiving Only	Positive/Fulfillment State	Closure restricts further receiving only	Syntra Ready
VAR-004	Close for Invoicing Only	Positive/Fulfillment State	Closure restricts further invoicing only	Syntra Ready
VAR-005	Close Partially Fulfilled Purchase Order	Positive/Fulfillment State	Closure applied while line is partially received or invoiced	Syntra Ready
VAR-006	Close With Reason — Fully Received	Positive	Close reason = Fully Received	Syntra Ready
VAR-007	Close Multiple Lines Individually	Positive	Each line closed independently on the same purchase order	Syntra Ready
VAR-008	Close by Authorized Buyer	Positive	Closed by the assigned buyer	Syntra Ready
VAR-009	Attempt to Close With Open Obligation Remaining	Negative/Fulfillment State	An outstanding receipt or unmatched invoice remains against the line	Syntra Ready
VAR-010	Attempt to Close in an Invalid Status	Negative	Purchase order or line is in a status that does not support closure	Syntra Ready
VAR-011	Closure Attempted by Unauthorized User	Negative	User lacks the close-purchase-order privilege	Syntra Ready
VAR-012	Attempt to Close an Already-Closed Purchase Order	Negative	Purchase order or line status is already Closed	Syntra Ready

Why a Blocked Closure Attempt Can Be a Passing Test

Positive Testing

Jarvis generates scenarios using combinations expected to successfully close an eligible purchase order or purchase order line.

Eligible Purchase Order + No Open Obligations → Purchase Order Closed Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's closure eligibility rules, validations and security around purchase order closure.

Open Obligation Remains → Expected Blocking Validation
Invalid Purchase Order Status → Expected Status Validation
Unauthorized User → Expected Security Validation
Already-Closed Purchase Order → Expected Duplicate-Closure Validation
Pending Transaction in Progress → Expected Concurrency Validation

A negative scenario passes when Oracle correctly enforces the expected business rule or validation.

Scenario	Oracle Outcome	Test Result
Valid PO	Purchase order created	PASS
Inactive supplier	Supplier validation occurs	PASS
Invalid account	Account 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 close-purchase-order scenarios and group them into reusable execution packs.

Purchase Order Closure Regression Pack

Close Fully Received Purchase Order
Close Single Purchase Order Line
Close for Receiving Only
Close for Invoicing Only
Close Partially Fulfilled Purchase Order
Close Multiple Lines Individually
Attempt to Close With Open Obligation Remaining
Attempt to Close in an Invalid Status
Closure Attempted by Unauthorized User
Attempt to Close an Already-Closed Purchase Order

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

Once scheduled, SyntraFlow executes the selected close-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	Purchase Order Closure Regression Pack
Schedule	Quarterly Update Regression
Tests	12 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

Closing a purchase order is a control action. Jarvis can generate persona-based variations to confirm that only authorized users can close purchase orders, using role and privilege data available through DataVault.

Persona	Action	Expected	Syntra Result
Buyer	Close Own PO	Allowed	PASS
Unauthorized User	Attempts Close	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 business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment across Positive, Negative, Boundary and Security categories.

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 — Close Purchase Order, 7 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

Navigate to the Purchase Order

May internally include

Open Purchase Orders Work Area → Focus Search → Enter PO Number → Search → Select Purchase Order → Confirm Line Status

Business Step

Confirm Closure

May internally include

Review Closure Details → Click Confirm/Submit → Capture Confirmation Response → Refresh Purchase Order Status

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 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
Select Close (Full Purchase Order or Line)	Pass	—
Confirm Closure	Pass	—
Verify Downstream Behavior Is Correct	Pass	Pass

Related Purchase Order Tests

Closing a purchase order is one of several terminal and inquiry actions covered in this cluster — explore the related cancel, inquiry and create scenarios below.

Cancel Purchase Order Purchase Order Inquiry Create Purchase Order

Turn This Standard Test into Your Oracle Purchase Order Regression Suite

Start with the Syntra Standard close-purchase-order test, use DataVault to provide environment-specific test data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

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

Purchase Orders Test Library Procurement Test Library SCM Test Library Oracle Fusion Test Library Oracle ERP Testing Tool Syntra DataVault

Frequently Asked Questions

What qualifies a purchase order for closure?

A purchase order or purchase order line generally qualifies for closure once it has reached an eligible status — for example, fully received, fully invoiced, or otherwise past the point where further receiving or invoicing activity is expected — and has no blocking open obligations. Exact eligibility rules depend on the customer's Oracle Fusion configuration.

What is the difference between cancelling and closing a purchase order?

Cancelling a purchase order or line typically ends it before fulfillment has meaningfully occurred, and is usually restricted once receiving or invoicing has started. Closing is generally used once a purchase order or line has reached an acceptable point in fulfillment — such as fully received or fully invoiced — and is intended to stop further processing rather than reverse what has already occurred.

Can a closed purchase order be reopened?

In many Oracle Fusion configurations, a closed purchase order or line can be reopened by an authorized user if further receiving or invoicing is later required, subject to the customer's security and business-process rules. Where reopening is supported, it is typically covered by a separate reopen scenario rather than this closure test.

What security considerations apply to closing a purchase order?

Closing a purchase order is a control action that should be restricted to authorized users. This scenario includes a negative variation confirming that a user without the appropriate security/privilege is correctly prevented from closing a purchase order.

How does SyntraFlow help determine why a close-purchase-order test failed?

SyntraFlow's execution evidence is designed to help distinguish expected Oracle validations from genuine issues. For example: Close Purchase Order failed — likely category EXPECTED_VALIDATION — evidence: the purchase order has an open obligation pending — recommended action: this is typically expected behavior, and the open obligation should be resolved before attempting to close the purchase order. A failure should not be labeled an Oracle defect without supporting evidence.