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

Syntra Standard Oracle Test Library

Oracle Fusion HCM National Identifier Test Cases

Validate creation, update and validation of permitted worker national identifiers in Oracle Fusion HCM, confirming that country-specific legislative rules, identifier-type configuration and the restricted security profile governing this sensitive data type are all correctly enforced.

Test ID	ORCL.HCM.COREHR.PERSON.NATIONAL_ID
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 HCM UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting; national identifier values used during execution are masked or DataVault-protected rather than real. This scenario is presented as 8 business-readable test steps; SyntraFlow's automation executes approximately 22 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates that Oracle Fusion HCM correctly creates, updates and validates permitted worker national identifiers, in line with country-specific legislative rules and the restricted security profile that governs this sensitive data type.

The scenario should confirm that:

the correct identifier type is available for the worker's country/legislation
a permitted national identifier is created and associated with the correct worker record
format and legislative validation rules are correctly applied to the identifier value
duplicate identifier values are correctly detected and rejected
only users with the appropriate security profile can view or edit national identifiers
sensitive identifier values are never exposed in plain form in test evidence, reports or screenshots

This scenario validates the Manage National Identifiers event within Person Management, alongside Manage Contact Information, Manage Emergency Contacts and Manage Address. Because national identifiers are the most sensitive data type in this cluster, this scenario places particular emphasis on security-profile enforcement and on how sensitive values are handled in test evidence.

When to Use This Test

Functional testing of national identifier creation and update for a new Oracle Fusion HCM implementation
Regression testing of identifier validation and security enforcement after an Oracle quarterly update
UAT sign-off confirming that only authorized roles can view or edit national identifiers before go-live
Security and compliance testing of restricted-data access controls across multiple countries/legislations

Where This Test Fits in the Person Management Process

Navigate to Person Management

→

Locate Worker Record

→

Open National Identifiers

→

Select Type and Country

→

Enter Identifier Value

→

Review

→

Submit

→

Verify and Restrict Access

This test covers adding, updating and validating a worker's national identifiers within Person Management. It sits alongside Manage Contact Information, Manage Emergency Contacts and Manage Address as part of the same worker-data maintenance activities, but is subject to a materially stricter security profile because national identifiers are classified as sensitive personal data.

← Previous Stage

Manage Address

Preconditions

The worker record is active.
The applicable national identifier type is configured for the worker's country/legislation.
The test user has the appropriate security profile and data-access privileges to view or edit national identifiers, a restricted data type in Oracle Fusion.
Reference data for country/legislation and identifier type is available and current.
Where masked or de-identified test values are required, they are sourced through Syntra DataVault rather than entered manually.

Exact identifier types, mandatory attributes and validation rules vary by country/legislation and by customer security configuration; not every identifier type is available in every legislation.

Sample Test Data

Person Number	${PERSON_NUMBER}
Country/Legislation	${COUNTRY_LEGISLATION}
Identifier Type	${IDENTIFIER_TYPE}
National Identifier Value	${NATIONAL_IDENTIFIER}
Issue Date	${ISSUE_DATE}
Expiration Date	${EXPIRATION_DATE}
Primary Indicator	${PRIMARY_INDICATOR}
Effective Date	${EFFECTIVE_DATE}
User Role	${USER_ROLE}

Sample values are illustrative ${PLACEHOLDER} tokens, never real national identifiers. Wherever a national identifier value must appear in test evidence, it is masked as ***-**-1234 rather than shown in plain form; replace placeholders with masked or DataVault-protected test data appropriate to the target Oracle Fusion environment.

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion HCM Sign in to Oracle Fusion Cloud with a user account that has the appropriate Person Management and national identifier security profile. ${USER_ROLE}	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Person Management Navigate to My Client Groups, or the equivalent workforce area, and open Person Management.	The Person Management work area opens successfully.
3	Locate the Worker Record Search for and open the target worker record using the person number. ${PERSON_NUMBER}	The correct worker record is retrieved and opened.
4	Initiate Add/Update National Identifier Open the National Identifiers section for the worker and start the add or update action.	The National Identifiers entry page opens, ready for input.
5	Select Identifier Type and Country Select the identifier type and country/legislation applicable to the worker. ${IDENTIFIER_TYPE} / ${COUNTRY_LEGISLATION}	The selected identifier type is accepted as valid for the chosen country/legislation.
6	Enter Identifier Value Enter the national identifier value using masked or placeholder test data, along with issue date, expiration date, primary indicator and effective date as applicable. ${NATIONAL_IDENTIFIER} (masked as *--1234 in test evidence) SyntraFlow always uses masked or ${PLACEHOLDER} test data for this field and never displays a real national identifier value in the UI, in logs or in captured evidence.	The entered identifier and related attributes are accepted without validation errors.
7	Review and Submit Review the entered identifier details and submit the change for processing.	Oracle Fusion HCM accepts the submission and returns a confirmation.
8	Verify Identifier Stored and Access RestrictedBusiness assertion Retrieve the worker record and confirm the identifier is stored correctly, then confirm that only users with the required security profile can view or edit it. This is the main business assertion for the scenario — the test does not stop merely because the submit action succeeded; correct storage and correct security enforcement must both be confirmed.	The identifier is stored correctly and associated with the correct type and country; the value remains masked in test evidence, and access is confirmed as restricted to authorized roles.

