{
  "test_id": "ORCL.SCM.PLAN.COLLECT",
  "scenario_name": "Collect Planning Data",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Supply Planning",
  "process": "Collect Planning Data",
  "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/collect-planning-data/",
  "objective": {
    "intro": "The objective of this test is to validate collection of planning data — including items, on-hand balances, open supply and demand orders, forecasts, sourcing rules, bills of material, routings and calendars — from source systems into the Oracle Fusion Supply Planning data store, using a valid collection template ${COLLECTION_TEMPLATE}, without assuming that every data category is collected on every run.",
    "confirms": [
      "each selected data category is correctly collected into the planning data store as configured by the collection template",
      "net-change collection correctly captures only records changed since the previous collection run",
      "source system unavailability is correctly flagged rather than allowed to silently succeed",
      "a collection run cannot be started while another collection job for the same template is already running",
      "collected data is available for downstream plan generation once collection completes",
      "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 collection of planning data as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover generating a supply plan from the collected data, analyzing planning exceptions, or releasing planned orders, which are covered by the separate Run Supply Plan, Planning Exceptions and Release Planned Order scenarios in the same Supply Planning cluster."
  },
  "preconditions": [
    "The test user has appropriate Planning Analyst or Planning Administrator access to run planning data collection.",
    "A valid collection template ${COLLECTION_TEMPLATE} is configured and active in the target Oracle Fusion environment.",
    "Source systems referenced by the collection template, including ${SOURCE_SYSTEM}, are reachable and configured for collection.",
    "The organization(s) ${ORGANIZATION} in which data is being collected are enabled for planning collection.",
    "No other collection job for the same collection template is currently running."
  ],
  "test_data": [
    {
      "field": "Collection Template",
      "example": "${COLLECTION_TEMPLATE}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Source System",
      "example": "${SOURCE_SYSTEM}"
    },
    {
      "field": "Collection Type",
      "example": "${COLLECTION_TYPE}"
    },
    {
      "field": "Job Status",
      "example": "${JOB_STATUS}"
    },
    {
      "field": "Data Category",
      "example": "${DATA_CATEGORY}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Supply Planning",
      "action": "Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the Supply Planning work area.",
      "test_data": "",
      "expected_result": "The Supply Planning work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Collection Template",
      "action": "Open the planning data collection template that defines which data categories and organizations are collected.",
      "test_data": "${COLLECTION_TEMPLATE}",
      "expected_result": "The collection template opens and shows the configured collection options.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select the Data Categories and Organizations to Collect",
      "action": "Select the data categories and organizations to include in the collection run, as supported by the template.",
      "test_data": "${DATA_CATEGORY} / ${ORGANIZATION}",
      "expected_result": "The selected data categories and organizations are accepted for the collection run.",
      "validation_type": "action",
      "note": "Not every data category is collected on every run — the selection depends on the collection template and what is relevant to the target organization."
    },
    {
      "step_number": 4,
      "step_name": "Submit the Collection Run",
      "action": "Submit the planning data collection run using the selected collection type, either full or net-change.",
      "test_data": "${COLLECTION_TYPE}",
      "expected_result": "Oracle Fusion successfully submits the collection run without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Monitor Job Status",
      "action": "Monitor the collection job status until it completes, fails, or reports a partial exception.",
      "test_data": "${JOB_STATUS}",
      "expected_result": "The collection job status is visible and updates to a completed, errored or partially completed state.",
      "validation_type": "action",
      "note": "A collection job already running for the same template should correctly block or queue a new run rather than starting a second, conflicting run."
    },
    {
      "step_number": 6,
      "step_name": "Verify Collected Data Completeness and Error Log",
      "action": "Verify the completeness of the collected data for the selected categories and review any error log entries.",
      "test_data": "",
      "expected_result": "The selected data categories are correctly collected into the planning data store, and any collection errors are logged rather than silently ignored.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — correctly and completely collected data is the expected pass condition, not merely a successful job submission."
    }
  ],
  "expected_results": [
    "Each selected data category is correctly collected into the planning data store as configured by the collection template.",
    "Net-change collection correctly captures only records changed since the previous collection run.",
    "Data and configuration validation errors, including an invalid collection template, are correctly enforced.",
    "Source system unavailability is correctly flagged rather than allowed to silently succeed.",
    "A concurrent collection run for the same template is correctly blocked or queued.",
    "Collected data is available and complete for downstream supply plan generation."
  ],
  "validation_checkpoints": [
    "Each selected data category correctly collected into the planning data store.",
    "Net-change collection correctly captures only changed records.",
    "Invalid collection template correctly rejected.",
    "Source unavailability correctly flagged rather than silently succeeding.",
    "Concurrent collection run correctly blocked or queued.",
    "Unauthorized collection run correctly blocked."
  ]
}