{
  "test_id": "ORCL.O2C.OM.CHG.HOLD.APPLY",
  "scenario_name": "Apply Order Hold",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Order Management",
  "module": "Order Management",
  "process": "Order Changes",
  "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/scm/order-management/order-changes/apply-order-hold/",
  "objective": {
    "intro": "Validate application of a hold on a sales order or a specific order line, confirming that Oracle Fusion correctly records the hold and blocks further fulfillment processing until it is released — while leaving unrelated orders and lines unaffected.",
    "confirms": [
      "an eligible submitted order, or a specific order line, can have a hold correctly applied",
      "the hold type and hold reason selected are correctly recorded against the order or line",
      "downstream fulfillment processing (such as scheduling, shipping or invoicing, as applicable) is correctly blocked while the hold is active",
      "unaffected order lines, or unrelated orders, continue processing normally",
      "hold application activity is retained in the order's history for audit purposes",
      "users without the appropriate role or access cannot apply a hold",
      "attempts to apply an invalid, duplicate, or out-of-scope hold are correctly prevented or flagged"
    ],
    "scope_note": "This scenario does not claim that hold release, order cancellation or subsequent order changes are covered — those are addressed by separate test scenarios in the Order Changes lifecycle."
  },
  "preconditions": [
    "Oracle Fusion Order Management access is configured and available for the test user.",
    "A submitted sales order, or a specific order line, exists and is eligible to have a hold applied.",
    "One or more hold types (for example credit, compliance/export, manual review, or pricing) are configured for the organization.",
    "The test user, or acting persona, has the appropriate role and access to apply the applicable hold type."
  ],
  "test_data": [
    {
      "field": "Order Number",
      "example": "${ORDER_NUMBER}"
    },
    {
      "field": "Item",
      "example": "${ITEM} — applicable when the hold is applied at the line level"
    },
    {
      "field": "Hold Type",
      "example": "${HOLD_TYPE} — customer-configured, for example credit, compliance/export, manual review, or pricing"
    },
    {
      "field": "Hold Reason",
      "example": "${HOLD_REASON}"
    },
    {
      "field": "Applied By",
      "example": "${APPLIED_BY} — user or persona applying the hold"
    },
    {
      "field": "Hold Scope",
      "example": "Order-level or line-level — scenario-defined"
    },
    {
      "field": "Order/Line Status",
      "example": "Status of the order or line at the time the hold is applied, for example Submitted or Scheduled"
    },
    {
      "field": "Hold Application Action",
      "example": "Apply Hold"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In",
      "action": "Sign in to Oracle Fusion as a user authorized to apply order holds.",
      "test_data": "${APPLIED_BY}",
      "expected_result": "The user signs in successfully and lands on the home page.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Order Management",
      "action": "Navigate to the Order Management work area.",
      "test_data": "",
      "expected_result": "The Order Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Order",
      "action": "Search for and open the order that is eligible to have a hold applied.",
      "test_data": "${ORDER_NUMBER}",
      "expected_result": "The correct order is opened and its current status is confirmed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening search, entering the order number, clicking Search and selecting the result."
    },
    {
      "step_number": 4,
      "step_name": "Select Hold Scope",
      "action": "Select whether the hold applies at the order level or to a specific order line.",
      "test_data": "${ITEM}",
      "expected_result": "The intended scope — order-level or line-level — is correctly selected before the hold is applied.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select Hold Type and Provide Reason",
      "action": "Select the applicable hold type and enter the hold reason.",
      "test_data": "${HOLD_TYPE} / ${HOLD_REASON}",
      "expected_result": "The selected hold type and reason are accepted by Oracle Fusion.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Apply the Hold",
      "action": "Submit the action to apply the hold to the selected order or line.",
      "test_data": "",
      "expected_result": "The hold application action is accepted by Oracle Fusion without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Downstream Processing Blocked",
      "action": "Confirm that further fulfillment processing on the held order or line is blocked while the hold is active.",
      "test_data": "",
      "expected_result": "Downstream processing — such as scheduling, shipping or invoicing, as applicable — is correctly blocked for the held order or line.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — the test does not stop merely because the hold action was accepted successfully."
    },
    {
      "step_number": 8,
      "step_name": "Verify Unaffected Orders/Lines Are Unimpacted",
      "action": "Confirm that orders or lines not subject to the hold continue processing normally.",
      "test_data": "",
      "expected_result": "Unrelated orders and unaffected lines are unimpacted and continue through fulfillment processing as expected.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The hold is correctly recorded against the order or line based on the selected scope, type and reason.",
    "Downstream fulfillment processing is blocked while the hold remains active.",
    "Orders and lines not subject to the hold continue processing normally and are unaffected.",
    "Hold application detail, including hold type, reason and applied-by, is retained in the order's history for audit purposes.",
    "Users without the appropriate role or access cannot apply the hold.",
    "Attempts to apply an invalid, duplicate, or out-of-scope hold are correctly prevented or flagged by Oracle Fusion validations."
  ],
  "validation_checkpoints": [
    "Hold is correctly recorded against the order/line.",
    "Downstream fulfillment processing is correctly blocked while the hold is active.",
    "Unaffected lines/orders continue processing normally.",
    "Hold application history/audit trail is recorded."
  ]
}