{
  "test_id": "ORCL.SCM.PLAN.EXCEPTIONS",
  "scenario_name": "Planning Exceptions",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Supply Planning",
  "process": "Planning Exceptions",
  "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/supply-planning/planning-exceptions/",
  "objective": {
    "intro": "The objective of this test is to validate that Oracle Fusion SCM Supply Planning correctly generates system planning exceptions from the supply plan output — including past due orders, items to expedite or de-expedite, shortage, overcapacity, resource conflict, excess supply and order-change exceptions — and that exception review and resolution routing behaves correctly, applying the site's Failure Intelligence discipline to planning-specific exceptions rather than assuming every exception is an application defect.",
    "confirms": [
      "each configured exception type is correctly detected and classified from the supply plan output",
      "exception detail correctly displays the supporting order and item data behind the exception",
      "severity-based filtering correctly narrows the exception list",
      "resolution actions such as reschedule or cancellation correctly update the underlying order",
      "invalid resolution actions and unauthorized resolution attempts are correctly rejected or blocked",
      "Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers review and resolution of planning exceptions as generated and configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover the underlying plan run itself or plan-wide supply/demand analysis, which are covered by the separate Run Supply Plan and Plan Analysis scenarios in the same Supply Planning cluster. Not every exception type described here is necessarily configured or enabled in every environment."
  },
  "preconditions": [
    "The test user has appropriate Supply Planner or Planning Manager access to review and resolve planning exceptions.",
    "A supply plan has been run and has completed, generating an exception workbench for review (see Run Supply Plan).",
    "Required exception types are configured and active for the target supply plan in the target Oracle Fusion environment.",
    "Test orders and items referenced in exception test data exist and are visible within the plan scope.",
    "Severity thresholds and resolution action configuration referenced in test data are configured and active."
  ],
  "test_data": [
    {
      "field": "Plan Name",
      "example": "${PLAN_NAME}"
    },
    {
      "field": "Exception Type",
      "example": "${EXCEPTION_TYPE}"
    },
    {
      "field": "Order",
      "example": "${ORDER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Severity",
      "example": "${SEVERITY}"
    },
    {
      "field": "Resolution Action",
      "example": "${RESOLUTION_ACTION}"
    },
    {
      "field": "Resource",
      "example": "${RESOURCE}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to the Planning Exceptions Workbench",
      "action": "Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the planning exceptions workbench for the target plan.",
      "test_data": "${PLAN_NAME}",
      "expected_result": "The planning exceptions workbench opens and displays exceptions generated for the target plan.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Filter by Exception Type or Severity",
      "action": "Filter the exception list by exception type and by severity level.",
      "test_data": "${EXCEPTION_TYPE} / ${SEVERITY}",
      "expected_result": "The exception list correctly narrows to exceptions matching the selected type and severity.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Review Exception Detail and Supporting Data",
      "action": "Open an individual exception and review its detail, including the supporting order and item data behind the exception.",
      "test_data": "${ORDER} / ${ITEM}",
      "expected_result": "The exception detail correctly displays the supporting order and item data behind the exception.",
      "validation_type": "action",
      "note": "Reviewing the underlying order and item data before acting lets the tester confirm the exception is genuinely applicable before resolution."
    },
    {
      "step_number": 4,
      "step_name": "Apply a Resolution Action",
      "action": "Apply a resolution action to the exception, such as rescheduling the order or cancelling it, using ${RESOLUTION_ACTION}.",
      "test_data": "${RESOLUTION_ACTION}",
      "expected_result": "Oracle Fusion accepts the resolution action without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Verify the Exception Clears",
      "action": "Refresh the exceptions workbench and confirm the resolved exception no longer appears in the active exception list.",
      "test_data": "",
      "expected_result": "The resolved exception correctly clears from the active exception list.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Underlying Order Updates Correctly",
      "action": "Open the underlying order referenced by the resolved exception and confirm it reflects the resolution action applied.",
      "test_data": "${ORDER}",
      "expected_result": "The underlying order correctly reflects the reschedule or cancellation applied during exception resolution.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — the exception clearing is not sufficient on its own; the underlying order must correctly reflect the resolution."
    }
  ],
  "expected_results": [
    "Each configured exception type is correctly detected and classified from the supply plan output.",
    "Exception detail correctly displays the supporting order and item data behind the exception.",
    "Severity-based filtering correctly narrows the exception list.",
    "Resolution actions correctly update the underlying order and clear the exception.",
    "Invalid resolution actions are correctly rejected before being applied.",
    "Unauthorized resolution attempts are correctly blocked."
  ],
  "validation_checkpoints": [
    "Each exception type correctly detected and classified from the supply plan output.",
    "Exception detail correctly displays supporting order and item data.",
    "Severity filtering correctly narrows the exception list.",
    "Reschedule and cancellation resolutions correctly update the underlying order.",
    "Invalid resolution actions correctly rejected.",
    "Unauthorized resolution correctly blocked."
  ]
}