{
  "test_id": "ORCL.HCM.COREHR.PERSON.CONTACT",
  "scenario_name": "Manage Contact 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/manage-contact-information/",
  "objective": {
    "intro": "The objective of this test is to validate that a worker's contact methods — including email addresses, phone numbers and other configured contact types — can be created and maintained correctly in Oracle Fusion HCM, with the correct contact type, primary designation and effective date applied.",
    "confirms": [
      "the correct contact method (email, phone or other configured type) is created or updated for the correct worker",
      "the contact type — such as personal, work or mobile — is captured correctly",
      "the primary indicator is set correctly where multiple contact methods of the same type exist",
      "the effective date is applied correctly, including for future-dated contact updates",
      "the previous contact method is retained as history where applicable, rather than being overwritten",
      "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 and maintenance of a worker's email, phone and other configured contact methods in Oracle Fusion HCM Core HR TEST/UAT environments. It does not cover the worker's postal address, national identifiers or emergency contacts, which are covered by the separate Manage Address, Manage National Identifiers and Manage Emergency Contacts scenarios in the same Person Management cluster."
  },
  "preconditions": [
    "The worker record is active in the target Oracle Fusion HCM environment.",
    "Contact method types — such as email and phone — are configured for the worker's legislation and enterprise.",
    "The test user has appropriate access to add or update contact information for the worker.",
    "Any existing contact methods on the worker record are visible on the contact information page.",
    "Where self-service is in scope, the employee self-service contact page is accessible to the test user."
  ],
  "test_data": [
    {
      "field": "Person Number",
      "example": "${PERSON_NUMBER}"
    },
    {
      "field": "Contact Type",
      "example": "${CONTACT_TYPE}"
    },
    {
      "field": "Email Type",
      "example": "${EMAIL_TYPE}"
    },
    {
      "field": "Email Address",
      "example": "${EMAIL_ADDRESS}"
    },
    {
      "field": "Phone Type",
      "example": "${PHONE_TYPE}"
    },
    {
      "field": "Country Code",
      "example": "${COUNTRY_CODE}"
    },
    {
      "field": "Phone Number",
      "example": "${PHONE_NUMBER}"
    },
    {
      "field": "Primary Indicator",
      "example": "${PRIMARY_INDICATOR}"
    },
    {
      "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 whose contact information will be maintained.",
      "test_data": "${PERSON_NUMBER}",
      "expected_result": "The correct worker's contact information page opens.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select Add or Update Contact Method",
      "action": "Choose to add a new contact method or select an existing one to update.",
      "test_data": "${CONTACT_TYPE}",
      "expected_result": "The contact method entry form opens for the selected type.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter Contact Details and Type",
      "action": "Enter the email address or phone number, including email/phone type and country code where applicable.",
      "test_data": "${EMAIL_TYPE} / ${EMAIL_ADDRESS} / ${PHONE_TYPE} / ${COUNTRY_CODE} / ${PHONE_NUMBER}",
      "expected_result": "The contact details are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Set Primary Flag and Effective Date",
      "action": "Designate the contact method as primary where applicable and enter the effective date.",
      "test_data": "${PRIMARY_INDICATOR} / ${EFFECTIVE_DATE}",
      "expected_result": "The primary designation and effective date are accepted and reflected on the record.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as toggling the primary indicator and confirming the effective-date field."
    },
    {
      "step_number": 6,
      "step_name": "Submit the Contact Method",
      "action": "Save the contact information update for the worker record.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the contact method update without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Contact Method Saved Correctly",
      "action": "Reopen or refresh the worker's contact information and confirm the new or updated contact method, primary flag and effective date.",
      "test_data": "",
      "expected_result": "The contact method, type, primary designation and effective date match the entered data, and any previous contact method is retained as history where applicable.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly saved contact method with accurate primary and effective-date data is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The contact method is created or updated for the correct worker.",
    "The contact type (email, phone or other configured type) is correct.",
    "The primary indicator correctly reflects the intended primary contact method.",
    "The effective date is correctly applied, including for future-dated changes.",
    "Any previous contact method is retained as history where applicable.",
    "No unrelated worker data is changed by the update."
  ],
  "validation_checkpoints": [
    "Correct contact method created.",
    "Primary flag correct.",
    "Effective date correct.",
    "Previous contact retained where applicable.",
    "No unrelated person data changed."
  ]
}