Oracle ERP Testing Tool > Test Library > SCM > Order Management > Sales Orders

Syntra Standard Oracle Test Library

Oracle Fusion Create Order With Tax Test Cases

Validate that tax is calculated correctly on a sales order line in Oracle Fusion SCM Order Management, based on the customer, ship-to location and item tax classification as configured in the Oracle Fusion tax engine, without assuming universal jurisdiction or regime coverage.

Test ID	ORCL.O2C.OM.SO.TAX
Application	Oracle Fusion Cloud
Product	SCM / Order Management
Module	Order Management
Process	Sales Orders
Business Flow	Order-to-Cash
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 22 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that Oracle Fusion correctly calculates tax on a sales order line based on the customer, ship-to location and item tax classification as configured in the Oracle Fusion tax engine, and that the resulting line and order totals reflect that calculation accurately.

The scenario should confirm that:

tax is calculated using the customer, ship-to location and item tax classification as configured, not a hard-coded or assumed rate
the calculated tax amount, when added to the line amount, produces the correct line total
tax-exempt customers and tax-exempt item classifications are correctly excluded from tax calculation where configured
the order-level tax total correctly aggregates tax calculated across all order lines
Oracle correctly enforces validation when tax configuration is missing, ship-to jurisdiction cannot be determined, or unauthorized manual overrides are attempted

This scenario covers tax calculation on a standard sales order line in Oracle Fusion SCM Order Management TEST/UAT environments, using whatever tax regimes, rules and rates are configured in the target environment. It does not assert coverage of any specific tax jurisdiction or regime beyond what is configured, and does not cover the separate Create Sales Order, Create Order With Discount or Submit Sales Order scenarios in the same Sales Orders cluster.

When to Use This Test

Functional testing of tax calculation on sales order lines for a new Oracle Fusion SCM Order Management implementation
Regression testing of tax determination logic after a tax configuration change or Oracle quarterly update
UAT sign-off for order entry specialists confirming tax is calculated correctly for representative customers and ship-to locations
Baseline arithmetic-verification case referenced alongside Create Sales Order, Create Order With Discount and Submit Sales Order in the same cluster
Diagnosing CONFIGURATION_ERROR and DATA_ERROR conditions when tax fails to calculate as expected, before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Order-to-Cash Sales Orders Process

Navigate to Order Management

→

Create Sales Order

→

Enter Order Line

→

Determine Tax Classification

→

Calculate Tax

→

Review Line/Order Total

→

Submit Order

Create Order With Tax builds on the base Create Sales Order scenario by validating that Oracle Fusion correctly determines and calculates tax on the order line, using the customer, ship-to location and item tax classification as configured in the tax engine. It sits alongside Create Order With Discount as a line-level calculation variant within the Sales Orders cluster, ahead of Submit Sales Order. Exact tax rules, rates and jurisdiction coverage depend entirely on the customer's Oracle Fusion tax configuration.

← Previous Stage

Create Order With Discount

Next Stage →

Submit Sales Order

Preconditions

A tax regime and applicable tax rules are configured for the jurisdiction relevant to this test in the target Oracle Fusion environment.
The customer used on the sales order has a tax classification configured.
The item used on the order line has a tax classification configured.
The ship-to address on the order determines the applicable tax jurisdiction and is active and correctly configured.
The order entry test user has appropriate access to view calculated tax on a sales order.

Tax regimes, rules, rates and jurisdiction coverage vary by customer, country and Oracle Fusion tax configuration. This test validates that tax is calculated based on the configuration present in the target environment — it does not assume or assert that any specific jurisdiction, regime or rate is supported.

Sample Test Data

Customer	${CUSTOMER}
Item	${ITEM}
Line Amount	${LINE_AMOUNT}
Ship-to Address	${SHIP_TO_ADDRESS}
Customer Tax Classification	${CUSTOMER_TAX_CLASSIFICATION}
Item Tax Classification	${ITEM_TAX_CLASSIFICATION}
Tax Rate	${TAX_RATE}
Tax Amount	${TAX_AMOUNT}
Line Total	${LINE_TOTAL}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. For illustration only: if Line Amount = ${LINE_AMOUNT} and Tax Rate = ${TAX_RATE}, then Tax Amount = Line Amount × Tax Rate and Line Total = Line Amount + Tax Amount — for example, a $1,000.00 line amount at an illustrative 8% placeholder rate produces $80.00 tax and a $1,080.00 line total. This is a placeholder example only and does not represent a universally supported tax rate or jurisdiction.

