Oracle ERP Testing Tool > Test Library > HCM > Compensation

Syntra Standard Oracle Test Library

Oracle Fusion Salary Change Test Cases

Validate entry, calculation and effective-dating of individual worker salary changes, including grade-range and downstream payroll behavior, without hard-coding any specific percentage or dollar figure as universal — a comprehensive catalog of 40 individual Salary Change test scenarios, the first family page in the Compensation cluster, spanning standard changes, employment-event-driven changes, salary basis/frequency, grade-range boundaries and downstream payroll/history testing.

Test ID	ORCL.HCM.COMP.SALARY.CHANGE
Application	Oracle Fusion Cloud
Product	HCM
Module	Compensation
Process	Salary Change
Business Flow	Compensation-to-Pay
Scenario Type	Positive / Negative / Boundary / Security
Test Usage	Functional Testing / Regression Testing / UAT Sign-Off
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion HCM Compensation 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 28 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates entry, calculation and effective-dating of individual worker salary changes in Oracle Fusion HCM Compensation, including grade-range and downstream payroll behavior, without hard-coding any specific percentage or dollar figure as a universal standard.

The scenario should confirm that:

a proposed salary change can be entered for a worker with the correct amount or percentage, change reason and effective date
salary changes correctly apply as current-dated, future-dated or backdated where backdating is permitted by configuration
salary changes correctly reflect the applicable salary basis and frequency (annual, hourly, monthly or another configured basis)
proposed salaries are correctly evaluated against the applicable grade minimum and maximum, including boundary and out-of-range values
deliberately invalid submissions — zero or negative salary, missing change reason, invalid effective date, inactive or terminated worker, unauthorized change — are correctly rejected or flagged rather than silently accepted
an approved salary change is correctly reflected in the worker's record, in payroll and in retained salary history

A negative or boundary Salary Change scenario passes when Oracle correctly enforces the expected data, grade-range or approval rule; this test does not attempt to certify a specific Oracle application defect, and does not hard-code any specific percentage or dollar figure as a universal standard — actual increase amounts, percentages and grade ranges depend entirely on customer-specific Oracle Fusion configuration. Where an entry or validation appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion. This page catalogs 40 individual Salary Change scenarios — the first family page in the Compensation cluster — as a single comprehensive reference rather than as separate indexable pages.

When to Use This Test

Functional testing of salary change entry, grade-range evaluation and effective-dating for a new Oracle Fusion HCM Compensation implementation
Regression testing of salary calculation and payroll impact after an Oracle quarterly update affecting Compensation
UAT sign-off for salary changes across standard entry, employment-event-driven changes, basis/frequency and grade-range boundary scenarios
Baseline salary-change coverage referenced by Individual Compensation, Workforce Compensation and Compensation Approval within the same Compensation cluster
Comprehensive scenario coverage for teams standardizing on a single Salary Change regression pack instead of dozens of near-duplicate scripts

Where This Test Fits in the Compensation-to-Pay Process

Salary Change

→

Individual Compensation

→

Workforce Compensation

→

Compensation Approval

Salary Change is the first and largest scenario family in the Compensation cluster. It exercises salary entry, calculation, grade-range evaluation and effective-dating, together with negative, boundary and security validation, and feeds Individual Compensation, Workforce Compensation and Compensation Approval downstream. Exact grade ranges, approval thresholds and payroll impact depend entirely on customer-specific Oracle Fusion Compensation configuration — no universal percentage or dollar figure is assumed.

Next Stage →

Individual Compensation

Preconditions

Oracle Fusion Compensation access is available to the test user.
A representative ${WORKER} with an active assignment and a current ${CURRENT_SALARY} on record is available.
Valid ${GRADE} configuration, including ${GRADE_MIN} and ${GRADE_MAX}, is available for the worker's position.
A ${SALARY_BASIS} configuration (annual, hourly, monthly or another configured basis) is available for testing basis and frequency scenarios.
A list of valid ${CHANGE_REASON} values is configured and available for selection.
An inactive or terminated worker record is available for negative testing, alongside a user without the required Compensation security access.
Where retroactive processing is configured, a payroll period suitable for testing backdated salary changes is available.

Exact grade ranges, salary basis configuration and retroactive/payroll processing rules may vary by Oracle Fusion implementation and customer-specific configuration; no universal percentage, dollar figure or approval threshold is assumed.

Sample Test Data

