EgisedgeOracle Partner
TestingERP Financials6 min readBy Egisedge Technologies

Oracle Fusion UAT Test Scripts: How to Write Them (with Template)

How to write Oracle Fusion Financials UAT test scripts: a step-by-step method, a sample script table, P2P, O2C and R2R scenarios, a checklist and common mistakes.

User acceptance testing (UAT) is where the business decides whether Oracle Fusion Cloud ERP is ready. The quality of that decision depends on the test scripts. A vague script produces a vague result. A precise script tells the tester exactly what to do, what to expect and what to record.

This guide sets out how to write UAT test scripts for Oracle Fusion Financials. Oracle feature and role names come from Oracle's current documentation. Confirm screens and tasks in your own instance. For the wider project sequence, see our Oracle Fusion Financials implementation steps.

What a UAT script must prove

System integration testing (SIT) proves that the configuration and integrations work. UAT proves that the business can run its processes in Oracle. So a UAT script should:

  • Follow a real business process from start to finish.
  • Be run by a business user, not a consultant.
  • Use the job role that person will have in production.
  • Have one clear expected result per step.
  • Leave evidence that someone else can check.

How to write Oracle Fusion UAT test scripts

1. Start from the process list

Do not start from screens. Start from the end-to-end processes in scope. Oracle Modern Best Practice gives a useful structure. Its ERP processes include Requisition to Payment, Supplier Invoice to Payment, Customer Invoice to Receipt, Bank Transactions to Cash Position, Asset Acquisition to Retirement and Period Close to Financial Reports. Map each in-scope process to the business owner who will sign it off.

2. Break each process into scenarios

A scenario is one business situation. "Pay a supplier" is a process. "Pay a supplier invoice matched to a purchase order and receipt, in INR, with TDS" is a scenario. Cover:

  • The normal path.
  • The common exceptions: holds, partial receipts, credit memos, reversals.
  • Each legal entity, business unit and currency that behaves differently.
  • Indian requirements in scope, such as GST and TDS.

3. Assign the job role

Each script must name the role that runs each step. Oracle delivers job roles such as Buyer, Accounts Payable Specialist, Accounts Receivable Specialist and General Accountant. Your project may use copies of these. Test with the roles users will actually get. If a tester uses an administrator login, you have tested nothing about security. Our Oracle Fusion security roles setup guide explains how to design them.

4. Define preconditions and test data

List what must exist before step one: supplier, customer, item, bank account, open period, approval rules. Give exact values. "Use supplier ABC Traders, site Gurugram, payment terms Net 30" is a precondition. "Use any supplier" is not.

5. Write steps and expected results

Write one action per step. Give one expected result per step, stated as something the tester can see: a status, an amount, an account, a document number. Avoid menu paths unless you have checked them in your instance.

6. Decide the evidence

Say what to capture: a screenshot, a report output, a document number, an accounting entry. Evidence is what lets the process owner sign off without rerunning the test.

7. Review with the business

The process owner should read and accept each script before UAT starts. This is the point to catch missing scenarios, not during execution.

Sample UAT test script

FieldExample
Script IDUAT-P2P-004
ProcessSupplier Invoice to Payment
ScenarioThree-way matched invoice, INR, within tolerance
RoleAccounts Payable Specialist
PreconditionsApproved PO 1001 for supplier ABC Traders; receipt entered for full quantity; AP period open
Steps1. Create invoice against PO 1001 for the received amount. 2. Validate the invoice. 3. Check holds. 4. Create accounting. 5. Review the accounting entries.
Expected resultInvoice validates with no holds; accounting debits the expense or accrual account and credits the liability account defined in the design
Actual resultFilled in by the tester
Pass/FailPass, Fail or Blocked
EvidenceInvoice number, screenshot of validation status, accounting entries
Defect IDLogged if failed
Tester and dateName and date of execution

Keep one row per script in a tracker, and the step detail in the script itself. Our UAT management template shows a tracker layout.

Sample scenarios by process

Procure-to-Pay

  • Raise a requisition, approve it and convert it to a purchase order (Buyer).
  • Receive part of a PO, then invoice the full amount. Expect a matching hold.
  • Enter a supplier credit memo and apply it.
  • Run a payment process and confirm the payment file and accounting.