Expected Results

A permitted national identifier is added or updated successfully using valid type, country and identifier data.
The identifier is correctly associated with the correct worker, identifier type and country/legislation.
Format and legislative validation rules are correctly enforced on the identifier value.
Duplicate identifier values are correctly detected and rejected.
Only users with the required security profile can view or edit the national identifier.
The identifier value is never exposed in plain form in test evidence, reports or screenshots.

Key Validation Checkpoints

Identifier stored correctly (confirmed via masked test evidence).
Correct identifier type and country/legislation associated.
Format validation applied.
Duplicate handling correct.
Access controls enforced — only authorized roles can view or edit.
Sensitive value handled securely in test evidence — never exposed in plain form.

Core Business Scenario

Manage National Identifiers

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 National Identifiers scenario. Jarvis AI can extend this scenario by generating additional positive and negative identifier variations across countries, identifier types and security personas, using masked or DataVault-protected test data rather than real national identifier values.

Teams do not need to manually build a separate identifier test for every country, identifier type and security-role combination. Jarvis uses the standard Manage National Identifiers scenario as the foundation and generates relevant, masked-data variations for the customer's environment.

From Standard Test to Executed Regression Pack

Locate Worker

The target worker record is located within Person Management.

Enter Identifier Details

Identifier type, country/legislation and a masked or placeholder identifier value are entered.

Submit Identifier Change

The add or update is submitted and processed by Oracle Fusion HCM.

Confirm Storage

Correct storage of the identifier is confirmed using masked test evidence.

Confirm Access Restriction

Access to the identifier is confirmed as restricted to authorized security profiles.

Regression Pack

Selected identifier variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Rather than maintaining a separate test for every country, identifier type and security-persona combination, SyntraFlow maintains one core Manage National Identifiers scenario and allows Jarvis AI to generate relevant, masked-data variations using the customer's available test data.

AI-Generated Test Variations

The same Manage National Identifiers 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 valid national identifier
Different identifier types
Different countries
Update permitted identifier attributes
Multiple identifier types where supported
HR Specialist access
Valid effective dates

Negative Scenarios

Invalid format
Duplicate identifier
Missing mandatory identifier
Unsupported identifier type
Invalid country/type combination
Unauthorized user
Invalid issue/expiry date
Worker record conflict

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, legislation and security profile — not every Oracle configuration behaves identically. No example in this list uses or represents a real national identifier value.

Generated Using Your DataVault Test Data

Generic placeholder data rarely reflects the identifier types, countries and security profiles configured in a real Oracle Fusion HCM environment. Where connected, Jarvis can use masked or protected test data available through Syntra DataVault to construct identifier scenarios relevant to the customer's actual implementation — never real national identifier values.

Standard Library Definition

Person Number               ${PERSON_NUMBER}
Country/Legislation          ${COUNTRY_LEGISLATION}
Identifier Type               ${IDENTIFIER_TYPE}
National Identifier Value     ${NATIONAL_IDENTIFIER}
Issue Date                    ${ISSUE_DATE}
Expiration Date               ${EXPIRATION_DATE}
Primary Indicator             ${PRIMARY_INDICATOR}
Effective Date                ${EFFECTIVE_DATE}
User Role                     ${USER_ROLE}

DataVault

Countries/Legislations
  Configured legislations and their identifier requirements
Identifier Types
  Identifier types permitted per legislation
Masked Identifier Values
  Format-valid, masked or synthetic identifier values — never real worker identifiers