Worker	${WORKER}
Current Salary	${CURRENT_SALARY}
Proposed Salary	${PROPOSED_SALARY}
Change Percent	${CHANGE_PERCENT}
Grade	${GRADE}
Grade Minimum	${GRADE_MIN}
Grade Maximum	${GRADE_MAX}
Salary Basis	${SALARY_BASIS}
Effective Date	${EFFECTIVE_DATE}
Change Reason	${CHANGE_REASON}

Sample values are illustrative ${PLACEHOLDER} tokens, not real salary, grade or worker data. Replace them with valid worker, grade and salary data from the target Oracle Fusion TEST or UAT environment; not every field applies to every scenario, and no specific percentage or dollar figure is a universal standard.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~28 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 Compensation access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Worker's Compensation Record Navigate to the compensation area for ${WORKER} and open the record used to enter a salary change. ${WORKER}	The worker's compensation record opens with the current salary and grade details visible.
3	Enter Proposed Salary Change Enter the proposed salary change with a change reason and effective date. ${PROPOSED_SALARY} / ${CHANGE_REASON} / ${EFFECTIVE_DATE}	The proposed salary, change reason and effective date are recorded correctly on the change entry.
4	Verify Against Grade RangeBusiness assertion Confirm the proposed salary is evaluated against the applicable grade range for the worker's position. ${GRADE} / ${GRADE_MIN} / ${GRADE_MAX} Correctly blocking or warning on an out-of-range salary is a passing outcome for negative and boundary scenarios, not a failure.	The proposed salary is correctly accepted, warned or blocked according to the configured grade-range rule.
5	Submit the Salary Change Submit the salary change for processing.	A valid salary change is submitted successfully, or a deliberately invalid submission is rejected with the expected validation.
6	Verify Change Reflected in Worker RecordBusiness assertion Confirm the salary change is reflected on the worker's compensation record after submission. ${PROPOSED_SALARY}	The worker's record correctly shows the new salary against the intended effective date.
7	Verify Payroll Picks Up the ChangeBusiness assertion Confirm that payroll correctly picks up the approved salary change for the applicable pay period. ${EFFECTIVE_DATE} This is the main downstream business assertion for the scenario across the full catalog of 40 Salary Change variations.	Payroll correctly reflects the new salary, including retro processing where configured for a backdated change.
8	Verify Salary History Retains Prior ValueBusiness assertion Confirm that the worker's salary history retains the prior salary value alongside the newly recorded value. ${CURRENT_SALARY}	Salary history correctly retains the prior value rather than overwriting it.

Expected Results

Each salary change recorded correctly with the intended proposed salary, change reason and effective date.
Percentage-based and amount-based changes correctly calculated the resulting proposed salary.
Grade-range rules correctly enforced — within range, at minimum, at maximum, below range, above range or warning-only as configured.
Employment-event-driven changes (promotion, transfer, global transfer, assignment change) correctly updated salary alongside the related event.
Deliberately invalid submissions raised the expected data, grade-range or security validation rather than being silently accepted.
Approved changes correctly reflected in the worker record, in payroll and in retained salary history.

Key Validation Checkpoints

Salary correctly recorded against the intended effective date.
Grade-range rules correctly enforced (warning or block as configured).
Percentage vs. amount changes calculate correctly.
Inactive/terminated worker changes correctly blocked.
Downstream worker record and payroll reflect the change accurately.
Salary history correctly retained.

Core Business Scenario

Salary Change

Scenario Catalog

40 Scenarios

Business Steps

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 Salary Change scenario. Jarvis AI can extend this scenario by systematically generating additional Positive, Negative, Boundary, Approval, Security and Retro variations using customer-specific worker, grade, salary and payroll data available through Syntra DataVault.

Teams do not need to manually construct dozens of near-identical salary scenarios to cover every grade, basis and effective-dating combination. Jarvis uses the standard salary change scenario as the foundation and generates coverage relevant to the customer's environment — without creating additional indexable pages.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Salary Change scenario and automation logic.

Customer DataVault

Provides approved customer-specific test data required for variation generation — Worker, Current Salary, Proposed Salary, Grade, Grade Range, Salary Basis, Effective Date and Change Reason.

Jarvis AI

Analyses the standard salary change scenario together with available test data and generates Positive, Negative, Boundary, Approval, Security and Retro variations.

Positive + Negative + Boundary + Approval + Security + Retro Variations

