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

Syntra Standard Oracle Test Library

Oracle Fusion HCM Emergency Contact Test Cases

Validate that emergency-contact information for a worker can be created, updated and removed correctly in Oracle Fusion HCM, including relationship, primary-contact designation and contact detail accuracy.

Test ID	ORCL.HCM.COREHR.PERSON.EMERGENCY_CONTACT
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	Medium
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 17 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that emergency-contact information for a worker can be created, updated and removed correctly in Oracle Fusion HCM, and that relationship, contact detail and primary-contact designation are captured and retained accurately.

The scenario should confirm that:

a new emergency contact is added correctly for the worker
the relationship between the worker and the contact is recorded accurately
the primary emergency-contact indicator is set and changed correctly
updated contact details — name, phone, email and address — are saved correctly
an emergency contact can be removed where the configuration allows it
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, update and removal of emergency-contact records for a worker in Oracle Fusion HCM Core HR TEST/UAT environments. It does not cover the worker's own person, address or national-identifier records, which are covered by the separate Update Person Information, Manage Address and Manage National Identifiers scenarios in the same Person Management cluster.

When to Use This Test

Functional testing of emergency-contact creation, update and removal for a new Oracle Fusion HCM implementation
Regression testing of emergency-contact behavior after an Oracle quarterly update
UAT sign-off for HR teams that routinely maintain emergency-contact records at hire and during the employee lifecycle
Verifying that changing the primary emergency contact correctly updates the primary indicator across contact records
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during emergency-contact maintenance before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Person Management Process

Locate Worker

→

Open Emergency Contacts

→

Add / Update Contact

→

Set Primary Indicator

→

Save

→

Verify

Manage Emergency Contacts is one of the recurring Person Management maintenance scenarios alongside Update Person Information, Manage Address and Manage National Identifiers. It is typically performed at hire and revisited whenever a worker's emergency-contact circumstances change. Exact fields available, relationship types and validation depend on legislative data group, worker type and customer-specific Oracle Fusion configuration.

Preconditions

The worker record is active in the target Oracle Fusion HCM environment.
Relationship types used for emergency contacts are configured in the target environment.
The test user has access to manage emergency-contact records for the worker.
Where an existing contact is being updated or removed, at least one emergency-contact record already exists for the worker.
The effective date used for the change falls within an open period for the worker's assignment.

Exact field availability, mandatory fields, relationship-type lists and validation messages may vary by Oracle Fusion implementation, legislative data group and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Person Number	${PERSON_NUMBER}
Contact Name	${CONTACT_NAME}
Relationship	${RELATIONSHIP}
Contact Phone	${CONTACT_PHONE}
Contact Email	${CONTACT_EMAIL}
Contact Address	${CONTACT_ADDRESS}
Primary Emergency Contact	${PRIMARY_EMERGENCY_CONTACT}
Effective Date	${EFFECTIVE_DATE}

Sample values are illustrative placeholder tokens only. Replace with valid data from the target Oracle Fusion HCM TEST/UAT environment. Never use real names, phone numbers, email addresses or other personal contact details on this public page — see the privacy note below.

Test Steps

7 business-readable steps. SyntraFlow's automation executes ~17 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 the Person Management work area.	The Person Management work area opens successfully.
2	Locate the Worker Record Search for and open the worker record that emergency-contact information will be maintained for. ${PERSON_NUMBER}	The correct worker record opens.
3	Select Add or Update Emergency Contact Open the worker's Emergency Contacts page and select Add for a new contact, or select an existing contact to update. ${EFFECTIVE_DATE}	The emergency-contact entry page opens for the worker as of the correct effective date.
4	Enter Contact Name and Relationship Enter the emergency contact's name and select the relationship to the worker. ${CONTACT_NAME} / ${RELATIONSHIP}	Contact name and relationship are accepted without unexpected validation errors.
5	Enter Contact Phone, Email and Address Enter the emergency contact's phone number, and email and address where captured. ${CONTACT_PHONE} / ${CONTACT_EMAIL} / ${CONTACT_ADDRESS}	Contact details are accepted without unexpected validation errors.
6	Set Primary Emergency Contact Indicator Set or change the primary emergency-contact indicator for the record being saved. ${PRIMARY_EMERGENCY_CONTACT} This single business step replaces multiple technical actions such as toggling the primary flag and confirming any related record is updated where the configuration restricts more than one primary contact.	The primary indicator is accepted and reflected correctly, including on any other contact record it affects.
7	Submit and Verify Contact Saved CorrectlyBusiness assertion Save the emergency-contact record and reopen the worker's Emergency Contacts page to confirm the change. This is the primary business assertion for the scenario — a correctly saved emergency-contact record is the expected pass condition, not merely a successful save action.	The emergency contact is saved with the correct name, relationship, phone, email, address and primary indicator, and the worker record otherwise remains unaffected.

