{
  "test_id": "ORCL.SCM.PIM.ITEM.UPDATE",
  "scenario_name": "Update Item",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Product Management",
  "process": "Update Item",
  "business_flow": "Item-to-Order",
  "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/product-management/update-item/",
  "objective": {
    "intro": "The objective of this test is to validate updates to purchasing, inventory, order management, manufacturing and planning attributes on an existing item in Oracle Fusion SCM Product Management, without assuming every attribute is universally editable after the item has been created.",
    "confirms": [
      "the selected attribute is updated correctly and is reflected across the relevant Oracle Fusion module (purchasing, inventory, order management, manufacturing or planning)",
      "the updated value passes Oracle's validation for the attribute's data type, value set or format",
      "an attribute that is restricted after item creation is correctly blocked from update, as configured for the item class and template",
      "an update attempted on an inactive item is correctly blocked",
      "a future-dated attribute change is correctly deferred and applied on its effective date",
      "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 updates to existing item attributes across purchasing, inventory, order management, manufacturing and planning in Oracle Fusion SCM Product Management TEST/UAT environments. It does not assume every attribute is universally editable after creation — which attributes remain open for update depends on the item class, item template and customer-specific Oracle Fusion configuration. Initial item creation is covered by the separate Create Item scenario in the same Product Management family."
  },
  "preconditions": [
    "The item to be updated already exists and is active in the target Oracle Fusion SCM Product Management environment.",
    "The attribute area to be updated (purchasing, inventory, order management, manufacturing or planning) is enabled for the item's organization assignment.",
    "The test user has appropriate access to update the selected item and attribute area.",
    "The item's status and item class permit the intended attribute change, where applicable.",
    "A comparison of prior and expected new attribute values is available for validation after the update."
  ],
  "test_data": [
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Description",
      "example": "${DESCRIPTION}"
    },
    {
      "field": "UOM",
      "example": "${UOM}"
    },
    {
      "field": "Purchasing Attribute",
      "example": "${PURCHASING_ATTRIBUTE}"
    },
    {
      "field": "Inventory Attribute",
      "example": "${INVENTORY_ATTRIBUTE}"
    },
    {
      "field": "Planning Attribute",
      "example": "${PLANNING_ATTRIBUTE}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Item Status",
      "example": "${ITEM_STATUS}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorised product data test user.",
      "test_data": "",
      "expected_result": "The Product Information Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Item Record",
      "action": "Search for and open the existing item to be updated.",
      "test_data": "${ITEM}",
      "expected_result": "The item record opens showing its current attribute values.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select the Attribute Area to Update",
      "action": "Select the relevant attribute area for the change — purchasing, inventory, order management, manufacturing or planning.",
      "test_data": "",
      "expected_result": "The selected attribute area opens for editing.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the specific attribute tab or region for the item class."
    },
    {
      "step_number": 4,
      "step_name": "Enter the New Attribute Value",
      "action": "Enter the new value for the selected attribute, including an effective date where the change is intended to apply on a future date.",
      "test_data": "${DESCRIPTION} / ${UOM} / ${PURCHASING_ATTRIBUTE} / ${INVENTORY_ATTRIBUTE} / ${PLANNING_ATTRIBUTE} / ${EFFECTIVE_DATE}",
      "expected_result": "The new value is accepted in the field and reflected on the item record.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Submit the Update",
      "action": "Review the change and submit the item update in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the update without unexpected errors.",
      "validation_type": "action",
      "note": "Reviewing the change before submission lets the tester catch an incorrect entry before the update is applied."
    },
    {
      "step_number": 6,
      "step_name": "Verify Change Applied and History Retained",
      "action": "Reopen or refresh the item and confirm the updated attribute value, and review the item's change history for the update.",
      "test_data": "",
      "expected_result": "The updated attribute value is correctly reflected on the item, and the change history records the prior value, new value, updated-by user and update date.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly applied attribute update with retained history is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The selected attribute is updated to the new value on the item.",
    "The update is correctly reflected in the relevant downstream module (purchasing, inventory, order management, manufacturing or planning).",
    "Restricted attributes remain correctly blocked from update.",
    "Invalid attribute values are correctly rejected.",
    "Future-dated changes apply on their effective date, not before.",
    "The item's change history records the update accurately."
  ],
  "validation_checkpoints": [
    "Attribute updates correctly applied and reflected across relevant modules.",
    "Restricted attribute changes correctly blocked.",
    "Invalid attribute values correctly rejected.",
    "Updates to inactive items correctly blocked.",
    "Future-dated changes correctly apply on the effective date.",
    "Unauthorized updates correctly blocked."
  ]
}