Correctly entered, calculated and approved salary changes and deliberately invalid, boundary, unauthorized or backdated conditions.

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 exception classification.

Rather than maintaining a separate test for every possible salary entry, calculation and grade-range condition, SyntraFlow maintains one core Salary Change scenario and allows Jarvis AI to generate Positive, Negative, Boundary, Approval, Security and Retro variations using the customer's available worker, grade and payroll test data.

AI-Generated Test Variations

The same Salary Change 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 Compensation.

Positive Scenarios

Standard salary increase and decrease entry
Promotion, transfer and global-transfer-driven salary changes
Salary basis and frequency handling (annual, hourly, monthly)
Salary correctly evaluated within the configured grade range
Multiple effective-dated salary changes maintained independently
Approved changes correctly reflected in the worker record and payroll

Negative Scenarios

Zero or negative proposed salary
Salary outside the configured grade range
Missing change reason on the salary entry
Salary change attempted for an inactive or terminated worker
Unauthorized user attempting a salary change
Invalid effective date or invalid salary basis

These are representative examples only. Grade ranges, approval thresholds and validation messages can depend on the customer's Oracle Fusion configuration and Compensation setup — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every worker, grade and salary combination in a real Oracle Fusion HCM Compensation environment. Where connected, Jarvis can use approved test data available through Syntra DataVault — Worker, Grade, Grade Range, Salary Basis and Payroll — to construct realistic Salary Change variations relevant to the customer's actual implementation.

Standard Library Definition

Worker                 ${WORKER}
Current Salary          ${CURRENT_SALARY}
Proposed Salary         ${PROPOSED_SALARY}
Change Percent          ${CHANGE_PERCENT}
Grade                   ${GRADE}
Grade Minimum           ${GRADE_MIN}
Grade Maximum           ${GRADE_MAX}
Salary Basis            ${SALARY_BASIS}
Effective Date          ${EFFECTIVE_DATE}
Change Reason           ${CHANGE_REASON}

DataVault

Workers and Grades
  Workers with valid and invalid grade/salary combinations
Grade Ranges
  Grades with configured minimum and maximum compensation values
Salary Basis
  Annual, hourly and other configured salary bases and frequencies
Payroll
  Payroll periods and elements used for downstream salary verification
Security
  Roles with and without salary change authorization

Jarvis AI Generates

Scenario 01 — Standard Salary Increase
Scenario 02 — Salary at Grade Maximum
Scenario 03 — Salary Above Grade Range
Scenario 04 — Backdated Salary Triggers Retro
Scenario 05 — Missing Change Reason
Scenario 06 — Unauthorized Salary Change
...

Salary Change test data can include sensitive worker compensation information. SyntraFlow test scenarios use masked or synthetic worker and salary data provided through Syntra DataVault rather than real salary figures — scenarios reference ${CURRENT_SALARY} and ${PROPOSED_SALARY} as parameterized tokens throughout rather than actual compensation amounts. See /datavault/data-masking/ for how DataVault protects worker and salary data used across the Compensation test catalog.

Example Test Variations

A comprehensive catalog of 40 individual Salary Change test scenarios spanning standard changes, employment-event-driven changes, salary basis/frequency, grade-range boundaries and downstream payroll/history testing. Filter or search below.

