{
  "test_id": "ORCL.P2P.AP.PAY.PPR",
  "scenario_name": "Payment Process Request",
  "application": "Oracle Fusion Cloud",
  "product": "Financials",
  "module": "Accounts Payable",
  "process": "Payments",
  "business_flow": "Procure-to-Pay",
  "scenario_type": "Positive / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/financials/accounts-payable/payments/payment-process-request/",
  "objective": {
    "intro": "The objective of this test is to verify that an authorised Accounts Payable user can create and submit a Payment Process Request that correctly selects eligible invoice installments and processes them into payments according to the configured selection criteria and payment processing rules.",
    "confirms": [
      "invoices matching the configured selection criteria are correctly identified as eligible",
      "invoices and suppliers that should be excluded are correctly excluded from selection",
      "proposed payments are grouped and calculated correctly by supplier, currency and payment method",
      "exceptions raised during selection or build are surfaced clearly rather than silently dropped",
      "the request progresses through its expected lifecycle to a completed status",
      "created payments are consistent with the invoices selected and the configured payment process profile"
    ],
    "scope_note": "This scenario validates selection, exception handling and payment build within Oracle Fusion. It does not claim that SyntraFlow transmits real funds or performs an actual bank transaction — testing is performed against Oracle Fusion TEST/UAT environments."
  },
  "preconditions": [
    "Oracle Fusion Accounts Payable and Payments access is available to the test user.",
    "Eligible, validated and approved invoices exist for the test payment business unit and supplier.",
    "A payment process profile is configured and available for selection.",
    "A disbursement bank account and payment method are configured and available.",
    "Supplier banking information required for the selected payment method is valid and complete.",
    "The relevant accounting period is open for payment processing."
  ],
  "test_data": [
    {
      "field": "Payment Business Unit",
      "example": "${PAYMENT_BUSINESS_UNIT}"
    },
    {
      "field": "Payment Process Profile",
      "example": "${PAYMENT_PROCESS_PROFILE}"
    },
    {
      "field": "Disbursement Bank Account",
      "example": "${DISBURSEMENT_BANK_ACCOUNT}"
    },
    {
      "field": "Payment Method",
      "example": "${PAYMENT_METHOD}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Supplier Site",
      "example": "${SUPPLIER_SITE}"
    },
    {
      "field": "Invoice Number",
      "example": "${INVOICE_NUMBER}"
    },
    {
      "field": "Due Date",
      "example": "${DUE_DATE}"
    },
    {
      "field": "Pay Through Date",
      "example": "${PAY_THROUGH_DATE}"
    },
    {
      "field": "Payment Currency",
      "example": "${PAYMENT_CURRENCY}"
    },
    {
      "field": "Payment Priority",
      "example": "${PAYMENT_PRIORITY}"
    },
    {
      "field": "Payment Group",
      "example": "${PAYMENT_GROUP}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Navigate to Payment Process Requests",
      "action": "Navigate to the Payment Process Requests work area within Oracle Fusion Payables.",
      "test_data": "",
      "expected_result": "The Payment Process Requests work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Create a New Request",
      "action": "Create a new Payment Process Request.",
      "test_data": "",
      "expected_result": "A new Payment Process Request is opened and ready for selection criteria entry.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select Payment Business Unit",
      "action": "Select the payment business unit for the request.",
      "test_data": "${PAYMENT_BUSINESS_UNIT}",
      "expected_result": "The selected payment business unit is applied to the request.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select Payment Process Profile",
      "action": "Select the payment process profile that determines how selected invoices will be processed into payments.",
      "test_data": "${PAYMENT_PROCESS_PROFILE} / ${DISBURSEMENT_BANK_ACCOUNT} / ${PAYMENT_METHOD}",
      "expected_result": "The selected payment process profile, bank account and payment method are applied to the request.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Selection Criteria",
      "action": "Enter the selection criteria that determine which invoice installments are eligible for this request, including supplier, due date range and pay-through date.",
      "test_data": "${SUPPLIER} / ${SUPPLIER_SITE} / ${DUE_DATE} / ${PAY_THROUGH_DATE} / ${PAYMENT_CURRENCY} / ${PAYMENT_PRIORITY} / ${PAYMENT_GROUP}",
      "expected_result": "Selection criteria are accepted and applied to the request.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the selection criteria panel, entering each individual field and confirming the entry."
    },
    {
      "step_number": 6,
      "step_name": "Submit Request",
      "action": "Submit the Payment Process Request for processing.",
      "test_data": "",
      "expected_result": "Oracle Fusion accepts the request and begins selecting eligible installments.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Review Selected Installments",
      "action": "Review the list of invoice installments selected against the configured criteria.",
      "test_data": "${INVOICE_NUMBER}",
      "expected_result": "Installments matching the selection criteria are listed, and ineligible installments are correctly excluded.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Resolve Applicable Exceptions",
      "action": "Review and, where applicable, resolve exceptions raised during selection, such as invoices or suppliers on hold or missing banking information.",
      "test_data": "",
      "expected_result": "Exceptions are clearly identified and, where resolvable within scope, are addressed before the request proceeds to build.",
      "validation_type": "action",
      "note": "Not every exception is expected to be resolvable within this scenario — some are expected to remain excluded, such as a supplier on payment hold."
    },
    {
      "step_number": 9,
      "step_name": "Build Payments",
      "action": "Initiate the payment build step to convert the reviewed installments into proposed payments.",
      "test_data": "",
      "expected_result": "Oracle Fusion builds proposed payments grouped by supplier, currency and payment method for the selected installments.",
      "validation_type": "action"
    },
    {
      "step_number": 10,
      "step_name": "Complete Payment Processing",
      "action": "Complete the Payment Process Request, including formatting and transmission where those stages are part of the tested scope.",
      "test_data": "",
      "expected_result": "The request progresses to a completed status without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 11,
      "step_name": "Verify Request Status",
      "action": "Confirm the final status of the Payment Process Request.",
      "test_data": "",
      "expected_result": "The request status correctly reflects a completed run, or clearly reflects any unresolved exceptions.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 12,
      "step_name": "Validate Created Payments",
      "action": "Review the payments created by the request and confirm they are consistent with the selected invoices, supplier grouping, currency and amounts.",
      "test_data": "",
      "expected_result": "Created payments match the selected invoices and configured processing rules, with correct supplier grouping, amounts and bank account.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — the test does not stop merely because the request completed without error."
    }
  ],
  "expected_results": [
    "Eligible invoice installments matching selection criteria are correctly selected.",
    "Excluded invoices and suppliers, such as those on hold, are correctly handled and not selected.",
    "Proposed payments are grouped correctly by supplier, currency and payment method.",
    "Payment amounts on created payments match the selected invoices.",
    "The correct bank account and payment process profile are applied to created payments.",
    "The request progresses through its lifecycle to a completed status without unexpected errors.",
    "Exceptions raised during selection or build are clearly identified rather than silently dropped.",
    "The final Payment Process Request status accurately reflects the outcome of the run."
  ],
  "validation_checkpoints": [
    "Correct invoices are selected against the configured criteria.",
    "Excluded invoices are correctly handled and not selected.",
    "Supplier and payment grouping on proposed payments is correct.",
    "Payment amounts match the selected invoice installments.",
    "The correct bank account and payment process profile are applied.",
    "Payment status progresses correctly through the request lifecycle.",
    "Exceptions are clearly identified during selection or build.",
    "Final Payment Process Request status is correct and consistent with the outcome."
  ]
}