Oracle ERP Testing Tool > Test Library > HCM > Core HR > Workforce Structures

Syntra Standard Oracle Test Library

Oracle Fusion HCM Location Test Cases

Validate that a workforce location can be created and maintained correctly in Oracle Fusion HCM, with the correct code, name, country, address and effective date, and that the location becomes available for use by workers, departments and assignments once active.

Test ID	ORCL.HCM.COREHR.STRUCTURE.LOCATION
Application	Oracle Fusion Cloud
Product	HCM
Module	Core HR
Process	Workforce Structures
Business Flow	Workforce Configuration
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 19 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates that a workforce location can be created and maintained in Oracle Fusion HCM with a correct code, name, country, address and effective date, and that the resulting location is available for use by departments, positions and worker assignments once active.

The scenario should confirm that:

the location is created with a unique location code and name
country and address data are captured and formatted correctly for the selected country
the effective date and status applied to the location are correct
an existing location can be updated without breaking existing references from departments or assignments
an inactivated location correctly restricts new usage while preserving existing historical references
Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers creation and maintenance of a single workforce location in Oracle Fusion HCM Core HR TEST/UAT environments. It does not cover the department, grade or job structures that reference a location, which are covered by the separate Departments, Grades and related Workforce Structures scenarios in the same cluster.

When to Use This Test

Functional testing of location creation for a new Oracle Fusion HCM Core HR implementation
Regression testing of location maintenance and country/address validation after an Oracle quarterly update
UAT sign-off for HR teams that add new office and site locations as the organization expands
Baseline case referenced by Department, Position and Assignment scenarios within the same Workforce Structures cluster
Verification that inactivating a location correctly restricts new assignment usage while preserving historical references

Where This Test Fits in Workforce Structures

Departments

→

Jobs

→

Grades

→

Locations

→

Positions

Locations is a foundational Workforce Structures object referenced by departments, positions and worker assignments across Core HR. A location typically needs to exist and be active before it can be selected when configuring a department or completing a worker assignment. Exact field availability, address formatting and validation depend on country, legislation and customer-specific Oracle Fusion configuration.

← Previous Stage

Grades

Preconditions

A location structure is configured in the target Oracle Fusion HCM environment.
The test user has appropriate Workforce Structures access to create and maintain locations.
Country and state/province reference data required for the address is configured and active.
Where the location will be referenced by a department or assignment test, the target department or assignment scenario is available.
The location code used for the test is not already in use in the target environment.

Exact field availability, mandatory fields and address formatting vary by Oracle Fusion implementation, country and customer-specific configuration.

Sample Test Data

Location Code	${LOCATION_CODE}
Location Name	${LOCATION_NAME}
Country	${COUNTRY}
Address Line 1	${ADDRESS_LINE_1}
City	${CITY}
State / Province	${STATE_PROVINCE}
Postal Code	${POSTAL_CODE}
Effective Date	${EFFECTIVE_DATE}
Status	${STATUS}

Sample values are illustrative placeholder tokens only. A location represents an organizational site or office address rather than a personal worker address, but placeholder tokens are used consistently across the Workforce Structures library. Replace them with valid location and country data from the target Oracle Fusion TEST/UAT environment; not every field applies to every country or customer configuration.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Workforce Structures Sign in to Oracle Fusion Cloud with a user account that has Workforce Structures access and navigate to the Workforce Structures work area.	The Workforce Structures work area opens successfully.
2	Initiate Create or Update Location Open the Locations page and either start creating a new location or select an existing location and choose Update. ${LOCATION_CODE}	The location entry page opens, ready for input.
3	Enter Location Code and Name Enter the location code and location name for the new or updated location. ${LOCATION_CODE} / ${LOCATION_NAME}	The location code and name are accepted, and the code is confirmed unique.
4	Enter Country and Address Select the country and enter the address lines, city, state/province and postal code for the location. ${COUNTRY} / ${ADDRESS_LINE_1} / ${CITY} / ${STATE_PROVINCE} / ${POSTAL_CODE}	The address details are accepted according to the selected country's formatting rules, without unexpected validation errors.
5	Set Effective Date and Status Set the date the location becomes effective and set the location status. ${EFFECTIVE_DATE} / ${STATUS}	The effective date and status are accepted and applied to the location record.
6	Review Location Details Review the entered location code, name, country, address, effective date and status before submitting. Reviewing the location before saving lets the tester catch an incorrect field entry before the location is created.	All entered location details display correctly for review.
7	Submit and Verify Location Available for AssignmentBusiness assertion Submit the location and confirm it can be selected from the location list of values in a department or worker assignment. This is the main business assertion for the scenario — the test does not stop merely because the save action succeeded; the location must be retrievable and selectable in downstream Workforce Structures usage.	The location is saved with the correct code, name, country, address, effective date and status, and is available for selection wherever active locations are used.