ID	Variation	Type	Key Difference	Execution
COMP-SAL-001	Enter Salary Change	Positive	Validate that a proposed salary change for ${WORKER} can be entered with ${PROPOSED_SALARY}, ${CHANGE_REASON} and ${EFFECTIVE_DATE}; Oracle Fusion records the salary change entry correctly.	SyntraFlow Ready
COMP-SAL-002	Salary Increase	Positive	Validate that a salary increase from ${CURRENT_SALARY} to a higher ${PROPOSED_SALARY} is entered for ${WORKER}; Oracle Fusion correctly records the increase against ${EFFECTIVE_DATE}.	SyntraFlow Ready
COMP-SAL-003	Salary Decrease	Positive	Validate that a salary decrease from ${CURRENT_SALARY} to a lower ${PROPOSED_SALARY} is entered for ${WORKER} with ${CHANGE_REASON}; Oracle Fusion correctly records the decrease.	SyntraFlow Ready
COMP-SAL-004	Percentage Increase	Positive	Validate that a salary change entered using ${CHANGE_PERCENT} rather than a flat amount correctly calculates ${PROPOSED_SALARY} from ${CURRENT_SALARY} for ${WORKER}.	SyntraFlow Ready
COMP-SAL-005	Amount Increase	Positive	Validate that a salary change entered as a flat amount rather than ${CHANGE_PERCENT} correctly sets ${PROPOSED_SALARY} for ${WORKER}.	SyntraFlow Ready
COMP-SAL-006	Future-Dated Salary Change	Positive	Validate that a salary change for ${WORKER} can be entered with ${EFFECTIVE_DATE} set in the future; Oracle Fusion correctly holds the change until the future effective date.	SyntraFlow Ready
COMP-SAL-007	Current-Date Salary Change	Positive	Validate that a salary change for ${WORKER} entered with ${EFFECTIVE_DATE} set to the current date is applied immediately and recorded correctly.	SyntraFlow Ready
COMP-SAL-008	Backdated Salary Change Where Permitted	Positive	Validate that where backdating is permitted by configuration, a salary change for ${WORKER} entered with an ${EFFECTIVE_DATE} in the past is correctly recorded and flagged for retroactive processing.	SyntraFlow Ready
COMP-SAL-009	Correct Existing Salary	Positive	Validate that an already-entered salary change for ${WORKER} on a given ${EFFECTIVE_DATE} can be corrected to a different ${PROPOSED_SALARY}; Oracle Fusion correctly updates the existing entry rather than creating a duplicate.	SyntraFlow Ready
COMP-SAL-010	Multiple Effective-Dated Salary Changes	Positive	Validate that multiple salary changes with different ${EFFECTIVE_DATE} values can be entered for ${WORKER} in sequence; Oracle Fusion correctly maintains each effective-dated record independently.	SyntraFlow Ready
COMP-SAL-011	Salary Change During Promotion	Positive	Validate that a salary change for ${WORKER} entered together with a promotion correctly updates ${PROPOSED_SALARY} and ${GRADE} in the same transaction.	SyntraFlow Ready
COMP-SAL-012	Salary Change During Transfer	Positive	Validate that a salary change for ${WORKER} entered together with a transfer to a new organization or position correctly updates ${PROPOSED_SALARY} alongside the transfer.	SyntraFlow Ready
COMP-SAL-013	Salary Change During Global Transfer Where Applicable	Positive	Validate that where global transfer is configured, a salary change for ${WORKER} entered as part of a global transfer correctly updates ${PROPOSED_SALARY} and ${SALARY_BASIS} for the new legal employer.	SyntraFlow Ready
COMP-SAL-014	Salary Change After Hire	Positive	Validate that a salary change entered for ${WORKER} shortly after hire correctly updates ${PROPOSED_SALARY} from the original hire salary with ${EFFECTIVE_DATE} recorded correctly.	SyntraFlow Ready
COMP-SAL-015	Salary Change During Assignment Change	Positive	Validate that a salary change for ${WORKER} entered together with an assignment change correctly updates ${PROPOSED_SALARY} in the same assignment transaction.	SyntraFlow Ready
COMP-SAL-016	Annual Salary	Positive	Validate that a salary change for ${WORKER} entered on an annual ${SALARY_BASIS} correctly records ${PROPOSED_SALARY} as an annualized figure.	SyntraFlow Ready
COMP-SAL-017	Hourly Salary Basis	Positive	Validate that a salary change for ${WORKER} entered on an hourly ${SALARY_BASIS} correctly records ${PROPOSED_SALARY} as an hourly rate.	SyntraFlow Ready
COMP-SAL-018	Monthly Salary Basis Where Configured	Positive	Validate that where a monthly ${SALARY_BASIS} is configured, a salary change for ${WORKER} correctly records ${PROPOSED_SALARY} as a monthly figure.	SyntraFlow Ready
COMP-SAL-019	Change Salary Basis Where Permitted	Positive	Validate that where permitted, ${SALARY_BASIS} for ${WORKER} can be changed (for example hourly to annual) alongside a salary change; Oracle Fusion correctly recalculates and records ${PROPOSED_SALARY} under the new basis.	SyntraFlow Ready
COMP-SAL-020	Salary Frequency Validation	Positive	Validate that the payment frequency associated with ${SALARY_BASIS} for ${WORKER} is correctly validated against the configured payroll frequency when a salary change is entered.	SyntraFlow Ready
COMP-SAL-021	Salary Within Grade Range	Positive	Validate that ${PROPOSED_SALARY} entered for ${WORKER} falls between ${GRADE_MIN} and ${GRADE_MAX} for ${GRADE}; Oracle Fusion accepts the change without a grade-range validation.	SyntraFlow Ready
COMP-SAL-022	Salary at Grade Minimum	Positive	Validate that ${PROPOSED_SALARY} entered for ${WORKER} exactly equal to ${GRADE_MIN} for ${GRADE} is accepted by Oracle Fusion as a valid boundary value.	SyntraFlow Ready
COMP-SAL-023	Salary at Grade Maximum	Positive	Validate that ${PROPOSED_SALARY} entered for ${WORKER} exactly equal to ${GRADE_MAX} for ${GRADE} is accepted by Oracle Fusion as a valid boundary value.	SyntraFlow Ready
COMP-SAL-024	Salary Below Grade Range	Negative/Boundary	Validate that ${PROPOSED_SALARY} entered for ${WORKER} below ${GRADE_MIN} for ${GRADE} is handled correctly; Oracle Fusion raises the expected grade-range validation or warning rather than silently accepting the out-of-range value.	SyntraFlow Ready
COMP-SAL-025	Salary Above Grade Range	Negative/Boundary	Validate that ${PROPOSED_SALARY} entered for ${WORKER} above ${GRADE_MAX} for ${GRADE} is handled correctly; Oracle Fusion raises the expected grade-range validation or warning rather than silently accepting the out-of-range value.	SyntraFlow Ready
COMP-SAL-026	Salary Range Warning Where Configured	Positive/Boundary	Validate that where a soft grade-range warning (rather than a hard block) is configured, ${PROPOSED_SALARY} near ${GRADE_MIN} or ${GRADE_MAX} for ${GRADE} correctly triggers the configured warning while still allowing the change to proceed.	SyntraFlow Ready
COMP-SAL-027	Zero Salary	Negative	Validate that entering ${PROPOSED_SALARY} as zero for ${WORKER} is handled correctly; Oracle Fusion raises the expected data validation rather than accepting a zero salary.	SyntraFlow Ready
COMP-SAL-028	Negative Salary	Negative	Validate that entering a negative value for ${PROPOSED_SALARY} for ${WORKER} is handled correctly; Oracle Fusion raises the expected data validation rather than accepting a negative salary.	SyntraFlow Ready
COMP-SAL-029	Missing Change Reason	Negative	Validate that submitting a salary change for ${WORKER} without ${CHANGE_REASON} is handled correctly; Oracle Fusion raises the expected data validation rather than accepting the incomplete change.	SyntraFlow Ready
COMP-SAL-030	Invalid Effective Date	Negative	Validate that submitting a salary change for ${WORKER} with an invalid or out-of-sequence ${EFFECTIVE_DATE} is handled correctly; Oracle Fusion raises the expected data validation.	SyntraFlow Ready
COMP-SAL-031	Salary Change for Inactive Worker	Negative	Validate that attempting a salary change for an inactive ${WORKER} is handled correctly; Oracle Fusion raises the expected validation rather than accepting the change.	SyntraFlow Ready
COMP-SAL-032	Salary Change for Terminated Worker	Negative	Validate that attempting a salary change for a terminated ${WORKER} is handled correctly; Oracle Fusion raises the expected validation rather than accepting the change.	SyntraFlow Ready
COMP-SAL-033	Unauthorized Salary Change	Negative/Security	Validate that a user without the required compensation security access attempting a salary change for ${WORKER} is blocked; Oracle Fusion raises the expected security validation and prevents the unauthorized change.	SyntraFlow Ready
COMP-SAL-034	Duplicate Effective-Date Change	Negative	Validate that submitting two conflicting salary changes for ${WORKER} on the same ${EFFECTIVE_DATE} is handled according to configuration; Oracle Fusion raises the expected validation rather than silently allowing an unintended duplicate.	SyntraFlow Ready
COMP-SAL-035	Invalid Salary Basis	Negative	Validate that entering a ${SALARY_BASIS} not valid for the worker's assignment is handled correctly for ${WORKER}; Oracle Fusion raises the expected data validation rather than accepting the invalid basis.	SyntraFlow Ready
COMP-SAL-036	Missing Required Salary Data	Negative	Validate that submitting a salary change for ${WORKER} with required fields such as ${PROPOSED_SALARY} or ${EFFECTIVE_DATE} missing is handled correctly; Oracle Fusion raises the expected data validation.	SyntraFlow Ready
COMP-SAL-037	Salary Change Reflected in Worker Record	Positive	Validate that an approved salary change for ${WORKER} is correctly reflected on the worker's compensation record with ${PROPOSED_SALARY} and ${EFFECTIVE_DATE}.	SyntraFlow Ready
COMP-SAL-038	Salary Change Reflected in Payroll	Positive	Validate that an approved salary change for ${WORKER} correctly flows through to payroll so ${PROPOSED_SALARY} is used for the next applicable payroll run.	SyntraFlow Ready
COMP-SAL-039	Backdated Salary Triggers Retro Where Configured	Positive	Validate that where retroactive processing is configured, a backdated salary change for ${WORKER} correctly triggers a retro payroll calculation reflecting ${PROPOSED_SALARY} from ${EFFECTIVE_DATE}.	SyntraFlow Ready
COMP-SAL-040	Salary History Retained	Positive	Validate that after a salary change for ${WORKER}, ${CURRENT_SALARY} is correctly retained in salary history alongside the new ${PROPOSED_SALARY} rather than being overwritten.	SyntraFlow Ready

