{
  "test_id": "ORCL.SCM.INV.TXN.CORRECT",
  "scenario_name": "Inventory Transaction Correction",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Inventory Management",
  "module": "Inventory Management",
  "process": "Item Transactions",
  "business_flow": "Plan-to-Produce",
  "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/inventory-management/item-transactions/inventory-transaction-correction/",
  "objective": {
    "intro": "The objective of this test is to validate that an Oracle Fusion inventory transaction eligible for correction can be corrected or reversed — where supported by the transaction type, transaction status and accounting period — while the resulting on-hand balance is adjusted correctly and the transaction's history retains an accurate record of the change.",
    "confirms": [
      "an eligible original transaction can be located and opened by an authorized user",
      "correction or reversal is available only for transaction types and statuses that support it",
      "a corrected quantity, lot or serial context is accepted without unexpected validation errors, when within allowed limits",
      "the resulting on-hand balance is adjusted or restored accurately after the correction is submitted",
      "a record of both the original and corrected transaction is retained in transaction history rather than silently overwritten",
      "corrections attempted against ineligible transactions, closed periods or by unauthorized users are correctly prevented"
    ],
    "scope_note": "This scenario covers correcting or reversing an inventory transaction that has already been recorded within Oracle Fusion Inventory Management TEST/UAT environments. Not every transaction type is eligible for correction — availability depends on transaction type, status, downstream consumption and customer configuration. It does not cover the original receipt, issue or transfer transactions, which are covered by the separate Miscellaneous Receipt, Miscellaneous Issue and Subinventory Transfer scenarios. Field-level correction variations, such as quantity, lot or serial context, are represented as data-driven variations of this same test rather than as separate published test pages."
  },
  "preconditions": [
    "The original transaction exists and is in a status that is eligible for correction.",
    "The accounting period for the original transaction is open, or correction is otherwise permitted by configuration.",
    "The user performing the correction has the appropriate inventory transaction correction privileges."
  ],
  "test_data": [
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Original Transaction ID",
      "example": "${ORIGINAL_TRANSACTION_ID}"
    },
    {
      "field": "Transaction Type",
      "example": "${TRANSACTION_TYPE}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Original Quantity",
      "example": "${ORIGINAL_QUANTITY}"
    },
    {
      "field": "Corrected Quantity",
      "example": "${CORRECTED_QUANTITY}"
    },
    {
      "field": "Lot",
      "example": "${LOT}"
    },
    {
      "field": "Serial",
      "example": "${SERIAL}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorized Inventory Management test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion signs the user in successfully and the home page loads.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Inventory Management",
      "action": "Navigate to the Inventory Management work area used to review recorded item transactions.",
      "test_data": "",
      "expected_result": "The Inventory Management work area opens and transaction search is available.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Original Transaction",
      "action": "Search for and open the original transaction eligible for correction.",
      "test_data": "${ORIGINAL_TRANSACTION_ID} / ${ITEM}",
      "expected_result": "The correct transaction is located and its current quantity, lot/serial context and status are displayed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening transaction search, entering the transaction identifier, and selecting the result."
    },
    {
      "step_number": 4,
      "step_name": "Initiate Correction or Reversal",
      "action": "Select the option to correct or reverse the located transaction, as applicable to its transaction type.",
      "test_data": "",
      "expected_result": "The correction or reversal page opens showing the current transaction values.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Corrected Values",
      "action": "Enter the corrected quantity, lot or serial context relevant to this variation.",
      "test_data": "${CORRECTED_QUANTITY} / ${LOT} / ${SERIAL}",
      "expected_result": "The corrected values are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Resulting On-Hand Impact",
      "action": "Review the projected on-hand balance impact of the correction before submitting.",
      "test_data": "",
      "expected_result": "The projected on-hand balance reflects the correction that is about to be submitted.",
      "validation_type": "action",
      "note": "Reviewing the resulting on-hand impact before submitting lets the tester catch an incorrect entry before it is committed."
    },
    {
      "step_number": 7,
      "step_name": "Submit the Correction",
      "action": "Submit and save the correction or reversal in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully saves the correction without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify On-Hand Adjusted and History Retained",
      "action": "Reopen or refresh the transaction and on-hand inquiry, and review the transaction history after the correction is saved.",
      "test_data": "",
      "expected_result": "The on-hand balance is adjusted or restored correctly, and the transaction history retains a record of both the original and corrected values.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the scenario — an accurately adjusted on-hand balance with a preserved history record is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "Correction or reversal is accepted without unexpected errors, when the transaction type, status and period support it.",
    "The corrected or reversed transaction is reflected accurately once the correction is submitted.",
    "The resulting on-hand balance is adjusted or restored correctly.",
    "A record of the correction is retained in the transaction's history.",
    "Corrections attempted against ineligible transaction types, closed periods or invalid quantities are correctly prevented.",
    "Unauthorized correction attempts are correctly prevented."
  ],
  "validation_checkpoints": [
    "Corrected or reversed transaction is reflected accurately.",
    "On-hand balance is adjusted or restored correctly.",
    "Transaction history retains a record of the original and corrected values."
  ]
}