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

Syntra Standard Oracle Test Library

Oracle Fusion HCM Contact Information Test Cases

Validate that a worker's email, phone and other configured contact methods can be added and maintained correctly in Oracle Fusion HCM, with the correct contact type, primary designation and effective date applied.

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

Test Objective

The objective of this test is to validate that a worker's contact methods — including email addresses, phone numbers and other configured contact types — can be created and maintained correctly in Oracle Fusion HCM, with the correct contact type, primary designation and effective date applied.

The scenario should confirm that:

the correct contact method (email, phone or other configured type) is created or updated for the correct worker
the contact type — such as personal, work or mobile — is captured correctly
the primary indicator is set correctly where multiple contact methods of the same type exist
the effective date is applied correctly, including for future-dated contact updates
the previous contact method is retained as history where applicable, rather than being overwritten
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 worker's email, phone and other configured contact methods in Oracle Fusion HCM Core HR TEST/UAT environments. It does not cover the worker's postal address, national identifiers or emergency contacts, which are covered by the separate Manage Address, Manage National Identifiers and Manage Emergency Contacts scenarios in the same Person Management cluster.

When to Use This Test

Functional testing of contact information maintenance for a new Oracle Fusion HCM implementation
Regression testing of email and phone contact method behavior after an Oracle quarterly update
UAT sign-off for HR teams that routinely maintain worker email and phone data
Validating employee self-service contact updates where self-service is enabled
Diagnosing DATA_ERROR and CONFIGURATION_ERROR conditions surfaced during a contact method update before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Person Management Process

Navigate to Person Management

→

Search Worker

→

Open Contact Information

→

Add/Update Contact Method

→

Set Primary & Effective Date

→

Save

→

Verify Contact Method

Manage Contact Information is one of several worker-record maintenance scenarios within Person Management, alongside Manage Address, Manage National Identifiers and Manage Emergency Contacts. Contact methods are typically maintained by HR Specialists or HR Managers, and in many implementations by the employee directly through self-service. Exact contact types available, mandatory fields and validation depend on legislation, enterprise configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Manage Address

Next Stage →

Manage National Identifiers

Preconditions

The worker record is active in the target Oracle Fusion HCM environment.
Contact method types — such as email and phone — are configured for the worker's legislation and enterprise.
The test user has appropriate access to add or update contact information for the worker.
Any existing contact methods on the worker record are visible on the contact information page.
Where self-service is in scope, the employee self-service contact page is accessible to the test user.

Exact contact types offered, mandatory fields, format validation and self-service availability may vary by Oracle Fusion implementation, legislation, enterprise configuration and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Person Number	${PERSON_NUMBER}
Contact Type	${CONTACT_TYPE}
Email Type	${EMAIL_TYPE}
Email Address	${EMAIL_ADDRESS}
Phone Type	${PHONE_TYPE}
Country Code	${COUNTRY_CODE}
Phone Number	${PHONE_NUMBER}
Primary Indicator	${PRIMARY_INDICATOR}
Effective Date	${EFFECTIVE_DATE}

Sample values are illustrative placeholder tokens only. Real email addresses and phone numbers must never be used on this public page — replace tokens with valid masked data from the target Oracle Fusion HCM TEST/UAT environment when executing the test. Not every field applies to every contact type — for example, country code typically applies only to phone entries.

Test Steps

7 business-readable steps. SyntraFlow's automation executes ~15 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 whose contact information will be maintained. ${PERSON_NUMBER}	The correct worker's contact information page opens.
3	Select Add or Update Contact Method Choose to add a new contact method or select an existing one to update. ${CONTACT_TYPE}	The contact method entry form opens for the selected type.
4	Enter Contact Details and Type Enter the email address or phone number, including email/phone type and country code where applicable. ${EMAIL_TYPE} / ${EMAIL_ADDRESS} / ${PHONE_TYPE} / ${COUNTRY_CODE} / ${PHONE_NUMBER}	The contact details are accepted without unexpected validation errors.
5	Set Primary Flag and Effective Date Designate the contact method as primary where applicable and enter the effective date. ${PRIMARY_INDICATOR} / ${EFFECTIVE_DATE} This single business step replaces multiple technical actions such as toggling the primary indicator and confirming the effective-date field.	The primary designation and effective date are accepted and reflected on the record.
6	Submit the Contact Method Save the contact information update for the worker record.	Oracle Fusion successfully processes the contact method update without unexpected errors.
7	Verify Contact Method Saved CorrectlyBusiness assertion Reopen or refresh the worker's contact information and confirm the new or updated contact method, primary flag and effective date. This is the primary business assertion for the scenario — a correctly saved contact method with accurate primary and effective-date data is the expected pass condition, not merely a successful save.	The contact method, type, primary designation and effective date match the entered data, and any previous contact method is retained as history where applicable.