Positive and Negative Salary Change Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion HCM correctly enters, calculates and applies a salary change when the proposed salary, grade, effective date and change reason are all valid.

Valid Worker + Salary Within Grade Range + Valid Effective Date → Salary Change Recorded and Reflected in Payroll

Negative Testing

Jarvis can also generate scenarios that deliberately violate a data, grade-range or security rule to confirm Oracle correctly rejects or flags the condition rather than silently accepting it.

Zero or Negative Salary → Expected Data Validation Displayed
Salary Outside Grade Range → Expected Grade-Range Validation Displayed
Missing Change Reason → Expected Data Validation Displayed
Salary Change for Terminated Worker → Expected Validation Displayed
Duplicate Effective-Date Change → Expected Validation Displayed
Unauthorized User → Access Prevented

A negative compensation scenario passes when Oracle correctly enforces the expected data, grade-range or approval rule

Scenario	Oracle Outcome	Test Result
Valid salary within range	Change recorded	PASS
Salary outside grade range	Validation occurs	PASS
Missing change reason	Validation occurs	PASS
Unauthorized user	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

HCM Salary Change Regression Pack

Enter Salary Change
Percentage Increase
Future-Dated Salary Change
Salary Change During Promotion
Salary Within Grade Range
Salary Below Grade Range
Zero Salary
Missing Change Reason
Unauthorized Salary Change
Salary Change Reflected in Payroll

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