Test Steps

8 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 and Navigate to Order Management Sign in to Oracle Fusion using an authorised order entry test user and navigate to the Order Management work area.	The Order Management work area opens successfully.
2	Navigate to Sales Orders Open the Sales Orders page to create or open a sales order. ${CUSTOMER}	The sales order page opens for the correct customer.
3	Create or Open a Sales Order Create a new sales order, or open an existing order, for the test customer. ${CUSTOMER} / ${SHIP_TO_ADDRESS}	A sales order is opened with the customer and ship-to address populated.
4	Select the Order Line Add or select the order line containing the item and line amount to be tested. ${ITEM} / ${LINE_AMOUNT}	The order line is accepted with the correct item and line amount.
5	Review Tax Classification and Ship-to Determination Review the customer tax classification, item tax classification and ship-to address used by Oracle Fusion to determine the applicable tax jurisdiction. ${CUSTOMER_TAX_CLASSIFICATION} / ${ITEM_TAX_CLASSIFICATION}	The tax classification and jurisdiction determination reflect the configured customer, item and ship-to data.
6	Review Calculated Tax Amount Review the tax amount Oracle Fusion calculates on the order line. ${TAX_RATE} / ${TAX_AMOUNT}	A tax amount is calculated and displayed on the order line.
7	Verify Arithmetic Against Expected FormulaBusiness assertion Confirm that the calculated tax amount and line total match the expected formula: Tax Amount = Line Amount × Tax Rate, and Line Total = Line Amount + Tax Amount. ${LINE_AMOUNT} / ${TAX_RATE} / ${TAX_AMOUNT} / ${LINE_TOTAL} This is the primary business assertion for the scenario — arithmetically correct tax calculation is the expected pass condition, not merely a displayed tax amount.	The line total equals the line amount plus the calculated tax amount, verified arithmetically against the expected formula.
8	Submit and Confirm Order Tax Total Submit the sales order and confirm the order-level tax total correctly aggregates the tax calculated across all order lines.	The sales order is submitted successfully and the order-level tax total correctly reflects the sum of line-level tax.

Expected Results

Tax is calculated on the order line based on the customer, ship-to location and item tax classification as configured.
The tax amount equals the line amount multiplied by the applicable tax rate.
The line total equals the line amount plus the calculated tax amount.
Tax-exempt customers and tax-exempt item classifications are correctly excluded from tax calculation where configured.
The order-level tax total correctly aggregates tax across all order lines.
The sales order is submitted successfully with the correct tax total.

Key Validation Checkpoints

Line total equals line amount plus calculated tax amount, verified arithmetically.
Tax is correctly determined by customer, ship-to and item tax classification, not a hard-coded rate.
Exemptions are correctly applied where configured.
Order-level tax total correctly aggregates line-level tax.

Core Business Scenario

Create Order With Tax

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 Create Order With Tax business scenario. Jarvis AI can extend this scenario by generating additional customer, ship-to, item tax classification, exemption and jurisdiction variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every customer, ship-to location or item tax classification combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Arithmetic Verification and Jurisdiction variations for the customer's environment — including exempt-customer and exempt-item cases and lines in jurisdictions where no tax rule is configured, since correctly enforced tax configuration is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Order With Tax business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Customers, Items, Ship-to Addresses, Tax Classifications and Tax Rules.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant customer, ship-to, item tax classification and jurisdiction variations.

Positive + Negative Test Variations

Valid tax calculation scenarios and edge cases such as missing tax classifications, invalid ship-to addresses or unconfigured jurisdictions.

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 customer, ship-to location, item tax classification or jurisdiction combination, SyntraFlow maintains one core Create Order With Tax scenario and allows Jarvis AI to generate customer, ship-to, tax classification and jurisdiction-specific variations using the customer's available test data and configured tax rules.

AI-Generated Test Variations

The same Create Order With Tax 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 Order Management Sales Orders.

Positive Scenarios

Calculate tax on a standard taxable order line
Calculate tax for a tax-exempt customer
Calculate tax for a tax-exempt item classification
Calculate tax across multiple lines with different tax classifications
Calculate tax for a ship-to address in a different configured jurisdiction

