{
  "test_id": "ORCL.E2E.R2RFD",
  "scenario_name": "Return-to-Refund",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Return-to-Refund",
  "business_flow": "Order-to-Cash",
  "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/return-to-refund/",
  "objective": {
    "intro": "The objective of this test is to validate the end-to-end Return-to-Refund journey — original sales order, return order, receive return, inspection, restock or disposition, credit and customer balance or refund — with emphasis on returned quantity and condition correctly driving the resulting financial adjustment, rather than re-testing each stage's individual field-level validation, which is already covered on the linked Order Management Returns and Financials Accounts Receivable family pages this scenario orchestrates.",
    "confirms": [
      "the return order's returned quantity correctly matches or is validated against the original sales order's shipped quantity",
      "the receipt against the return order correctly reflects the return order's item and quantity",
      "the inspection result correctly determines the returned item's disposition",
      "restock or scrap/disposition of the returned item correctly follows the inspection result where configured",
      "the credit memo amount correctly derives from the returned quantity and the original invoice price",
      "the customer's open balance is correctly reduced by the credit amount, or a refund is correctly issued where configured",
      "returns made after partial or full payment of the original order correctly flow through to the correct balance or refund outcome",
      "duplicate, invalid-reason or out-of-window returns are correctly blocked or routed to exception handling"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-stage data integrity of the Return-to-Refund journey across Oracle Fusion SCM and Financials TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Create Return Order, Receive Return, Return Order Exceptions, Create Transaction, Credit Memo, Apply Receipt, Unapply Receipt and Reverse Receipt family pages — this page links to and orchestrates those live pages into an end-to-end journey."
  },
  "preconditions": [
    "The return order, receiving, inspection, billing and Financials AR family pages referenced by this journey are individually functional in the target Oracle Fusion SCM and Financials environment.",
    "A valid customer, item and original sales order — with or without prior payment applied — are available and enabled for returns processing.",
    "Return authorization, inspection disposition and credit memo approval workflows are configured for the test user's business unit.",
    "The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.",
    "Return window tolerances, inspection dispositions and refund-versus-balance-application rules are configured according to the target environment; this scenario does not assume a universal configuration."
  ],
  "test_data": [
    {
      "field": "Return Order",
      "example": "${RETURN_ORDER}"
    },
    {
      "field": "Original Sales Order",
      "example": "${ORIGINAL_SALES_ORDER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Inspection Result",
      "example": "${INSPECTION_RESULT}"
    },
    {
      "field": "Credit Memo",
      "example": "${CREDIT_MEMO}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create the Return Order Referencing the Original Sales Order",
      "action": "Create a return order for the returned item and quantity, referencing the original sales order, using the standard Create Return Order test scenario.",
      "test_data": "${RETURN_ORDER} / ${ORIGINAL_SALES_ORDER} / ${ITEM}",
      "expected_result": "The return order is created and correctly references the original sales order before receiving begins.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Receive the Returned Item",
      "action": "Receive the returned item against the return order — in full or as a partial return where the scenario calls for it — referencing the standard Receive Return and Return Order Exceptions test scenarios.",
      "test_data": "${RETURN_ORDER} / ${QUANTITY}",
      "expected_result": "The receipt is recorded against the return order with the correct quantity, and any exception is routed as expected.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Record the Inspection Result and Disposition",
      "action": "Where inspection is required, record the inspection result for the returned item and confirm the resulting disposition.",
      "test_data": "${ITEM} / ${INSPECTION_RESULT}",
      "expected_result": "The inspection result is recorded and correctly determines the returned item's disposition.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Restock or Dispose of the Returned Item",
      "action": "Route the returned item to sellable inventory for restock, or to scrap/disposition where configured, based on the recorded inspection result.",
      "test_data": "${ITEM} / ${INSPECTION_RESULT}",
      "expected_result": "The returned item is correctly restocked to sellable inventory or scrapped/dispositioned according to the inspection result and configuration.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Issue the Credit Memo Based on Returned Quantity and Price",
      "action": "Issue a credit memo for the returned quantity, referencing the original invoice price, using the standard Create Transaction and Credit Memo test scenarios.",
      "test_data": "${CREDIT_MEMO} / ${QUANTITY} / ${ORIGINAL_SALES_ORDER}",
      "expected_result": "The credit memo amount correctly derives from the returned quantity and the original invoice price.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — the credit memo amount correctly reflecting returned quantity and original price is the expected pass condition, not merely a successfully created credit memo document."
    },
    {
      "step_number": 6,
      "step_name": "Apply the Resulting Balance Adjustment",
      "action": "Apply the credit memo against the customer's open balance where configured, issue a refund where configured, or unapply/reverse a prior receipt to allow reallocation, using the standard Apply Receipt, Unapply Receipt and Reverse Receipt test scenarios.",
      "test_data": "${CREDIT_MEMO} / ${CUSTOMER}",
      "expected_result": "The customer's open balance is correctly reduced by the credit amount, or a refund is correctly issued where configured, including when the return follows partial or full payment of the original order.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — the correct balance or refund outcome, including for returns made after partial or full payment, is the expected pass condition."
    },
    {
      "step_number": 7,
      "step_name": "Verify Audit Trail Links Return Order, Receipt, Inspection and Credit Memo",
      "action": "Review the audit trail or document reference chain connecting the return order, receipt, inspection result and credit memo for the journey.",
      "test_data": "${RETURN_ORDER} / ${CREDIT_MEMO}",
      "expected_result": "The return order, receipt, inspection and credit memo are correctly linked in the audit trail, confirming the end-to-end journey is traceable.",
      "validation_type": "business_assertion",
      "note": "This is the final business assertion for the scenario — a traceable, correctly linked document chain from return order through credit memo is the expected pass condition for the full journey."
    }
  ],
  "expected_results": [
    "The return order is created and correctly references the original sales order before receiving begins.",
    "The receipt correctly reflects the return order's item and quantity, including partial and exception returns.",
    "Inspection results correctly determine the returned item's disposition.",
    "The returned item is correctly restocked or scrapped/dispositioned according to the inspection result.",
    "The credit memo amount correctly derives from the returned quantity and the original invoice price.",
    "The customer's open balance is correctly reduced by the credit amount, or a refund is correctly issued where configured.",
    "Duplicate, invalid-reason and out-of-window returns are correctly blocked or routed to exception handling."
  ],
  "validation_checkpoints": [
    "returned quantity correctly validated against the original shipped quantity",
    "inspection results correctly route to accepted (restock) or rejected/scrap disposition",
    "credit memo amount correctly derives from returned quantity and original price",
    "customer balance correctly reduced by the credit amount",
    "receipt unapply/reversal correctly restores balances for reallocation",
    "duplicate or invalid returns correctly blocked"
  ]
}