Oracle Fusion Partial Completion Test Cases
Validate multiple sequential partial completion transactions against a single work order in Oracle Fusion SCM Manufacturing, including correct tracking of remaining open quantity across transactions, without assuming a fixed number of partial completions is permitted.
| Test ID | ORCL.SCM.MFG.COMP.PARTIAL |
| Application | Oracle Fusion Cloud |
| Product | SCM |
| Module | Manufacturing |
| Process | Partial Completion |
| Business Flow | Plan-to-Produce |
| Scenario Type | Positive / Functional |
| Test Usage | Functional Testing / Regression Testing / UAT |
| Priority | High |
| Automation | SyntraFlow Ready |
| Library | Syntra Standard |
Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 6 business-readable test steps; SyntraFlow's automation executes approximately 13 underlying Oracle Fusion UI actions to complete it.
Test Objective
The objective of this test is to validate multiple sequential partial completion transactions recorded against a single work order in Oracle Fusion SCM Manufacturing, including correct tracking of the remaining open quantity across transactions.
The scenario should confirm that:
- a first partial completion transaction against a work order with an open remaining quantity correctly reduces that remaining quantity
- a second and subsequent sequential partial completion correctly accumulates toward the total work order quantity
- partial completions recorded across different dates and against different lot numbers are correctly tracked
- the remaining open quantity is correctly reported after each partial completion transaction
- a final partial completion that consumes the remaining balance correctly reflects the work order's completed status
- Oracle correctly enforces validation and security restrictions when a completion quantity exceeds the remaining open quantity or an unauthorized user attempts the transaction (EXPECTED_VALIDATION, SECURITY_ERROR)
This scenario covers sequential partial completion transactions against a single work order in Oracle Fusion SCM Manufacturing TEST/UAT environments. The number of partial completions a work order may receive before it is fully completed is governed by customer-specific manufacturing organization parameters and work definition setup — this scenario does not assume a fixed number of partial completions is permitted across Oracle Fusion implementations. It does not cover completion of a work order in a single transaction, scrap quantity recording, or work order closure, which are covered by the separate Complete Work Order, Scrap Quantity and Close Work Order scenarios in the same Manufacturing test library.
When to Use This Test
- Functional testing of sequential partial completion transactions for a new Oracle Fusion SCM Manufacturing implementation
- Regression testing of remaining-open-quantity tracking after an Oracle quarterly update
- UAT sign-off for production operators and supervisors who record partial completions across multiple shifts or days
- Validating that a completion quantity exceeding the remaining open quantity is correctly blocked or flagged
- Diagnosing EXPECTED_VALIDATION and SECURITY_ERROR conditions surfaced during partial completion before escalating as a possible APPLICATION_ERROR
Where This Test Fits in the Manufacturing Completions Process
Partial Completion is the second scenario in the Completions family within Plan-to-Produce, following single-transaction Complete Work Order and preceding Scrap Quantity. Exact partial completion behavior, the number of partial completions permitted, and remaining-quantity tracking depend on manufacturing organization parameters, work definition setup and customer-specific Oracle Fusion configuration.
Preconditions
- The work order exists in Oracle Fusion SCM Manufacturing with a status eligible for completion and has an open remaining quantity.
- The work order quantity, quantity already completed, and remaining open quantity are known before each partial completion transaction.
- Where required by the item or work definition, a valid lot number is available for the partial completion transaction.
- The test user has appropriate access to record partial completions for the manufacturing organization.
- For sequential scenarios, prior partial completion transactions have been recorded against the same work order.
Exact field availability, the number of partial completions permitted before a work order is considered fully completed, and remaining-quantity tracking behavior may vary by Oracle Fusion implementation, manufacturing organization parameters, work definition setup and customer-specific configuration. This scenario does not assume a fixed number of partial completions is permitted.
Sample Test Data
| Work Order | ${WORK_ORDER} |
| Work Order Quantity | ${WORK_ORDER_QUANTITY} |
| Completed Quantity | ${COMPLETED_QUANTITY} |
| Remaining Quantity | ${REMAINING_QUANTITY} |
| Lot | ${LOT} |
| Completion Date | ${COMPLETION_DATE} |
Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. The number of partial completions permitted and remaining-quantity tracking behavior depend on manufacturing organization configuration.
Test Steps
6 business-readable steps. SyntraFlow's automation executes ~13 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Sign In and Navigate to Manufacturing Sign in to Oracle Fusion using an authorised manufacturing test user and navigate to the Manufacturing work area. | The Manufacturing work area opens successfully. |
| 2 | Navigate to the Work Order Open the work order with an open remaining quantity from the work order list. ${WORK_ORDER} | The work order details page opens showing the work order quantity, completed quantity and remaining open quantity. |
| 3 | Enter the Partial Completion Quantity and Lot Enter the quantity to complete in this transaction, and the lot number where required by the item or work definition. ${COMPLETED_QUANTITY} / ${LOT} This single business step replaces multiple technical actions such as opening the completion transaction, entering the quantity field and selecting the lot. | The partial completion quantity and lot are accepted for the transaction, or the expected blocking condition is confirmed for negative scenarios. |
| 4 | Submit the Transaction Submit the partial completion transaction. ${COMPLETION_DATE} | Oracle Fusion successfully processes the partial completion transaction without unexpected errors, or correctly returns a blocking validation for negative scenarios. |
| 5 | Verify the Remaining Open Quantity Updates CorrectlyBusiness assertion Reopen or refresh the work order and confirm the remaining open quantity after the transaction. ${REMAINING_QUANTITY} This is the primary business assertion for the scenario — the remaining open quantity correctly updating after each partial completion is the expected pass condition, not merely a successful save. | The remaining open quantity correctly reflects the total work order quantity less all completed quantity recorded to date. |
| 6 | Repeat Until the Work Order Is Fully CompletedBusiness assertion Repeat the partial completion transaction for subsequent quantities, dates and lots as applicable, until the work order's remaining open quantity reaches zero. ${WORK_ORDER} | Sequential partial completions correctly accumulate toward the total work order quantity, and the final partial completion correctly closes out the remaining balance. |
Expected Results
- Each partial completion correctly reduces the remaining open work order quantity.
- Sequential partial completions correctly accumulate toward the total work order quantity.
- Partial completions recorded against different lots are correctly tracked as separate transactions.
- A final partial completion correctly closes out the remaining balance.
- A completion quantity exceeding the remaining open quantity is correctly blocked or flagged.
- Unauthorized partial completion is correctly blocked.
Key Validation Checkpoints
- Each partial completion correctly reduces the remaining open work order quantity.
- Sequential completions correctly accumulate toward the total work order quantity.
- Different lots correctly tracked across separate partial completions.
- Final partial completion correctly closes out the remaining balance.
- Over-completion beyond the remaining open quantity correctly blocked or flagged.
- Unauthorized partial completion correctly blocked.
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core Partial Completion business scenario. Jarvis AI can extend this scenario by generating additional sequence, lot, date, remaining-quantity and security variations using customer-specific test data and configuration available through Syntra DataVault.
Teams do not need to manually build a separate test for every partial completion sequence, lot combination or remaining-quantity scenario. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment — including over-completion attempts and unauthorized partial completion, since correctly enforced validation and security across a sequence of transactions is an important part of what this scenario proves.
From Standard Test to Executed Regression Pack
Rather than maintaining a separate test page for every possible partial completion sequence, lot combination, completion date or remaining-quantity condition, SyntraFlow maintains one core Partial Completion scenario and allows Jarvis AI to generate sequence, quantity and security-specific variations using the customer's available test data.
AI-Generated Test Variations
The same Partial Completion business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to SCM Manufacturing.
- Record the first partial completion against a work order with an open remaining quantity
- Record a second sequential partial completion that correctly accumulates toward the total work order quantity
- Record partial completions across different dates and lot numbers
- Verify the remaining open quantity updates correctly after each partial completion
- Record a final partial completion that closes out the remaining balance
- Attempt a partial completion with a quantity exceeding the remaining open quantity
- Attempt an unauthorized partial completion by a user without the required access
These are representative examples only. Negative-scenario behavior, available field combinations and the number of partial completions permitted can depend on the customer's Oracle Fusion configuration, controls and security — not every Oracle configuration behaves identically.
Generated Using Your DataVault Test Data
Generic test data rarely represents every work order quantity, completion sequence, lot and date combination in a real Oracle Fusion SCM Manufacturing environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Partial Completion scenarios relevant to the customer's actual implementation.
Standard Library Definition
Work Order ${WORK_ORDER}
Work Order Quantity ${WORK_ORDER_QUANTITY}
Completed Quantity ${COMPLETED_QUANTITY}
Remaining Quantity ${REMAINING_QUANTITY}
Lot ${LOT}
Completion Date ${COMPLETION_DATE}
DataVault
Work Orders Eligible work orders with open remaining quantity, by manufacturing organization Quantities Work order, completed and remaining quantity per transaction Lots Valid lot numbers per item and work definition Completion Dates Valid transaction dates per manufacturing calendar
Jarvis AI Generates
Scenario 01 — First Partial Completion Scenario 02 — Second Sequential Partial Completion Scenario 03 — Partial Completions Across Different Days Scenario 04 — Partial Completion with Different Lots Scenario 05 — Final Partial Completion Closes Remaining Quantity Scenario 06 — Over-Completion Beyond Remaining Quantity ...
Partial Completion test data can include sensitive manufacturing categories such as work order quantity, lot and completion date information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific manufacturing dimensions remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/data-masking/ for details.
Example Test Variations
8 individual Partial Completion test scenarios spanning sequential partial completion transactions, remaining-quantity tracking and negative/security partial-completion testing. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| MFG-PART-001 | First Partial Completion | Positive | A first partial completion of ${COMPLETED_QUANTITY} is recorded against work order ${WORK_ORDER} with total quantity ${WORK_ORDER_QUANTITY}, and the remaining open quantity correctly reduces. | SyntraFlow Ready |
| MFG-PART-002 | Second Sequential Partial Completion | Positive | A second partial completion is recorded against work order ${WORK_ORDER} following the first, and correctly accumulates toward the total work order quantity. | SyntraFlow Ready |
| MFG-PART-003 | Multiple Partial Completions Across Different Days | Positive | Sequential partial completions are recorded against work order ${WORK_ORDER} on different values of ${COMPLETION_DATE}, and each is correctly tracked. | SyntraFlow Ready |
| MFG-PART-004 | Partial Completion with Different Lot Numbers | Positive | Partial completions are recorded against work order ${WORK_ORDER} using different values of ${LOT}, and each lot is correctly tracked as a separate transaction. | SyntraFlow Ready |
| MFG-PART-005 | Verify Remaining Open Quantity After Partial | Positive | After a partial completion, the remaining open quantity ${REMAINING_QUANTITY} for work order ${WORK_ORDER} is retrieved and confirmed correct. | SyntraFlow Ready |
| MFG-PART-006 | Final Partial Completion Closes Remaining Quantity | Positive | A final partial completion consuming the remaining balance ${REMAINING_QUANTITY} of work order ${WORK_ORDER} is recorded, and the work order correctly reflects full completion. | SyntraFlow Ready |
| MFG-PART-007 | Partial Completion Exceeding Remaining Open Quantity | Negative/Boundary | A partial completion quantity exceeding remaining open quantity ${REMAINING_QUANTITY} for work order ${WORK_ORDER} is attempted and correctly blocked or flagged. | SyntraFlow Ready |
| MFG-PART-008 | Unauthorized Partial Completion | Negative/Security | A user with role ${USER_ROLE} lacking completion privileges attempts to record a partial completion against work order ${WORK_ORDER} and is correctly denied. | SyntraFlow Ready |
No variations match this filter.
Automatically Expand Positive and Negative Partial Completion Coverage
Positive Testing
Jarvis generates scenarios using work order, quantity, lot and date combinations expected to be recorded successfully as sequential partial completions in Oracle Fusion Manufacturing.
Valid Work Order + Completion Quantity Within Remaining Balance + Valid Lot → Partial Completion Recorded
Negative Testing
Jarvis can also generate scenarios designed to exercise Oracle's validations around remaining-quantity limits and partial completion security.
- Completion Quantity Exceeds Remaining Open Quantity → Expected Status Validation
- Unauthorized User → Expected Access Restriction
A negative manufacturing scenario passes when Oracle correctly enforces the expected data, configuration or security rule
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Valid work order data | Work order created | PASS |
| Invalid item or work definition | Validation occurs | PASS |
| Component shortage | Validation or warning occurs | PASS |
| Unauthorized user | Access prevented | PASS |
| Unexpected application exception | Unexpected failure | FAIL |
Turn AI-Generated Variations into a Regression Pack
Users can select generated Partial Completion scenarios and group them into reusable execution packs.
SCM Manufacturing Partial Completion Regression Pack
- First Partial Completion
- Second Sequential Partial Completion
- Multiple Partial Completions Across Different Days
- Partial Completion with Different Lot Numbers
- Verify Remaining Open Quantity After Partial
- Final Partial Completion Closes Remaining Quantity
- Partial Completion Exceeding Remaining Open Quantity
- Unauthorized Partial Completion
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected Partial Completion scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected Partial Completion scenarios unattended and records the outcome of each test and business assertion.
| Pack | SCM Manufacturing Partial Completion Regression Pack |
| Schedule | Quarterly Update Regression |
| Tests | 8 scenarios |
| Execution | Batch Mode |
| Start | 10:00 PM |
| Environment | Oracle Fusion TEST |
| Status | Scheduled |
Illustrative example — not a live schedule.
Review Results Across the Entire Test Pack
Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.
Illustrative example data — not actual production metrics.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
Security & Partial Completion Variations
Access to record partial completions for a given manufacturing organization is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that partial completion access behaves as expected for each role — not to assert a single universal Oracle security model.
| Persona | Action | Expected | Syntra Result |
|---|---|---|---|
| Production Operator | Record Partial Completion | Allowed | PASS |
| Production Supervisor | Close Remaining Quantity via Final Partial | Allowed | PASS |
| Unauthorized User | Attempts to Record Partial Completion | Access prevented | PASS |
Understand Why a Test Failed
SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.
From Business Scenario to Execution Evidence
Business teams get readable test documentation; automation teams retain detailed execution traceability.
Meet Jarvis — SyntraFlow's AI Testing Engine
Jarvis extends the Syntra Standard Test Library by analysing the Partial Completion scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Security coverage for the customer's environment.
How SyntraFlow Automates This Test
The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
Action Status vs. Business Validation
A successful UI interaction does not automatically prove the remaining open quantity was tracked correctly — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. When a step fails, SyntraFlow's evidence trail is designed to help a tester classify the likely cause across eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Partial Completion Failed — Likely category: EXPECTED_VALIDATION — Evidence: Completion quantity exceeds remaining open quantity ${REMAINING_QUANTITY} — Recommendation: Confirm completion quantity does not exceed the remaining open balance. A failure should never be labeled as an Oracle defect without eliminating data, configuration, security, automation and integration causes first.
| Step | Action Status | Business Validation |
|---|---|---|
| Enter the Partial Completion Quantity and Lot | Pass | — |
| Submit the Transaction | Pass | — |
| Verify the Remaining Open Quantity Updates Correctly | Pass | Pass |
Related Manufacturing Tests
Partial Completion sits within the Completions cluster alongside single-transaction completion and scrap recording — explore the related scenarios below.
Turn This Standard Test into Your Oracle SCM Partial Completion Regression Suite
Start with the Syntra Standard Partial Completion test, use DataVault to provide environment-specific test data, let Jarvis generate additional sequence, lot, remaining-quantity and security variations, and execute the resulting regression pack automatically with SyntraFlow.
Use This Oracle Fusion Test Case
Download Test Case
Excel, CSV or JSON export.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.