{
  "test_id": "ORCL.HCM.DATA.HDL",
  "scenario_name": "HCM Data Loader",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "HCM Data & Security",
  "process": "HCM Data Loader",
  "business_flow": "HDL-to-Payroll",
  "scenario_type": "Positive / Negative / Boundary / Security / Integration",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/hcm-data-and-security/hcm-data-loader/",
  "objective": {
    "intro": "This test validates bulk load of workers, assignments, workforce structures and related data via Oracle HCM Data Loader (HDL), including file-level validation, dependency ordering, referential integrity and reprocessing, using masked/synthetic test data with protected national-identifier handling.",
    "confirms": [
      "new and existing ${WORKER} records, ${ASSIGNMENT}s and workforce structures (${JOB}, ${POSITION}, ${DEPARTMENT}, ${LOCATION}, ${GRADE}) load correctly from a valid ${HDL_FILE}",
      "dependency order is correctly enforced so parent ${OBJECT_TYPE} records are loaded before dependent child records",
      "deliberately invalid submissions — missing mandatory attributes, invalid references, broken referential integrity, malformed or empty files — are correctly rejected with a clear validation error rather than silently accepted",
      "protected fields such as ${NATIONAL_IDENTIFIER} and ${SALARY} are loaded and validated using masked, synthetic DataVault test data only, never real workforce PII",
      "failed records are correctly identified, correctable and reprocessable, and successfully reprocessed records do not create duplicates",
      "unauthorized load attempts by a user without HCM Data Loader privileges are correctly blocked"
    ],
    "scope_note": "A negative or boundary HCM Data Loader scenario passes when Oracle correctly enforces the expected data, referential-integrity or access-control rule; this test does not attempt to certify a specific Oracle application defect. This page catalogs 54 individual HCM Data Loader scenarios — the largest catalog in the HCM Data & Security library — as a single comprehensive reference rather than as separate indexable pages. All worker, assignment and identifier values referenced throughout are ${PLACEHOLDER} tokens or explicitly masked test data, never real workforce PII."
  },
  "preconditions": [
    "Oracle Fusion HCM Data Loader access is available to the test user with the required load privileges.",
    "Valid and invalid ${HDL_FILE} test files are available, including files with missing, malformed or invalid data.",
    "Representative ${WORKER}, ${ASSIGNMENT} and workforce structure test data (${JOB}, ${POSITION}, ${DEPARTMENT}, ${LOCATION}, ${GRADE}) is available or can be constructed.",
    "Masked, synthetic ${NATIONAL_IDENTIFIER} values are available for protected-identifier testing — never real national identifiers.",
    "A valid ${LEGAL_EMPLOYER} is configured in the target Oracle Fusion environment.",
    "Object dependency order (parent/child) is documented for the object types under test.",
    "A user without HCM Data Loader load privileges is available for unauthorized-load security testing."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Assignment",
      "example": "${ASSIGNMENT}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Job",
      "example": "${JOB}"
    },
    {
      "field": "Position",
      "example": "${POSITION}"
    },
    {
      "field": "Department",
      "example": "${DEPARTMENT}"
    },
    {
      "field": "National Identifier",
      "example": "${NATIONAL_IDENTIFIER} (masked)"
    },
    {
      "field": "HDL File",
      "example": "${HDL_FILE}"
    },
    {
      "field": "Object Type",
      "example": "${OBJECT_TYPE}"
    },
    {
      "field": "Load Status",
      "example": "${LOAD_STATUS}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion HCM",
      "action": "Sign in to Oracle Fusion Cloud with a user account that has HCM Data Loader access.",
      "test_data": "",
      "expected_result": "The Oracle Fusion Cloud home page loads successfully for the authenticated user.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Prepare and Validate the HDL Source File",
      "action": "Prepare or select the ${HDL_FILE} containing ${OBJECT_TYPE} records to be loaded, and validate its structure before submission.",
      "test_data": "${HDL_FILE} / ${OBJECT_TYPE}",
      "expected_result": "The source file is structurally valid and ready for submission, or a deliberately invalid file is correctly identified as malformed.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Submit HDL File for Load",
      "action": "Submit the ${HDL_FILE} to Oracle HCM Data Loader for processing.",
      "test_data": "${HDL_FILE}",
      "expected_result": "The file is accepted for processing and a load process is initiated successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Verify Load Processed in Correct Dependency Order",
      "action": "Confirm that parent ${OBJECT_TYPE} records are processed before dependent child records within the submitted file.",
      "test_data": "${OBJECT_TYPE}",
      "expected_result": "Objects are processed in the correct dependency order, or a deliberate child-before-parent condition is correctly deferred or flagged.",
      "validation_type": "business_assertion",
      "note": "Dependency-order enforcement is a core business assertion across the file/batch and integration scenarios in this catalog."
    },
    {
      "step_number": 5,
      "step_name": "Review Load Status and Error Messages",
      "action": "Review the resulting ${LOAD_STATUS} and any error messages generated for the submission.",
      "test_data": "${LOAD_STATUS}",
      "expected_result": "The load status and any error messages accurately reflect the outcome of each record in the file.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Correct Failed Records Where Applicable",
      "action": "Correct any records that failed validation, using the reported error detail to identify the required fix.",
      "test_data": "${OBJECT_TYPE}",
      "expected_result": "Failed records are corrected successfully and prepared for reprocessing.",
      "validation_type": "action",
      "note": "Not applicable to scenarios where no records failed."
    },
    {
      "step_number": 7,
      "step_name": "Reprocess Corrected Records",
      "action": "Resubmit the corrected records for reprocessing via HDL.",
      "test_data": "${HDL_FILE}",
      "expected_result": "Corrected records load successfully on reprocessing without creating duplicate entries.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Worker/Structure Data Matches Source File",
      "action": "Verify that the loaded ${WORKER}, ${ASSIGNMENT} or workforce structure data matches the values submitted in the source ${HDL_FILE}.",
      "test_data": "${WORKER} / ${HDL_FILE}",
      "expected_result": "Loaded data matches the source file exactly across all mandatory attributes, or a deliberately invalid submission was correctly rejected rather than partially loaded.",
      "validation_type": "business_assertion",
      "note": "Correctly rejecting an invalid or incomplete submission is a passing outcome for negative scenarios, not a failure."
    },
    {
      "step_number": 9,
      "step_name": "Verify Downstream Data Integrity",
      "action": "Confirm that loaded worker, assignment and structure data is available and consistent for downstream processes such as payroll.",
      "test_data": "${OBJECT_TYPE}",
      "expected_result": "Downstream data integrity is correctly maintained for a successful load, with no orphaned or inconsistent records introduced.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario across the full catalog of 54 HCM Data Loader variations."
    }
  ],
  "expected_results": [
    "Loaded ${WORKER}, ${ASSIGNMENT} and structure data matches the source ${HDL_FILE} exactly.",
    "Dependency order (parent before child) correctly enforced across dependent ${OBJECT_TYPE} objects.",
    "Invalid or missing mandatory data correctly rejected with a clear validation error.",
    "Referential integrity violations correctly blocked rather than partially committed.",
    "Failed records correctly identified, corrected and reprocessed without creating duplicates.",
    "Unauthorized load attempts correctly blocked."
  ],
  "validation_checkpoints": [
    "Loaded worker/assignment/structure data matches the source file exactly.",
    "Dependency order (parent-before-child) correctly enforced.",
    "Invalid or missing mandatory data correctly rejected with a clear error.",
    "Referential integrity violations correctly blocked.",
    "Failed records correctly identified, correctable and reprocessable.",
    "Unauthorized load attempts correctly blocked."
  ]
}