Oracle ERP Testing Tool > Test Library > Financials > Fixed Assets

Syntra Standard Oracle Test Library

Oracle Fusion Add Asset Test Cases

Validate creation of a new asset in Oracle Fusion Fixed Assets using valid asset book, category, cost, in-service date, location and accounting information.

Test ID	ORCL.R2R.FA.ASSET.ADD
Application	Oracle Fusion Cloud
Product	Financials
Module	Fixed Assets
Process	Asset Lifecycle
Business Flow	Record-to-Report
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 10 business-readable test steps; SyntraFlow's automation executes approximately 29 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorised Fixed Assets user can add a new asset in Oracle Fusion using valid asset book, category, cost, in-service date, location and accounting information.

The scenario should confirm that:

the selected asset book is accepted
the selected asset category is accepted and relevant default attributes are applied
asset description and cost are accepted
the in-service date is accepted and falls within a valid, open period
location and, where applicable, employee/assignment and cost center are accepted
depreciation method and useful life are complete and consistent with the book and category
the asset can be saved successfully
the newly added asset is assigned an asset number and status, and is available for subsequent lifecycle processing

This scenario covers asset addition only. It does not claim that the asset is capitalized, depreciated, adjusted, transferred, retired or reinstated — those are separate downstream test scenarios.

When to Use This Test

Functional testing of a new Oracle Fusion Fixed Assets implementation
Regression testing after an Oracle quarterly update
UAT sign-off for Fixed Assets asset-addition processing
Baseline case referenced by capitalization, depreciation, adjustment, transfer, retirement and reinstatement scenarios within the same asset lifecycle

Where This Test Fits in the Asset Lifecycle

Add

→

Capitalize

→

Adjust / Transfer

→

Depreciate

→

Retire

→

Reinstate

This test covers the addition of a new asset record and serves as the entry point of the asset lifecycle — a prerequisite for subsequent capitalization, depreciation, adjustment, transfer, retirement and reinstatement scenarios.

Next Stage →

Capitalize Asset

Preconditions

Oracle Fusion Fixed Assets is configured and available.
A valid asset book is configured.
A valid asset category is configured.
The accounting period intended for the asset addition is open.
Valid account combinations are available for asset clearing, cost and depreciation accounts.
The test user has the appropriate asset-entry security and role to add assets.

Exact setup, field availability and default depreciation rules may vary by Oracle Fusion implementation and security configuration.

Sample Test Data

Asset Book	${ASSET_BOOK} — e.g. FA CORP BOOK
Asset Category	${ASSET_CATEGORY} — e.g. Computer Equipment
Asset Description	${ASSET_DESCRIPTION}
Asset Number	${ASSET_NUMBER} — system-generated, or manually entered where configured
In-Service Date	${IN_SERVICE_DATE}
Cost	${COST}
Currency	${CURRENCY} — e.g. USD
Location	${LOCATION}
Employee / Assignment	${EMPLOYEE_ASSIGNMENT} — where the asset is tracked to an individual or assignment
Cost Center	${COST_CENTER}
Depreciation Method	${DEPRECIATION_METHOD} — e.g. Straight Line
Life (Years/Units)	${USEFUL_LIFE} — e.g. 5 years
Account Information	${ASSET_CLEARING_ACCOUNT} / ${DEPRECIATION_EXPENSE_ACCOUNT}
Source / Invoice Reference	${SOURCE_REFERENCE} — where the asset originates from a payables invoice or mass addition

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

Test Steps

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

#	User Action	Expected Result
1	Navigate to Fixed Assets Navigate to the Fixed Assets work area in Oracle Fusion.	The Fixed Assets work area opens successfully.
2	Open Add Asset Open the Add Asset task.	The Add Asset page is displayed.
3	Select Asset Book Select the required asset book for the new asset. ${ASSET_BOOK}	The asset book is accepted and book-specific fields become available.
4	Select Asset Category Select the required asset category for the new asset. ${ASSET_CATEGORY} This single business step replaces multiple technical actions such as opening the category list of values, searching, selecting and confirming.	The asset category is accepted and relevant default attributes, where configured, are applied.
5	Enter Asset Description and Cost Enter the asset description and cost. ${ASSET_DESCRIPTION} / ${COST}	Description and cost are accepted and displayed correctly.
6	Enter In-Service Date Select or enter the date the asset is placed in service. ${IN_SERVICE_DATE} The automation may use several date-picker actions internally. Individual increment/decrement actions are not exposed as separate business test steps.	The in-service date is accepted and falls within a valid, open period.
7	Enter Location and Assignment Enter or select the asset location and, where applicable, the responsible employee/assignment and cost center. ${LOCATION} / ${EMPLOYEE_ASSIGNMENT} / ${COST_CENTER}	Location and assignment information is accepted without unexpected validation errors.
8	Review Depreciation Information Review the depreciation method, useful life and related depreciation attributes defaulted or entered for the asset. ${DEPRECIATION_METHOD} / ${USEFUL_LIFE}	Depreciation information is complete and consistent with the selected asset book and category.
9	Save the Asset Select Save.	Oracle Fusion successfully processes the save request without unexpected errors.
10	Verify Asset CreationBusiness assertion Confirm the Oracle save acknowledgement and verify that the newly created asset record is available with the expected status. This is the main business assertion for the scenario — the test does not stop merely because Save was clicked successfully.	The asset is successfully created, assigned an asset number and expected status, and is available for subsequent lifecycle processing.

