{
  "test_id": "ORCL.E2E.SUP2PAY",
  "scenario_name": "Supplier-to-Payment",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Supplier-to-Payment",
  "business_flow": "Procure-to-Pay",
  "scenario_type": "End-to-End / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard Journey",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/scm/end-to-end/supplier-to-payment/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Supplier-to-Payment journey in Oracle Fusion SCM and Financials — new supplier setup, supplier site, banking, qualification, purchase order, receipt, invoice matching and first payment — with emphasis on supplier master data correctly gating downstream procurement and payment activity, such as an inactive supplier or a missing bank account correctly blocking the flow, rather than re-testing each stage's individual field-level validation, which is already covered on the linked Create Supplier, Create Supplier Site, Supplier Bank Account, Supplier Qualification, Update Supplier, Supplier Inactivation, Create Purchase Order, Receive Purchase Order, Create PO-Matched Invoice, Create Payment and Electronic Payment family pages this scenario orchestrates.",
    "confirms": [
      "a newly created supplier and supplier site correctly become available for downstream procurement once active",
      "supplier bank account setup correctly gates the ability to create a payment",
      "supplier qualification status correctly gates procurement where the customer has configured it to do so, rather than assuming a single universal qualification rule",
      "an inactive supplier or supplier site correctly blocks new purchase order creation",
      "purchase order, receipt and invoice data correctly carries forward through to payment",
      "an invalid supplier bank account correctly blocks payment until corrected",
      "unauthorized users are correctly blocked from creating or updating supplier banking data at any stage of the journey"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-stage data integrity of the Supplier-to-Payment journey in Oracle Fusion SCM and Financials TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Create Supplier, Create Supplier Site, Supplier Bank Account, Supplier Qualification, Update Supplier, Supplier Inactivation, Create Purchase Order, Receive Purchase Order, Create PO-Matched Invoice, Create Payment and Electronic Payment family pages — this page links to and orchestrates those live pages into an end-to-end journey."
  },
  "preconditions": [
    "The Suppliers, Purchase Orders, Receiving and Accounts Payable family pages referenced by this journey — Create Supplier, Create Supplier Site, Supplier Bank Account, Supplier Qualification, Update Supplier, Supplier Inactivation, Create Purchase Order, Receive Purchase Order, Create PO-Matched Invoice, Create Payment and Electronic Payment — are individually functional in the target Oracle Fusion SCM and Financials environment.",
    "A valid business unit, procurement business unit, supplier type and payment terms are available and enabled for supplier onboarding.",
    "Supplier qualification, if configured, has a defined questionnaire or criteria available for the test supplier.",
    "The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.",
    "Supplier qualification requirements and bank-account validation rules are configured according to the target environment — this scenario does not assume a single universal qualification or banking rule applies to every supplier."
  ],
  "test_data": [
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Supplier Site",
      "example": "${SUPPLIER_SITE}"
    },
    {
      "field": "Disbursement Bank Account",
      "example": "${DISBURSEMENT_BANK_ACCOUNT}"
    },
    {
      "field": "Purchase Order",
      "example": "${PURCHASE_ORDER}"
    },
    {
      "field": "Receipt",
      "example": "${RECEIPT}"
    },
    {
      "field": "Invoice",
      "example": "${INVOICE}"
    },
    {
      "field": "Payment",
      "example": "${PAYMENT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create the Supplier and Supplier Site",
      "action": "Create the supplier and supplier site, referencing the standard Create Supplier and Create Supplier Site test scenarios.",
      "test_data": "${SUPPLIER} / ${SUPPLIER_SITE}",
      "expected_result": "The supplier and supplier site are created and become available for downstream procurement once active.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Set Up Supplier Banking and Qualification",
      "action": "Set up supplier banking and qualification, referencing the standard Supplier Bank Account and Supplier Qualification test scenarios.",
      "test_data": "${DISBURSEMENT_BANK_ACCOUNT} / ${QUALIFICATION_STATUS}",
      "expected_result": "The disbursement bank account is correctly added and qualification status is correctly recorded, where configured.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Create and Receive a Purchase Order Against the Supplier",
      "action": "Create and receive a purchase order against the supplier, referencing the standard Create Purchase Order and Receive Purchase Order test scenarios.",
      "test_data": "${PURCHASE_ORDER} / ${SUPPLIER} / ${RECEIPT}",
      "expected_result": "The purchase order is created against the active supplier and site and correctly received.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Create and Match the AP Invoice",
      "action": "Create and match the AP invoice against the purchase order and receipt, referencing the standard Create PO-Matched Invoice test scenario.",
      "test_data": "${INVOICE} / ${PURCHASE_ORDER} / ${RECEIPT}",
      "expected_result": "The invoice is correctly matched to the purchase order and receipt within configured tolerance.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Submit Payment",
      "action": "Submit payment for the matched invoice, referencing the standard Create Payment test scenario.",
      "test_data": "${PAYMENT} / ${INVOICE}",
      "expected_result": "Payment is created for the matched invoice using a valid supplier bank account.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Payment Method and Bank Account Correctness",
      "action": "Verify payment method and disbursement bank account correctness, referencing the standard Electronic Payment test scenario.",
      "test_data": "${PAYMENT_METHOD} / ${DISBURSEMENT_BANK_ACCOUNT}",
      "expected_result": "Payment correctly reflects the configured payment method and a valid disbursement bank account.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — a valid bank account and payment method on the completed payment is the expected pass condition, not merely a successful transaction."
    },
    {
      "step_number": 7,
      "step_name": "Verify the Supplier-to-Payment Audit Trail",
      "action": "Verify the audit trail links supplier through payment together — supplier, purchase order, receipt, invoice and payment.",
      "test_data": "${SUPPLIER} / ${PURCHASE_ORDER} / ${INVOICE} / ${PAYMENT}",
      "expected_result": "Supplier, purchase order, receipt, invoice and payment correctly cross-reference each other end to end.",
      "validation_type": "business_assertion",
      "note": "This is the final business assertion for the scenario — a fully cross-referenced audit trail from supplier through payment is the expected pass condition for the full journey."
    }
  ],
  "expected_results": [
    "The supplier and supplier site are correctly created and become available for downstream procurement once active.",
    "Supplier banking and qualification are correctly set up and required before payment and, where configured, before procurement.",
    "The purchase order and receipt correctly reference the supplier and site, with quantity and pricing carried forward.",
    "The AP invoice correctly matches to the purchase order and receipt within configured tolerance.",
    "Payment is correctly created for the matched invoice using a valid supplier bank account and payment method.",
    "Unauthorized supplier, banking or payment actions are correctly blocked at any stage of the journey."
  ],
  "validation_checkpoints": [
    "supplier and site correctly must be active to create a new PO",
    "supplier qualification status correctly gates procurement where configured",
    "supplier bank account correctly required before payment creation",
    "PO/receipt/invoice data correctly carries forward to payment",
    "invalid bank details correctly block payment until corrected",
    "document linkage preserved end to end"
  ]
}