Oracle ERP Testing Tool > Test Library > HCM > Core HR > Person Management

Syntra Standard Oracle Test Library

Oracle Fusion HCM Update Person Information Test Cases

Validate that a permitted update to a worker's personal information — such as preferred name, title, marital status or other legislation-permitted attributes — is applied correctly in Oracle Fusion HCM while effective dating, auditability and the worker's existing employment relationship are preserved.

Test ID	ORCL.HCM.COREHR.PERSON.UPDATE
Application	Oracle Fusion Cloud
Product	HCM
Module	Core HR
Process	Person Management
Business Flow	Employee Lifecycle
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 16 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a permitted update to an active worker's personal information — such as preferred name, legal name, title, marital status, date of birth or gender, where applicable under legislation and configuration — is captured and applied correctly in Oracle Fusion HCM, with effective dating, auditability and the worker's existing employment relationship preserved.

The scenario should confirm that:

the change is applied to the correct worker record
the new attribute value(s) take effect from the entered effective date
fields that were not part of the change remain unaffected
the worker's employment relationship and assignment are unaffected by the change
prior effective-dated values remain visible in the worker's history rather than being overwritten
only users with appropriate security access can make the change

This scenario covers a general-purpose effective-dated update to one or more personal information attributes for an existing active worker within Oracle Fusion HCM TEST/UAT environments. It does not cover the initial hire event or address and contact-information updates, which are covered by the separate Hire Employee, Manage Address and Manage Contact Information scenarios within the same Core HR Person Management area.

When to Use This Test

Functional testing of effective-dated preferred name, title or other permitted personal attribute changes for a new Oracle Fusion HCM implementation
Regression testing of person-update and effective-dating behavior after an Oracle quarterly update
UAT sign-off for HR teams that routinely process personal information changes on behalf of workers
Security testing of employee self-service versus HR Specialist access to personal information fields

Where This Test Fits in Core HR Person Management

Hire Employee

→

Update Person Information

→

Manage Address

→

Manage Contact Information

Update Person Information is the general-purpose way of maintaining a worker's personal details after hire, such as preferred name, legal name, title and other legislation-permitted attributes. It sits alongside Manage Address and Manage Contact Information as core Person Management maintenance scenarios that follow the initial Hire Employee event. Exact fields available, self-service access and validation depend on worker type, legislative data group, security and customer-specific Oracle Fusion configuration.

Preconditions

An active worker record exists in Oracle Fusion HCM.
The test user holds the appropriate role and data security access to update the attribute being changed.
The legislative context (legislative data group) for the worker is known and configured.
The effective date entered for the change is a valid date within an open period.

Exact field availability, self-service access and validation messages may vary by Oracle Fusion implementation, worker type, legislative data group and security configuration.

Sample Test Data

Person Number	${PERSON_NUMBER}
Worker Type	${WORKER_TYPE}
Effective Date	${EFFECTIVE_DATE}
Preferred Name	${PREFERRED_NAME}
Legal Name	${LEGAL_NAME}
Title	${TITLE}
Marital Status	${MARITAL_STATUS}
Date of Birth	${DATE_OF_BIRTH}
Gender	${GENDER}
Legislative Context	${LEGISLATIVE_CONTEXT}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Fields such as marital status, date of birth and gender are only updatable where applicable per legislation and configuration — not every field is available or changed in every scenario.

Test Steps

8 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 and Navigate to Person Management Sign in to Oracle Fusion using an authorised HR test user and navigate to Person Management.	The Person Management landing page opens successfully.
2	Locate the Worker Record Search for and open the active worker whose personal information will be updated. ${PERSON_NUMBER} This single business step replaces multiple technical actions such as opening worker search, entering search criteria and selecting the result.	The correct worker and current personal information are displayed.
3	Initiate Personal Information Update Select the option to update the worker's personal information.	The personal information update screen opens for the selected worker.
4	Enter Effective Date Enter the date from which the personal information change should take effect. ${EFFECTIVE_DATE}	The effective date is accepted without unexpected validation errors.
5	Select Attribute(s) to Update Select and enter the new value(s) for the attribute(s) being updated, such as preferred name, title or other permitted personal attributes. ${PREFERRED_NAME} / ${LEGAL_NAME} / ${TITLE} / ${MARITAL_STATUS} / ${DATE_OF_BIRTH} / ${GENDER}	The new attribute value(s) are accepted and reflected on the pending update.
6	Review Updated Information Review the updated personal information as calculated by Oracle Fusion before submitting the change. Reviewing the updated information before submission lets the tester catch an incorrect field entry before the change is created.	The previewed information reflects the intended new values alongside unchanged fields.
7	Submit the Update Submit and confirm the personal information update for creation in the test environment.	Oracle Fusion successfully processes the update without unexpected errors.
8	Verify Update Applied Correctly With History PreservedBusiness assertion Reopen or refresh the worker's personal information and confirm the new attribute values and prior history. This is the primary business assertion for the scenario — correctly effective-dated values with preserved history are the expected pass condition, not merely a successful save.	The new values are correctly effective as of ${EFFECTIVE_DATE} and the prior effective-dated record remains visible in the worker's history.