Once scheduled, SyntraFlow executes the selected Salary Change 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 Salary Change Regression Pack
Schedule	Weekly Regression
Tests	40 scenarios
Execution	Batch Mode
Start	9: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

296

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

DataVault HCM Persona

Rather than generating variations from disconnected field values, Jarvis can draw on a DataVault persona built for salary changes — a pre-grouped, internally consistent set of worker, grade, salary and payroll dimensions, so Jarvis constructs realistic Salary Change scenarios rather than combining incompatible data.

Persona: Standard Salaried Employee

Worker Status	Active
Assignment	Active
Salary Basis	Annual
Current Salary	${CURRENT_SALARY} (Parameterized)
Grade	${GRADE} (Valid)
Grade Range	${GRADE_RANGE} (Parameterized)
Manager	${MANAGER} (Active)
Payroll	${PAYROLL} (Active)

DataVault personas group dependent compensation dimensions so Jarvis generates coherent, internally consistent Salary Change scenarios rather than arbitrary and potentially unrepresentative field combinations.

Security & Access Variations

Oracle Fusion HCM Compensation role and security configuration is customer-specific, so SyntraFlow can exercise salary change entry under different personas to confirm the customer's own access model behaves as expected, rather than assuming a universal Oracle security model.

Persona	Action	Expected	Syntra Result
Manager	Enter Salary Change for Direct Report	Allowed	PASS
Compensation Administrator	Enter Salary Change for Any Worker	Allowed	PASS
Unauthorized User	Attempts Salary Change	Access prevented	PASS

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Salary Change scenario, available DataVault test data and expected business outcomes to systematically generate Positive, Negative, Boundary, Approval, Security and Retro coverage for the customer's environment.

Generate

Positive, Negative, Boundary, Approval, Security and Retro variations.

Parameterize

Use relevant worker, grade and salary 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 — Salary Change, 8 Business Steps

