{
  "test_id": "ORCL.SCM.PIM.ITEM.LIFECYCLE",
  "scenario_name": "Item Lifecycle Status",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Product Management",
  "process": "Item Lifecycle Status",
  "business_flow": "Item Master Management",
  "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/item-lifecycle-status/",
  "objective": {
    "intro": "The objective of this test is to validate item lifecycle status transitions (for example New, Active, Inactive, Obsolete or Pending, as configured) and correct enforcement of status-driven transaction restrictions, without assuming a fixed universal status set.",
    "confirms": [
      "the item's lifecycle status correctly transitions per the statuses and rules configured for the organization",
      "effective-dated status transitions are correctly applied on or after the configured effective date",
      "status-driven transaction restrictions are correctly enforced immediately after a status change",
      "invalid status transitions are correctly rejected",
      "status changes on items with open transactions are correctly blocked or flagged, as configured",
      "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 transitioning the lifecycle status of an existing item and validating status-driven transaction restriction enforcement in Oracle Fusion SCM Product Management TEST/UAT environments. It does not cover creation of the item itself, its category or organization assignment, which are covered by the separate Create Item, Item Category Assignment and Item Organization Assignment scenarios in the same Product Management family. Lifecycle statuses and their configured behavior vary by customer setup and are never assumed to be a fixed universal set."
  },
  "preconditions": [
    "The item already exists and is created in Oracle Fusion SCM Product Management.",
    "The lifecycle statuses and transition rules relevant to the test are configured for the item's item class and organization.",
    "Where effective dating is used, the effective date field is enabled for the lifecycle status attribute.",
    "The test user has appropriate access to change the item's lifecycle status.",
    "Any open transactions referenced in negative test data exist against the item in the test environment."
  ],
  "test_data": [
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Current Status",
      "example": "${CURRENT_STATUS}"
    },
    {
      "field": "New Status",
      "example": "${NEW_STATUS}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Open Transaction",
      "example": "${OPEN_TRANSACTION}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Product Management",
      "action": "Sign in to Oracle Fusion using an authorised product data test user and navigate to the Product Information Management work area.",
      "test_data": "",
      "expected_result": "The Product Information Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Item's Status Field",
      "action": "Search for and open the item record and navigate to its lifecycle status field.",
      "test_data": "${ITEM}",
      "expected_result": "The item's lifecycle status field is accessible and the current status ${CURRENT_STATUS} is displayed.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select the New Lifecycle Status and Effective Date",
      "action": "Select the new lifecycle status and, where applicable, enter the effective date for the transition.",
      "test_data": "${NEW_STATUS} / ${EFFECTIVE_DATE}",
      "expected_result": "The new status and effective date are accepted by the item record.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Save the Status Change",
      "action": "Save the item record to submit the lifecycle status change for processing in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the status change without unexpected errors.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as triggering the save action and confirming the submission confirmation message."
    },
    {
      "step_number": 5,
      "step_name": "Verify the Item Reflects the New Status",
      "action": "Reopen or refresh the item record and confirm the lifecycle status has updated.",
      "test_data": "",
      "expected_result": "The item correctly reflects the new lifecycle status ${NEW_STATUS} as of ${EFFECTIVE_DATE}.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Status-Driven Transaction Restrictions Apply Correctly",
      "action": "Attempt a transaction type that should be governed by the new status and confirm the resulting restriction, or allowance, matches what is configured for ${NEW_STATUS}.",
      "test_data": "${NEW_STATUS}",
      "expected_result": "Status-driven transaction restrictions are correctly enforced according to the new status.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a status that correctly restricts or allows downstream transactions is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The item's lifecycle status correctly transitions to the intended status.",
    "Effective-dated transitions apply on the correct effective date.",
    "Status-driven transaction restrictions are correctly enforced after the change.",
    "Invalid status transitions are correctly rejected.",
    "Status changes on items with open transactions are correctly blocked or flagged.",
    "Unauthorized status changes are correctly blocked."
  ],
  "validation_checkpoints": [
    "Item status correctly transitions per configured lifecycle rules.",
    "Effective date correctly applied to the transition.",
    "Status-driven transaction restrictions correctly enforced after the change.",
    "Invalid transitions correctly rejected.",
    "Status change on items with open transactions correctly blocked or flagged.",
    "Unauthorized status change correctly blocked."
  ]
}