Expected Results

Oracle Fusion successfully creates the asset record with the selected book, category, cost, in-service date, location and depreciation attributes, and assigns the expected asset status.
Correct asset book is associated with the new asset.
Correct asset category is associated with the new asset.
Asset description and cost are retained accurately.
In-service date falls within a valid, open period.
Location, employee/assignment and cost center are captured where provided.
Depreciation method and useful life are complete and internally consistent.
No unexpected save errors occur.
Newly created asset can be identified or retrieved after Save.
Asset is available for subsequent capitalization, depreciation, adjustment, transfer, retirement and reinstatement scenarios.

Key Validation Checkpoints

Asset book matches the intended test data.
Asset category selection is correct.
Cost is entered correctly and matches expected value.
In-service date is correct and within an open period.
Location and assignment information is correct where applicable.
Cost center is correctly associated.
Depreciation method and useful life are valid for the category.
Account combinations are valid.
Save acknowledgement is received.
Asset record and asset number exist after Save.

Core Business Scenario

Add Asset

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 Add Asset 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 asset-addition test dozens of times simply to cover different combinations of book, category, cost, location, cost center, depreciation method and useful life. 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 — Asset Books, Categories, Assets, Costs, In-Service Dates, Locations, Employees/Assignments, Cost Centers, Depreciation Methods, Useful Lives, Currencies, Periods and Accounts.

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 asset-addition 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 Add Asset 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 Fixed Assets.

Positive Scenarios

Basic capital asset addition
Different asset categories
Different asset books
Different asset costs
Different in-service dates
Different locations
Different cost centers
Different depreciation methods
Different useful lives
Asset linked to a source transaction (e.g. payables invoice / mass addition)

Negative Scenarios

Invalid asset category
Invalid asset book
Missing cost
Invalid in-service date
Invalid location
Invalid account combination
Closed accounting period
Missing mandatory data
Disabled asset category

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 often fails to represent the configuration of a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to create variations relevant to the customer's actual implementation.

Standard Library Definition

Asset Book         ${ASSET_BOOK}
Asset Category      ${ASSET_CATEGORY}
Cost                ${COST}
In-Service Date     ${IN_SERVICE_DATE}
Location            ${LOCATION}
Employee/Assignment ${EMPLOYEE_ASSIGNMENT}
Cost Center         ${COST_CENTER}
Depreciation Method ${DEPRECIATION_METHOD}
Useful Life         ${USEFUL_LIFE}
Currency            ${CURRENCY}

DataVault

Asset Books
  FA CORP BOOK
  FA TAX BOOK
Categories
  Computer Equipment
  Furniture & Fixtures
  Machinery
Locations
  Region A / Site 1
  Region B / Site 2
Depreciation Methods
  Straight Line
  Declining Balance
Accounting
  Valid configured combinations

Jarvis AI Generates

Scenario 01 — FA CORP BOOK + Computer Equipment + Region A
Scenario 02 — FA TAX BOOK + Machinery + Region B
Scenario 03 — Furniture & Fixtures + Declining Balance
Scenario 04 — High-Value Asset + Extended Useful Life
Scenario 05 — Invalid Asset Category
Scenario 06 — Closed Accounting Period
...

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 asset book, category, location and employee/assignment details remain within the customer's controlled SyntraFlow environment and access model.

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	Basic Capital Asset Add	Positive	Single asset, valid book, category and cost	Syntra Ready
VAR-002	Computer Equipment Category	Positive/Category	Asset category = Computer Equipment	Syntra Ready
VAR-003	Furniture & Fixtures Category	Positive/Category	Asset category = Furniture & Fixtures	Syntra Ready
VAR-004	Corporate Book Asset	Positive/Book	Asset book = FA CORP BOOK	Syntra Ready
VAR-005	Tax Book Asset	Positive/Book	Asset book = FA TAX BOOK	Syntra Ready
VAR-006	Minimal Cost Asset	Positive/Cost	Cost at the low capitalization threshold	Syntra Ready
VAR-007	High-Value Asset	Positive/Cost	Cost at the high end of typical capital assets	Syntra Ready
VAR-008	Prior-Period In-Service Date	Positive	In-service date falls in a prior open period	Syntra Ready
VAR-009	Current-Period In-Service Date	Positive	In-service date falls in the current period	Syntra Ready
VAR-010	Region A Location	Positive/Location	Location = Region A / Site 1	Syntra Ready
VAR-011	Region B Location	Positive/Location	Location = Region B / Site 2	Syntra Ready
VAR-012	Straight-Line Depreciation	Positive/Method	Depreciation method = Straight Line	Syntra Ready
VAR-013	Declining-Balance Depreciation	Positive/Method	Depreciation method = Declining Balance	Syntra Ready
VAR-014	Extended Useful Life (7 Years)	Positive	Useful life = 7 years	Syntra Ready
VAR-015	Asset from Source Transaction	Positive	Asset linked to a payables invoice / mass addition line	Syntra Ready
VAR-016	Multi-Unit Asset	Positive	Single addition representing multiple units of an asset	Syntra Ready
VAR-017	Invalid Asset Category	Negative/Category	Category code does not exist	Syntra Ready
VAR-018	Invalid Asset Book	Negative/Book	Book code does not exist	Syntra Ready
VAR-019	Missing Cost	Negative/Cost	Required cost field left blank	Syntra Ready
VAR-020	Invalid In-Service Date	Negative	In-service date outside a valid or open range	Syntra Ready
VAR-021	Invalid Location	Negative/Location	Location code does not exist	Syntra Ready
VAR-022	Invalid Account Combination	Negative	Account combination fails validation	Syntra Ready
VAR-023	Closed Accounting Period	Negative	In-service date falls within a closed period	Syntra Ready
VAR-024	Missing Mandatory Data	Negative	Required field (book or category) left blank	Syntra Ready
VAR-025	Disabled Asset Category	Negative/Category	Category is inactive/disabled for use	Syntra Ready
VAR-026	Invalid Depreciation Configuration	Negative/Method	Depreciation method/life combination is invalid for the category	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the asset-addition business process.