Expected Results

The location is created or updated with a unique location code and name.
Country and address data are recorded correctly per the applicable country address format.
The effective date applied to the location is correct.
The location status (active or inactive) is applied correctly.
The location is available for selection in department, position and worker assignment setup where active.
Inactivating a location restricts new usage while historical references remain intact.

Key Validation Checkpoints

Location created correctly.
Address correct.
Country correct.
Effective dates correct.
Status correct.
Available for worker assignment where active.

Core Business Scenario

Location

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 Location scenario. Jarvis AI can extend this scenario by generating additional Positive, Negative, Country and Status variations across address structures, countries and effective dates using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate location test for every country and status combination. Jarvis uses the standard Location scenario as the foundation and generates relevant variations for the customer's environment — for example a valid US address, a valid UK address, a location referenced by an active assignment, or an attempt to inactivate a location that is still in use.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Location business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Location Codes, Countries, Addresses and Effective Dates.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant country, address, status and security variations.

Positive + Negative Test Variations

Valid location scenarios and edge cases such as duplicate codes, invalid addresses or restricted inactivation.

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 for every country, address structure and status combination, SyntraFlow maintains one core Location scenario and allows Jarvis AI to generate relevant Positive, Negative, Country and Status variations using the customer's available test data.

AI-Generated Test Variations

The same Location 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 HCM Core HR Workforce Structures.

Positive Scenarios

Create a new location
Create locations for different countries
Create locations with different address structures
Update an existing location
Create a future-dated location
Inactivate a location no longer in use
Use a location in a worker assignment
Use a location across different organizational usage such as department and position setup

Negative Scenarios

Attempt to create a location with a duplicate location code
Enter an invalid or incomplete address
Enter an invalid country
Enter an invalid state/country combination
Enter an invalid postal code format
Enter an invalid effective date
Attempt to inactivate a location that is still in use where restricted
Attempt creation or update by an unauthorized user

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, legislation and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely reflects the countries, address formats and site population configured in a real Oracle Fusion HCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Location scenarios relevant to the customer's actual implementation.

Standard Library Definition

Location Code          ${LOCATION_CODE}
Location Name          ${LOCATION_NAME}
Country                ${COUNTRY}
Address Line 1         ${ADDRESS_LINE_1}
City                   ${CITY}
State / Province       ${STATE_PROVINCE}
Postal Code            ${POSTAL_CODE}
Effective Date         ${EFFECTIVE_DATE}
Status                 ${STATUS}

DataVault

Locations
  Configured location codes and their current status
Countries
  Configured countries and address layout rules
States / Provinces
  Valid state/province reference data by country
Effective Dates
  Valid current and future effective-date ranges
Usage
  Departments, positions and assignments referencing each location

Jarvis AI Generates

Scenario 01 — Create Location (${COUNTRY})
Scenario 02 — Update Existing Location
Scenario 03 — Future-Dated Location
Scenario 04 — Alternate Country Address
Scenario 05 — Duplicate Location Code
Scenario 06 — Invalid State/Country Combination
...

Location test data represents an organizational site or office address rather than a personal worker address. The public Syntra Standard Test Library nonetheless uses illustrative placeholder tokens for consistency with the rest of the Workforce Structures library. Where Syntra DataVault is connected, customer-specific location and address data remains 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 Location scenarios Jarvis can generate from this business scenario, spanning country, address and status 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	Create New Location	Positive	New location created with a unique code and name	Syntra Ready
VAR-002	Valid US Address	Positive/Country	Location created using US address format, state and ZIP code rules	Syntra Ready
VAR-003	Valid UK Address	Positive/Country	Location created using UK address format and postcode rules	Syntra Ready
VAR-004	Alternate Address Structure	Positive	Location created with a different address line and city structure	Syntra Ready
VAR-005	Update Existing Location	Positive	Existing location updated with revised address or name	Syntra Ready
VAR-006	Future-Dated Location	Positive/Status	Location created with an effective date ahead of the current date	Syntra Ready
VAR-007	Inactivate Location	Positive/Status	Active location inactivated when no longer in use	Syntra Ready
VAR-008	Location Used in Worker Assignment	Positive	Active location selected and confirmed on a worker assignment	Syntra Ready
VAR-009	Location Used in Department Setup	Positive	Active location selected in department organizational usage	Syntra Ready
VAR-010	Duplicate Location Code	Negative	Location code entered already exists in the target environment	Syntra Ready
VAR-011	Invalid or Incomplete Address	Negative	A required address element is missing or malformed	Syntra Ready
VAR-012	Invalid Country	Negative/Country	Country reference is invalid or not configured	Syntra Ready
VAR-013	Invalid State/Country Combination	Negative/Country	State/province entered does not belong to the selected country	Syntra Ready
VAR-014	Invalid Postal Code Format	Negative/Country	Postal code does not match the selected country's expected format	Syntra Ready
VAR-015	Invalid Effective Date	Negative/Status	Effective date entered is outside a supported or logical range	Syntra Ready

