{
  "test_id": "ORCL.REGRESSION.RECRUIT2PAY",
  "scenario_name": "Recruit-to-Pay Regression Pack",
  "application": "Oracle Fusion Cloud",
  "product": "Regression",
  "module": "Regression Packs",
  "process": "Recruit-to-Pay Regression",
  "business_flow": "Recruit-to-Pay Regression",
  "scenario_type": "Regression Pack / Composition",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Regression Pack",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/regression-packs/recruit-to-pay-regression/",
  "objective": {
    "intro": "The objective of the Recruit-to-Pay Regression Pack is to give release and QA teams a defined, repeatable set of 20 flow-shaped Oracle Fusion Recruit-to-Pay scenarios — spanning Requisition, Candidate Application, Screening, Interview, Offer, Offer Acceptance, Hire, Assignment/Salary, Payroll and Payment — that can be run together ahead of a quarterly update, patch or configuration change, without needing to execute the full 45-scenario Recruit-to-Pay End-to-End journey every cycle.",
    "confirms": [
      "the 20 referenced REG-R2PAY scenario IDs are correctly composed from their underlying Recruiting, Core HR, Compensation and Payroll family pages",
      "requisition, candidate, offer and worker data correctly carry across the flow — from offer into hire, hire into assignment and salary, and hire salary into the first payroll calculation and payment",
      "offer salary correctly carries into hire salary, and hire salary correctly drives the worker's first payroll calculation",
      "negative and security validations are correctly enforced across the composed pack rather than only within a single family page",
      "a batch execution of the pack correctly records pass/fail status per scenario, with failures classified into a likely root-cause category",
      "the pack can be scheduled and re-run on a defined cadence, such as ahead of a quarterly Oracle update",
      "unauthorized users are correctly blocked from accessing recruiting, hire, compensation or payroll data at any stage of the flow"
    ],
    "scope_note": "This pack does not duplicate the individual field-level scenario coverage already tested on the Job Requisition, Candidate Application, Candidate Screening, Interview, Job Offer, Candidate-to-Worker, Payroll Calculation, Prepayments, Payment Processing and Costing family pages. It also does not duplicate the detailed, step-by-step 45-scenario coverage documented on the Recruit-to-Pay End-to-End journey page — this compact 20-scenario pack references those same scenario IDs and family pages, but is scoped for faster, more frequent regression runs. For full step-by-step detail, see the Recruit-to-Pay end-to-end journey."
  },
  "preconditions": [
    "The Job Requisition, Candidate Application, Candidate Screening, Interview, Job Offer, Candidate-to-Worker, Payroll Calculation, Prepayments, Payment Processing and Costing family pages referenced by this pack's 20 scenario IDs are individually functional in the target Oracle Fusion environment.",
    "A valid requisition, legal employer, salary basis and payroll definition are available and enabled across Recruiting, Core HR, Compensation and Payroll.",
    "The test user holds the roles required to execute each referenced scenario, or alternate unauthorized-user personas are available for security testing.",
    "DataVault test data bindings for the referenced scenario IDs are current for the environment under test.",
    "Approval hierarchies, salary basis, payroll cutoff dates and security roles are configured according to the target environment — this pack does not assume a single universal configuration applies to every scenario."
  ],
  "test_data": [
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Candidate",
      "example": "${CANDIDATE}"
    },
    {
      "field": "Offer",
      "example": "${OFFER}"
    },
    {
      "field": "Offer Salary",
      "example": "${OFFER_SALARY}"
    },
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Salary",
      "example": "${SALARY}"
    },
    {
      "field": "Payroll",
      "example": "${PAYROLL}"
    },
    {
      "field": "Hire Date",
      "example": "${HIRE_DATE}"
    },
    {
      "field": "Payment",
      "example": "${PAYMENT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create and Approve the Requisition",
      "action": "Create requisition ${REQUISITION} for ${LEGAL_EMPLOYER} and route it through requisition approval, referencing the standard Job Requisition family page and scenarios REG-R2PAY-001 and REG-R2PAY-002.",
      "test_data": "${REQUISITION} / ${LEGAL_EMPLOYER}",
      "expected_result": "The requisition is correctly created and approved, and is available for candidate application.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Progress the Candidate Through Application, Screening and Interview",
      "action": "Progress candidate ${CANDIDATE} through application, screening and interview against requisition ${REQUISITION}, referencing the standard Candidate Application, Candidate Screening and Interview family pages and scenarios REG-R2PAY-003 through REG-R2PAY-005.",
      "test_data": "${CANDIDATE} / ${REQUISITION}",
      "expected_result": "The candidate is correctly progressed through application, screening and interview stages.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Extend and Approve the Offer",
      "action": "Extend offer ${OFFER} with salary ${OFFER_SALARY} to candidate ${CANDIDATE} and route it through offer approval, referencing the standard Job Offer family page and scenarios REG-R2PAY-006 and REG-R2PAY-007.",
      "test_data": "${OFFER} / ${OFFER_SALARY}",
      "expected_result": "The offer is correctly created and approved with the intended salary and position detail.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Confirm Offer Acceptance",
      "action": "Confirm candidate ${CANDIDATE} accepts offer ${OFFER}, referencing the standard Job Offer family page and scenario REG-R2PAY-008.",
      "test_data": "${OFFER} / ${CANDIDATE}",
      "expected_result": "Offer acceptance is correctly recorded and the candidate is ready for conversion to worker.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Convert the Candidate to a Worker and Hire",
      "action": "Convert accepted candidate ${CANDIDATE} to worker ${WORKER} and complete the hire for ${LEGAL_EMPLOYER} on ${HIRE_DATE}, referencing the standard Candidate-to-Worker family page and scenarios REG-R2PAY-009 and REG-R2PAY-010.",
      "test_data": "${WORKER} / ${HIRE_DATE}",
      "expected_result": "Worker ${WORKER} is correctly hired, carrying candidate identity and legal employer forward from the offer.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Assignment and Salary Continuity",
      "action": "Compare offer salary ${OFFER_SALARY} against hire salary for worker ${WORKER}, and confirm the worker's assignment values match the offer, referencing scenarios REG-R2PAY-011 and REG-R2PAY-012.",
      "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": "business_assertion",
      "note": "This is a primary business assertion for the pack — correctly enforced offer-to-hire and assignment continuity, not merely a successful hire, is the expected pass condition."
    },
    {
      "step_number": 7,
      "step_name": "Confirm Payroll Assignment",
      "action": "Confirm worker ${WORKER} is correctly assigned to payroll ${PAYROLL} before the first payroll calculation runs, referencing the standard Payroll Calculation family page and scenario REG-R2PAY-013.",
      "test_data": "${PAYROLL}",
      "expected_result": "A valid payroll relationship exists for ${WORKER} on payroll ${PAYROLL}.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "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, referencing the standard Payroll Calculation family page and scenario REG-R2PAY-014.",
      "test_data": "${SALARY} / ${PAYROLL}",
      "expected_result": "The first payroll calculation correctly reflects hire salary ${SALARY}.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Generate Prepayments, Payment and Costing",
      "action": "Generate prepayments, payment ${PAYMENT} and payroll costing for worker ${WORKER}'s first payroll calculation, referencing the standard Prepayments, Payment Processing and Costing family pages and scenarios REG-R2PAY-015 through REG-R2PAY-017.",
      "test_data": "${PAYMENT}",
      "expected_result": "Prepayments and payment amounts correctly equal the calculated net pay, and payroll costing is correctly generated.",
      "validation_type": "action"
    },
    {
      "step_number": 10,
      "step_name": "Verify End-to-End Continuity and Access Control",
      "action": "Trace offer-to-hire salary continuity and hire-to-pay worker continuity, and confirm security restrictions are correctly enforced across the flow, referencing the Recruit-to-Pay End-to-End journey and User Access family page and scenarios REG-R2PAY-018 through REG-R2PAY-020.",
      "test_data": "${WORKER} / ${OFFER_SALARY} / ${SALARY}",
      "expected_result": "Offer salary correctly carries through hire into the first payroll payment, worker identity remains consistent end-to-end, and unauthorized access is correctly blocked at every stage.",
      "validation_type": "business_assertion",
      "note": "This is the final business assertion for the pack — correctly reconciled continuity and correctly enforced access control across all ten flow stages is the expected pass condition."
    }
  ],
  "expected_results": [
    "All 20 referenced REG-R2PAY scenario IDs are correctly included and resolvable against the target environment.",
    "Test data binds correctly to each scenario via DataVault before execution.",
    "Each scenario in the batch run records a pass, fail or exception status.",
    "Offer salary and worker identity continuity remain correctly consistent from requisition through hire, assignment, payroll and payment.",
    "The worker is correctly assigned to the configured payroll relationship before the first payroll calculation runs.",
    "Any failure is correctly classified into a likely root-cause category rather than assumed to be an Oracle defect.",
    "The pack's aggregate result is available as evidence for a release go/no-go decision."
  ],
  "validation_checkpoints": [
    "all 20 scenario IDs correctly resolved from their referenced family pages",
    "DataVault test data correctly bound to each scenario before execution",
    "batch execution correctly records pass/fail/exception per scenario",
    "offer salary correctly carries into hire salary",
    "worker correctly assigned to the configured payroll relationship before calculation",
    "negative and security scenarios correctly enforce the expected restriction",
    "failed scenarios correctly classified using the 8-category taxonomy",
    "aggregate pack result correctly available for release sign-off"
  ]
}