Security Profiles
  Personas and roles used for access-control testing
Workers
  Active worker records eligible for identifier maintenance

Jarvis AI Generates

Scenario 01 — Add Identifier, Country A, Identifier Type 1
Scenario 02 — Add Identifier, Country B, Identifier Type 2
Scenario 03 — Update Effective Date on Existing Identifier
Scenario 04 — Duplicate Identifier Value Rejected
Scenario 05 — Unauthorized User Access Denied
Scenario 06 — Invalid Country/Type Combination Rejected
...

Privacy notice — national identifiers are sensitive personal data: this Syntra Standard test library page never displays a real national identifier anywhere in its documentation, sample test data or illustrative evidence. Every example on this page uses either an abstract ${NATIONAL_IDENTIFIER} placeholder token or an explicitly labeled masking illustration such as ***-**-1234, and neither form represents an actual worker's identifier in any format, country or legislation. When SyntraFlow executes this scenario against a real Oracle Fusion environment, national identifier values should be sourced as masked or protected test data through Syntra DataVault (/datavault/) using its data-masking controls (/datavault/data-masking/) rather than entered, stored or displayed in plain form at any stage of test design, execution, evidence capture or reporting. Because this data type carries a materially higher sensitivity and regulatory profile than most other HCM fields, treat masking as a mandatory control for this scenario, not an optional convenience.

Example Test Variations

Representative examples of Manage National Identifiers scenarios Jarvis can generate from this business scenario, spanning identifier type, country and security conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one. No example uses or represents a real national identifier value.

ID	Variation	Type	Key Difference	Execution
VAR-001	Add Valid National Identifier	Positive	Adds a permitted national identifier using a valid type and country combination	Syntra Ready
VAR-002	Different Identifier Type	Positive	Adds an identifier using an alternate permitted identifier type	Syntra Ready
VAR-003	Different Country/Legislation	Positive/Country	Adds an identifier under an alternate country/legislation	Syntra Ready
VAR-004	Update Permitted Identifier Attribute	Positive	Updates an editable attribute of an existing identifier record	Syntra Ready
VAR-005	Multiple Identifier Types	Positive	Worker record holds more than one identifier type where the legislation supports it	Syntra Ready
VAR-006	HR Specialist Access	Positive/Security	Authorized HR Specialist adds or updates the identifier	Syntra Ready
VAR-007	HR Manager View Access	Positive/Security	Authorized HR Manager views an existing identifier record	Syntra Ready
VAR-008	Valid Effective Date	Positive	Identifier change submitted with a valid effective date	Syntra Ready
VAR-009	Invalid Format	Negative	Identifier value entered does not match the expected format for the legislation	Syntra Ready
VAR-010	Duplicate Identifier	Negative	Identifier value duplicates an existing record	Syntra Ready
VAR-011	Missing Mandatory Identifier	Negative	Legislation-mandated identifier is left blank	Syntra Ready
VAR-012	Unsupported Identifier Type	Negative	Identifier type is not supported for the selected legislation	Syntra Ready
VAR-013	Invalid Country/Type Combination	Negative/Country	Identifier type is not valid for the selected country	Syntra Ready
VAR-014	Unauthorized User	Negative/Security	User without the required security profile attempts to view or edit the identifier	Syntra Ready
VAR-015	Invalid Issue/Expiry Date	Negative	Issue date or expiration date fails date validation	Syntra Ready
VAR-016	Worker Record Conflict	Negative	Identifier change conflicts with existing worker record state	Syntra Ready

Positive and Negative National Identifier Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion HCM successfully creates or updates a worker's national identifier when the identifier type, country/legislation and identifier value are all valid and the acting user holds the required security profile.

Valid Identifier Type + Valid Country + Authorized Security Profile → Identifier Saved Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's format, legislative and security validations around national identifiers.

Invalid Format → Expected Format Validation
Duplicate Identifier → Expected Duplicate Validation
Missing Mandatory Identifier → Expected Required-Field Validation
Invalid Country/Type Combination → Expected Configuration Validation
Unauthorized User → Expected Access Restriction
Invalid Issue/Expiry Date → Expected Date Validation

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 national identifier scenarios and group them into reusable execution packs.

HCM Manage National Identifiers Regression Pack