Negative Scenarios

Attempt to calculate tax with no tax classification set on the item
Enter an invalid ship-to address preventing jurisdiction determination
Apply conflicting exemption certificates to the same order
Attempt tax calculation where tax engine configuration is missing for the jurisdiction
Attempt an unauthorized manual tax override
Enter a negative or invalid tax rate

These are representative examples only. Tax determination behavior, jurisdiction coverage and available field combinations depend entirely on the customer's Oracle Fusion tax configuration — not every Oracle environment configures the same jurisdictions, regimes or exemptions.

Generated Using Your DataVault Test Data

Generic test data rarely represents every customer, ship-to location, item tax classification and jurisdiction combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Order With Tax scenarios relevant to the customer's actual tax configuration.

Standard Library Definition

Customer                ${CUSTOMER}
Item                    ${ITEM}
Line Amount             ${LINE_AMOUNT}
Ship-to Address         ${SHIP_TO_ADDRESS}
Customer Tax Class.     ${CUSTOMER_TAX_CLASSIFICATION}
Item Tax Class.         ${ITEM_TAX_CLASSIFICATION}
Tax Rate                ${TAX_RATE}
Tax Amount              ${TAX_AMOUNT}
Line Total              ${LINE_TOTAL}

DataVault

Customers
  Active customers with configured tax classifications
Items
  Active items with configured tax classifications
Ship-to Addresses
  Configured ship-to addresses mapped to tax jurisdictions
Tax Rules
  Configured tax regimes, rules and rates per jurisdiction
Exemption Certificates
  Configured customer and item exemptions

Jarvis AI Generates

Scenario 01 — Standard Taxable Line
Scenario 02 — Tax-Exempt Customer
Scenario 03 — Tax-Exempt Item Classification
Scenario 04 — Multiple Lines, Different Tax Classifications
Scenario 05 — Ship-to in Alternate Configured Jurisdiction
Scenario 06 — Missing Tax Classification on Item
...

Create Order With Tax test data can include sensitive commercial categories such as customer, pricing and tax information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific tax and pricing 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 Create Order With Tax scenarios Jarvis can generate from this business scenario, spanning customer, item, ship-to jurisdiction and exemption 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	Standard Taxable Line	Positive	Order line taxed using standard configured customer, item and ship-to classification	Syntra Ready
VAR-002	Tax-Exempt Customer	Positive/Exemption	Customer is configured as tax-exempt and no tax is calculated on the line	Syntra Ready
VAR-003	Tax-Exempt Item Classification	Positive/Exemption	Item tax classification is configured as exempt	Syntra Ready
VAR-004	Multiple Lines, Different Tax Classifications	Positive	Order contains multiple lines each with a different configured tax classification	Syntra Ready
VAR-005	Ship-to in Alternate Jurisdiction	Positive/Jurisdiction	Ship-to address maps to a different configured tax jurisdiction	Syntra Ready
VAR-006	Boundary Line Amount	Positive	Tax calculated correctly at a boundary line amount value	Syntra Ready
VAR-007	Combined Customer and Item Exemption	Positive/Exemption	Both customer and item are configured as exempt on the same line	Syntra Ready
VAR-008	Missing Item Tax Classification	Negative	Item has no tax classification configured	Syntra Ready
VAR-009	Invalid Ship-to Address	Negative/Jurisdiction	Ship-to address is invalid and jurisdiction cannot be determined	Syntra Ready
VAR-010	Conflicting Exemption Certificates	Negative/Exemption	Customer has conflicting exemption certificates on file	Syntra Ready
VAR-011	Missing Tax Configuration for Jurisdiction	Negative/Jurisdiction	No tax rule is configured for the ship-to jurisdiction	Syntra Ready
VAR-012	Unauthorized Manual Tax Override	Negative	User without appropriate access attempts to manually override calculated tax	Syntra Ready

Automatically Expand Positive and Negative Tax Calculation Coverage

Positive Testing

Jarvis generates scenarios using customer, item, ship-to and tax classification combinations expected to calculate tax correctly on a sales order line in Oracle Fusion.

Valid Customer + Active Item + Configured Ship-to Jurisdiction → Tax Calculated Correctly

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around tax classification, jurisdiction determination, exemptions and security.