Expected Results

The emergency contact is created, updated or removed correctly for the intended worker.
The relationship recorded between worker and contact is correct.
The primary emergency-contact indicator is correct, including where changing it affects another contact record.
Contact name, phone, email and address are correct.
The worker's other person-management records remain unaffected by the emergency-contact change.
A history of prior emergency-contact values is retained where the configuration supports it.

Key Validation Checkpoints

Contact created correctly.
Relationship correct.
Primary flag correct.
Contact details correct.
Worker record unaffected.
History retained where available.

Core Business Scenario

Manage Emergency Contacts

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 Manage Emergency Contacts business scenario. Jarvis AI can extend this scenario by generating additional relationship, primary-contact, contact-detail and security variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every relationship type, contact-detail combination or worker type. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including primary-contact edge cases, since correctly enforced single-primary and relationship rules are an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Manage Emergency Contacts business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Workers, Relationship Types, Contact Details.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant relationship, primary-contact and security variations.

Positive + Negative Test Variations

Valid emergency-contact scenarios and edge cases such as invalid relationships, duplicate primary contacts 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 relationship, primary-contact or contact-detail combination, SyntraFlow maintains one core Manage Emergency Contacts scenario and allows Jarvis AI to generate relationship, primary-contact and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Manage Emergency Contacts 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

Add a new emergency contact
Add multiple emergency contacts for the same worker
Change the primary emergency contact
Update the emergency contact's phone number
Update the emergency contact's relationship
Remove an emergency contact where the configuration allows it
Manage emergency contacts across different worker types

Negative Scenarios

Attempt to save an emergency contact with a missing name
Enter an invalid relationship type
Enter an invalid phone number format
Attempt to set a duplicate primary contact where restricted to a single primary
Attempt an unauthorized update to another worker's emergency contact
Enter an invalid effective date
Attempt to manage an emergency contact for a worker who is not active

These are representative examples only. Negative-scenario behavior and available field 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 relationship type, contact-detail format and worker type in a real Oracle Fusion HCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Manage Emergency Contacts scenarios relevant to the customer's actual implementation.

Standard Library Definition

Person Number             ${PERSON_NUMBER}
Contact Name               ${CONTACT_NAME}
Relationship                ${RELATIONSHIP}
Contact Phone               ${CONTACT_PHONE}
Contact Email                ${CONTACT_EMAIL}
Contact Address              ${CONTACT_ADDRESS}
Primary Emergency Contact    ${PRIMARY_EMERGENCY_CONTACT}
Effective Date               ${EFFECTIVE_DATE}

DataVault

Workers
  Active worker records eligible for emergency-contact maintenance
Relationship Types
  Configured relationship values for emergency contacts
Contact Details
  Masked placeholder name, phone, email and address values
Primary Contact Rules
  Single-primary or multi-primary configuration by legislative data group
Effective Dates
  Valid dates within an open assignment period

Jarvis AI Generates

Scenario 01 — Worker A + New Primary Contact
Scenario 02 — Worker A + Second Contact, Not Primary
Scenario 03 — Worker B + Change Primary Contact
Scenario 04 — Worker C + Update Phone Only
Scenario 05 — Duplicate Primary Contact Attempt
Scenario 06 — Unauthorized User Attempts Update
...

Emergency-contact test data is personal contact information and is never rendered with real names or phone numbers on this public page. Where DataVault is connected, Jarvis constructs scenarios using masked or placeholder contact-name and phone values only — no real emergency-contact details are ever exposed on the Syntra Standard Test Library. See /datavault/ and /datavault/data-masking/ for details on DataVault's data masking policies.

Example Test Variations

Representative examples of Manage Emergency Contacts scenarios Jarvis can generate from this business scenario, spanning relationship, primary-contact 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	Add New Emergency Contact	Positive	A new emergency-contact record is created for the worker	Syntra Ready
VAR-002	Add Multiple Contacts	Positive	A second and third emergency contact are added for the same worker	Syntra Ready
VAR-003	Change Primary Contact	Positive/Primary	Primary indicator is moved from one contact record to another	Syntra Ready
VAR-004	Update Contact Phone	Positive	Existing contact's phone number is updated	Syntra Ready
VAR-005	Update Contact Relationship	Positive/Relationship	Existing contact's relationship value is changed	Syntra Ready
VAR-006	Remove Emergency Contact	Positive	An emergency-contact record is removed where the configuration allows it	Syntra Ready
VAR-007	Different Worker Types	Positive	Emergency contact maintained across employee, contingent worker and pending worker types	Syntra Ready
VAR-008	Missing Contact Name	Negative	Contact record saved without a name value	Syntra Ready
VAR-009	Invalid Relationship	Negative/Relationship	Relationship value entered does not exist or is inactive	Syntra Ready
VAR-010	Invalid Phone Format	Negative	Contact phone number entered does not meet the expected format	Syntra Ready
VAR-011	Duplicate Primary Contact	Negative/Primary	A second contact is marked primary where the configuration restricts a single primary contact	Syntra Ready
VAR-012	Unauthorized Update	Negative	User without access attempts to update another worker's emergency contact	Syntra Ready
VAR-013	Worker Not Active	Negative	Emergency-contact update attempted for a worker who is not active	Syntra Ready

