{
  "test_id": "ORCL.HCM.DATA.EXTRACT",
  "scenario_name": "HCM Extracts",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "HCM Data & Security",
  "process": "HCM Extracts",
  "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-extracts/",
  "objective": {
    "intro": "This test validates HCM Extract execution, parameters, output format/content, scheduling/delivery and downstream data-quality checks, using masked/synthetic extracted data.",
    "confirms": [
      "each configured HCM Extract can be executed on demand or per schedule with the correct extract definition and parameter values applied",
      "extract output correctly reflects the configured worker, assignment, payroll, benefits and absence population and effective-date parameters",
      "generated output files are structurally correct — header, trailer, delimiter/format and, where configured, XML or CSV/text output",
      "sensitive fields are correctly masked in extract output where applicable, and record counts match the source population",
      "scheduled, recurring and manually triggered extracts correctly execute and deliver to the configured destination",
      "deliberately invalid conditions — invalid or missing parameters, empty result sets, delivery failures, process failures and duplicate records — are correctly rejected, flagged or handled rather than silently producing incorrect output"
    ],
    "scope_note": "A negative or boundary HCM Extracts scenario passes when Oracle correctly enforces the expected data, format or delivery rule; this test does not attempt to certify a specific Oracle application defect, and does not assume a universal extract configuration, output format or delivery destination — all depend entirely on customer-specific Oracle Fusion configuration. Where an entry or validation appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion. This page catalogs 40 individual HCM Extracts scenarios as a single comprehensive reference rather than as separate indexable pages."
  },
  "preconditions": [
    "Oracle Fusion HCM Extracts access is available to the test user.",
    "A representative ${EXTRACT_DEFINITION} covering worker, assignment, payroll, benefits and absence data is configured and available.",
    "Valid and invalid ${EXTRACT_PARAMETER} values, including ${DATE_RANGE} and ${LEGAL_EMPLOYER}, are available for parameter-driven testing.",
    "At least one ${WORKER} population, including single-worker and multi-worker sets, is available for extraction.",
    "A configured ${DELIVERY_DESTINATION} (for example an SFTP location, UCM or web service endpoint) is available for delivery testing.",
    "Masked/synthetic worker, payroll and benefits data is available through DataVault so no real workforce PII is used in extract output.",
    "A user without the required Extracts security access is available for security testing, and parameters capable of producing an empty ${RECORD_COUNT} result set are available for boundary testing."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Extract Definition",
      "example": "${EXTRACT_DEFINITION}"
    },
    {
      "field": "Extract Parameter",
      "example": "${EXTRACT_PARAMETER}"
    },
    {
      "field": "Date Range",
      "example": "${DATE_RANGE}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Output Format",
      "example": "${OUTPUT_FORMAT}"
    },
    {
      "field": "Delivery Destination",
      "example": "${DELIVERY_DESTINATION}"
    },
    {
      "field": "Record Count",
      "example": "${RECORD_COUNT}"
    },
    {
      "field": "File Name",
      "example": "${FILE_NAME}"
    },
    {
      "field": "Extract Status",
      "example": "${EXTRACT_STATUS}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to HCM Extracts",
      "action": "Sign in to Oracle Fusion Cloud with a user account that has HCM Extracts access and navigate to the Extracts work area.",
      "test_data": "",
      "expected_result": "The Oracle Fusion Cloud HCM Extracts work area loads successfully for the authenticated user.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Configure or Select Extract Definition and Parameters",
      "action": "Select an existing extract definition or configure the extract parameters, including date range and legal employer.",
      "test_data": "${EXTRACT_DEFINITION} / ${EXTRACT_PARAMETER}",
      "expected_result": "The extract definition and parameters are recorded correctly before execution.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Run the Extract Manually or via Schedule",
      "action": "Trigger the extract manually on demand, or allow it to run according to its configured schedule.",
      "test_data": "${EXTRACT_STATUS}",
      "expected_result": "The extract process starts and reaches the expected status for the configured trigger method.",
      "validation_type": "action",
      "note": "Exact scheduling options depend on the customer's own Oracle Fusion Extracts configuration."
    },
    {
      "step_number": 4,
      "step_name": "Verify Output File Generated with Correct Structure",
      "action": "Confirm the output file is generated with the correct file name, output format, header, trailer and delimiter/format.",
      "test_data": "${FILE_NAME} / ${OUTPUT_FORMAT}",
      "expected_result": "The output file is generated with the correct name, format and structure, or a deliberately invalid run is correctly rejected.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Validate Record Count Against Source Population",
      "action": "Compare the record count in the extract output against the source worker population defined by the extract parameters.",
      "test_data": "${RECORD_COUNT}",
      "expected_result": "The extract record count matches the expected source population, or a deliberately empty or large result set is handled as expected.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 6,
      "step_name": "Verify Sensitive Field Masking Where Applicable",
      "action": "Confirm that sensitive worker fields in the output are masked or excluded where masking is configured.",
      "test_data": "",
      "expected_result": "Sensitive fields are correctly masked in the output where applicable.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 7,
      "step_name": "Verify Delivery to Configured Destination",
      "action": "Confirm the output file is delivered to the configured delivery destination, or that a deliberate delivery failure is correctly flagged and retried.",
      "test_data": "${DELIVERY_DESTINATION}",
      "expected_result": "The file is correctly delivered to the configured destination, or the expected delivery failure and retry behavior occurs.",
      "validation_type": "business_assertion",
      "note": "Correctly flagging a delivery or process failure is a passing outcome for negative scenarios, not a failure."
    },
    {
      "step_number": 8,
      "step_name": "Verify Downstream Data Accuracy",
      "action": "Confirm that worker attribute and effective-date values in the extract output accurately reflect the source Oracle Fusion HCM data used downstream.",
      "test_data": "",
      "expected_result": "Downstream data accuracy is confirmed, or a deliberate discrepancy such as a duplicate record is correctly detected.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario across the full catalog of 40 HCM Extracts variations."
    }
  ],
  "expected_results": [
    "Each configured HCM Extract executed correctly with the intended definition, parameters and worker/assignment/payroll/benefits/absence population.",
    "Output files structurally correct — file name, header, trailer, delimiter/format and, where configured, XML or CSV/text output.",
    "Extract record counts correctly matched the source population, including deliberately empty and large result sets.",
    "Sensitive fields correctly masked in output where applicable.",
    "Scheduled, recurring and manually triggered extracts correctly executed and delivered to the configured destination.",
    "Deliberately invalid parameters, delivery failures, process failures and duplicate records correctly rejected, flagged or handled rather than silently producing incorrect output."
  ],
  "validation_checkpoints": [
    "Extract output correctly reflects the configured parameters and population.",
    "File structure — header, trailer, delimiter and format — correctly validated.",
    "Record count in the extract matches the source population.",
    "Sensitive fields correctly masked in output where applicable.",
    "Scheduled and recurring extracts correctly execute and deliver.",
    "Delivery and process failures correctly trigger retry/error handling."
  ]
}