{
  "test_id": "ORCL.HCM.RECRUIT.REQ",
  "scenario_name": "Job Requisition",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Recruiting",
  "process": "Job Requisition",
  "business_flow": "Recruit-to-Hire",
  "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/recruiting/job-requisition/",
  "objective": {
    "intro": "This test validates creation, configuration, approval routing and posting of job requisitions across Oracle Fusion HCM Recruiting, without assuming a universal approval hierarchy or posting channel.",
    "confirms": [
      "each job requisition can be created with a position, job, grade, location and required qualifications configured correctly",
      "requisitions route through the approver or approvers configured for the customer's own approval hierarchy — single-level, multi-level, budget-based or organization-hierarchy-based",
      "approved requisitions can be posted to the internal, external or other channels configured for the customer's own career site setup, on demand or on a scheduled date",
      "requisition lifecycle transitions — hold, reopen, cancel, fill, extend, clone and update — are recorded correctly",
      "hiring team assignment (hiring manager, recruiter and interview team) is recorded and can be updated correctly",
      "deliberately invalid submissions — missing fields, invalid grade, headcount exceeding budget, missing hiring manager, duplicate requisition, unapproved posting, inactive position, unauthorized creation — are correctly rejected or flagged rather than silently accepted"
    ],
    "scope_note": "A negative or boundary Job Requisition scenario passes when Oracle correctly enforces the expected rule; this test does not attempt to certify a specific Oracle application defect, and does not assume a universal approval hierarchy or posting channel — both 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 Job Requisition scenarios — the largest catalog in the Recruiting library — as a single comprehensive reference rather than as separate indexable pages."
  },
  "preconditions": [
    "Oracle Fusion Recruiting access is available to the test user.",
    "A representative ${POSITION} and ${JOB}, including both new and existing positions, are available or can be constructed.",
    "Valid and invalid ${GRADE} values for the position, plus an associated compensation range, are available.",
    "${HIRING_MANAGER} and ${RECRUITER} test users with the appropriate Recruiting security access are available.",
    "A configured approval hierarchy for ${ORGANIZATION}, including single-level, multi-level and budget-based approval where applicable, is in place.",
    "At least one internal and one external ${POSTING_CHANNEL} is configured for testing posting scenarios.",
    "A user without the required Recruiting security access is available for security testing, and an inactive ${POSITION} is available for negative testing."
  ],
  "test_data": [
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Position",
      "example": "${POSITION}"
    },
    {
      "field": "Job",
      "example": "${JOB}"
    },
    {
      "field": "Grade",
      "example": "${GRADE}"
    },
    {
      "field": "Hiring Manager",
      "example": "${HIRING_MANAGER}"
    },
    {
      "field": "Recruiter",
      "example": "${RECRUITER}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Location",
      "example": "${LOCATION}"
    },
    {
      "field": "Headcount Budget",
      "example": "${HEADCOUNT_BUDGET}"
    },
    {
      "field": "Posting Channel",
      "example": "${POSTING_CHANNEL}"
    }
  ],
  "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 Recruiting 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 Recruiting",
      "action": "Navigate to the Recruiting work area used to create and manage job requisitions.",
      "test_data": "",
      "expected_result": "The Recruiting work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Create Requisition from Job or Template",
      "action": "Create a new requisition either from an existing job template or by entering the position and job details manually.",
      "test_data": "${JOB} / ${POSITION} / ${REQUISITION}",
      "expected_result": "The requisition is created in draft status with the selected job or template details populated.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Configure Grade, Compensation and Location",
      "action": "Configure the requisition's grade, compensation range and work location.",
      "test_data": "${GRADE} / ${LOCATION}",
      "expected_result": "Grade, compensation range and location are recorded correctly on the requisition.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Assign the Hiring Team",
      "action": "Assign the hiring manager, recruiter and, where applicable, the interview team to the requisition.",
      "test_data": "${HIRING_MANAGER} / ${RECRUITER}",
      "expected_result": "The hiring team is recorded correctly on the requisition.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit for Approval",
      "action": "Submit the requisition for approval according to the configured approval hierarchy.",
      "test_data": "",
      "expected_result": "The requisition routes to the correct approver or approvers, or a deliberately invalid submission is rejected with the expected validation.",
      "validation_type": "action",
      "note": "Exact approval routing depends on the customer's own single-level, multi-level, budget-based or organization-hierarchy configuration."
    },
    {
      "step_number": 7,
      "step_name": "Post to Selected Channels Upon Approval",
      "action": "Post the approved requisition to the internal, external or other selected posting channels.",
      "test_data": "${POSTING_CHANNEL}",
      "expected_result": "The approved requisition is correctly posted to each selected channel, and posting of an unapproved requisition is correctly prevented.",
      "validation_type": "business_assertion",
      "note": "Correctly preventing posting for an unapproved requisition is a passing outcome for negative scenarios, not a failure."
    },
    {
      "step_number": 8,
      "step_name": "Verify Requisition Status and Headcount Tracking",
      "action": "Confirm that the requisition status and tracked headcount against the approved budget are correct after creation, approval and posting.",
      "test_data": "${HEADCOUNT_BUDGET}",
      "expected_result": "Requisition status and headcount tracking accurately reflect a valid submission, or an expected validation for an invalid one.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario across the full catalog of 40 Job Requisition variations."
    }
  ],
  "expected_results": [
    "Each job requisition recorded correctly with the intended position, job, grade, location and required qualifications.",
    "Approval routing correctly followed the configured single-level, multi-level, budget-based or organization-hierarchy approval rule.",
    "Approved requisitions correctly reached the selected internal, external or other configured posting channels.",
    "Requisition lifecycle transitions — hold, reopen, cancel, fill, extend, clone and update — recorded correctly.",
    "Hiring team assignment recorded and updated correctly across hiring manager, recruiter and interview team.",
    "Deliberately invalid submissions raised the expected data, budget or security validation rather than being silently accepted."
  ],
  "validation_checkpoints": [
    "Requisition correctly reflects position/grade/compensation configuration.",
    "Approval routes to the correct approver per configured hierarchy.",
    "Posting correctly reaches selected channels.",
    "Headcount correctly tracked against budget.",
    "Lifecycle state transitions correctly (draft/approved/posted/on hold/filled/cancelled).",
    "Unauthorized creation correctly blocked."
  ]
}