{
  "test_id": "ORCL.O2C.AR.BILL.DEBIT.MEMO",
  "scenario_name": "Create Debit Memo",
  "application": "Oracle Fusion Cloud",
  "product": "Receivables",
  "module": "Accounts Receivable",
  "process": "Billing",
  "business_flow": "Order-to-Cash",
  "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-receivable/billing/debit-memo/",
  "objective": {
    "intro": "The objective of this test is to verify that an authorised Accounts Receivable user can successfully create a valid debit memo transaction in Oracle Fusion Receivables using valid business unit, customer, transaction type, amount, currency and accounting information.",
    "confirms": [
      "the selected Business Unit is accepted",
      "the correct customer and customer site can be selected",
      "the debit memo transaction type is accepted",
      "transaction line details and amount are accepted",
      "applicable tax is calculated or applied where relevant",
      "a valid receivable/revenue account combination is assigned",
      "the transaction can be saved and completed successfully",
      "the completed debit memo is available for subsequent lifecycle processing"
    ],
    "scope_note": "This scenario does not claim that the debit memo is collected, applied to a receipt or reconciled — those are separate downstream test cases."
  },
  "preconditions": [
    "Oracle Fusion Receivables is configured and available.",
    "The test user has access to Oracle Fusion Receivables.",
    "Relevant Business Unit exists and is active.",
    "Customer exists and is active for the Business Unit.",
    "Valid debit memo transaction type is configured.",
    "Accounting period is open.",
    "Valid receivable/revenue account combination is available.",
    "Applicable tax configuration exists where the scenario requires tax."
  ],
  "test_data": [
    {
      "field": "Business Unit",
      "example": "Active Receivables Business Unit"
    },
    {
      "field": "Customer",
      "example": "Active customer"
    },
    {
      "field": "Transaction Type",
      "example": "Valid debit memo type"
    },
    {
      "field": "Currency",
      "example": "Enabled currency"
    },
    {
      "field": "Amount",
      "example": "Scenario-defined"
    },
    {
      "field": "Transaction Date",
      "example": "Valid / open-period date"
    },
    {
      "field": "Account",
      "example": "Valid account combination"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign in to Oracle Fusion",
      "action": "Sign in to the Oracle Fusion environment using an authorised Accounts Receivable test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion home page is displayed successfully and the user session is established.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Receivables",
      "action": "Navigate to the Receivables work area.",
      "test_data": "",
      "expected_result": "The Receivables work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Open Billing",
      "action": "Open the Billing task from within Receivables.",
      "test_data": "",
      "expected_result": "The Billing transactions page is displayed.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Create a New Debit Memo Transaction",
      "action": "Select Create to start a new transaction.",
      "test_data": "",
      "expected_result": "A new transaction entry page is displayed.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select Business Unit",
      "action": "Select or enter the required Business Unit.",
      "test_data": "${BUSINESS_UNIT}",
      "expected_result": "The Business Unit is accepted and transaction-entry fields are available.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Select Debit Memo Transaction Type",
      "action": "Select the debit memo transaction type.",
      "test_data": "${TRANSACTION_TYPE}",
      "expected_result": "The debit memo transaction type is accepted.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Select Customer and Site",
      "action": "Open customer search, search for the required customer, select the customer and confirm the bill-to site.",
      "test_data": "${CUSTOMER}",
      "expected_result": "The correct customer and site are selected and customer-related details are populated or available.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening search, entering customer, clicking Search, selecting the result and confirming the site."
    },
    {
      "step_number": 8,
      "step_name": "Enter Transaction Date",
      "action": "Select or enter the transaction date.",
      "test_data": "${TRANSACTION_DATE}",
      "expected_result": "The required transaction date is populated correctly.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Enter Transaction Line Details",
      "action": "Enter transaction line description and relevant line-level details.",
      "test_data": "${LINE_DETAILS}",
      "expected_result": "Transaction line details are accepted.",
      "validation_type": "action"
    },
    {
      "step_number": 10,
      "step_name": "Enter Amount",
      "action": "Enter the transaction line amount.",
      "test_data": "${AMOUNT}",
      "expected_result": "The amount is accepted and displayed correctly.",
      "validation_type": "action"
    },
    {
      "step_number": 11,
      "step_name": "Validate Tax and Distributions",
      "action": "Review calculated tax where applicable, and enter or confirm the receivable/revenue account distribution.",
      "test_data": "${ACCOUNT}",
      "expected_result": "Tax, where applicable, and the accounting distribution are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 12,
      "step_name": "Save Transaction",
      "action": "Select Save.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the save request without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 13,
      "step_name": "Complete Transaction",
      "action": "Select Complete to finalize the transaction.",
      "test_data": "",
      "expected_result": "The transaction is completed and its status changes accordingly.",
      "validation_type": "action"
    },
    {
      "step_number": 14,
      "step_name": "Validate Transaction Number and Status",
      "action": "Confirm the generated transaction number and verify that the completed debit memo record is available.",
      "test_data": "",
      "expected_result": "The debit memo is successfully created and can be identified by the generated transaction number, with a status consistent with a completed transaction.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — the test does not stop merely because Save or Complete was clicked successfully."
    }
  ],
  "expected_results": [
    "Oracle Fusion successfully creates the debit memo using the selected test data, assigns the appropriate transaction identifier and produces the expected transaction status and financial information.",
    "Correct Business Unit is associated with the transaction.",
    "Correct customer and site are associated with the transaction.",
    "Transaction type, date and amount are retained correctly.",
    "Applicable tax, where relevant, is calculated or applied.",
    "Valid receivable/revenue account distribution is associated with the transaction.",
    "No unexpected save or completion errors occur.",
    "Completed debit memo is available for subsequent adjustment, accounting and collections scenarios."
  ],
  "validation_checkpoints": [
    "Business Unit matches the intended test data.",
    "Customer and site selection are correct.",
    "Debit memo transaction type is applied correctly.",
    "Transaction date falls within an open period.",
    "Transaction line amount is correct.",
    "Tax calculation, where applicable, is correct.",
    "Account combination is valid.",
    "Save and Complete acknowledgements are received.",
    "Transaction number is generated and retrievable.",
    "Transaction status reflects a completed debit memo."
  ]
}