↓

DataVault — HCM Persona-Specific Test Data

↓

Jarvis AI — Generate Positive/Negative/Boundary/Approval/Security/Retro 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 Proposed Salary Change

May internally include

Open Compensation Panel → Enter Proposed Salary → Select Change Reason → Set Effective Date → Save

Business Step

Verify Against Grade Range

May internally include

Retrieve Grade Minimum/Maximum → Compare Proposed Salary → Display Warning or Block If Out of Range → Capture Result

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 a salary change was correctly calculated, grade-validated or paid — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. Because this page aggregates 40 individual scenarios across standard changes, employment events, salary basis/frequency, grade-range boundaries and downstream payroll/history testing, evidence-based failure classification matters most here. When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause into one of eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — rather than assuming a defect. For example: Salary outside allowed range correctly rejected — Likely category: EXPECTED_VALIDATION — Evidence: the grade-range validation message matches the configured minimum or maximum for the grade — Recommended action: confirm the grade range configuration and close as expected behavior. Approved salary not reaching Payroll — Likely category: INTEGRATION_ERROR / CONFIGURATION_ERROR depending on evidence — Evidence: the worker record shows the new salary but the payroll element or payroll run does not reflect it — Recommended action: verify the compensation-to-payroll element mapping and payroll run parameters before resubmitting. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.

Step	Action Status	Business Validation
Enter Proposed Salary Change	Pass	—
Submit the Salary Change	Pass	—
Verify Change Reflected in Worker Record and Payroll	Pass	Pass

Related Compensation Tests

Salary Change is the first, largest scenario family in the Compensation cluster, covering 40 individual scenarios that feed Individual Compensation, Workforce Compensation and Compensation Approval downstream.

Individual Compensation Workforce Compensation Compensation Approval

Turn This Standard Test into Your Oracle HCM Salary Change Regression Suite

Start with the Syntra Standard Salary Change test, use DataVault to provide environment-specific worker, grade and salary data, let Jarvis generate additional Positive, Negative, Boundary, Approval, Security and Retro variations, and execute the resulting regression pack automatically with SyntraFlow.

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

Frequently Asked Questions

How many test scenarios does this Salary Change catalog cover, and why are they grouped on one page?

This page catalogs 40 individual Salary Change test scenarios — the first and largest family page in the Compensation cluster — spanning standard changes, employment-event-driven changes, salary basis/frequency, grade-range boundaries and downstream payroll/history testing. They are grouped on a single page rather than published as 40 separate URLs so search engines and users find one authoritative, comprehensive reference for Salary Change rather than dozens of thin near-duplicate pages; every scenario remains individually executable within SyntraFlow.

How does SyntraFlow test grade-range boundaries for a salary change?

Dedicated scenarios test a proposed salary within the configured grade range, exactly at the grade minimum, exactly at the grade maximum, below the grade minimum, above the grade maximum, and a soft warning-only condition where configured. Actual grade-range enforcement — hard block, soft warning or no enforcement — depends entirely on the customer's own Oracle Fusion Compensation configuration; no universal range is assumed.

Does SyntraFlow test backdated and retroactive salary changes?

Yes. Scenarios cover a backdated salary change entered where backdating is permitted by configuration, and a dedicated scenario confirms that, where retroactive processing is configured, a backdated change correctly triggers a retro payroll calculation. Actual retro processing rules depend on the customer's own payroll and compensation configuration.

How is salary basis and frequency tested?

Scenarios cover annual, hourly and, where configured, monthly salary bases, as well as changing the salary basis itself where permitted, and validating that the associated payment frequency is correctly recognized. Actual available bases and frequencies depend on the customer's own Oracle Fusion Compensation configuration.

How does SyntraFlow classify a failed Salary Change test?

When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause into one of eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — along with supporting evidence and a recommended action. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.

Why doesn't SyntraFlow hard-code a specific percentage or dollar amount for salary changes?

Salary increase percentages, dollar amounts, grade ranges and approval thresholds are entirely customer-specific and depend on the organization's own compensation structure and Oracle Fusion configuration. SyntraFlow's scenarios use ${CURRENT_SALARY}, ${PROPOSED_SALARY}, ${CHANGE_PERCENT}, ${GRADE_MIN} and ${GRADE_MAX} as parameterized tokens so the same scenario can be executed against any customer's real, environment-specific compensation data rather than a fixed universal figure.