{
  "test_id": "ORCL.O2C.AR.BILL.TXN.ADJUST",
  "scenario_name": "Receivables Transaction Adjustments",
  "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/transaction-adjustments/",
  "objective": {
    "intro": "The objective of this test is to verify that an authorised Accounts Receivable user can adjust an existing Receivables transaction — at the full, partial, line, tax or account level — with correct business validation, including adjustment reason capture and approval routing where required.",
    "confirms": [
      "an existing, valid Receivables transaction can be located and opened for adjustment",
      "the appropriate adjustment type is accepted (full, partial, line, tax or account-level)",
      "a valid adjustment reason code can be selected and is retained",
      "the adjustment amount is accepted and correctly reduces or changes the transaction balance",
      "the adjustment is routed for approval when the configured business rule requires it",
      "the Receivable and Revenue account impact reflects the adjustment type",
      "the adjustment can be saved successfully",
      "the updated transaction balance and adjustment history are available for subsequent review"
    ],
    "scope_note": "This scenario does not claim that every adjustment automatically completes without approval — approval requirements are business-rule-dependent and are validated as part of the scenario, not assumed."
  },
  "preconditions": [
    "Oracle Fusion Receivables is configured and available.",
    "The test user has access to Receivables Billing.",
    "A valid, existing Receivables transaction is available to adjust.",
    "The customer associated with the transaction is active.",
    "An adjustment reason code is configured and active.",
    "The relevant accounting period is open.",
    "A valid account combination is available for account-level adjustments.",
    "The applicable approval workflow is configured, where adjustments of this type or amount require approval."
  ],
  "test_data": [
    {
      "field": "Original Transaction",
      "example": "Existing valid AR transaction"
    },
    {
      "field": "Adjustment Type",
      "example": "Full, partial, line, tax or account-level"
    },
    {
      "field": "Adjustment Reason",
      "example": "Valid reason code"
    },
    {
      "field": "Adjustment Amount",
      "example": "Scenario-defined"
    },
    {
      "field": "Approval Required",
      "example": "Yes/No per policy"
    },
    {
      "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": "Open the Oracle Fusion Navigator and go 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 within Receivables.",
      "test_data": "",
      "expected_result": "The Billing work area is displayed, showing existing transactions.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Locate the Transaction to Adjust",
      "action": "Search for and open the existing transaction that requires adjustment.",
      "test_data": "${TRANSACTION_NUMBER}",
      "expected_result": "The correct transaction is located and its details are displayed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening search, entering the transaction number, clicking Search and selecting the result."
    },
    {
      "step_number": 5,
      "step_name": "Initiate Transaction Adjustment",
      "action": "From the transaction, initiate the Adjustment action.",
      "test_data": "",
      "expected_result": "The Adjustment entry page or panel is displayed.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Select Adjustment Type",
      "action": "Select the applicable adjustment type — full, partial, line, tax or account.",
      "test_data": "${ADJUSTMENT_TYPE}",
      "expected_result": "The selected adjustment type is accepted and the relevant entry fields become available.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Select Adjustment Reason",
      "action": "Select a valid adjustment reason code.",
      "test_data": "${ADJUSTMENT_REASON}",
      "expected_result": "The adjustment reason is accepted and retained on the adjustment.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Enter Adjustment Amount and Details",
      "action": "Enter the adjustment amount and any line, tax or account-level detail required by the selected adjustment type.",
      "test_data": "${ADJUSTMENT_AMOUNT}",
      "expected_result": "The adjustment amount and supporting details are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Submit for Approval Where Required",
      "action": "Submit the adjustment, allowing Oracle Fusion to route it for approval if the configured business rule requires it.",
      "test_data": "",
      "expected_result": "The adjustment is submitted, and — where approval is required by policy — is routed to the correct approver.",
      "validation_type": "action",
      "note": "Whether approval is triggered depends on the customer's configured approval workflow and adjustment thresholds, not on a fixed rule."
    },
    {
      "step_number": 10,
      "step_name": "Validate Accounting Impact",
      "action": "Review the projected or resulting Receivable and Revenue account distributions for the adjustment.",
      "test_data": "${ACCOUNT_COMBINATION}",
      "expected_result": "The accounting impact is consistent with the adjustment type and amount entered.",
      "validation_type": "action"
    },
    {
      "step_number": 11,
      "step_name": "Save the Adjustment",
      "action": "Select Save to commit the adjustment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the save request without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 12,
      "step_name": "Validate Adjustment Status",
      "action": "Confirm the resulting status of the adjustment — approved, pending approval, or applied.",
      "test_data": "",
      "expected_result": "The adjustment status correctly reflects whether approval is pending or the adjustment has been applied.",
      "validation_type": "action"
    },
    {
      "step_number": 13,
      "step_name": "Validate Updated Transaction Balance",
      "action": "Re-open the transaction and confirm the outstanding balance reflects the adjustment.",
      "test_data": "",
      "expected_result": "The transaction balance is updated by the adjustment amount, consistent with the adjustment type.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the scenario — the test does not stop merely because Save was clicked successfully."
    },
    {
      "step_number": 14,
      "step_name": "Validate Audit / Adjustment History",
      "action": "Review the adjustment history or audit trail associated with the transaction.",
      "test_data": "",
      "expected_result": "The adjustment — including type, reason, amount and approval outcome — is recorded in the transaction's adjustment history.",
      "validation_type": "business_assertion",
      "note": "Confirms the adjustment is traceable after Save, not only that the save action succeeded."
    }
  ],
  "expected_results": [
    "The selected adjustment type (full, partial, line, tax or account-level) is applied to the transaction.",
    "The adjustment reason and amount are retained on the transaction.",
    "The outstanding transaction balance is updated to reflect the adjustment.",
    "Receivable and Revenue accounting distributions are updated consistently with the adjustment type.",
    "The adjustment is routed for approval when the configured business rule requires it.",
    "No unexpected save errors occur.",
    "The adjustment status accurately reflects pending-approval or applied outcomes.",
    "The adjustment is recorded in the transaction's adjustment/audit history.",
    "The adjusted transaction is available for subsequent accounting and receipt-application scenarios."
  ],
  "validation_checkpoints": [
    "Correct original transaction is selected.",
    "Adjustment type matches the intended test data.",
    "Adjustment reason is valid and retained.",
    "Adjustment amount is correct.",
    "Approval routing occurs when required by policy.",
    "Receivable/Revenue account impact is consistent with the adjustment.",
    "Transaction balance is updated correctly.",
    "Save acknowledgement is received.",
    "Adjustment status is accurate.",
    "Adjustment history/audit trail reflects the change.",
    "Line-level and tax-level adjustments net correctly against the header.",
    "Account-level adjustments post to a valid account combination."
  ]
}
