{
  "test_id": "ORCL.SCM.INV.CC.SEQUENCE",
  "scenario_name": "Generate Count Sequences",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Inventory Management",
  "module": "Inventory Management",
  "process": "Cycle Counts",
  "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/inventory-management/cycle-counts/generate-count-sequences/",
  "objective": {
    "intro": "The objective of this test is to validate that count sequences — the system-generated batch of items due to be counted — are correctly produced from an existing, active cycle count definition, reflecting the configured ABC classification, schedule and subinventory scope.",
    "confirms": [
      "count sequences are generated only from an active cycle count definition",
      "the correct items are included in the generated sequence based on ABC class and schedule",
      "sequence numbers are assigned correctly to each generated item",
      "subinventory scoping is respected when generation is limited to selected subinventories",
      "the generated sequence is available for count entry once produced",
      "Oracle correctly enforces validation when no items are due, the reference is invalid or generation is attempted incorrectly (DATA_ERROR, CONFIGURATION_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario assumes a cycle count definition already exists, typically built via the separate Create Cycle Count scenario. It covers generation of the count sequence only. It does not cover entering physical count quantities, which is covered by the Enter Cycle Count scenario, or the review of variances, which is covered by Cycle Count Exceptions, both in the same Cycle Counts cluster."
  },
  "preconditions": [
    "An active cycle count definition exists in the target Oracle Fusion SCM environment.",
    "Items assigned to the definition's inventory organization and ABC classes are eligible for count under the configured schedule.",
    "The inventory organization's count calendar and workday configuration are set up correctly.",
    "The test user has appropriate access to generate count sequences for the definition.",
    "Where subinventory scoping is used, the relevant subinventories are configured and active."
  ],
  "test_data": [
    {
      "field": "Cycle Count Name",
      "example": "${CYCLE_COUNT_NAME}"
    },
    {
      "field": "Inventory Organization",
      "example": "${INVENTORY_ORGANIZATION}"
    },
    {
      "field": "Count Date",
      "example": "${COUNT_DATE}"
    },
    {
      "field": "ABC Class",
      "example": "${ABC_CLASS}"
    },
    {
      "field": "Subinventory",
      "example": "${SUBINVENTORY}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Inventory",
      "action": "Sign in to Oracle Fusion using an authorised inventory test user and navigate to the Inventory Management work area.",
      "test_data": "",
      "expected_result": "The Inventory Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Cycle Counts",
      "action": "Open the Cycle Counts page for the relevant inventory organization.",
      "test_data": "${INVENTORY_ORGANIZATION}",
      "expected_result": "The Cycle Counts page opens for the correct inventory organization.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Cycle Count Definition",
      "action": "Search for and open the existing, active cycle count definition that count sequences will be generated from.",
      "test_data": "${CYCLE_COUNT_NAME}",
      "expected_result": "The correct cycle count definition is opened and confirmed active.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Initiate Generate Count Sequences",
      "action": "Start the Generate Count Sequences action for the selected cycle count definition.",
      "test_data": "",
      "expected_result": "The generate count sequences request is accepted for processing.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the generation dialog and confirming the source definition."
    },
    {
      "step_number": 5,
      "step_name": "Select Count Date",
      "action": "Select the count date, and subinventory scope where applicable, for the sequence being generated.",
      "test_data": "${COUNT_DATE} / ${SUBINVENTORY}",
      "expected_result": "The count date and scope are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Generated Item List",
      "action": "Review the resulting list of items included in the generated count sequence, checking ABC class and sequence numbering.",
      "test_data": "${ABC_CLASS}",
      "expected_result": "The generated item list reflects the correct items, ABC classification and assigned sequence numbers.",
      "validation_type": "action",
      "note": "Reviewing the generated list before confirming lets the tester catch an unexpected item selection before the sequence is finalized."
    },
    {
      "step_number": 7,
      "step_name": "Confirm and Save",
      "action": "Confirm and save the generated count sequence for the cycle count definition.",
      "test_data": "",
      "expected_result": "The count sequence is saved and becomes available for count entry, with correct items and sequence numbers.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly generated sequence with accurate item selection and numbering is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "Count sequences are generated only from an active cycle count definition.",
    "The correct items are included based on ABC class, schedule and subinventory scope.",
    "Sequence numbers are assigned correctly to each generated item.",
    "The generated sequence is available for count entry.",
    "No sequence is generated when no items are currently due for count.",
    "Oracle correctly rejects generation against an invalid or inactive cycle count reference."
  ],
  "validation_checkpoints": [
    "Correct items included in the generated sequence.",
    "Sequence numbers assigned correctly.",
    "Sequence available for entry."
  ]
}