Missing Item Tax Classification → Expected Configuration Validation
Invalid Ship-to Address → Expected Jurisdiction Determination Failure
Conflicting Exemption Certificates → Expected Exemption Validation
Missing Tax Configuration for Jurisdiction → Expected Configuration Error
Unauthorized Manual Tax Override → Expected Access Restriction

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

Scenario	Oracle Outcome	Test Result
Valid sales order	Order created	PASS
Invalid customer	Customer validation occurs	PASS
Credit hold	Credit check enforced	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Create Order With Tax scenarios and group them into reusable execution packs.

SCM Order Management Create Order With Tax Regression Pack

Standard Taxable Line
Tax-Exempt Customer
Tax-Exempt Item Classification
Multiple Lines, Different Tax Classifications
Ship-to in Alternate Jurisdiction
Missing Item Tax Classification
Invalid Ship-to Address
Missing Tax Configuration for Jurisdiction
Unauthorized Manual Tax Override
Negative or Invalid Tax Rate

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

Once scheduled, SyntraFlow executes the selected Create Order With Tax scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter tax configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	SCM Order Management Create Order With Tax 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 & Approval Variations

Access to view calculated tax, and to attempt a manual tax override, on a sales order is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that tax-related access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Order Entry Specialist	View Calculated Tax	Allowed	PASS
Unauthorized User	Attempts Manual Tax Override	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 Create Order With Tax scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Arithmetic Verification and Jurisdiction coverage — including exempt-customer and exempt-item cases and lines in jurisdictions where no tax rule is configured — 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 — Create Order With Tax, 8 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

Review Tax Classification and Ship-to Determination

May internally include

Open Order Line Tax Details → Read Customer Tax Classification → Read Item Tax Classification → Read Ship-to Jurisdiction → Confirm Determination

Business Step

Verify Arithmetic Against Expected Formula

May internally include

Read Line Amount → Read Tax Rate → Read Tax Amount → Compute Expected Tax Amount → Compute Expected Line Total → Compare Against Displayed 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 tax was calculated 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: Create Order With Tax failed — Likely category: CONFIGURATION_ERROR — Evidence: no tax rule is configured for the ship-to jurisdiction — Recommended action: verify tax configuration for the jurisdiction before re-running the test. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Review Calculated Tax Amount	Pass	—
Submit and Confirm Order Tax Total	Pass	—
Verify Arithmetic Against Expected Formula	Pass	Pass

Related Sales Order Tests

Create Order With Tax is part of the Sales Orders cluster — explore the related create, discount and submission scenarios below.

Create Sales Order Create Order With Discount Submit Sales Order

Turn This Standard Test into Your Oracle SCM Create Order With Tax Regression Suite

Start with the Syntra Standard Create Order With Tax test, use DataVault to provide environment-specific customer, item and tax configuration data, let Jarvis generate additional jurisdiction, exemption and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Order Management Sales 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

Oracle ERP Testing Tool Test Library SCM Test Library Order Management Test Library Sales Orders Test Library Syntra DataVault

Frequently Asked Questions

How does Oracle Fusion determine which tax jurisdiction applies to a sales order line?

Oracle Fusion determines the applicable tax jurisdiction using the ship-to address on the order together with the customer and item tax classifications, as configured in the Oracle Fusion tax engine for the target environment. This test validates that determination using whatever tax regime and rules are configured — it does not perform tax determination itself.

Does this test support all tax jurisdictions and tax regimes?

No. This test validates tax calculation based on whatever tax regime, rules and rates are configured in the customer's Oracle Fusion environment. It does not claim universal coverage of every tax jurisdiction or regime — coverage depends entirely on the customer's tax configuration.

How are tax-exempt customers or items handled?

Where a customer or item is configured as tax-exempt in Oracle Fusion, the exemption is expected to be applied during tax calculation and reflected in the calculated tax amount. This scenario includes representative exempt-customer and exempt-item variations to confirm exemptions are applied as configured.

What is the arithmetic check used to validate calculated tax?

This test verifies that Tax Amount equals Line Amount multiplied by the applicable Tax Rate, and that Line Total equals Line Amount plus Tax Amount, using the actual values returned by Oracle Fusion rather than assumed values.

How does security testing work for viewing or overriding calculated tax?

Access to view calculated tax, and to attempt a manual tax override, is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an order entry specialist versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.