Valid Book + Valid Category + Valid Cost → Asset Created

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's validations, business rules and exception handling around asset addition.

Invalid Category → Expected Category Validation
Closed Period → Expected Period Validation
Invalid Location → Expected Location Validation
Disabled Account → Expected Accounting Validation
Invalid Method → Expected Depreciation Configuration Validation

A negative test should not be marked as failed simply because Oracle blocks or flags invalid asset data. If the expected Oracle validation occurs, the negative test has passed.

Scenario	Oracle Outcome	Test Result
Valid asset add	Asset created successfully	PASS
Invalid asset category	Expected category validation appears	PASS
Closed accounting period	Expected period validation appears	PASS
Unexpected system error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated scenarios and group them into reusable execution packs.

Fixed Assets Add Regression Pack

Basic Capital Asset Add
Computer Equipment Category
Tax Book Asset
High-Value Asset
Region A Location
Straight-Line Depreciation
Asset from Source Transaction
Invalid Asset Category
Missing Cost
Closed Accounting Period

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 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.

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

Pack	Fixed Assets Add Regression Pack
Schedule	Quarterly Update Regression
Tests	26 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

Asset Lifecycle

Exact lifecycle behavior depends on the asset book, category, depreciation rules and customer configuration. Stages link to the corresponding test scenario family.

Add

→Capitalize→Adjust / Transfer→Depreciate→Retire→Reinstate

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.

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 — Add Asset, 10 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

Select Asset Category

May internally include

Open Category Search → Focus Category → Enter Category → Search → Select Category → Confirm

Business Step

Enter In-Service Date

May internally include

Open Date Field → Open Date Picker → Navigate Month → Select Date

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
Enter Cost	Pass	—
Click Save	Pass	—
Verify Asset Created	Pass	Pass

Related Fixed Asset Tests

Adding an asset is the first stage of the Oracle Fixed Assets lifecycle — continue with capitalization, adjustment, transfer and depreciation testing below.

Capitalize Asset Adjust Asset Transfer Asset Run Depreciation

Turn This Standard Test into Your Oracle Fixed Assets Regression Suite

Start with the Syntra Standard Add Asset 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 Fixed Assets 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

Fixed Assets Test Library Oracle Fixed Assets Testing Tool Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What does the Add Asset test validate in Oracle Fusion Fixed Assets?

It validates that a new asset can be added successfully using a valid asset book, category, cost, in-service date, location and accounting information, and that the asset is assigned an asset number and expected status.

What asset attributes are captured when adding a new asset?

Asset book, asset category, description, cost, in-service date, location, employee/assignment, cost center, depreciation method, useful life and relevant account information are captured, where applicable to the configuration.

What happens if an invalid asset category is used?

Oracle Fusion is expected to display a category validation message and prevent the asset from being saved. This negative scenario passes when the expected validation appears, not when the asset is incorrectly created.

Does adding an asset also capitalize it?

No. This scenario covers asset addition only. Capitalization is a separate downstream test scenario in the asset lifecycle.

How are the many Add Asset test variations generated?

Jarvis AI uses this standard Add Asset scenario together with available DataVault test data and configuration to generate relevant positive, negative and boundary variations for the customer's environment.

Can the Add Asset scenario and its variations be scheduled?

Yes. Selected Add Asset variations can be grouped into a regression pack and scheduled for on-demand or unattended batch execution.