Add Valid National Identifier
Different Identifier Type
Different Country/Legislation
Update Permitted Identifier Attribute
Multiple Identifier Types
HR Specialist Access
Invalid Format
Duplicate Identifier
Missing Mandatory Identifier
Invalid Country/Type Combination
Unauthorized User
Worker Record Conflict

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 National Identifiers scenarios individually or as a batch, using masked or DataVault-protected identifier values. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected identifier scenarios unattended and records the outcome of each test and business assertion, with sensitive values kept masked throughout.

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

Pack	HCM Manage National Identifiers Regression Pack
Schedule	Nightly 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 masked 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

National identifiers are a restricted data type in Oracle Fusion HCM, and role and security configuration is customer-specific. SyntraFlow can exercise Manage National Identifiers under different personas to confirm the customer's own access model correctly allows or prevents viewing and editing, rather than assuming a universal Oracle security model.

Persona	Action	Expected	Syntra Result
HR Specialist	Update Worker National Identifier	Allowed if security profile permits	PASS
HR Manager	View National Identifier	Allowed if security profile permits	PASS
Line Manager	Attempts to View National Identifier	Access prevented	PASS
Unauthorized User	Attempts Same 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

Masked Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Manage National Identifiers scenario, available masked DataVault test data and expected business outcomes to generate additional identifier and security coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use masked, relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business and security 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 National Identifiers, 8 Business Steps

↓

DataVault — Masked Identifier Test Data

↓

Jarvis AI — Generate Positive + Negative + Security Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Masked Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Select Identifier Type and Country

May internally include

Open Identifier Type LOV → Select Type → Open Country/Legislation LOV → Select Country → Confirm

Business Step

Verify Identifier Stored and Access Restricted

May internally include

Retrieve Worker → Confirm Identifier Record → Mask Value in Evidence → Attempt Access as Restricted Persona → Confirm Denial

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceMasked / redacted evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause, for example DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR, rather than assuming a defect. For example: Manage National Identifiers failed — Likely category: SECURITY_ERROR — Evidence: Test user's security profile does not grant access to national identifier maintenance — Recommended action: Assign the correct security profile and rerun. A failure should not be labeled as an Oracle application defect without supporting evidence; most failures trace back to test data, configuration, security or environment conditions.

Step	Action Status	Business Validation
Submit	Pass	—
Enter Identifier Value	Pass	—
Verify Identifier Stored and Access Restricted	Pass	Pass

Related Person Management Tests

Managing national identifiers is one of several worker-data maintenance activities within Person Management. Explore the related contact, emergency-contact and address scenarios below.

Manage Contact Information Manage Emergency Contacts Manage Address

Turn This Standard Test into Your Oracle HCM National Identifier Regression Suite

Start with the Syntra Standard Manage National Identifiers test, use DataVault to provide masked, environment-specific identifier and security-persona data, let Jarvis generate additional positive, negative and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore HCM 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 Person Management Syntra DataVault DataVault Data Masking

Frequently Asked Questions

How are national identifier values protected in test evidence?

SyntraFlow never displays a real national identifier value in the UI, in logs or in captured evidence. Test data uses ${PLACEHOLDER} tokens, and wherever a value must appear in evidence it is shown in an explicitly masked form such as ***-**-1234, or is sourced as a protected value through Syntra DataVault.

What national identifier types does this test support?

Supported identifier types vary by country/legislation and by customer configuration in Oracle Fusion HCM. Jarvis can generate variations covering the identifier types relevant to a customer's configured legislations rather than assuming a single universal identifier type.

Who can view or edit a worker's national identifier?

National identifiers are a restricted data type in Oracle Fusion HCM, and access is governed by the customer's own security profile and role configuration. This test scenario, and its security variations, are designed to confirm that only users with the required security profile can view or edit the identifier — not to assume a specific universal access model.

How is duplicate identifier detection tested?

Negative variations of this scenario submit an identifier value that matches an existing record to confirm that Oracle Fusion correctly detects and rejects the duplicate, rather than silently accepting it.

How does SyntraFlow approach security testing for this scenario?

SyntraFlow can exercise Manage National Identifiers under multiple personas — for example an authorized HR Specialist versus a Line Manager or an unauthorized user — to confirm that Oracle correctly allows or prevents access, based on the customer's own security configuration.

Where can I read more about how SyntraFlow masks sensitive test data?

See Syntra DataVault and DataVault Data Masking for more detail on how masked and protected test values are generated and used across sensitive HCM fields, including national identifiers.