{
  "test_id": "ORCL.R2R.GL.JRN.IMPORT",
  "scenario_name": "Import Journals",
  "application": "Oracle Fusion Cloud",
  "product": "Financials",
  "module": "General Ledger",
  "process": "Journals",
  "business_flow": "Record-to-Report",
  "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/financials/general-ledger/journals/import-journals/",
  "objective": {
    "intro": "The objective of this test is to verify that journal data brought into Oracle Fusion General Ledger from a configured import source — depending on the configured import mechanism, this may be a file-based import, an interface table, an API or a subledger integration — results in the expected journal outcome: valid data produces correctly formed journal batches, and invalid or incomplete data produces the expected import exception.",
    "confirms": [
      "the configured import source or interface is accepted for the run",
      "the selected ledger and accounting period are accepted",
      "the import process completes and returns a status",
      "valid source data produces new journal(s) with the expected header and line detail",
      "the imported journal batch, journal source and journal category are correctly recorded",
      "invalid or incomplete source data produces the expected import exception rather than a malformed journal",
      "import exceptions or rejected records are visible for review",
      "successfully imported journals are available for subsequent validation and posting"
    ],
    "scope_note": "This scenario validates the outcome of an import as observed through the Oracle Fusion UI — the resulting journal, its data and its validation/error state. It does not claim to test or control the underlying file transfer, interface mechanics or API integration itself, and does not claim that the imported journal has been validated or posted — those are separate downstream test cases."
  },
  "preconditions": [
    "Oracle Fusion General Ledger is configured and available.",
    "A configured import source or interface is available for the target ledger.",
    "A valid ledger exists and the target accounting period is open.",
    "A journal source is configured and enabled for import.",
    "Valid account combinations exist in the source data for successful scenarios.",
    "The test user has permission to run journal import and review import results.",
    "Import source data has been prepared or staged for the scenario being tested."
  ],
  "test_data": [
    {
      "field": "Import Source",
      "example": "${IMPORT_SOURCE}"
    },
    {
      "field": "Ledger",
      "example": "${LEDGER}"
    },
    {
      "field": "Accounting Period",
      "example": "${ACCOUNTING_PERIOD}"
    },
    {
      "field": "Journal Source",
      "example": "${JOURNAL_SOURCE}"
    },
    {
      "field": "Journal Category",
      "example": "${JOURNAL_CATEGORY}"
    },
    {
      "field": "Currency",
      "example": "${CURRENCY}"
    },
    {
      "field": "Batch Name",
      "example": "${BATCH_NAME}"
    },
    {
      "field": "Number of Journals in Batch",
      "example": "${JOURNAL_COUNT}"
    },
    {
      "field": "Account Combination",
      "example": "${ACCOUNT_COMBINATION}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign in to Oracle Fusion",
      "action": "Sign in to the Oracle Fusion environment using an authorised General Ledger test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion home page is displayed successfully and the user session is established.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to General Ledger > Journals",
      "action": "Navigate to the General Ledger Journals work area.",
      "test_data": "",
      "expected_result": "The Journals work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Initiate Journal Import",
      "action": "Open Tasks and initiate the journal import process.",
      "test_data": "",
      "expected_result": "The journal import submission page is displayed.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select Import Source / Interface",
      "action": "Select the configured import source or interface to be used for this run.",
      "test_data": "${IMPORT_SOURCE}",
      "expected_result": "The selected import source is accepted for the run.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select Ledger and Period",
      "action": "Select the target ledger and the accounting period the imported journals should apply to.",
      "test_data": "${LEDGER}, ${ACCOUNTING_PERIOD}",
      "expected_result": "Ledger and period are accepted and consistent with the import source.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit the Import Process",
      "action": "Submit the journal import process for the selected source, ledger and period.",
      "test_data": "",
      "expected_result": "The import process is submitted successfully and a process instance is generated.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Monitor Import Process Status",
      "action": "Monitor the submitted import process until it reaches a completed or ended status.",
      "test_data": "",
      "expected_result": "The process reaches a final status (for example, succeeded, succeeded with warnings, or error) without remaining indefinitely in a running state.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Review Import Results / Log",
      "action": "Open the import process results or log for the completed run.",
      "test_data": "",
      "expected_result": "The import log or results output is available and identifies the number of journals processed, rejected or excepted.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the process monitor, locating the process by name, and opening its output/log files."
    },
    {
      "step_number": 9,
      "step_name": "Locate the Imported Journal(s)",
      "action": "Search for and open the journal batch produced by the import run.",
      "test_data": "${BATCH_NAME}",
      "expected_result": "The imported journal batch is located and matches the expected journal source, category and period.",
      "validation_type": "action"
    },
    {
      "step_number": 10,
      "step_name": "Review Imported Journal Header and Lines",
      "action": "Review the journal header and line detail for a representative imported journal.",
      "test_data": "",
      "expected_result": "Journal header and line detail reflect the source data, including account combinations, amounts and currency.",
      "validation_type": "action"
    },
    {
      "step_number": 11,
      "step_name": "Review Import Exceptions Where Present",
      "action": "For scenarios involving invalid or incomplete source data, review any import exception, rejection or error detail recorded for the run.",
      "test_data": "",
      "expected_result": "Import exceptions correctly identify the affected records and the reason for exclusion, and valid records within the same batch are unaffected.",
      "validation_type": "action"
    },
    {
      "step_number": 12,
      "step_name": "Validate Imported Journal Status",
      "action": "Confirm the final status of the imported journal(s) or the recorded import exception.",
      "test_data": "",
      "expected_result": "Valid source data results in journal(s) available for subsequent validation and posting; invalid or incomplete source data results in the expected import exception rather than a silently incorrect journal.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — the test does not stop merely because the import process completed."
    }
  ],
  "expected_results": [
    "Oracle Fusion successfully imports valid journal data into new journal(s) with the expected header and line detail.",
    "Imported journal batch, journal source and journal category match the import run configuration.",
    "Ledger, period, currency and account combinations on imported journals reflect the source data.",
    "Invalid or incomplete source data produces the expected import exception rather than a silently incorrect journal.",
    "Import exceptions identify the affected records and the reason for exclusion.",
    "Valid records within a batch that also contains exceptions are imported correctly and are not blocked by unrelated errors.",
    "Successfully imported journals are available for subsequent validation and posting scenarios."
  ],
  "validation_checkpoints": [
    "Import source / interface selection is correct.",
    "Ledger and accounting period are correct.",
    "Import process reaches a final status.",
    "Journal batch name matches the import run.",
    "Journal source and journal category are correctly recorded.",
    "Imported journal header and line detail match source data.",
    "Account combinations on imported lines are valid.",
    "Currency on imported journals is correct.",
    "Import exceptions are raised for invalid or incomplete records.",
    "Valid records are unaffected by unrelated exceptions in the same batch.",
    "Imported journal is available for downstream validation and posting.",
    "Captured batch name/identifier can be used by subsequent automated scenarios."
  ]
}