{ "test_id": "ORCL.P2P.AP.INV.DISTRIBUTION", "scenario_name": "Invoice Distributions", "application": "Oracle Fusion Cloud", "product": "Financials", "module": "Accounts Payable", "process": "Invoice Processing", "business_flow": "Procure-to-Pay", "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/accounts-payable/invoice-processing/invoice-distributions/", "objective": { "intro": "This test case validates the creation and processing of accounting distributions associated with Oracle Fusion Payables invoice lines, confirming that a line's total amount is correctly and completely divided across valid account combinations before accounting.", "confirms": [ "A single invoice line can generate one or multiple accounting distributions", "Distribution amounts sum exactly to the parent invoice line amount with no variance", "Each distribution carries a valid, enabled, detail-postable account combination", "Cost center, balancing segment, and natural account segments combine correctly per the chart of accounts", "Project-related distributions carry valid project, task, and expenditure type values", "Distributions flagged for asset tracking are correctly identified for transfer to Fixed Assets", "Distribution accounting dates fall within an open or future-enterable GL period", "Distributions derived from a Distribution Set or PO match populate with correct default combinations", "Invalid, disabled, or mismatched distribution data is rejected during invoice validation" ], "scope_note": "Distribution mechanics \u2014 how one line's amount splits across accounts, cost centers, projects, and asset flags \u2014 are distinct from the overall Create Accounting process covered by the sibling Invoice Accounting test case, which validates the resulting journal entries and GL posting." }, "preconditions": [ "Oracle Fusion Payables invoice (standard or PO-matched) exists in Incomplete or Saved status with at least one invoice line", "Business unit is associated with a ledger and a valid chart of accounts structure", "Cross-validation rules and account combination security rules are configured for the chart of accounts", "Distribution Set, if used, is defined and assigned to the supplier site or invoice line", "Project, task, and expenditure type combinations are set up in Oracle Project Costing for project-related lines", "Asset category and corporate book are configured in Fixed Assets for asset-tracked lines", "GL period corresponding to the distribution accounting date is in Open or Future Enterable status", "User has Accounts Payable Invoice Entry, or an equivalent duty role, with distribution edit privileges", "Supplier site is not on an invoice or payment hold that would block distribution entry" ], "test_data": [ { "field": "Invoice Line Amount", "example": "12,500.00 USD" }, { "field": "Distribution Line 1 Amount", "example": "7,500.00 USD (60%)" }, { "field": "Distribution Line 2 Amount", "example": "5,000.00 USD (40%)" }, { "field": "Natural Account (Distribution 1)", "example": "71100 - Office Supplies Expense" }, { "field": "Natural Account (Distribution 2)", "example": "71150 - IT Equipment Expense" }, { "field": "Cost Center (Distribution 1)", "example": "4100 - Finance Dept" }, { "field": "Cost Center (Distribution 2)", "example": "4200 - IT Dept" }, { "field": "Balancing Segment (Company)", "example": "01 - US Operating Entity" }, { "field": "Project Number", "example": "PRJ-10045 - ERP Rollout Phase 2" }, { "field": "Task Number", "example": "1.2 - Testing & Validation" }, { "field": "Expenditure Type", "example": "Contract Labor" }, { "field": "Distribution Accounting Date", "example": "15-Mar-2026" } ], "business_steps": [ { "step_number": 1, "step_name": "Open Invoice Distributions", "action": "Open the invoice and navigate to the Lines tab, then expand Distributions for the selected invoice line.", "test_data": "", "expected_result": "Distributions region displays with existing or auto-generated distribution rows for the line.", "validation_type": "action" }, { "step_number": 2, "step_name": "Review Auto-Generated Distribution", "action": "Review the distribution line(s) automatically created from the PO match or the assigned Distribution Set.", "test_data": "Distribution Set: Standard Office Expense Split", "expected_result": "Auto-generated distribution reflects the source PO schedule or Distribution Set percentages.", "validation_type": "action" }, { "step_number": 3, "step_name": "Split Line into Multiple Distributions", "action": "Split the invoice line amount into two distributions by entering a specific amount or percentage for each.", "test_data": "Distribution 1: 7,500.00 USD (60%); Distribution 2: 5,000.00 USD (40%)", "expected_result": "Two distribution rows are created; combined amounts equal the invoice line total.", "validation_type": "action" }, { "step_number": 4, "step_name": "Enter Natural Account Segment", "action": "Enter the natural account segment for each distribution to identify the expense or asset classification.", "test_data": "71100 - Office Supplies Expense; 71150 - IT Equipment Expense", "expected_result": "Natural account segment is accepted and displayed on each distribution line.", "validation_type": "action" }, { "step_number": 5, "step_name": "Enter Cost Center Segment", "action": "Enter the cost center segment for each distribution to identify the responsible department.", "test_data": "4100 - Finance Dept; 4200 - IT Dept", "expected_result": "Cost center segment is accepted and combined with the natural account into a full combination.", "validation_type": "action" }, { "step_number": 6, "step_name": "Enter Balancing Segment", "action": "Confirm or enter the balancing segment (company/legal entity) for each distribution.", "test_data": "01 - US Operating Entity", "expected_result": "Balancing segment is valid for the invoice's ledger and legal entity.", "validation_type": "action" }, { "step_number": 7, "step_name": "Enter Project Distribution Details", "action": "For project-related distributions, enter the project, task, and expenditure type.", "test_data": "PRJ-10045; Task 1.2; Contract Labor", "expected_result": "Project, task, and expenditure type are accepted and pass Project Costing edit validation.", "validation_type": "action", "note": "Applies only to distributions tied to a capital or billable project." }, { "step_number": 8, "step_name": "Flag Distribution as Asset", "action": "Mark the distribution as Track as Asset and select the asset category where the cost is capitalizable.", "test_data": "Asset Category: IT Equipment - Computers", "expected_result": "Distribution is flagged for transfer to Fixed Assets Mass Additions after accounting.", "validation_type": "action", "note": "Applies only to asset-related distributions." }, { "step_number": 9, "step_name": "Set or Override Distribution Accounting Date", "action": "Confirm the default distribution accounting date or override it to prorate across periods.", "test_data": "15-Mar-2026", "expected_result": "Accounting date is accepted and falls within an open or future-enterable period.", "validation_type": "action" }, { "step_number": 10, "step_name": "Verify Distribution Total", "action": "Verify that the sum of all distribution amounts equals the invoice line amount before saving.", "test_data": "Line Amount: 12,500.00 USD", "expected_result": "Distribution total matches the line amount exactly; no variance is flagged.", "validation_type": "action" }, { "step_number": 11, "step_name": "Submit Invoice for Validation", "action": "Submit the invoice for validation to trigger Oracle's distribution and account combination edits.", "test_data": "", "expected_result": "Invoice validation engine checks each distribution's account combination, cross-validation rules, and total.", "validation_type": "action" }, { "step_number": 12, "step_name": "Confirm Distribution Readiness", "action": "Confirm the invoice reaches Validated status with all distributions correctly formed and ready for accounting.", "test_data": "", "expected_result": "All distributions carry valid, enabled account combinations; totals reconcile to each line; invoice is ready for Create Accounting.", "validation_type": "business_assertion" } ], "expected_results": [ "Distributions generated automatically from PO match reflect the PO shipment/distribution schedule", "Manually added distribution lines accept user-entered account segments", "Split distributions sum precisely to the invoice line amount with no rounding variance", "Distributions with invalid account combinations are rejected with a clear validation error", "Distributions referencing disabled accounts are blocked from saving or validation", "Distributions with mismatched totals prevent the invoice from reaching Validated status", "Project-related distributions correctly populate the interface used for cost import to Project Costing", "Asset-tracked distributions become eligible for Mass Additions after invoice accounting", "Distributions dated in a closed period are rejected or require accounting date correction", "Successfully validated distributions are ready for the Create Accounting process without further correction" ], "validation_checkpoints": [ "Distribution total equals invoice line amount exactly, with no variance", "Each distribution account combination exists and is enabled in the chart of accounts", "Account combination is a valid, detail (non-summary) posting combination", "Combination passes all applicable cross-validation rules", "Balancing segment value is valid for the invoice's ledger and legal entity", "Cost center segment maps to an active department", "Project, task, and expenditure type values, where present, are valid and open for charging", "Asset flag, when set, is paired with a valid asset category", "Distribution accounting date falls within an open or future-enterable period", "Distribution accounting date defaults correctly from the invoice or line unless explicitly overridden", "Number of distribution lines matches the expected split (manual, Distribution Set, or PO-derived)", "Invoice validation status reflects success or failure consistent with distribution data quality" ] }