{ "test_id": "ORCL.O2C.AR.BILL.TXN.COMPLETE", "scenario_name": "Complete & Incomplete Transactions", "application": "Oracle Fusion Cloud", "product": "Receivables", "module": "Accounts Receivable", "process": "Billing", "business_flow": "Order-to-Cash", "scenario_type": "Positive / Negative / Functional", "priority": "High", "automation_status": "SyntraFlow Ready", "library": "Syntra Standard", "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/financials/accounts-receivable/billing/transaction-completion/", "objective": { "intro": "The objective of this test is to verify Oracle Receivables transaction completion, incompletion and prerequisite business rules — confirming that an authorised Receivables user can successfully complete a valid transaction, and that Oracle Fusion correctly blocks completion when required prerequisite data such as customer, accounting or transaction line information is missing or invalid.", "confirms": [ "the transaction date falls within an open accounting period", "a valid customer and customer site are associated with the transaction", "required accounting information is present and valid", "transaction lines are complete and internally consistent", "the transaction can be completed successfully when all prerequisite data is valid", "completion is correctly blocked when required customer, accounting, line or date data is missing or invalid", "the transaction's completion status accurately reflects the underlying data condition", "a transaction number is assigned and retained after successful completion" ], "scope_note": "This scenario focuses on the completion/incompletion decision itself and the prerequisite business rules that govern it — it does not claim to validate downstream transaction accounting, receipt application or revenue recognition, which are covered by separate test cases." }, "preconditions": [ "Oracle Fusion Receivables is configured and available.", "The test user has permission to complete Receivables transactions.", "A valid draft/incomplete transaction exists and is ready for completion.", "Customer exists, is active, and has the required data configured.", "Customer site is active and valid for the transaction.", "Accounting period is open for the transaction date.", "A valid account combination is available for accounting.", "All mandatory transaction header and line fields are populated (for the positive completion path)." ], "test_data": [ { "field": "Transaction", "example": "Draft/incomplete transaction ready for completion" }, { "field": "Customer Information", "example": "Complete and valid" }, { "field": "Accounting Information", "example": "Valid account combination" }, { "field": "Accounting Period", "example": "Open" }, { "field": "Transaction Date", "example": "Valid/open-period date" }, { "field": "Missing Field Scenario", "example": "Scenario-defined — e.g. missing customer or accounting information for negative cases" } ], "business_steps": [ { "step_number": 1, "step_name": "Sign in to Oracle Fusion", "action": "Sign in to the Oracle Fusion environment using an authorised Receivables 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 Receivables", "action": "Open the Navigator and navigate to the Receivables work area.", "test_data": "", "expected_result": "The Receivables work area opens successfully.", "validation_type": "action" }, { "step_number": 3, "step_name": "Open Billing", "action": "Open the Billing task within Receivables and access the transactions list.", "test_data": "", "expected_result": "The Billing transactions list is displayed.", "validation_type": "action" }, { "step_number": 4, "step_name": "Locate the Draft/Incomplete Transaction", "action": "Search for and open the draft or incomplete transaction identified for completion testing.", "test_data": "${TRANSACTION_NUMBER}", "expected_result": "The correct transaction is located and opened.", "validation_type": "action", "note": "This single business step replaces multiple technical actions such as opening search, entering the transaction number, clicking Search and selecting the result." }, { "step_number": 5, "step_name": "Review Transaction Header and Line Data", "action": "Review the transaction date, customer, customer site, accounting information and transaction lines.", "test_data": "", "expected_result": "Transaction header and line data are displayed and available for review.", "validation_type": "action" }, { "step_number": 6, "step_name": "Verify Required Fields Are Populated", "action": "Confirm whether fields required for completion — transaction date, customer, customer site, accounting information and transaction lines — are populated as defined for this scenario.", "test_data": "", "expected_result": "Required fields are populated as defined for the scenario — complete for positive cases, intentionally missing or invalid for negative cases.", "validation_type": "action" }, { "step_number": 7, "step_name": "Attempt Transaction Completion", "action": "Select Complete on the transaction.", "test_data": "", "expected_result": "Oracle Fusion processes the completion request.", "validation_type": "action" }, { "step_number": 8, "step_name": "Validate Completion Business Rules", "action": "Allow Oracle to evaluate prerequisite completion business rules — accounting period status, customer and customer site validity, accounting information and transaction line completeness.", "test_data": "", "expected_result": "Oracle correctly applies completion business rules based on the data present on the transaction.", "validation_type": "business_assertion", "note": "This is a core business assertion — the scenario evaluates whether Oracle's rule evaluation matches the expected outcome for the data provided, not merely whether the Complete action was clicked." }, { "step_number": 9, "step_name": "Review Completion Status", "action": "Review the resulting transaction status after the completion attempt.", "test_data": "", "expected_result": "For valid, complete data the transaction status changes to Complete. For missing or invalid prerequisite data the transaction remains Incomplete.", "validation_type": "business_assertion" }, { "step_number": 10, "step_name": "Review the Exception/Error Reason (If Incomplete)", "action": "Where completion is blocked, review the exception or error message returned by Oracle.", "test_data": "", "expected_result": "The exception/error reason correctly identifies the missing or invalid prerequisite data.", "validation_type": "action" }, { "step_number": 11, "step_name": "Correct Missing/Invalid Data Where Applicable", "action": "For scenarios that require it, correct the missing or invalid field identified in the exception.", "test_data": "${CORRECTED_FIELD_VALUE}", "expected_result": "The corrected field value is accepted.", "validation_type": "action" }, { "step_number": 12, "step_name": "Re-Attempt Completion", "action": "Select Complete again after correcting the data.", "test_data": "", "expected_result": "Oracle Fusion re-processes the completion request.", "validation_type": "action" }, { "step_number": 13, "step_name": "Validate Final Transaction Status", "action": "Confirm the final transaction status following the completion attempt(s).", "test_data": "", "expected_result": "The final status matches the expected outcome for the scenario — Complete for corrected/valid data, Incomplete where the scenario intentionally leaves prerequisite data missing or invalid.", "validation_type": "business_assertion" }, { "step_number": 14, "step_name": "Validate Transaction Number Assignment on Successful Completion", "action": "Where the transaction completes successfully, confirm the transaction number is assigned or retained.", "test_data": "", "expected_result": "The transaction number is available and can be used by subsequent scenarios.", "validation_type": "business_assertion", "note": "This is the main business assertion for the positive completion path — the test does not stop merely because Complete was clicked without error." } ], "expected_results": [ "Oracle Fusion successfully completes a transaction when all required, valid prerequisite data is present and assigns/retains the transaction number.", "Attempts to complete a transaction with missing or invalid customer, accounting, transaction line or date data are correctly blocked with an appropriate exception.", "The transaction's completion status accurately reflects the underlying data condition.", "Correcting the missing or invalid data and re-attempting completion succeeds.", "No unexpected application errors occur during completion or blocked-completion scenarios.", "Completed transactions are available for subsequent accounting and downstream Order-to-Cash processing." ], "validation_checkpoints": [ "Transaction date falls within an open accounting period.", "Customer and customer site are valid and active.", "Accounting information is present and valid.", "Transaction lines are complete and consistent.", "Completion is accepted only when prerequisite rules are satisfied.", "Exception/error message correctly identifies the missing or invalid data.", "Completion status accurately reflects the outcome.", "Transaction number is assigned/retained on successful completion.", "Corrected transactions can be successfully re-completed.", "Incomplete transactions remain in Draft/Incomplete status until corrected." ] }