Expected Results

The contact method is created or updated for the correct worker.
The contact type (email, phone or other configured type) is correct.
The primary indicator correctly reflects the intended primary contact method.
The effective date is correctly applied, including for future-dated changes.
Any previous contact method is retained as history where applicable.
No unrelated worker data is changed by the update.

Key Validation Checkpoints

Correct contact method created.
Primary flag correct.
Effective date correct.
Previous contact retained where applicable.
No unrelated person data changed.

Core Business Scenario

Manage Contact 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 Manage Contact Information business scenario. Jarvis AI can extend this scenario by generating additional contact type, primary designation, effective-date 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 email type, phone type or country code combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including format-validation and primary-contact edge cases, since correctly enforced validation is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Manage Contact Information business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Person Numbers, Contact Types and masked Email/Phone values.

Jarvis AI

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

Positive + Negative Test Variations

Valid contact-method scenarios and edge cases such as invalid formats, missing country codes 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 email type, phone type, country code or primary-contact combination, SyntraFlow maintains one core Manage Contact Information scenario and allows Jarvis AI to generate contact type, primary and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Manage Contact 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

Add a personal email address
Add a work email address
Update an existing email address to a new value
Add a mobile phone number
Add a work phone number with a different country code
Change the primary phone or email designation
Add a future-dated contact method update

Negative Scenarios

Enter an invalid email address format
Enter an invalid phone number format
Omit a required country code
Attempt to add a duplicate primary contact where restricted
Attempt an unauthorized contact information update
Attempt to save without a required value
Enter an invalid effective date

These are representative examples only. Negative-scenario behavior and available contact types 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 represents every email type, phone type, country code and primary-contact combination in a real Oracle Fusion HCM environment. Where connected, Jarvis can use approved, masked test data available through Syntra DataVault to construct Manage Contact Information scenarios relevant to the customer's actual implementation.

Standard Library Definition

Person Number      ${PERSON_NUMBER}
Contact Type        ${CONTACT_TYPE}
Email Type          ${EMAIL_TYPE}
Email Address       ${EMAIL_ADDRESS}
Phone Type          ${PHONE_TYPE}
Country Code        ${COUNTRY_CODE}
Phone Number        ${PHONE_NUMBER}
Primary Indicator   ${PRIMARY_INDICATOR}
Effective Date      ${EFFECTIVE_DATE}

DataVault

Person Numbers
  Active workers eligible for contact maintenance
Contact Types
  Configured email and phone types per legislation
Email / Phone Values
  Masked, format-valid placeholder values
Country Codes
  Valid codes per configured phone format
Effective Dates
  Valid dates within an open period

Jarvis AI Generates

Scenario 01 — Worker A + Personal Email Added
Scenario 02 — Worker A + Work Phone + Different Country Code
Scenario 03 — Worker B + Primary Email Changed
Scenario 04 — Worker C + Future-Dated Phone Update
Scenario 05 — Invalid Email Format
Scenario 06 — Unauthorized User Attempts Contact Update
...

Contact Information test data includes sensitive personal details such as email addresses and phone numbers. The public Syntra Standard Test Library uses illustrative ${PLACEHOLDER} tokens only — no real email addresses or phone numbers appear on this page. Where DataVault is connected, customer-specific contact data remains masked and access-controlled according to DataVault's data masking policies. See /datavault/ and /datavault/data-masking/ for details.

Example Test Variations

