{
  "test_id": "ORCL.SCM.MFG.OPS.REJECT",
  "scenario_name": "Reject Operation",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Manufacturing",
  "process": "Reject Operation",
  "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/manufacturing/operations/reject-operation/",
  "objective": {
    "intro": "The objective of this test is to validate rejection of operation quantity at quality checkpoints in Oracle Fusion SCM Manufacturing, including disposition to scrap or rework and reason-code capture, without assuming rework is always available as a disposition option across Oracle Fusion implementations.",
    "confirms": [
      "a completed operation quantity can be rejected and correctly disposed to scrap or rework, individually or with a reason code",
      "rejected quantity is correctly recorded against the operation and reflected in the resulting disposition record",
      "rejection at a quality inspection checkpoint is correctly triggered and processed",
      "rejection of a quantity greater than the completed quantity is correctly blocked or flagged",
      "rejection without a required reason code is correctly blocked where reason capture is mandatory",
      "Oracle correctly enforces validation and security restrictions when data, configuration or authorization issues are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers rejection of operation quantity in Oracle Fusion SCM Manufacturing TEST/UAT environments, including scrap and rework disposition and reason-code capture. Availability of rework as a disposition option is governed by customer-specific work definition and operation configuration — this scenario does not assume rework is always available. It does not cover the underlying operation completion itself, which is covered by the separate Complete Operation scenario, or scrap transactions initiated outside of rejection, which are covered by the separate Scrap Quantity scenario."
  },
  "preconditions": [
    "A work order with a completed operation quantity exists in Oracle Fusion SCM Manufacturing.",
    "The operation is configured with a quality inspection checkpoint where rejection is applicable.",
    "Reject reason codes are set up in the manufacturing organization where reason-code capture is required.",
    "Scrap and/or rework disposition is configured for the operation, where applicable to the test scenario.",
    "The test user has appropriate access to reject operation quantities for the manufacturing organization."
  ],
  "test_data": [
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Operation",
      "example": "${OPERATION}"
    },
    {
      "field": "Reject Quantity",
      "example": "${REJECT_QUANTITY}"
    },
    {
      "field": "Completed Quantity",
      "example": "${COMPLETED_QUANTITY}"
    },
    {
      "field": "Reject Reason",
      "example": "${REJECT_REASON}"
    },
    {
      "field": "Disposition",
      "example": "${DISPOSITION}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Manufacturing",
      "action": "Sign in to Oracle Fusion using an authorised manufacturing test user and navigate to the Manufacturing work area.",
      "test_data": "",
      "expected_result": "The Manufacturing work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Completed Operation Quantity",
      "action": "Open the work order and operation with a completed quantity available for quality disposition.",
      "test_data": "${WORK_ORDER} / ${OPERATION}",
      "expected_result": "The operation transaction page opens showing the completed quantity ${COMPLETED_QUANTITY} available for rejection.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select Reject Action and Disposition",
      "action": "Select the reject action for the operation and choose the disposition — scrap or rework — as configured for the operation.",
      "test_data": "${DISPOSITION}",
      "expected_result": "The reject transaction opens with the selected disposition, and Oracle reflects only the disposition options actually configured for the operation.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the reject dialog and filtering available disposition options."
    },
    {
      "step_number": 4,
      "step_name": "Enter Reject Reason Code",
      "action": "Enter the reject quantity and select the applicable reject reason code.",
      "test_data": "${REJECT_QUANTITY} / ${REJECT_REASON}",
      "expected_result": "The reject quantity and reason code are accepted for a valid entry, in line with reason-code requirements for the manufacturing organization.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Submit the Rejection",
      "action": "Submit the rejection transaction.",
      "test_data": "${REJECT_QUANTITY}",
      "expected_result": "Oracle Fusion successfully processes the rejection without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Resulting Quantity and Disposition Record",
      "action": "Reopen or refresh the operation and confirm the rejected quantity and disposition record.",
      "test_data": "",
      "expected_result": "The rejected quantity is correctly recorded against the operation, and the disposition (scrap or rework) and reason code are correctly reflected.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a rejected quantity correctly recorded with the right disposition and reason code is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "Rejected quantity is correctly recorded against the operation.",
    "Disposition (scrap or rework) is correctly applied.",
    "Reason code is correctly captured.",
    "Rejection of a quantity exceeding the completed quantity is correctly blocked or flagged.",
    "Missing reject reason is correctly blocked where reason capture is required.",
    "Unauthorized rejection is correctly blocked."
  ],
  "validation_checkpoints": [
    "Rejected quantity correctly recorded against the operation.",
    "Disposition (scrap or rework) correctly applied.",
    "Reason code correctly captured.",
    "Over-rejection correctly blocked or flagged.",
    "Missing reason correctly blocked where required.",
    "Unauthorized rejection correctly blocked."
  ]
}