Expected Results

The personal information update is accepted and processed for the correct worker.
New attribute values are effective from the correct effective date.
Fields that were not part of the change remain unchanged.
The worker's employment relationship and assignment remain intact.
The prior effective-dated record remains preserved in the worker's history.
Access restrictions are correctly honored for the requesting user.
The change is visible and traceable in the worker's history.

Key Validation Checkpoints

Intended value is updated correctly.
Correct effective date is applied.
Historical data is retained — the prior effective-dated row is preserved.
Unaffected attributes remain unchanged.
Worker's employment relationship remains intact.
Audit/history is visible where available.
Access restrictions are correctly honored.

Core Business Scenario

Update Person Information

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 Update Person Information business scenario. Jarvis AI can extend this scenario by generating additional attribute, effective-date, security and legislative variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every personal-information attribute or legislative combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Effective-Date and Security variations for the customer's environment — with attention to legislative rules, since which attributes are updatable and by whom depends heavily on legislation and configuration.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Update Person Information business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Workers, Worker Types, Legislative Contexts and permitted attributes.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant attribute, effective-date and security variations.

Positive + Negative Test Variations

Valid attribute-change scenarios and edge cases such as invalid effective dates, missing mandatory values or restricted access.

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 personal-information attribute or legislative combination, SyntraFlow maintains one core Update Person Information scenario and allows Jarvis AI to generate attribute-driven, effective-date and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Update Person Information 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 Person Management.

Positive Scenarios

Update preferred name to a new value
Update title
Update marital status where applicable
Update other permitted personal attributes within legislative rules
Change effective as of the current date
Future-dated change where supported by configuration
Change performed for different worker types
Change performed across different legislative contexts

Negative Scenarios

Invalid effective date entered
Missing mandatory value for the attribute being updated
Invalid value entered for a legislative-specific field
Unauthorized field update attempted
Unauthorized worker access attempted
Duplicate or conflicting effective-dated change already exists
Worker is not in an active status
Attempt to change a restricted attribute

These are representative examples only. Negative-scenario behavior and available attribute combinations 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 every permitted personal-information attribute or legislative rule in a real Oracle Fusion HCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Update Person Information scenarios relevant to the customer's actual implementation.

Standard Library Definition

Person Number         ${PERSON_NUMBER}
Worker Type            ${WORKER_TYPE}
Effective Date         ${EFFECTIVE_DATE}
Preferred Name         ${PREFERRED_NAME}
Legal Name             ${LEGAL_NAME}
Title                  ${TITLE}
Marital Status         ${MARITAL_STATUS}
Date of Birth          ${DATE_OF_BIRTH}
Gender                 ${GENDER}
Legislative Context    ${LEGISLATIVE_CONTEXT}

DataVault

Workers
  Active workers eligible for a personal information update
Worker Types
  Employee, Contingent Worker, Pending Worker
Legislative Contexts
  Legislative data groups configured for the customer
Permitted Attributes
  Fields updatable per legislation and security configuration
Effective Date
  Valid dates within open periods

Jarvis AI Generates

Scenario 01 — Worker A + Preferred Name Update
Scenario 02 — Worker B + Title Update
Scenario 03 — Worker C + Marital Status Update (Where Applicable)
Scenario 04 — Worker D + Future-Dated Change
Scenario 05 — Invalid Effective Date
Scenario 06 — Unauthorized Field Update Attempt
...

Update Person Information test data can include sensitive personal categories such as legal name, date of birth, marital status and gender. The public Syntra Standard Test Library uses illustrative, masked placeholder tokens only — real employee personal data should never be entered directly into this test. Where DataVault is connected, customer-specific worker attributes remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/ and /datavault/data-masking/ for details.

Example Test Variations