Automatically Expand Positive and Negative Emergency Contact Coverage

Positive Testing

Jarvis generates scenarios using relationship, contact-detail and primary-indicator combinations expected to successfully create, update or remove an emergency-contact record in Oracle Fusion.

Valid Worker + Valid Relationship + Complete Contact Detail → Emergency Contact Saved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around relationship type, contact-detail format, primary-contact rules and security.

Missing Contact Name → Expected Mandatory Field Validation
Invalid Relationship → Expected Relationship Validation
Invalid Phone Format → Expected Format Validation
Duplicate Primary Contact → Expected Primary-Contact 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 Manage Emergency Contacts scenarios and group them into reusable execution packs.

HCM Core HR Manage Emergency Contacts Regression Pack

Add New Emergency Contact
Add Multiple Contacts
Change Primary Contact
Update Contact Phone
Update Contact Relationship
Remove Emergency Contact
Different Worker Types
Duplicate Primary Contact
Unauthorized Update
Worker Not Active

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

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

Persona	Action	Expected	Syntra Result
HR Specialist	Manage Emergency Contact	Allowed	PASS
Employee	Manage Own Emergency Contact via Self-Service	Allowed where configured	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 Manage Emergency Contacts scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Relationship and Primary-contact 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 — Manage Emergency Contacts, 7 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

Set Primary Emergency Contact Indicator

May internally include

Open Contact Record → Toggle Primary Indicator → Check Existing Primary Contact → Confirm Single-Primary Rule → Save

Business Step

Submit and Verify Contact Saved Correctly

May internally include

Save Record → Reopen Emergency Contacts Page → Read Saved Name/Relationship/Phone/Email/Address/Primary Flag → Compare Against Entered 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 emergency contact was saved 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: Update Emergency Contact failed — Likely category: DATA_ERROR — Evidence: contact phone value did not meet the configured format — Recommended action: correct the phone value and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Contact Phone, Email and Address	Pass	—
Set Primary Emergency Contact Indicator	Pass	—
Submit and Verify Contact Saved Correctly	Pass	Pass

Related Person Management Tests

Manage Emergency Contacts is the fifth and final page in the Person Management cluster, alongside Update Person Information, Manage Address, Manage Contact Information and Manage National Identifiers. Explore the related scenarios below.

Manage National Identifiers Update Person Information Terminate Worker

Turn This Standard Test into Your Oracle HCM Emergency Contact Regression Suite

Start with the Syntra Standard Manage Emergency Contacts test, use DataVault to provide environment-specific test data, let Jarvis generate additional relationship, primary-contact 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

How is the primary emergency contact determined for a worker?

A worker's primary emergency contact is the contact record explicitly flagged as primary in Oracle Fusion. This test validates that setting or changing the primary indicator on one contact is applied correctly, including where the configuration restricts a worker to a single primary contact at a time.

Can a worker have more than one emergency contact?

Yes, in most configurations a worker can have multiple emergency-contact records, typically with one designated as primary. This scenario covers adding multiple contacts and confirming each is saved with the correct relationship and detail, and does not assume a fixed maximum number of contacts.

What happens to emergency-contact records when a worker is terminated?

This scenario focuses on maintaining emergency-contact records for an active worker and does not assert automatic behavior on termination. Retention or visibility of emergency-contact data after termination depends on the customer's Oracle Fusion configuration and data-retention policy — see the related Terminate Worker scenario for termination-specific testing.

Can workers update their own emergency contacts through self-service?

Where configured, workers can typically maintain their own emergency-contact records through Oracle Fusion self-service, subject to the customer's security setup. This test can be executed for both an HR specialist maintaining a worker's record and, where enabled, a worker maintaining their own record.

How is security tested for emergency-contact maintenance?

Access to view or update a worker's emergency-contact records is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an HR specialist, a worker acting on their own record, and an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.