{
  "test_id": "ORCL.HCM.COREHR.ASSIGNMENT.CHANGE",
  "scenario_name": "Change Assignment",
  "application": "Oracle Fusion Cloud HCM",
  "product": "Human Capital Management",
  "module": "Core HR",
  "process": "Hire-to-Retire",
  "business_flow": "Employee Lifecycle",
  "scenario_type": "Positive / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/core-hr/hire-to-retire/change-assignment/",
  "objective": {
    "intro": "The objective of this test is to validate that an effective-dated change to an active worker's assignment — such as department, job, position, location, manager, grade or working hours — is captured and applied correctly in Oracle Fusion HCM, and that the worker's prior assignment history is preserved rather than overwritten.",
    "confirms": [
      "the change is applied to the correct worker and assignment",
      "the new attribute value(s) take effect from the entered effective date",
      "fields that were not part of the change remain unaffected",
      "manager, department and job values on the resulting assignment are correct",
      "the assignment status correctly reflects the change where applicable",
      "the prior assignment record remains visible in the worker's employment history rather than being lost"
    ],
    "scope_note": "This scenario covers a general-purpose effective-dated change to one or more assignment attributes for an existing active worker within Oracle Fusion HCM TEST/UAT environments. It does not cover the initial hire event, promotion-specific business rules, or a change of legal employer / business unit, which are covered by the separate Hire Employee, Promote Worker and Transfer Worker scenarios in the same Hire-to-Retire lifecycle."
  },
  "preconditions": [
    "An active worker exists in Oracle Fusion HCM with an eligible, active assignment.",
    "The target department, job, position, location and manager for the change are valid and active.",
    "The effective date entered for the change is a valid date within an open period.",
    "The test user holds the appropriate HR role and data access to change the worker's assignment.",
    "Where position control is in effect, the target position has available headcount."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Current Department",
      "example": "${CURRENT_DEPARTMENT}"
    },
    {
      "field": "New Department",
      "example": "${NEW_DEPARTMENT}"
    },
    {
      "field": "Current Job",
      "example": "${CURRENT_JOB}"
    },
    {
      "field": "New Job",
      "example": "${NEW_JOB}"
    },
    {
      "field": "New Position",
      "example": "${NEW_POSITION}"
    },
    {
      "field": "New Location",
      "example": "${NEW_LOCATION}"
    },
    {
      "field": "New Manager",
      "example": "${NEW_MANAGER}"
    },
    {
      "field": "New Grade",
      "example": "${NEW_GRADE}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Employment Information",
      "action": "Sign in to Oracle Fusion using an authorised HR test user and navigate to the worker's employment information.",
      "test_data": "",
      "expected_result": "The worker's employment information page opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Locate the Worker's Assignment",
      "action": "Search for and open the active worker whose assignment will be changed.",
      "test_data": "${WORKER}",
      "expected_result": "The correct worker and current assignment details are displayed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening worker search, entering search criteria and selecting the result."
    },
    {
      "step_number": 3,
      "step_name": "Initiate Assignment Change",
      "action": "Select the option to change the worker's assignment.",
      "test_data": "",
      "expected_result": "The assignment change entry screen opens for the selected worker.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter Effective Date",
      "action": "Enter the date from which the assignment change should take effect.",
      "test_data": "${EFFECTIVE_DATE}",
      "expected_result": "The effective date is accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select Attribute(s) to Change",
      "action": "Select and enter the new value(s) for the attribute(s) being changed, such as department, job, position, location, manager or grade.",
      "test_data": "${NEW_DEPARTMENT} / ${NEW_JOB} / ${NEW_POSITION} / ${NEW_LOCATION} / ${NEW_MANAGER} / ${NEW_GRADE}",
      "expected_result": "The new attribute value(s) are accepted and reflected on the pending assignment change.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Resulting Assignment",
      "action": "Review the resulting assignment as calculated by Oracle Fusion before submitting the change.",
      "test_data": "",
      "expected_result": "The previewed assignment reflects the intended new values alongside unchanged fields.",
      "validation_type": "action",
      "note": "Reviewing the resulting assignment before submission lets the tester catch an incorrect field entry before the change is created."
    },
    {
      "step_number": 7,
      "step_name": "Submit the Assignment Change",
      "action": "Submit and confirm the assignment change for creation in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the assignment change without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify New Values Are Effective From the Correct Date",
      "action": "Reopen or refresh the worker's assignment and confirm the new attribute values.",
      "test_data": "",
      "expected_result": "The new assignment values are correctly effective as of ${EFFECTIVE_DATE}.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — correctly effective-dated values are the expected pass condition, not merely a successful save."
    },
    {
      "step_number": 9,
      "step_name": "Verify Prior Assignment History Is Preserved",
      "action": "Review the worker's assignment history after the change is recorded.",
      "test_data": "",
      "expected_result": "The prior assignment record remains visible in the worker's employment history and is not overwritten.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The assignment change is accepted and processed for the correct worker.",
    "New assignment values are effective from the correct effective date.",
    "Fields that were not part of the change remain unchanged.",
    "Manager, department and job values on the resulting assignment are correct.",
    "Assignment status correctly reflects the change where applicable.",
    "The prior assignment record remains preserved in the worker's employment history.",
    "The change is visible and traceable in the worker's employment history."
  ],
  "validation_checkpoints": [
    "New assignment values are effective from the correct effective date.",
    "Prior assignment history remains preserved and intact.",
    "Fields not part of the change remain unchanged.",
    "Manager, department and job values on the resulting assignment are correct.",
    "Assignment status is correct following the change.",
    "The change is visible in the worker's employment history."
  ]
}