Representative examples of Update Person Information scenarios Jarvis can generate from this business scenario, spanning attribute, effective-date and security 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	Update Preferred Name	Positive	Worker's preferred name updated to a new, valid value	Syntra Ready
VAR-002	Update Title	Positive	Worker's title updated to a new, valid value	Syntra Ready
VAR-003	Update Marital Status (Where Applicable)	Positive	Marital status updated where permitted by legislation	Syntra Ready
VAR-004	Update Permitted Personal Attributes	Positive	Other legislation-permitted personal attributes updated	Syntra Ready
VAR-005	Current-Dated Change	Positive/Effective Date	Change entered with an effective date of the current date	Syntra Ready
VAR-006	Future-Dated Change	Positive/Effective Date	Change entered with an effective date ahead of the current date, where supported	Syntra Ready
VAR-007	Different Worker Type	Positive	Update performed for a different eligible worker type	Syntra Ready
VAR-008	Different Legislative Context	Positive	Update performed for a worker in a different legislative data group	Syntra Ready
VAR-009	HR Specialist Update	Positive/Security	Update performed by an HR Specialist on behalf of the worker	Syntra Ready
VAR-010	Employee Self-Service Update	Positive/Security	Update performed by the employee via self-service where permitted	Syntra Ready
VAR-011	Invalid Effective Date	Negative/Effective Date	Effective date entered outside a supported or open range	Syntra Ready
VAR-012	Missing Mandatory Value	Negative	Mandatory value left blank for the attribute being updated	Syntra Ready
VAR-013	Invalid Legislative Value	Negative	Invalid value entered for a legislative-specific field	Syntra Ready
VAR-014	Unauthorized Field Update	Negative/Security	Requesting user attempts to update a field outside their authority	Syntra Ready
VAR-015	Unauthorized Worker Access	Negative/Security	Requesting user attempts to access a worker outside their authority	Syntra Ready
VAR-016	Restricted Attribute Change Attempt	Negative/Security	Requesting user attempts to change a restricted or read-only attribute	Syntra Ready

Automatically Expand Positive and Negative Update Person Information Coverage

Positive Testing

Jarvis generates scenarios using attribute values and effective dates expected to successfully update a worker's personal information while Oracle Fusion's effective-dating correctly preserves prior history.

Active Worker + New Preferred Name + Effective Date within Open Period → Personal Information Updated and History Preserved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around mandatory fields, effective dates, legislative rules and security.

Invalid Effective Date → Expected Date Validation
Missing Mandatory Value → Expected Field Validation
Invalid Legislative Value → Expected Legislative Validation
Unauthorized Field Update → Expected Access Restriction
Unauthorized Worker Access → Expected Access Restriction
Restricted Attribute Change Attempt → 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 Update Person Information scenarios and group them into reusable execution packs.

HCM Update Person Information Regression Pack

Update Preferred Name
Update Title
Update Marital Status (Where Applicable)
Current-Dated Change
Future-Dated Change
HR Specialist Update
Employee Self-Service Update
Invalid Effective Date
Unauthorized Field Update
Restricted Attribute Change Attempt

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

Once scheduled, SyntraFlow executes the selected Update Person Information 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 Update Person Information Regression Pack
Schedule	Quarterly Update Regression
Tests	16 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 update a worker's personal information is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that update access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
HR Specialist	Update Person Information	Allowed	PASS
Employee	Update Own Preferred Name via Self-Service	Allowed where configured	PASS
Line Manager	Attempts Update Outside Authority	Access prevented	PASS
Unauthorized User	Attempts Update	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 Update Person Information scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Effective-Date and Security 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 — Update Person Information, 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

Locate the Worker Record

May internally include

Open Worker Search → Enter Person Number/Name → Search → Select Worker → Open Person Management → Confirm

Business Step

Review Updated Information

May internally include

Open Review Screen → Read Updated Field Values → Compare Against Entered New 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 the personal information update was applied correctly or effective-dated correctly — 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 Effective Date	Pass	—
Submit the Update	Pass	—
Verify Update Applied Correctly With History Preserved	Pass	Pass

Related Person Management Tests

Update Person Information is one of the core Person Management maintenance scenarios that follow the initial hire event — explore the related address, contact information and hire scenarios below.

Manage Address Manage Contact Information Hire Employee

Turn This Standard Test into Your Oracle HCM Update Person Information Regression Suite

Start with the Syntra Standard Update Person Information test, use DataVault to provide environment-specific test data, let Jarvis generate additional attribute, effective-date and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Person Management 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 Test Library Core HR Test Library Person Management Test Library Syntra DataVault DataVault Data Masking

Frequently Asked Questions

Which attributes are typically updatable with the Update Person Information scenario?

Depending on legislation, configuration and security, typically updatable attributes include preferred name, legal name and title, with fields such as marital status, date of birth and gender only updatable where applicable per legislative rules and configuration. Exact field availability varies by customer implementation.

How does effective dating preserve history when personal information is updated?

Oracle Fusion HCM is effective-dated, meaning a change is recorded with a specific effective date rather than overwriting the record in place. This test verifies that new attribute values take effect from the entered date while the prior effective-dated record remains available in the worker's history for the period before that date.

Can employees update their own personal information through self-service, or is this HR Specialist only?

Both paths can be relevant depending on customer configuration. Some attributes, such as preferred name, may be updatable by the employee through self-service, while other attributes may be restricted to an HR Specialist role. This scenario includes security variations covering both paths.

Does the set of updatable fields vary by legislative context?

Yes. Which personal information attributes are available for update, and under what rules, can depend on the worker's legislative data group and country-specific configuration. This test can be run across different legislative contexts to confirm expected behavior for each.

How is security tested for Update Person Information?

Jarvis can generate persona-based variations — such as HR Specialist, Line Manager, Employee and Unauthorized User — to confirm that update access behaves as expected for each role, without asserting a single universal Oracle security model.