{
  "test_id": "ORCL.HCM.OTL.TIMECARD.APPROVAL",
  "scenario_name": "Timecard Approval",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Time and Labor",
  "process": "Timecard Approval",
  "business_flow": "Time-to-Pay",
  "scenario_type": "Functional / Workflow / Security Testing",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/time-and-labor/timecard-approval/",
  "objective": {
    "intro": "This test validates submission, approval and rejection of worker timecards according to configured Oracle Fusion Time and Labor approval rules, without assuming a single universal routing structure.",
    "confirms": [
      "the correct approver is identified for each timecard according to configured routing — never assumed universal",
      "approval and rejection decisions are correctly recorded on the timecard status",
      "rejection reasons are captured and retained through correction and resubmission",
      "a resubmitted timecard routes correctly back to the appropriate approver",
      "delegation is correctly honored when a configured approver is unavailable",
      "unauthorized approval attempts are correctly blocked by Oracle Fusion security"
    ],
    "scope_note": "A Timecard Approval negative scenario passes when Oracle correctly enforces the expected approval, routing or security rule. This scenario does not attempt to certify a specific Oracle application defect. Where an approval outcome appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion."
  },
  "preconditions": [
    "Oracle Fusion Time and Labor access is available to the test user, approver and, where applicable, a delegate.",
    "${WORKER} exists with a timecard for ${TIME_PERIOD} that can be submitted for approval.",
    "Approval rules are configured for the relevant ${ORGANIZATION} or ${PROJECT}, defining ${APPROVER} and any required ${APPROVAL_LEVEL} sequence.",
    "Where delegation is in scope, ${DELEGATE} is configured as an authorized delegate for ${APPROVER}.",
    "A representative ${TIMECARD} exists, or can be constructed, in each relevant state — Submitted, Approved, Rejected, Withdrawn.",
    "The test user, or Syntra DataVault, can reproduce approval routing, rejection, delegation and unauthorized-approval conditions."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Timecard",
      "example": "${TIMECARD}"
    },
    {
      "field": "Approver",
      "example": "${APPROVER}"
    },
    {
      "field": "Approval Level",
      "example": "${APPROVAL_LEVEL}"
    },
    {
      "field": "Delegate",
      "example": "${DELEGATE}"
    },
    {
      "field": "Rejection Reason",
      "example": "${REJECT_REASON}"
    },
    {
      "field": "Time Period",
      "example": "${TIME_PERIOD}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Project",
      "example": "${PROJECT}"
    }
  ],
  "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 Time and Labor 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": "Navigate to Time and Labor",
      "action": "Navigate to the Time and Labor work area used to review and act on submitted timecards.",
      "test_data": "",
      "expected_result": "The Time and Labor work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Submitted Timecard",
      "action": "Locate ${TIMECARD} for ${WORKER} covering ${TIME_PERIOD} in the approver's worklist or notifications.",
      "test_data": "${WORKER} / ${TIMECARD} / ${TIME_PERIOD}",
      "expected_result": "The submitted timecard is visible and available for review by the configured approver.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Review Hours and Time Types",
      "action": "Review the recorded hours, time types and any overtime entries on the timecard before making an approval decision.",
      "test_data": "",
      "expected_result": "The hours and time types displayed match what was recorded by the worker for the period.",
      "validation_type": "business_assertion",
      "note": "Confirms the approver is reviewing accurate, complete timecard data before a decision is recorded."
    },
    {
      "step_number": 5,
      "step_name": "Approve or Reject with a Reason",
      "action": "Select Approve, or Reject and enter ${REJECT_REASON}, according to the scenario under test.",
      "test_data": "${REJECT_REASON}",
      "expected_result": "The approval or rejection decision, including any reason, is captured for submission.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit the Decision",
      "action": "Submit the approval or rejection decision at the appropriate ${APPROVAL_LEVEL} in the configured routing.",
      "test_data": "${APPROVER} / ${APPROVAL_LEVEL}",
      "expected_result": "The decision is submitted and processed by Oracle Fusion.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Status and Notification",
      "action": "Confirm the timecard status updates correctly and that ${WORKER} and ${APPROVER} receive the expected notification.",
      "test_data": "",
      "expected_result": "The timecard status accurately reflects the decision, and the correct notification is generated for the worker and approver.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — a correct UI action does not by itself confirm the approval routing rule was correctly enforced."
    }
  ],
  "expected_results": [
    "The correct approver is identified for each timecard according to configured routing rules.",
    "Approval and rejection decisions are correctly recorded on the timecard status.",
    "Rejection reasons are retained and visible to the worker.",
    "Resubmitted timecards route correctly to the appropriate approver.",
    "Delegation is correctly honored when an approver is unavailable.",
    "Unauthorized approval attempts are correctly blocked."
  ],
  "validation_checkpoints": [
    "Correct approver identified per configured routing — never assumed universal.",
    "Approval/rejection status correctly recorded.",
    "Rejection reason retained.",
    "Resubmission routes correctly.",
    "Delegation correctly honored.",
    "Unauthorized approval attempts correctly blocked."
  ]
}