{
  "test_id": "ORCL.P2P.PROC.SUPPLIER.BANK",
  "scenario_name": "Supplier Bank Account",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Procurement",
  "module": "Procurement",
  "process": "Suppliers",
  "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/scm/procurement/suppliers/supplier-bank-account/",
  "objective": {
    "intro": "The objective of this test is to validate that supplier payment bank information can be created and maintained in Oracle Fusion SCM Procurement where applicable, using valid bank, branch, account and routing details, payment method and currency, and that sensitive banking values are appropriately protected throughout the process.",
    "confirms": [
      "a new supplier bank account can be added with valid bank, branch, account and routing details",
      "the bank account is correctly associated with the intended supplier (and supplier site, where applicable)",
      "the selected payment method and currency are correctly reflected on the bank account",
      "an existing supplier bank account can be updated where the business process requires it",
      "sensitive banking values are masked or restricted in captured test evidence and reports",
      "Oracle correctly enforces validation and security restrictions when data errors, configuration errors or unauthorized access are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers creation and maintenance of supplier payment bank information within Oracle Fusion SCM Procurement TEST/UAT environments only. It does not cover the underlying supplier or supplier site creation, which are covered by the separate Create Supplier and Create Supplier Site scenarios in the same Suppliers cluster, and it never uses real bank account numbers, routing numbers or other sensitive banking information."
  },
  "preconditions": [
    "The supplier exists and is active in the target Oracle Fusion SCM environment.",
    "The test user has appropriate — typically restricted — access to maintain supplier banking data.",
    "Bank and bank branch configuration required for the intended payment method is already set up in the environment.",
    "A valid payment method and currency are configured for the supplier's business unit.",
    "The supplier site to which the bank account will apply, where applicable, is active."
  ],
  "test_data": [
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Supplier Site",
      "example": "${SUPPLIER_SITE}"
    },
    {
      "field": "Bank Name",
      "example": "${BANK_NAME}"
    },
    {
      "field": "Bank Branch",
      "example": "${BANK_BRANCH}"
    },
    {
      "field": "Routing Details",
      "example": "${ROUTING_DETAILS}"
    },
    {
      "field": "Bank Account Number",
      "example": "${BANK_ACCOUNT_NUMBER}"
    },
    {
      "field": "Payment Method",
      "example": "${PAYMENT_METHOD}"
    },
    {
      "field": "Currency",
      "example": "${CURRENCY}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In With Appropriate Banking Access",
      "action": "Sign in to Oracle Fusion using an authorised test user with appropriate — typically restricted — access to supplier banking data.",
      "test_data": "",
      "expected_result": "Oracle Fusion home page is displayed and the user session is established with the correct banking data access.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Supplier Banking Information",
      "action": "Navigate to the supplier record and open the banking information for the correct supplier, and supplier site where applicable.",
      "test_data": "${SUPPLIER} / ${SUPPLIER_SITE}",
      "expected_result": "The supplier's banking information page opens for the correct supplier.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Add a New Bank Account",
      "action": "Initiate adding a new bank account for the supplier.",
      "test_data": "",
      "expected_result": "A new, unsaved bank account entry is opened for the supplier.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the add bank account panel and confirming the supplier context."
    },
    {
      "step_number": 4,
      "step_name": "Enter Account and Routing Details",
      "action": "Enter the bank name, branch, account number and routing details for the new bank account.",
      "test_data": "${BANK_NAME} / ${BANK_BRANCH} / ${ROUTING_DETAILS} / ${BANK_ACCOUNT_NUMBER}",
      "expected_result": "The bank, branch, account and routing details are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select Payment Method and Currency",
      "action": "Select the payment method and currency the bank account will support.",
      "test_data": "${PAYMENT_METHOD} / ${CURRENCY}",
      "expected_result": "The selected payment method and currency are accepted and reflected on the bank account.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Entered Bank Account Information",
      "action": "Review the entered bank, branch, account, routing and payment attribute information before saving.",
      "test_data": "",
      "expected_result": "The reviewed information matches the entered supplier, bank, routing and payment attribute data.",
      "validation_type": "action",
      "note": "Reviewing the bank account before saving lets the tester catch an incorrect field entry before it is created."
    },
    {
      "step_number": 7,
      "step_name": "Save the Bank Account",
      "action": "Save the bank account for the supplier in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion accepts the bank account submission and processes it without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Association and Appropriate Handling of Sensitive Data",
      "action": "Reopen the supplier's banking information and confirm the bank account is correctly associated, payment attributes are correct, and sensitive values are masked or restricted in captured evidence and reports.",
      "test_data": "",
      "expected_result": "The bank account is correctly associated with the supplier, payment attributes are correct, and sensitive banking values are masked or restricted in evidence and reports.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly associated bank account that also protects sensitive banking data is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "A new bank account is successfully added for the supplier.",
    "The bank account is correctly associated with the correct supplier, and supplier site where applicable.",
    "Payment method, currency and other payment attributes are correct.",
    "Bank, branch and routing details are captured correctly.",
    "Only appropriately authorized users can create, update or view supplier banking data.",
    "Sensitive banking values are masked or restricted in test evidence and reports."
  ],
  "validation_checkpoints": [
    "The bank account is associated correctly with the correct supplier and site.",
    "Payment attributes — payment method, currency and account status — are correct.",
    "Sensitive banking values are handled appropriately, with masking or restriction applied in evidence and reports."
  ]
}