{
  "test_id": "ORCL.REGRESSION.R2R",
  "scenario_name": "R2R Regression Pack",
  "application": "Oracle Fusion Cloud",
  "product": "Regression",
  "module": "Regression",
  "process": "R2R Regression",
  "business_flow": "R2R Regression Pack",
  "scenario_type": "Regression Pack / Composition",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Regression Pack",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/regression-packs/r2r-regression/",
  "objective": {
    "intro": "The objective of this regression pack is to compose 18 high-risk, high-frequency Record-to-Report scenarios — spanning GL Journals, Intercompany, Fixed Assets and Cash Management, plus ledger security — into one referenced, schedulable pack, with emphasis on journal transactions correctly posting to the ledger and subledger balances correctly reconciling through to the General Ledger, rather than re-testing each scenario's individual field-level validation, which is already covered on the linked GL Journals, Intercompany, Fixed Assets, Bank Statements, Data Role Security, AP Payments and AR Receipts family pages this pack orchestrates.",
    "confirms": [
      "the referenced GL Journals, Intercompany, Fixed Assets, Bank Statements, Data Role Security, AP Payments and AR Receipts family scenarios remain individually functional in the target Oracle Fusion environment",
      "manual and imported journals correctly pass approval and correctly post to the ledger",
      "intercompany transactions correctly balance across the initiating and receiving legal entities before posting to GL",
      "fixed asset accounting entries correctly transfer through to the General Ledger",
      "cash accounting entries from bank transactions correctly transfer through to the General Ledger",
      "unbalanced journals and invalid account combinations are correctly rejected rather than silently accepted",
      "closed-period posting attempts are correctly blocked rather than silently accepted",
      "ledger security correctly restricts journal and posting actions to authorized personas",
      "subledger-to-GL reconciliation is correctly available where the target environment supports it"
    ],
    "scope_note": "This pack validates the composition, scheduling and cross-area accounting continuity of the R2R Regression scenario set in Oracle Fusion TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the GL Journals, Intercompany, Fixed Assets, Bank Statements, Data Role Security, AP Payments and AR Receipts family pages — this page references and orchestrates those live pages into a schedulable regression pack."
  },
  "preconditions": [
    "The GL Journals, Intercompany, Fixed Assets, Bank Statements, Data Role Security, AP Payments and AR Receipts family pages referenced by this pack are individually functional in the target Oracle Fusion environment.",
    "A valid ledger, business unit and chart of accounts are configured and available for journal, intercompany, fixed asset and cash accounting transactions.",
    "The test user holds the roles required to execute each referenced scenario, or alternate unauthorized-user personas are available for security testing.",
    "The current accounting period is open for the ledgers under test, with at least one prior period available closed for closed-period validation.",
    "Ledger security, journal approval hierarchies and account combination rules are configured according to the target environment — this pack does not assume a single universal configuration applies to every ledger."
  ],
  "test_data": [
    {
      "field": "Ledger",
      "example": "${LEDGER}"
    },
    {
      "field": "Journal",
      "example": "${JOURNAL}"
    },
    {
      "field": "Journal Batch",
      "example": "${JOURNAL_BATCH}"
    },
    {
      "field": "Business Unit",
      "example": "${BUSINESS_UNIT}"
    },
    {
      "field": "Legal Entity",
      "example": "${LEGAL_ENTITY}"
    },
    {
      "field": "Intercompany Transaction",
      "example": "${INTERCOMPANY_TRANSACTION}"
    },
    {
      "field": "Asset",
      "example": "${ASSET}"
    },
    {
      "field": "Bank Account",
      "example": "${BANK_ACCOUNT}"
    },
    {
      "field": "Account Combination",
      "example": "${ACCOUNT_COMBINATION}"
    },
    {
      "field": "GL Date",
      "example": "${GL_DATE}"
    },
    {
      "field": "Accounting Period",
      "example": "${ACCOUNTING_PERIOD}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Confirm Referenced Family Scenarios Are Available",
      "action": "Confirm the GL Journals, Intercompany, Fixed Assets, Bank Statements, Data Role Security, AP Payments and AR Receipts family pages are individually functional in the target environment before running the pack.",
      "test_data": "${LEDGER} / ${BUSINESS_UNIT}",
      "expected_result": "Each referenced family scenario is confirmed available and ready to execute as part of the pack.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Execute Journals Critical Scenarios",
      "action": "Run REG-R2R-001 through REG-R2R-006, referencing the standard GL Journals family scenarios for manual entry, import, approval, posting, reversal and correction.",
      "test_data": "${JOURNAL} / ${LEDGER} / ${GL_DATE}",
      "expected_result": "Manual journal creation, import, approval, posting, reversal and correction scenarios correctly complete and correctly reflect the ledger balance.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Execute Intercompany and Subledger-to-GL Scenarios",
      "action": "Run REG-R2R-007 through REG-R2R-009, referencing the standard Intercompany, AP Payments and AR Receipts family scenarios for intercompany accounting and subledger accounting transfer to GL.",
      "test_data": "${INTERCOMPANY_TRANSACTION} / ${LEGAL_ENTITY} / ${JOURNAL}",
      "expected_result": "Intercompany transactions correctly balance across legal entities, and AP and AR subledger accounting entries correctly transfer through to the General Ledger.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Execute Fixed Assets and Cash Accounting Scenarios",
      "action": "Run REG-R2R-010 and REG-R2R-011, referencing the standard Fixed Assets and Bank Statements family scenarios for asset accounting and cash accounting.",
      "test_data": "${ASSET} / ${BANK_ACCOUNT} / ${GL_DATE}",
      "expected_result": "Fixed asset and cash accounting entries correctly create the expected journal lines in the General Ledger.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Execute Negative and Ledger Security Scenarios",
      "action": "Run REG-R2R-012 through REG-R2R-015, referencing the standard GL Journals and Data Role Security family scenarios for unbalanced journal, invalid account combination, closed-period and ledger security validation.",
      "test_data": "${ACCOUNT_COMBINATION} / ${ACCOUNTING_PERIOD} / ${LEDGER}",
      "expected_result": "Unbalanced journal, invalid account combination, closed-period and unauthorized ledger access attempts are correctly rejected or blocked rather than silently accepted.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Subledger-to-GL Traceability and Pack-Wide Result",
      "action": "Run REG-R2R-016 through REG-R2R-018, comparing subledger balances against the GL trial balance where available, confirming a representative period close smoke check, and reviewing the full pack result across all coverage areas.",
      "test_data": "${LEDGER} / ${BUSINESS_UNIT} / ${ACCOUNTING_PERIOD}",
      "expected_result": "Subledger-to-GL reconciliation and period close smoke are correctly available where the target environment supports it, and the R2R end-to-end accounting continuity review correctly links each REG-R2R-### scenario back to its source family page and execution result.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the pack — correctly reconciled subledger-to-GL balances and a complete pack-wide traceability chain is the expected pass condition, not merely 18 individually successful transactions."
    }
  ],
  "expected_results": [
    "Manual journal, import, approval, posting, reversal and correction scenarios correctly complete across REG-R2R-001 through REG-R2R-006.",
    "Intercompany accounting and AP/AR subledger accounting transfer to GL scenarios correctly complete across REG-R2R-007 through REG-R2R-009.",
    "Fixed asset and cash accounting scenarios correctly complete across REG-R2R-010 and REG-R2R-011.",
    "Unbalanced journal, invalid account combination and closed-period validation scenarios (REG-R2R-012 through REG-R2R-014) are correctly rejected rather than silently accepted.",
    "Ledger security validation (REG-R2R-015) correctly restricts journal and posting actions to authorized personas.",
    "Subledger-to-GL reconciliation, period close smoke and R2R end-to-end accounting continuity (REG-R2R-016 through REG-R2R-018) are correctly available and correctly link each scenario back to its source family page."
  ],
  "validation_checkpoints": [
    "all 18 referenced REG-R2R-### scenarios correctly execute against their source family page definitions",
    "manual and imported journals correctly pass approval and correctly post to the ledger",
    "intercompany transactions correctly balance across legal entities before posting to GL",
    "fixed asset and cash accounting entries correctly transfer through to the General Ledger",
    "unbalanced journals and invalid account combinations are correctly rejected rather than silently accepted",
    "closed-period posting attempts are correctly blocked",
    "ledger security correctly restricts journal and posting actions to authorized personas",
    "subledger-to-GL reconciliation is correctly available where supported"
  ]
}