Representative examples of Manage Contact Information scenarios Jarvis can generate from this business scenario, spanning contact type, primary and format 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 Personal Email	Positive/Contact Type	New personal email contact method added	Syntra Ready
VAR-002	Add Work Email	Positive/Contact Type	New work email contact method added	Syntra Ready
VAR-003	Update Existing Email	Positive/Contact Type	Existing email address updated to a new value	Syntra Ready
VAR-004	Add Mobile Phone	Positive/Contact Type	New mobile phone contact method added	Syntra Ready
VAR-005	Add Work Phone — Different Country Code	Positive/Contact Type	Work phone added using an alternate valid country code	Syntra Ready
VAR-006	Change Primary Contact Method	Positive/Primary	Primary indicator moved from one existing contact method to another	Syntra Ready
VAR-007	Future-Dated Contact Update	Positive	Contact method saved with an effective date ahead of the current date	Syntra Ready
VAR-008	Invalid Email Format	Negative/Contact Type	Email address entered without a valid format	Syntra Ready
VAR-009	Invalid Phone Format	Negative/Contact Type	Phone number entered without a valid format	Syntra Ready
VAR-010	Missing Country Code	Negative	Phone number entered without a required country code	Syntra Ready
VAR-011	Duplicate Primary Contact	Negative/Primary	Attempt to mark a second contact method of the same type as primary where restricted	Syntra Ready
VAR-012	Unauthorized Contact Update	Negative	Requesting user lacks access to update the worker's contact information	Syntra Ready
VAR-013	Missing Required Value	Negative	Contact method saved with a required field left blank	Syntra Ready
VAR-014	Invalid Effective Date	Negative	Effective date entered outside a supported or open range	Syntra Ready

Automatically Expand Positive and Negative Contact Information Coverage

Positive Testing

Jarvis generates scenarios using contact type, format, primary-designation and effective-date combinations expected to successfully create or update a contact method in Oracle Fusion.

Valid Worker + Correctly Formatted Email/Phone + Correct Primary Flag → Contact Method Saved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around email/phone format, mandatory fields, primary-contact rules and security.

Invalid Email Format → Expected Format Validation
Invalid Phone Format → Expected Format Validation
Missing Country Code → Expected Mandatory Field Validation
Duplicate Primary Contact → Expected Primary 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 Contact Information scenarios and group them into reusable execution packs.

HCM Core HR Manage Contact Information Regression Pack

Add Personal Email
Add Work Email
Update Existing Email
Add Mobile Phone
Add Work Phone — Different Country Code
Change Primary Contact Method
Future-Dated Contact Update
Invalid Email Format
Duplicate Primary Contact
Unauthorized Contact Update

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

Once scheduled, SyntraFlow executes the selected Manage Contact 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 Core HR Manage Contact Information Regression Pack
Schedule	Quarterly Update Regression
Tests	14 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 add or update a worker's contact information is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that contact-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 Contact Information	Allowed	PASS
Employee	Update Own Contact Info via Self-Service	Allowed where configured	PASS
Unauthorized User	Attempts Contact 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 Contact Information scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative 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 — Manage Contact Information, 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

Enter Contact Details and Type

May internally include

Open Contact Method Panel → Select Type → Enter Value → Select Country Code (Phone) → Confirm Format → Add

Business Step

Verify Contact Method Saved Correctly

May internally include

Reopen Contact Information → Read Saved Values → Compare Against Entered Values → Confirm Primary Flag and Effective 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 contact method 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: Submit the Contact Method failed — Likely category: DATA_ERROR — Evidence: email address format invalid — Recommended action: correct the format and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Contact Details and Type	Pass	—
Submit the Contact Method	Pass	—
Verify Contact Method Saved Correctly	Pass	Pass

Related Person Management Tests

Manage Contact Information is one of several worker-record maintenance scenarios in the Person Management cluster — explore the related address, national identifier and emergency contact scenarios below.

Manage Address Manage National Identifiers Manage Emergency Contacts

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

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

What is the difference between personal and work contact types?

Oracle Fusion HCM allows a worker to hold multiple contact methods of the same kind — for example a personal email and a work email, or a home phone and a mobile phone — distinguished by a configured contact type. This scenario validates that the selected type is captured correctly on each contact method, alongside the value itself.

How is a primary contact method handled when a worker has more than one?

Where multiple contact methods of the same type exist, Oracle Fusion typically supports designating one as primary, which can drive default behavior elsewhere in the system. This test validates that the primary indicator is set and changed correctly, and that changing the primary designation does not incorrectly remove other valid contact methods.

Does this test validate email and phone format checking?

Yes. Negative variations of this scenario are designed to confirm that Oracle Fusion correctly enforces expected format validation — for example rejecting an improperly formatted email address or a phone number missing a required country code — rather than silently accepting invalid values.

Can employees update their own contact information through self-service?

In many Oracle Fusion HCM implementations, employees can update certain contact methods through employee self-service, subject to the customer's security and approval configuration. Where self-service is enabled, this scenario can include a representative self-service variation; where it is not enabled, updates are typically restricted to HR Specialists or HR Managers.

How does SyntraFlow test security around contact information updates?

Access to add or update a worker's contact information is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an HR Specialist, an employee via self-service, and an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.