{
  "test_id": "ORCL.HCM.COREHR.PERSON.EMERGENCY_CONTACT",
  "scenario_name": "Manage Emergency Contacts",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Core HR",
  "process": "Person Management",
  "business_flow": "Employee Lifecycle",
  "scenario_type": "Positive / Functional",
  "priority": "Medium",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/core-hr/person-management/manage-emergency-contacts/",
  "objective": {
    "intro": "The objective of this test is to validate that emergency-contact information for a worker can be created, updated and removed correctly in Oracle Fusion HCM, and that relationship, contact detail and primary-contact designation are captured and retained accurately.",
    "confirms": [
      "a new emergency contact is added correctly for the worker",
      "the relationship between the worker and the contact is recorded accurately",
      "the primary emergency-contact indicator is set and changed correctly",
      "updated contact details — name, phone, email and address — are saved correctly",
      "an emergency contact can be removed where the configuration allows it",
      "Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers creation, update and removal of emergency-contact records for a worker in Oracle Fusion HCM Core HR TEST/UAT environments. It does not cover the worker's own person, address or national-identifier records, which are covered by the separate Update Person Information, Manage Address and Manage National Identifiers scenarios in the same Person Management cluster."
  },
  "preconditions": [
    "The worker record is active in the target Oracle Fusion HCM environment.",
    "Relationship types used for emergency contacts are configured in the target environment.",
    "The test user has access to manage emergency-contact records for the worker.",
    "Where an existing contact is being updated or removed, at least one emergency-contact record already exists for the worker.",
    "The effective date used for the change falls within an open period for the worker's assignment."
  ],
  "test_data": [
    {
      "field": "Person Number",
      "example": "${PERSON_NUMBER}"
    },
    {
      "field": "Contact Name",
      "example": "${CONTACT_NAME}"
    },
    {
      "field": "Relationship",
      "example": "${RELATIONSHIP}"
    },
    {
      "field": "Contact Phone",
      "example": "${CONTACT_PHONE}"
    },
    {
      "field": "Contact Email",
      "example": "${CONTACT_EMAIL}"
    },
    {
      "field": "Contact Address",
      "example": "${CONTACT_ADDRESS}"
    },
    {
      "field": "Primary Emergency Contact",
      "example": "${PRIMARY_EMERGENCY_CONTACT}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    }
  ],
  "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 the Person Management work area.",
      "test_data": "",
      "expected_result": "The Person Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Locate the Worker Record",
      "action": "Search for and open the worker record that emergency-contact information will be maintained for.",
      "test_data": "${PERSON_NUMBER}",
      "expected_result": "The correct worker record opens.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select Add or Update Emergency Contact",
      "action": "Open the worker's Emergency Contacts page and select Add for a new contact, or select an existing contact to update.",
      "test_data": "${EFFECTIVE_DATE}",
      "expected_result": "The emergency-contact entry page opens for the worker as of the correct effective date.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter Contact Name and Relationship",
      "action": "Enter the emergency contact's name and select the relationship to the worker.",
      "test_data": "${CONTACT_NAME} / ${RELATIONSHIP}",
      "expected_result": "Contact name and relationship are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Contact Phone, Email and Address",
      "action": "Enter the emergency contact's phone number, and email and address where captured.",
      "test_data": "${CONTACT_PHONE} / ${CONTACT_EMAIL} / ${CONTACT_ADDRESS}",
      "expected_result": "Contact details are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Set Primary Emergency Contact Indicator",
      "action": "Set or change the primary emergency-contact indicator for the record being saved.",
      "test_data": "${PRIMARY_EMERGENCY_CONTACT}",
      "expected_result": "The primary indicator is accepted and reflected correctly, including on any other contact record it affects.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as toggling the primary flag and confirming any related record is updated where the configuration restricts more than one primary contact."
    },
    {
      "step_number": 7,
      "step_name": "Submit and Verify Contact Saved Correctly",
      "action": "Save the emergency-contact record and reopen the worker's Emergency Contacts page to confirm the change.",
      "test_data": "",
      "expected_result": "The emergency contact is saved with the correct name, relationship, phone, email, address and primary indicator, and the worker record otherwise remains unaffected.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly saved emergency-contact record is the expected pass condition, not merely a successful save action."
    }
  ],
  "expected_results": [
    "The emergency contact is created, updated or removed correctly for the intended worker.",
    "The relationship recorded between worker and contact is correct.",
    "The primary emergency-contact indicator is correct, including where changing it affects another contact record.",
    "Contact name, phone, email and address are correct.",
    "The worker's other person-management records remain unaffected by the emergency-contact change.",
    "A history of prior emergency-contact values is retained where the configuration supports it."
  ],
  "validation_checkpoints": [
    "Contact created correctly.",
    "Relationship correct.",
    "Primary flag correct.",
    "Contact details correct.",
    "Worker record unaffected.",
    "History retained where available."
  ]
}