Oracle Fusion Make-to-Order Test Scenarios
Validate the complete Make-to-Order journey in Oracle Fusion SCM — customer order, demand, planning, work order, manufacture, finished goods, reserve, pick, ship, AR billing and customer receipt — with emphasis on customer demand correctly driving and reconciling against production output across Order Management, Supply Planning, Manufacturing and Financials AR, orchestrating rather than duplicating the individual family pages this journey links to.
| Test ID | ORCL.E2E.MTO |
| Application | Oracle Fusion Cloud |
| Product | SCM |
| Module | End-to-End SCM |
| Process | Make-to-Order |
| Business Flow | Plan-to-Produce |
| Scenario Type | End-to-End / Functional |
| Test Usage | Functional Testing / Regression Testing / UAT |
| Priority | High |
| Automation | SyntraFlow Ready |
| Library | Syntra Standard Journey |
Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions across each Order Management, Supply Planning, Manufacturing and Financials AR family page automatically while presenting the journey as business-readable test steps for documentation, review and reporting. This scenario is presented as 9 business-readable test steps; SyntraFlow's automation executes approximately 156 underlying Oracle Fusion UI actions to complete it.
Test Objective
Validate the complete Make-to-Order journey — customer order, demand, planning, work order, manufacture, finished goods, reserve, pick, ship, AR billing and customer receipt — with emphasis on customer demand correctly driving and reconciling against production output across Order Management, Supply Planning, Manufacturing and Financials AR, rather than re-testing each stage's atomic validation already covered on the linked family pages this scenario orchestrates.
The scenario should confirm that:
- the sales order demand for a make-to-order item correctly flows through supply planning to generate a linked, released work order with matching quantity
- production completion correctly triggers reservation against the specific originating sales order
- pick release and shipment correctly consume the completed, reserved production quantity
- AR billing correctly reflects the shipped quantity tied back to the originating sales order
- the customer receipt correctly applies against the AR transaction, reducing the open balance
- a sales order cancellation after work order creation correctly flags the resulting orphaned work order
- unauthorized users are correctly blocked from completing a make-to-order work order without the production role
This scenario validates the hand-offs and cross-module data integrity of the Make-to-Order journey in Oracle Fusion SCM TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the 18 linked family pages across Order Management, Supply Planning, Manufacturing and Financials AR — this page links to and orchestrates those live pages into the broadest cross-module journey on the site.
When to Use This Test
- Regression testing that customer sales order demand for a make-to-order item correctly drives demand, planning, a linked work order, production completion, reservation, pick, shipment, AR billing and customer receipt across four Oracle Fusion pillars
- Validating hand-offs across the 18 linked family pages spanning Order Management, Supply Planning, Manufacturing and Financials AR, rather than re-testing each page's individual field-level scenarios
- UAT sign-off for order management, planning, manufacturing and billing teams who need confidence the full demand-to-production-to-billing-to-receipt journey works end-to-end, not just each transaction in isolation
- Diagnosing cross-module data mismatches, orphaned work orders, reservation shortfalls or billing discrepancies before escalating as a possible APPLICATION_ERROR
- Baseline orchestration scenario representing the broadest cross-module journey on the site, connecting Order Management, Supply Planning, Manufacturing and Financials AR
The Make-to-Order Journey
This Make-to-Order scenario spans the broadest cross-module journey on the site within the broader Plan-to-Produce business flow, orchestrating 18 linked family pages across Order Management, Supply Planning, Manufacturing and Financials AR rather than duplicating their individual scenario coverage.
Preconditions
- The Order Management, Supply Planning, Manufacturing and Financials AR family pages referenced by this journey are individually functional in the target Oracle Fusion SCM environment.
- A valid make-to-order item, customer, work definition, manufacturing organization and supply plan are available and enabled for sales, planning, production and billing.
- Work order auto-creation or manual linkage from the sales order via supply planning is configured for the test user's business unit.
- The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.
- Reservation rules, production completion tolerances, pick/ship configuration and AR transaction type setup are configured according to the target environment — this scenario does not assume a universal configuration.
Exact demand-to-work-order linkage configuration, reservation rules, production completion tolerances, pick/ship rules and AR transaction setup vary by Oracle Fusion implementation and customer-specific configuration. This scenario validates that Oracle correctly enforces whatever configuration is in place at each hand-off, not a single universal rule.
Sample Test Data
| Sales Order | ${SALES_ORDER} |
| Customer | ${CUSTOMER} |
| Item | ${ITEM} |
| Quantity | ${QUANTITY} |
| Work Order | ${WORK_ORDER} |
| Manufacturing Org | ${MANUFACTURING_ORG} |
| Shipment | ${SHIPMENT} |
| AR Transaction | ${AR_TRANSACTION} |
Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field applies to every journey variation — for example, reservation and mismatch fields apply only where those exception paths are being exercised.
Test Steps
9 business-readable steps. SyntraFlow's automation executes ~156 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Create the Customer Sales Order for the Make-to-Order Item Create a sales order for a make-to-order item, customer and quantity, referencing the standard Create Sales Order and Create Multi-Line Order test scenarios. ${SALES_ORDER} / ${CUSTOMER} / ${ITEM} / ${QUANTITY} | The sales order is created with a confirmed make-to-order line, ready to generate demand. |
| 2 | Verify the Linked Planned and Released Work Order Matches QuantityBusiness assertion Confirm the sales order demand flows into the supply plan and generates a planned work order, then release it to production, referencing the standard Run Supply Plan, Release Planned Order, Create Work Order and Release Work Order test scenarios; compare the work order quantity to the sales order line quantity. ${WORK_ORDER} / ${SALES_ORDER} / ${QUANTITY} / ${MANUFACTURING_ORG} This is a primary business assertion for the journey — matching quantity between the sales order line and the released work order is the expected pass condition, not merely a successfully released work order. | The released work order is correctly linked to the originating sales order with a matching quantity. |
| 3 | Issue Material and Complete the Work Order Issue component material to the work order and complete it in full or partially, referencing the standard Issue Material, Complete Work Order and Partial Completion test scenarios. ${WORK_ORDER} / ${QUANTITY} / ${MANUFACTURING_ORG} | The work order completion is recorded with the correct completed quantity, and finished goods enter inventory. |
| 4 | Verify Production Completion Triggers Reservation Against the Sales OrderBusiness assertion Confirm that the completed production quantity correctly triggers or updates a reservation against the specific originating sales order, referencing the standard Reserve Order test scenario. ${RESERVATION} / ${WORK_ORDER} / ${SALES_ORDER} This is a primary business assertion for the journey — the reservation must tie back to the specific sales order that generated the demand, not merely any open order. | The completed quantity is correctly reserved against the originating sales order, with any quantity mismatch flagged. |
| 5 | Release the Reserved Quantity for Pick Release the reserved quantity to the warehouse for picking, referencing the standard Pick Release test scenario. ${RESERVATION} / ${SALES_ORDER} | The reserved quantity is correctly released for picking. |
| 6 | Confirm Shipment of the Picked Quantity Ship-confirm the picked quantity against the sales order, referencing the standard Ship Confirm test scenario. ${SHIPMENT} / ${SALES_ORDER} | The shipment correctly consumes the picked, reserved quantity and updates the sales order fulfillment status. |
| 7 | Create the AR Billing Transaction Referencing the Shipment Create the AR transaction for the shipped quantity, referencing the standard Create Transaction (Billing) test scenario. ${AR_TRANSACTION} / ${SHIPMENT} / ${SALES_ORDER} | The AR transaction correctly reflects the shipped quantity and references the originating sales order. |
| 8 | Create and Apply the Customer Receipt Create the customer receipt and apply it against the AR transaction, referencing the standard Create Standard Receipt test scenario. ${RECEIPT} / ${AR_TRANSACTION} / ${CUSTOMER} | The customer receipt is created and correctly applied, reducing the open AR balance. |
| 9 | Verify Full Audit Trail Links Every Document TogetherBusiness assertion Review the audit trail or document reference chain connecting the sales order, work order, reservation, shipment, AR transaction and receipt for the journey. ${SALES_ORDER} / ${WORK_ORDER} / ${AR_TRANSACTION} / ${RECEIPT} This is the final business assertion for the scenario — a traceable, correctly linked document chain across Order Management, Supply Planning, Manufacturing and Financials AR is the expected pass condition for the full journey. | The sales order, work order, reservation, shipment, invoice and receipt are correctly linked in the audit trail, confirming the end-to-end journey is traceable. |
Expected Results
- The sales order is created and confirmed for the make-to-order item before production is initiated.
- The sales order demand correctly flows into the supply plan and generates a linked, released work order.
- Production completion correctly triggers reservation against the specific originating sales order.
- Pick release and shipment correctly consume the reserved, completed production quantity.
- AR billing correctly reflects the shipped quantity tied back to the originating sales order.
- The customer receipt correctly applies against the AR transaction, reducing the open balance.
- A sales order cancellation after work order creation is correctly flagged as an orphaned work order.
- Unauthorized work order completion attempts are correctly blocked at any stage of the journey.
Key Validation Checkpoints
- sales order demand correctly generates a linked work order with matching quantity
- production completion correctly triggers reservation against the specific originating sales order
- shipment correctly consumes the completed, reserved quantity
- AR billing correctly reflects shipped quantity tied back to the sales order
- quantity changes before production correctly re-flow through planning and the work order
- order cancellation after work order creation correctly flags the resulting orphaned work order
- production/shipment delay correctly surfaces as a fulfillment schedule impact
- unauthorized completion correctly blocked
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core Make-to-Order journey as an orchestration across the Order Management, Supply Planning, Manufacturing and Financials AR family pages within SCM. Jarvis AI extends this scenario by following the pipeline from SCM to Functional Area, Process/Scenario Family and Standard Test Scenarios, then combining it with DataVault test data to generate Jarvis Variations — organized as Positive, Negative, Boundary, Integration and Security categories — before they can be assembled into a Regression Pack and Scheduled Execution, with results surfaced through Failure Intelligence.
Teams do not need to manually stitch together sales order, demand, planning, work order, completion, reservation, pick, shipment, billing and receipt tests for every item, customer or exception path. Jarvis uses the standard journey as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment — including component shortages, production delays, order holds and quantity mismatches — since correctly enforced hand-offs across four Oracle Fusion pillars, not just individually correct transactions, is what this journey scenario proves. These Jarvis-generated variations do not create additional public SEO pages, and this page itself does not duplicate the individual scenario coverage already tested on the family pages it links to; this page remains the canonical reference for the end-to-end journey.
From Standard Test to Executed Regression Pack
Rather than re-testing every sales order, planning, work order, completion, reservation, pick, shipment, AR transaction and receipt field individually — already covered on their respective family pages — SyntraFlow maintains one core Make-to-Order journey scenario, with 37 example end-to-end scenarios documented below, and allows Jarvis AI to generate item, customer, configuration and security-specific journey variations using the customer's available test data. These variations do not create additional public SEO pages.
AI-Generated Test Variations
The same Make-to-Order 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 End-to-End.
- Standard end-to-end make-to-order journey from customer order through production to shipment, billing and receipt
- Single-line and multi-line sales orders for manufactured items
- Demand-driven supply planning correctly generating and releasing a linked work order
- Full component availability enabling work order release and material issue without delay
- Production completion — partial and full — correctly reflected in finished goods inventory
- Finished goods correctly reserved against the originating sales order
- Pick release and ship confirm correctly consuming the reserved, completed quantity
- AR billing and customer receipt correctly reflecting the shipped quantity and applying against the invoice
- Component shortage correctly flagged before production can proceed
- Customer cancellation before or after production correctly handled, including any resulting orphaned work order
- Production or shipment delay correctly surfaced as a fulfillment schedule impact
- Order hold correctly blocking downstream stages until released
- Manufacturing or billing failure correctly flagged rather than silently passing
- Receipt reversal correctly restoring the customer's AR balance
These are representative examples only. Journey behavior, work-order linkage configuration and available hand-off paths 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 item, customer, work definition and exception path in a real Oracle Fusion Make-to-Order journey. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct journey scenarios relevant to the customer's actual implementation.
Standard Library Definition
Sales Order ${SALES_ORDER}
Customer ${CUSTOMER}
Item ${ITEM}
Quantity ${QUANTITY}
Work Order ${WORK_ORDER}
Manufacturing Org ${MANUFACTURING_ORG}
Shipment ${SHIPMENT}
AR Transaction ${AR_TRANSACTION}
DataVault
Customers Active customers enabled for order management Items Active make-to-order and engineered items with work definitions Work Definitions Routing and resource setup by manufacturing organization Reservations Reservation rules by item and organization Security Roles authorised at each stage of the journey
Jarvis AI Generates
Scenario 01 — Standard Journey, ${ITEM}
Scenario 08 — Component Shortage at Work Order Release
Scenario 27 — Customer Cancels Before Production
Scenario 29 — Production Delay Impacts Fulfillment Schedule
Scenario 31 — Order Hold Blocks Downstream Stages
Scenario 36 — End-to-End Quantity Traceability
...
Sales order, work order, reservation, shipment, AR billing and receipt data used in Make-to-Order testing are masked or synthetic through Syntra DataVault — never real production data. The public Syntra Standard Test Library uses illustrative placeholder data only, and where DataVault is connected, customer-specific item, customer and work-definition 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
This catalog spans 37 end-to-end Make-to-Order journey scenarios validating customer-demand-to-production-to-billing continuity across Order Management, Supply Planning, Manufacturing and Financials AR, plus negative/boundary journey testing. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.
| ID | Variation | Type | Key Difference | Execution |
|---|---|---|---|---|
| E2E-MTO-001 | Standard Make-to-Order Happy Path | Positive | Create sales order ${SALES_ORDER} for make-to-order item ${ITEM}, flow demand through supply planning to a released work order ${WORK_ORDER}, complete production, reserve, pick, ship and bill — all stage data matches end-to-end. | SyntraFlow Ready |
| E2E-MTO-002 | Single-Line Make-to-Order | Positive | Create a single-line sales order ${SALES_ORDER} for one manufactured item ${ITEM}, referencing Create Sales Order, and verify the journey completes for the single line. | SyntraFlow Ready |
| E2E-MTO-003 | Multi-Line Order with Manufactured Item | Positive | Create multi-line sales order ${SALES_ORDER} referencing Create Multi-Line Order, and verify the manufactured line correctly generates its own linked work order ${WORK_ORDER}. | SyntraFlow Ready |
| E2E-MTO-004 | Customer Order Creates Demand | Positive | Verify that sales order ${SALES_ORDER} demand for make-to-order item ${ITEM} correctly appears as demand in the supply plan, referencing Run Supply Plan. | SyntraFlow Ready |
| E2E-MTO-005 | Planned Work Order Generated | Positive | Run the supply plan and verify a planned work order is correctly generated for sales order ${SALES_ORDER} demand, referencing Run Supply Plan and Release Planned Order. | SyntraFlow Ready |
| E2E-MTO-006 | Work Order Released | Positive | Release planned order into work order ${WORK_ORDER} for manufacturing org ${MANUFACTURING_ORG}, referencing Release Planned Order and Release Work Order. | SyntraFlow Ready |
| E2E-MTO-007 | Components Fully Available | Positive | Verify all component items for work order ${WORK_ORDER} are fully available at release and issue, referencing Issue Material. | SyntraFlow Ready |
| E2E-MTO-008 | Component Shortage | Boundary | Release work order ${WORK_ORDER} when component on-hand quantity is at or below the required build quantity boundary, referencing Issue Material and Manufacturing Exceptions; verify Oracle correctly flags the shortage. | SyntraFlow Ready |
| E2E-MTO-009 | Planned Procurement for Missing Component | Positive | Verify a component shortage on work order ${WORK_ORDER} correctly generates a planned procurement recommendation, referencing Run Supply Plan. | SyntraFlow Ready |
| E2E-MTO-010 | Component Receipt Enables Production | Positive | Receive the shortfall component and verify work order ${WORK_ORDER} can now correctly issue material and proceed to production, referencing Issue Material. | SyntraFlow Ready |
| E2E-MTO-011 | Partial Production | Positive | Complete work order ${WORK_ORDER} for a quantity less than ${QUANTITY}, referencing Partial Completion, and verify the partial completed quantity is correctly recorded. | SyntraFlow Ready |
| E2E-MTO-012 | Full Production | Positive | Complete work order ${WORK_ORDER} for the full ${QUANTITY}, referencing Complete Work Order. | SyntraFlow Ready |
| E2E-MTO-013 | Finished Goods Enters Inventory | Positive | Verify the completed quantity from work order ${WORK_ORDER} correctly enters finished goods inventory in manufacturing org ${MANUFACTURING_ORG}, referencing Complete Work Order. | SyntraFlow Ready |
| E2E-MTO-014 | Customer Order Reserves Produced Quantity | Positive | Verify the completed finished goods quantity is correctly reserved against originating sales order ${SALES_ORDER}, referencing Reserve Order. | SyntraFlow Ready |
| E2E-MTO-015 | Partial Reservation | Positive | Following a partial completion, verify reservation ${RESERVATION} correctly reflects only the partial completed quantity against sales order ${SALES_ORDER}, referencing Reserve Order. | SyntraFlow Ready |
| E2E-MTO-016 | Full Reservation | Positive | Following full completion, verify reservation ${RESERVATION} correctly reflects the full completed quantity ${QUANTITY} against sales order ${SALES_ORDER}, referencing Reserve Order. | SyntraFlow Ready |
| E2E-MTO-017 | Pick Release | Positive | Release the reserved quantity on sales order ${SALES_ORDER} for picking, referencing Pick Release. | SyntraFlow Ready |
| E2E-MTO-018 | Partial Pick | Positive | Pick release a quantity less than the full reserved quantity on sales order ${SALES_ORDER}, referencing Pick Release, and verify the partial pick is correctly recorded. | SyntraFlow Ready |
| E2E-MTO-019 | Partial Shipment | Positive | Ship-confirm shipment ${SHIPMENT} for a partial picked quantity against sales order ${SALES_ORDER}, referencing Ship Confirm. | SyntraFlow Ready |
| E2E-MTO-020 | Full Shipment | Positive | Ship-confirm shipment ${SHIPMENT} for the full picked and reserved quantity against sales order ${SALES_ORDER}, referencing Ship Confirm. | SyntraFlow Ready |
| E2E-MTO-021 | AR Invoice Created | Positive | Create AR transaction ${AR_TRANSACTION} for shipment ${SHIPMENT}, referencing Create Transaction (Billing), and verify the billed quantity matches the shipped quantity. | SyntraFlow Ready |
| E2E-MTO-022 | Customer Receipt Created | Positive | Create a customer receipt for customer ${CUSTOMER} against AR transaction ${AR_TRANSACTION}, referencing Create Standard Receipt. | SyntraFlow Ready |
| E2E-MTO-023 | Full Receipt Application | Positive | Apply the customer receipt in full against AR transaction ${AR_TRANSACTION}, referencing Create Standard Receipt, and verify the balance is fully cleared. | SyntraFlow Ready |
| E2E-MTO-024 | Partial Receipt Application | Positive | Apply the customer receipt for less than the full amount against AR transaction ${AR_TRANSACTION}, referencing Create Standard Receipt, and verify the remaining open balance is correct. | SyntraFlow Ready |
| E2E-MTO-025 | Quantity Increased Before Production | Positive | Increase the quantity on sales order ${SALES_ORDER} before work order release, referencing Change Order Quantity, and verify the increase correctly re-flows through supply planning and work order ${WORK_ORDER}. | SyntraFlow Ready |
| E2E-MTO-026 | Quantity Decreased Before Production | Positive | Decrease the quantity on sales order ${SALES_ORDER} before work order release, referencing Change Order Quantity, and verify the decrease correctly re-flows through supply planning and work order ${WORK_ORDER}. | SyntraFlow Ready |
| E2E-MTO-027 | Customer Cancels Before Production | Negative | Cancel sales order ${SALES_ORDER} before work order ${WORK_ORDER} release, referencing Cancel Sales Order and Cancel Work Order, and verify the work order is correctly cancelled with no production initiated. | SyntraFlow Ready |
| E2E-MTO-028 | Customer Cancels After Production | Negative | Cancel sales order ${SALES_ORDER} after work order ${WORK_ORDER} completion, referencing Cancel Sales Order, and verify the resulting orphaned work order or finished goods is correctly flagged. | SyntraFlow Ready |
| E2E-MTO-029 | Production Delay | Negative | Complete work order ${WORK_ORDER} after its planned completion date, referencing Complete Work Order and Manufacturing Exceptions, and verify the delay is correctly reflected as a fulfillment schedule impact. | SyntraFlow Ready |
| E2E-MTO-030 | Shipment Delay | Negative | Ship-confirm shipment ${SHIPMENT} after its scheduled ship date, referencing Ship Confirm, and verify the delay is correctly reflected as a fulfillment schedule impact on sales order ${SALES_ORDER}. | SyntraFlow Ready |
| E2E-MTO-031 | Order Hold | Negative | Place a hold on sales order ${SALES_ORDER} mid-journey and verify downstream stages including pick, ship and billing are correctly blocked while the hold is active. | SyntraFlow Ready |
| E2E-MTO-032 | Hold Release | Positive | Release the hold on sales order ${SALES_ORDER} and verify the journey correctly resumes from the blocked stage without data loss. | SyntraFlow Ready |
| E2E-MTO-033 | Manufacturing Failure | Negative | Attempt to complete work order ${WORK_ORDER} with an exception condition, referencing Manufacturing Exceptions and Cancel Work Order, and verify the failure is correctly flagged rather than silently passing. | SyntraFlow Ready |
| E2E-MTO-034 | Billing Failure | Negative | Attempt to create AR transaction ${AR_TRANSACTION} for shipment ${SHIPMENT} with an invalid billing condition, referencing Create Transaction (Billing), and verify Oracle correctly flags the billing failure rather than creating an incorrect invoice. | SyntraFlow Ready |
| E2E-MTO-035 | Receipt Reversal | Negative | Reverse a previously applied customer receipt against AR transaction ${AR_TRANSACTION}, referencing Create Standard Receipt, and verify the AR balance is correctly restored. | SyntraFlow Ready |
| E2E-MTO-036 | End-to-End Quantity Traceability | Positive/Integration | Trace ${QUANTITY} from sales order ${SALES_ORDER} through work order ${WORK_ORDER}, reservation ${RESERVATION}, shipment ${SHIPMENT} and AR transaction ${AR_TRANSACTION}, verifying quantity continuity across every stage. | SyntraFlow Ready |
| E2E-MTO-037 | End-to-End Financial Traceability | Positive/Integration | Trace the billed amount on AR transaction ${AR_TRANSACTION} back through shipment ${SHIPMENT} to the originating sales order ${SALES_ORDER}, verifying amount continuity through to customer receipt ${RECEIPT}. | SyntraFlow Ready |
No variations match this filter.
Positive and Negative Journey Testing
Positive Testing
Jarvis generates journey scenarios using sales order, demand, planning, work order, item, customer and manufacturing organization combinations expected to successfully complete the Make-to-Order journey in Oracle Fusion.
Confirmed Sales Order + Linked Planned/Released Work Order + Matching Completion + Reserved Shipment + Billed AR Transaction + Applied Receipt → Journey Completed
Negative Testing
Jarvis can also generate journey scenarios designed to exercise Oracle's validations around component shortages, order cancellation, production/shipment delay, order holds, manufacturing or billing failure, and receipt reversal at any stage of the hand-off.
- Component Shortage at Work Order Release → Expected Shortage Flag
- Customer Cancels Sales Order After Production → Expected Orphaned Work Order Flag
- Production Delay → Expected Fulfillment Schedule Impact Reflected
- Shipment Delay → Expected Fulfillment Schedule Impact Reflected
- Order Placed on Hold → Expected Downstream Stages Blocked
- Manufacturing or Billing Failure → Expected Validation, Not Silent Pass
A negative end-to-end scenario passes when Oracle correctly enforces the expected data, configuration or security rule at any stage of the journey
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Valid journey data at every stage | Journey completes end-to-end | PASS |
| Data mismatch between stages | Validation or warning occurs | PASS |
| Missing required upstream document | Validation occurs | PASS |
| Unauthorized user at any stage | Access prevented | PASS |
| Unexpected application exception | Unexpected failure | FAIL |
Turn AI-Generated Variations into a Regression Pack
Users can select generated Make-to-Order journey scenarios and group them into reusable execution packs.
SCM End-to-End Make-to-Order Regression Pack
- Standard Make-to-Order Happy Path
- Planned Work Order Generated
- Work Order Released
- Full Production
- Finished Goods Enters Inventory
- Customer Order Reserves Produced Quantity
- Full Shipment
- AR Invoice Created
- Full Receipt Application
- Component Shortage
- Customer Cancels After Production
- Production Delay
- Order Hold
- End-to-End Quantity Traceability
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected Make-to-Order journey scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected Make-to-Order journey scenarios unattended and records the outcome of each stage hand-off and business assertion.
| Pack | SCM End-to-End Make-to-Order Regression Pack |
| Schedule | Quarterly Update Regression |
| Tests | 37 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 journey scenario, its business steps, the underlying automation actions across each Order Management, Supply Planning, Manufacturing and Financials AR family page, and the evidence captured for each.
Illustrative example data — not actual production metrics.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
DataVault Journey Persona
This persona groups the linked dimensions of a single Make-to-Order journey execution so that DataVault-driven test data stays consistent across every stage.
| Customer | ${CUSTOMER} |
| Sales Order | ${SALES_ORDER} |
| Item | ${ITEM} |
| Quantity | ${QUANTITY} |
| Work Order | ${WORK_ORDER} |
| Manufacturing Org | ${MANUFACTURING_ORG} |
| Reservation | ${RESERVATION} |
| Shipment | ${SHIPMENT} |
| AR Transaction | ${AR_TRANSACTION} |
| Receipt | ${RECEIPT} |
| Ship Date | ${SHIP_DATE} |
Because these dimensions are linked, generating one journey persona automatically produces sales order, work order, reservation, shipment, billing and receipt test data that reference the same customer, item and quantity throughout.
Security & Approval Variations
Access to each stage of the Make-to-Order journey — creating a sales order, releasing a work order, completing a make-to-order work order, or creating an AR transaction — is controlled by Oracle Fusion's security configuration, which varies by customer and spans four separate product areas. Jarvis can generate representative persona-based variations to confirm that access behaves as expected at each stage — not to assert a single universal Oracle security model.
| Persona | Action | Expected | Syntra Result |
|---|---|---|---|
| Order Management Specialist | Create Sales Order and Verify Reservation | Allowed | PASS |
| Production Operator | Complete Make-to-Order Work Order | Allowed | PASS |
| Unauthorized User | Attempts to Complete Work Order Without Role | Access prevented | PASS |
Cross-Stage Business Assertions
These assertions verify that quantity, document linkage, status and monetary amount remain consistent as the journey moves from customer demand through production to billing.
| Stage Transition | Assertion | Example | Status |
|---|---|---|---|
| Customer Order -> Work Order | Customer Demand = Planned Supply = Work Order Target | Order qty ${QUANTITY} = work order ${WORK_ORDER} target qty | PASS |
| Completion -> Reservation | Completed Qty correctly available for Reserved Qty | Completed qty ${COMPLETED_QTY} -> reserved qty ${RESERVED_QTY} against ${SALES_ORDER} | PASS |
| Reservation -> Shipment | Reserved Qty = Shipped Qty (subject to split shipment) | Reserved qty ${RESERVED_QTY} = shipped qty on ${SHIPMENT} | PASS |
| Shipment -> Billing | Shipped Qty -> Billed Qty and Amount | Shipped qty drives billed amount on ${AR_TRANSACTION} | PASS |
Illustrative example using DataVault variables — not hard-coded production values.
Stage-by-Stage Execution Evidence
This illustrative example shows how SyntraFlow records pass/fail status at each stage of a single Make-to-Order journey execution, with downstream stages correctly withheld once an upstream stage fails.
Illustrative example run — not a live execution.
Journey Failure Model
The following worked example shows how a single mid-journey failure is diagnosed and classified, and how it correctly blocks only the downstream stages that depend on it.
| Planning | PASS |
| Manufacturing | PASS |
End-to-End Quantity Traceability
Produced quantity is fully available for reservation against the originating sales order.
Produced quantity = 90; required reservation = 100.
Pick, ship and billing blocked until the reservation shortfall is resolved.
Verify completion quantity against the sales order demand, or complete the remaining work order quantity before reserving.
Do not label as an Oracle application defect without eliminating data, configuration, security, automation, environment and integration causes first.
Additional Named Regression Packs
This journey can be executed as one pack or split into focused packs covering specific behavior.
MTO Standard Pack
- Standard Make-to-Order Happy Path
- Planned Work Order Generated
- Full Production
- Customer Order Reserves Produced Quantity
- Full Shipment
- AR Invoice Created
- Full Receipt Application
MTO Component Shortage Pack
- Component Shortage
- Planned Procurement for Missing Component
- Component Receipt Enables Production
MTO Production Delay Pack
- Production Delay
- Shipment Delay
- Manufacturing Failure
- Partial Production
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 Make-to-Order journey, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary, Integration and Security coverage for the customer's environment, following the SCM → Functional Area → Process/Scenario Family → Standard Test Scenarios → DataVault Test Data → Jarvis Variations → Regression Pack → Scheduled Execution → Failure Intelligence pipeline. These variations do not create additional public SEO pages, and this page itself does not duplicate the individual scenario coverage already tested on the Order Management, Supply Planning, Manufacturing and Financials AR family pages it links to and orchestrates.
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 at any single stage does not automatically prove the end-to-end journey is correct — this is illustrative of how SyntraFlow separates action success from cross-stage business validation; it does not reflect a specific live execution. When a hand-off fails, SyntraFlow's evidence trail is designed to help a tester classify the likely cause using an eight-category taxonomy — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically; see the Journey Failure Model below for a worked example. A failure should never be labeled as an Oracle defect without first eliminating data, configuration, security, automation, environment and integration causes.
| Step | Action Status | Business Validation |
|---|---|---|
| Issue Material and Complete the Work Order | Pass | — |
| Verify Production Completion Triggers Reservation Against the Sales Order | Pass | Pass |
| Verify Full Audit Trail Links Every Document Together | Pass | Pass |
Related End-to-End Journeys & Family Tests
Make-to-Order is the broadest cross-module journey on the site, and links directly to the 18 individual Order Management, Supply Planning, Manufacturing and Financials AR family pages it orchestrates.
Turn This Standard Journey into Your Oracle SCM Make-to-Order Regression Suite
Start with the Syntra Standard Make-to-Order journey spanning 18 linked family pages, use DataVault to provide environment-specific test data, let Jarvis generate additional item, customer, boundary 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.