Order-to-Cash

  • Create a Receivables invoice with GST and check the tax lines (Accounts Receivable Specialist).
  • Apply a customer receipt to two invoices.
  • Reverse a receipt and check the invoice reopens.
  • Run the Receivables Aging Report and agree it to the ledger.

Record-to-Report

  • Enter, approve and post a manual journal (General Accountant).
  • Run a recurring journal or allocation.
  • Revalue foreign currency balances at period end.
  • Close the period and run the trial balance.

Prepare the UAT environment

Oracle lets you refresh a test environment from production (production-to-test, or P2T) or from another test environment. Points from Oracle's documentation that affect UAT:

  • The refresh copies the source's most recent backup. Changes made after that backup are not included.
  • The target is unavailable while the refresh runs.
  • A target can be refreshed only once every seven days.
  • Some items are not copied, for example endpoint URLs to other environments, pending approval notifications and multi-factor authentication enrolment.

Plan the refresh before UAT starts. Then recheck integrations, approvals and user access in the target. Do not change configuration in the UAT environment without logging it.

Reuse scripts for quarterly updates

Oracle updates test environments on the first Friday of the update month and production two weeks later. Oracle advises retesting key processes and customisations in that window, and recommends test automation to make use of it. In Oracle Cloud Success Navigator, Oracle also lists the Oracle Cloud Application Testing Service, a premium regression testing service. Your UAT scripts are the natural base for any of these. See our quarterly update testing checklist.

UAT test script checklist

  • Every in-scope process has an owner and at least one scenario
  • Exceptions and Indian tax scenarios included
  • Each script names the production job role
  • Preconditions list exact data values
  • One action and one expected result per step
  • Evidence defined for each script
  • Test environment refreshed and integrations rechecked
  • Testers have their own user accounts and roles
  • Defect process and severity levels agreed
  • Entry and exit criteria agreed
  • Process owners have accepted the scripts
  • Sign-off recorded with open defects and accepted risks

Common mistakes

Testing with administrator access. The process passes in UAT and fails on day one in production.

Scripts written as screen tours. They check that a page opens, not that the business outcome is right.

No accounting check. In Financials, the transaction is only half the test. Check the accounting entries too.

Shared test data. Two testers use the same PO, and one blocks the other. Give each script its own data.

Skipping the exceptions. Holds, reversals and credit memos cause most live issues.

Signing off without evidence. If nobody can see what was tested, the sign-off is weak.

Our SIT and UAT playbook shows how UAT fits after SIT.

How Egisedge helps

Egisedge Technologies is an Oracle Partner, founded in 2019, with offices in Gurugram and Mahendergarh. We implement Oracle Fusion Cloud ERP.

We help finance teams build UAT scenarios from their processes, write test scripts with real job roles and data, prepare the test environment and run UAT through to sign-off. The same scripts then support quarterly update testing.

Planning Oracle Fusion UAT? Email info@egisedge.com to talk to our team.

Frequently asked questions

What is a UAT test script in Oracle Fusion?

It is a written test that a business user runs in an Oracle Fusion test environment to prove that a business process works the way the business needs. Each script names the process, the job role, the starting data, the steps, the expected result and the evidence to capture.

Who should write and run Oracle Fusion UAT scripts?

Business process owners should own the scenarios and run the scripts, using the job roles they will have in production. The implementation team can draft scripts from the solution design, but the business must review and accept them before UAT starts.

Which environment should we use for UAT?

Use a non-production environment kept for testing. Oracle lets you refresh a test environment from production (a P2T refresh) once you are live. Before go-live, many projects load converted data into a dedicated test environment. Freeze configuration in that environment while UAT runs.

Can we reuse UAT scripts for quarterly update testing?

Yes. Oracle updates test environments about two weeks before production, and recommends that you retest key business processes and customisations in that window. A well-written UAT pack becomes your regression suite and a starting point for test automation.

Talk to Egisedge about ERP Financials

Tell us where you are and a senior consultant will reply with next steps.