{
  "test_id": "ORCL.HCM.E2E.RECRUIT2PAY",
  "scenario_name": "Recruit-to-Pay",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "End-to-End HCM",
  "process": "Recruit-to-Pay",
  "business_flow": "Hire-to-Retire",
  "scenario_type": "End-to-End / Cross-Module",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard Journey",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/end-to-end/recruit-to-pay/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Oracle Fusion Recruit-to-Pay journey — job requisition, candidate, offer, offer acceptance, worker, assignment, compensation, payroll enrollment, payroll calculation, prepayments and payment — with emphasis on offer salary correctly carrying into hire salary and hire salary correctly carrying into the worker's first payroll calculation, not on re-testing each stage's own atomic, field-level validation. This page is an orchestration and journey test: it does not duplicate the scenario coverage already tested individually on the linked Job Requisition, Candidate Application, Candidate Screening, Interview, Job Offer, Candidate-to-Worker, Convert Pending Worker, Hire Employee, Salary Change, Payroll Processing, Payroll Calculation, QuickPay, Retro Pay, Prepayments, Payment Processing, Costing and Payroll Validation pages. Instead, it links to those live pages and adds scenarios that specifically test the hand-offs and value continuity between them.",
    "confirms": [
      "job requisition, candidate, offer, worker, assignment, compensation and payroll data correctly carry forward from one stage to the next",
      "offer salary correctly carries into hire salary at the point of hire",
      "hire salary correctly drives the worker's first payroll calculation and payment",
      "job, position and legal employer correctly carry from offer to worker assignment",
      "the worker is correctly assigned to the configured payroll relationship before the first payroll calculation runs",
      "prepayments and payment amounts correctly equal the calculated net pay for the worker's first payroll period",
      "Oracle correctly enforces validation when data errors, configuration errors, security restrictions or missing payroll setup are introduced at any stage of the journey (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario orchestrates and links to the individually tested Recruiting, Core HR, Compensation and Payroll family pages listed on this page; it does not re-test each stage's own field-level validation, which remains covered on those pages. It covers the standard Recruit-to-Pay journey in Oracle Fusion Cloud HCM TEST/UAT environments and does not cover internal transfers or promotions without a preceding recruiting event, which are covered by separate Core HR scenarios outside this journey."
  },
  "preconditions": [
    "A job requisition ${REQUISITION} is approved and open for ${LEGAL_EMPLOYER} in the target Oracle Fusion environment.",
    "Recruiting, Core HR, Compensation and Payroll are configured for the legal employer, including salary basis, payroll definitions and payment methods.",
    "The test user or users hold appropriate access to progress a transaction through recruiting, hire, assignment, compensation and payroll stages.",
    "A valid payroll relationship, payroll calendar and an open ${HIRE_DATE}-relevant payroll period are configured in the target environment.",
    "This scenario assumes each linked family page's own preconditions are separately satisfied — it does not re-verify field-level setup already covered on those pages."
  ],
  "test_data": [
    {
      "field": "Candidate",
      "example": "${CANDIDATE}"
    },
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Offer",
      "example": "${OFFER}"
    },
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Salary",
      "example": "${SALARY}"
    },
    {
      "field": "Payroll",
      "example": "${PAYROLL}"
    },
    {
      "field": "Hire Date",
      "example": "${HIRE_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create and Approve the Job Requisition Through Offer Acceptance",
      "action": "Create job requisition ${REQUISITION} for ${LEGAL_EMPLOYER}, progress candidate ${CANDIDATE} through application, screening and interview, extend offer ${OFFER}, and confirm offer acceptance, using the linked Job Requisition, Candidate Application, Candidate Screening, Interview and Job Offer scenarios.",
      "test_data": "${REQUISITION} / ${CANDIDATE} / ${OFFER}",
      "expected_result": "The requisition, candidate and offer are correctly created and progressed, with offer salary ${SALARY} carried forward for hire.",
      "validation_type": "action",
      "note": "This step orchestrates the Job Requisition, Candidate Application, Candidate Screening, Interview and Job Offer family pages rather than repeating their individual field-level test coverage."
    },
    {
      "step_number": 2,
      "step_name": "Convert the Candidate to a Worker and Hire",
      "action": "Convert accepted candidate ${CANDIDATE} to pending worker ${WORKER} and complete the hire for ${LEGAL_EMPLOYER} on ${HIRE_DATE}, using the linked Candidate-to-Worker, Convert Pending Worker and Hire Employee scenarios.",
      "test_data": "${WORKER} / ${HIRE_DATE}",
      "expected_result": "Worker ${WORKER} is correctly hired, carrying candidate identity, job, position and legal employer forward from the offer.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Verify Salary and Assignment Continuity",
      "action": "Compare offer salary ${OFFER_SALARY} against hire salary for worker ${WORKER}, and confirm job, position and legal employer on the worker's assignment match the offer, using the linked Salary Change scenario where a correction is required.",
      "test_data": "${SALARY}",
      "expected_result": "Offer salary correctly carries into hire salary, and job, position and legal employer correctly carry into the worker's assignment.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Verify Payroll Relationship and Payment Method Setup",
      "action": "Confirm worker ${WORKER} is assigned to payroll ${PAYROLL} with a valid personal payment method and bank details, using the linked Payroll Processing scenario.",
      "test_data": "${PAYROLL}",
      "expected_result": "A valid payroll relationship and payment method exist for ${WORKER} before the first payroll calculation runs.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Run the First Payroll Calculation",
      "action": "Execute the first payroll calculation for worker ${WORKER} on payroll ${PAYROLL}, confirming hire salary correctly drives the calculated pay, using the linked Payroll Calculation scenario.",
      "test_data": "",
      "expected_result": "The first payroll calculation correctly reflects hire salary ${SALARY} and any applicable bonus, allowance, benefit deduction, time or absence input.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Resolve Any Payroll Validation Exceptions",
      "action": "Review and resolve any payroll validation exceptions raised during the first payroll calculation for ${WORKER}, using the linked Payroll Validation scenario, before resubmitting for prepayments.",
      "test_data": "",
      "expected_result": "Validation exceptions are correctly identified and resolved, or the calculation correctly proceeds where no exception applies.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Generate Prepayments and Payment",
      "action": "Generate prepayments and payment for worker ${WORKER}'s first payroll calculation, using the linked Prepayments, Payment Processing and Costing scenarios.",
      "test_data": "",
      "expected_result": "Prepayments and payment amounts correctly equal the calculated net pay, and payroll costing is correctly generated.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify the Full Audit Trail Links Recruiting Through Payment Together",
      "action": "Trace the completed transaction from job requisition through candidate, offer, hire, assignment, compensation, payroll calculation, prepayments and payment to confirm the audit trail links every stage together.",
      "test_data": "",
      "expected_result": "The audit trail correctly links requisition ${REQUISITION}, candidate ${CANDIDATE}, offer ${OFFER}, worker ${WORKER} and payroll ${PAYROLL} end-to-end, with payment correctly reflecting hire salary.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a fully linked, correctly continuous and correctly paid worker across every stage is the expected pass condition, not merely a successful hire."
    }
  ],
  "expected_results": [
    "The job requisition, candidate, offer, worker, assignment, compensation and payroll are correctly linked end-to-end.",
    "Offer salary correctly carries into hire salary at the point of hire.",
    "Hire salary correctly drives the worker's first payroll calculation and payment.",
    "The worker is correctly assigned to the configured payroll relationship before the first payroll calculation runs.",
    "Prepayments and payment amounts correctly equal the calculated net pay for the first payroll period.",
    "Payroll validation exceptions and unauthorized actions at any stage of the journey are correctly enforced."
  ],
  "validation_checkpoints": [
    "Offer salary correctly carries into hire salary.",
    "Worker correctly assigned to the configured payroll relationship.",
    "Missing payroll relationship correctly blocks calculation.",
    "Payment method and bank details correctly validated before payment.",
    "First payroll calculation correctly reflects bonus, allowance, benefit and time inputs.",
    "Salary correction correctly triggers retro calculation.",
    "Payroll costing correctly generated.",
    "Unauthorized payroll or payment access correctly blocked."
  ]
}