Positive and Negative Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion HCM successfully creates or updates a workforce location when the code, name, country, address and effective date are all valid.

Unique Location Code + Valid Country/Address Data → Location Created and Available for Assignment

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around location code uniqueness, address format, country, effective date and security.

Duplicate Location Code → Expected Uniqueness Validation
Invalid Address → Expected Address Validation
Invalid Country → Expected Country Validation
Invalid State/Country Combination → Expected Reference-Data Validation
Unauthorized User → Expected Access Restriction

A negative test passes when Oracle correctly enforces the expected validation, effective-date or security rule

Scenario	Oracle Outcome	Test Result
Valid address	Address saved	PASS
Invalid postal code	Validation occurs	PASS
Unauthorized national ID access	Access prevented	PASS
Duplicate job code	Duplicate validation occurs	PASS
Unexpected system error	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

HCM Core HR Locations Regression Pack

Create New Location
Valid US Address
Valid UK Address
Update Existing Location
Future-Dated Location
Inactivate Location
Location Used in Worker Assignment
Duplicate Location Code
Invalid State/Country Combination
Unauthorized User Attempts Location Change

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

Once scheduled, SyntraFlow executes the selected Location 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	HCM Core HR Locations Regression Pack
Schedule	Nightly Regression
Tests	15 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

Access to create or update a workforce location is controlled by Oracle Fusion's role-based and data security, which varies by customer. Jarvis can generate representative persona-based variations to confirm that location-maintenance access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
HR Specialist	Create/Update Location	Allowed	PASS
Unauthorized User	Attempts Location Change	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 Location scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Country and Status coverage for the customer's environment — for example a valid US address, a valid UK address, a duplicate location code, an invalid state/country relationship, and an attempt to inactivate a location that is still referenced by an active assignment.

Generate

Positive, Negative, Country and Status 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 — Location, 7 Business Steps

↓

DataVault — Customer-Specific Location/Address Test Data

↓

Jarvis AI — Generate Positive + Negative + Country 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

Enter Country and Address

May internally include

Open Country LOV → Select Country → Load Country Address Layout → Enter Address Lines → Validate Format

Business Step

Submit and Verify Location Available for Assignment

May internally include

Validate Form → Submit Location → Poll Confirmation → Query Location LOV in Assignment → Confirm Location Selectable

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 location was created or maintained 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. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Country and Address	Pass	—
Set Effective Date and Status	Pass	—
Submit and Verify Location Available for Assignment	Pass	Pass

Related Workforce Structures Tests

Locations are referenced by departments, positions and worker assignments across Core HR — explore the related Workforce Structures and Hire-to-Retire scenarios below.

Departments Grades Hire Employee

Turn This Standard Test into Your Oracle HCM Workforce Structures Regression Suite

Start with the Syntra Standard Location test, use DataVault to provide environment-specific location, country and address test data, let Jarvis generate additional Positive, Negative, Country and Status variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Workforce Structures 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 HCM Core HR Workforce Structures Syntra DataVault

Frequently Asked Questions

Is a workforce location the same as a worker's home address?

No. A location in Oracle Fusion HCM Workforce Structures is an organizational site or office address used by departments, positions and worker assignments. It is separate from a worker's personal home address, which is maintained through Person Management and covered by a different test scenario.

How does Oracle Fusion apply country-specific address rules when creating a location?

Oracle Fusion loads the address layout, field labels and validation rules that apply to the selected country — for example which fields are mandatory and how postal codes are formatted. Jarvis can generate variations across different countries to confirm the correct country-specific rules are enforced for location addresses.

What happens when a location is inactivated but still referenced by a department or assignment?

Inactivating a location is generally expected to prevent it from being selected for new departments or assignments while preserving existing historical references that already use it. Where the customer's configuration restricts inactivation of a location that is currently in use, Jarvis can generate a variation to confirm that restriction is enforced.

How does effective-date behavior work for a location change?

A location can be created or updated with a future effective date so the change takes effect automatically on that date. This test confirms the effective date is recorded correctly and that the location becomes available for use from the expected date.

How does security testing work for location maintenance?

Access to create or update a location is controlled by Oracle Fusion's role-based and data security, which varies by customer. Jarvis can generate representative persona-based variations — such as an authorized HR Specialist versus an unauthorized user — to confirm that location-maintenance access behaves as expected, without asserting a single universal Oracle security model.