{
  "test_id": "ORCL.HCM.COREHR.PERSON.UPDATE",
  "scenario_name": "Update Person Information",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Core HR",
  "process": "Person Management",
  "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/person-management/update-person-information/",
  "objective": {
    "intro": "The objective of this test is to validate that a permitted update to an active worker's personal information — such as preferred name, legal name, title, marital status, date of birth or gender, where applicable under legislation and configuration — is captured and applied correctly in Oracle Fusion HCM, with effective dating, auditability and the worker's existing employment relationship preserved.",
    "confirms": [
      "the change is applied to the correct worker record",
      "the new attribute value(s) take effect from the entered effective date",
      "fields that were not part of the change remain unaffected",
      "the worker's employment relationship and assignment are unaffected by the change",
      "prior effective-dated values remain visible in the worker's history rather than being overwritten",
      "only users with appropriate security access can make the change"
    ],
    "scope_note": "This scenario covers a general-purpose effective-dated update to one or more personal information attributes for an existing active worker within Oracle Fusion HCM TEST/UAT environments. It does not cover the initial hire event or address and contact-information updates, which are covered by the separate Hire Employee, Manage Address and Manage Contact Information scenarios within the same Core HR Person Management area."
  },
  "preconditions": [
    "An active worker record exists in Oracle Fusion HCM.",
    "The test user holds the appropriate role and data security access to update the attribute being changed.",
    "The legislative context (legislative data group) for the worker is known and configured.",
    "The effective date entered for the change is a valid date within an open period."
  ],
  "test_data": [
    {
      "field": "Person Number",
      "example": "${PERSON_NUMBER}"
    },
    {
      "field": "Worker Type",
      "example": "${WORKER_TYPE}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Preferred Name",
      "example": "${PREFERRED_NAME}"
    },
    {
      "field": "Legal Name",
      "example": "${LEGAL_NAME}"
    },
    {
      "field": "Title",
      "example": "${TITLE}"
    },
    {
      "field": "Marital Status",
      "example": "${MARITAL_STATUS}"
    },
    {
      "field": "Date of Birth",
      "example": "${DATE_OF_BIRTH}"
    },
    {
      "field": "Gender",
      "example": "${GENDER}"
    },
    {
      "field": "Legislative Context",
      "example": "${LEGISLATIVE_CONTEXT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Person Management",
      "action": "Sign in to Oracle Fusion using an authorised HR test user and navigate to Person Management.",
      "test_data": "",
      "expected_result": "The Person Management landing page opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Locate the Worker Record",
      "action": "Search for and open the active worker whose personal information will be updated.",
      "test_data": "${PERSON_NUMBER}",
      "expected_result": "The correct worker and current personal information 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 Personal Information Update",
      "action": "Select the option to update the worker's personal information.",
      "test_data": "",
      "expected_result": "The personal information update screen opens for the selected worker.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter Effective Date",
      "action": "Enter the date from which the personal information 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 Update",
      "action": "Select and enter the new value(s) for the attribute(s) being updated, such as preferred name, title or other permitted personal attributes.",
      "test_data": "${PREFERRED_NAME} / ${LEGAL_NAME} / ${TITLE} / ${MARITAL_STATUS} / ${DATE_OF_BIRTH} / ${GENDER}",
      "expected_result": "The new attribute value(s) are accepted and reflected on the pending update.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Updated Information",
      "action": "Review the updated personal information as calculated by Oracle Fusion before submitting the change.",
      "test_data": "",
      "expected_result": "The previewed information reflects the intended new values alongside unchanged fields.",
      "validation_type": "action",
      "note": "Reviewing the updated information before submission lets the tester catch an incorrect field entry before the change is created."
    },
    {
      "step_number": 7,
      "step_name": "Submit the Update",
      "action": "Submit and confirm the personal information update for creation in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the update without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Update Applied Correctly With History Preserved",
      "action": "Reopen or refresh the worker's personal information and confirm the new attribute values and prior history.",
      "test_data": "",
      "expected_result": "The new values are correctly effective as of ${EFFECTIVE_DATE} and the prior effective-dated record remains visible in the worker's history.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — correctly effective-dated values with preserved history are the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The personal information update is accepted and processed for the correct worker.",
    "New attribute values are effective from the correct effective date.",
    "Fields that were not part of the change remain unchanged.",
    "The worker's employment relationship and assignment remain intact.",
    "The prior effective-dated record remains preserved in the worker's history.",
    "Access restrictions are correctly honored for the requesting user.",
    "The change is visible and traceable in the worker's history."
  ],
  "validation_checkpoints": [
    "Intended value is updated correctly.",
    "Correct effective date is applied.",
    "Historical data is retained — the prior effective-dated row is preserved.",
    "Unaffected attributes remain unchanged.",
    "Worker's employment relationship remains intact.",
    "Audit/history is visible where available.",
    "Access restrictions are correctly honored."
  ]
}