Oracle ERP Testing Tool > Test Library > SCM > Inventory Management > Transfers

Syntra Standard Oracle Test Library

Oracle Fusion Create Transfer Order Test Cases

Validate that an interorganization transfer order can be created in Oracle Fusion SCM Inventory Management between two valid inventory organizations, with correct item, quantity, unit of measure, ship method and requested date on the resulting order.

Test ID	ORCL.SCM.INV.XFER.CREATE
Application	Oracle Fusion Cloud
Product	SCM / Inventory Management
Module	Inventory Management
Process	Transfers
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 8 business-readable test steps; SyntraFlow's automation executes approximately 22 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that an interorganization transfer order can be created in Oracle Fusion SCM Inventory Management using a valid source organization, destination organization, item, quantity, unit of measure, ship method and requested date, and that the resulting transfer order is created with correct header and line detail.

The scenario should confirm that:

the transfer order is created between the correct source and destination inventory organizations
the item, quantity and unit of measure on each transfer order line are captured correctly
the selected ship method and requested date are correctly reflected on the transfer order
the transfer order receives a system-generated order number and correct status
the transfer order is available downstream for shipment processing once created
Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers creation of a single or multi-line interorganization transfer order in Oracle Fusion SCM Inventory Management TEST/UAT environments. It does not cover shipment or receipt of the transfer, which are covered by the separate Ship Transfer Order and Receive Transfer Order scenarios in the same Transfers cluster.

When to Use This Test

Functional testing of transfer order creation for a new Oracle Fusion SCM Inventory Management implementation
Regression testing of transfer order creation behavior after an Oracle quarterly update
UAT sign-off for inventory planners who routinely move stock between organizations
Baseline case referenced by the Ship Transfer Order and Receive Transfer Order scenarios within the same Transfers cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during transfer order creation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Inventory Management Transfers Process

Navigate to Inventory

→

Create Transfer Order

→

Select Organizations

→

Add Item Lines

→

Select Ship Method/Date

→

Review

→

Submit

Create Transfer Order is the entry point of the Transfers scenario family within Plan-to-Produce. Once a transfer order is created, it is typically shipped from the source organization and received at the destination organization — covered by the Ship Transfer Order and Receive Transfer Order scenarios in this same cluster. Exact fields available, defaulting behavior and validation depend on organization parameters, item setup and customer-specific Oracle Fusion configuration.

Next Stage →

Interorganization Transfer

Preconditions

The source and destination inventory organizations are configured and enabled for transfer between one another.
The item being transferred is active in both the source and destination organizations.
Sufficient on-hand quantity exists in the source organization to support eventual fulfillment of the transfer order — this is not required at order-creation time.
The test user has appropriate access to create a transfer order for the source organization.
The ship method used on the transfer order is configured and active.

Exact field availability, mandatory fields and validation messages may vary by Oracle Fusion implementation, organization parameters, item setup and customer-specific configuration. On-hand quantity in the source organization affects later shipment, not creation of the transfer order itself.

Sample Test Data

Source Organization	${SOURCE_ORGANIZATION}
Destination Organization	${DESTINATION_ORGANIZATION}
Transfer Order Type	${TRANSFER_ORDER_TYPE}
Item	${ITEM}
Item Description	${ITEM_DESCRIPTION}
Quantity	${QUANTITY}
UOM	${UOM}
Ship Method	${SHIP_METHOD}
Requested Date	${REQUESTED_DATE}
Note / Reference	${TRANSFER_NOTE}

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 line — for example, item description may default from the item master rather than requiring re-entry.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~22 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Sign In and Navigate to Inventory Sign in to Oracle Fusion using an authorised inventory test user and navigate to the Inventory Management work area.	The Inventory Management work area opens successfully.
2	Navigate to Transfer Orders Open the Transfer Orders page to begin creating a new transfer order.	The transfer order creation page opens.
3	Initiate Create Transfer Order Initiate a new transfer order and select the transfer order type where applicable. ${TRANSFER_ORDER_TYPE} This single business step replaces multiple technical actions such as opening the create page and confirming the order type.	A new, unsaved transfer order is opened.
4	Select Source and Destination Organizations Select the source organization the stock will transfer from and the destination organization it will transfer to. ${SOURCE_ORGANIZATION} / ${DESTINATION_ORGANIZATION}	The source and destination organizations are accepted and reflected on the transfer order header.
5	Add Item Lines with Quantity and UOM Search for and add the item to be transferred, entering the quantity and unit of measure for the line. ${ITEM} / ${QUANTITY} / ${UOM}	The item line is accepted and added to the transfer order with the correct quantity and UOM.
6	Select Ship Method and Requested Date Select the ship method for the transfer and enter the requested date. ${SHIP_METHOD} / ${REQUESTED_DATE}	The ship method and requested date are accepted and reflected on the transfer order.
7	Review and Submit Transfer Order Review the transfer order header and line detail, then submit it for creation in the test environment. Reviewing the transfer order before submission lets the tester catch an incorrect field entry before the order is created.	Oracle Fusion successfully processes the transfer order without unexpected errors.
8	Verify Order Created with Correct StatusBusiness assertion Reopen or refresh the transfer order and confirm the generated order number, status and line detail. This is the primary business assertion for the scenario — a correctly created transfer order with accurate header and line detail is the expected pass condition, not merely a successful save.	An order number is generated, the transfer order status is correct, and source, destination, item, quantity and UOM match the entered data.

Expected Results

The transfer order is created between the correct source and destination organizations.
A system-generated transfer order number is assigned.
Line data — item, quantity and UOM — is correct.
The selected ship method and requested date are correct.
The transfer order status correctly reflects a newly created order.
The transfer order is available for downstream shipment processing.

Key Validation Checkpoints

Transfer order created with correct status.
Source/destination correctly recorded.
Line item details accurate.
Order available for shipment processing.

Core Business Scenario

Create Transfer Order

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Create Transfer Order business scenario. Jarvis AI can extend this scenario by generating additional organization pair, item, quantity, ship method 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 organization pair, item or quantity combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Organization Pair variations for the customer's environment — including large-quantity boundary cases and transfer orders between less commonly paired organizations, since correctly enforced validation at the edges of expected values is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Transfer Order business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Organizations, Items, Ship Methods and Locations.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant organization pair, item, quantity and security variations.

Positive + Negative Test Variations

Valid transfer order scenarios and edge cases such as invalid organizations, inactive items or restricted access.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining a separate test page for every possible source/destination organization pair, item, quantity or ship method combination, SyntraFlow maintains one core Create Transfer Order scenario and allows Jarvis AI to generate organization, item, quantity and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Transfer 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 Inventory Management Transfers.

Positive Scenarios

Create a standard transfer order
Create a transfer order with multiple line items
Create transfer orders across different organization pairs
Create transfer orders with different quantities
Create transfer orders using different ship methods
Create a transfer order with a scheduled requested date

Negative Scenarios

Attempt to create a transfer order with an invalid source organization
Attempt to create a transfer order with an invalid destination organization
Enter the same organization as both source and destination
Attempt to transfer an item that is inactive in the destination organization
Enter an invalid quantity
Enter an invalid ship method
Attempt to save with missing required fields

These are representative examples only. Negative-scenario behavior and available field combinations 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 organization pair, item, quantity and ship method combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Transfer Order scenarios relevant to the customer's actual implementation.

Standard Library Definition

Source Organization      ${SOURCE_ORGANIZATION}
Destination Organization  ${DESTINATION_ORGANIZATION}
Transfer Order Type      ${TRANSFER_ORDER_TYPE}
Item                     ${ITEM}
Item Description         ${ITEM_DESCRIPTION}
Quantity                 ${QUANTITY}
UOM                      ${UOM}
Ship Method              ${SHIP_METHOD}
Requested Date           ${REQUESTED_DATE}
Note / Reference         ${TRANSFER_NOTE}

DataVault

Organizations
  Active organizations enabled for transfer, by pair
Items
  Active items shared across source and destination organizations
Ship Methods
  Configured ship methods per organization pair
Locations
  Configured shipping and receiving locations
Calendars
  Requested and scheduled date windows

Jarvis AI Generates

Scenario 01 — Org A to Org B + Single Item Line
Scenario 02 — Org A to Org B + Multi-Line
Scenario 03 — Org A to Org C + Different Ship Method
Scenario 04 — Scheduled Requested Date
Scenario 05 — Invalid Destination Organization
Scenario 06 — Unauthorized User Attempts Create Transfer Order
...

Create Transfer Order test data can include sensitive supply chain categories such as organization, item and quantity information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific inventory dimensions remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/ for details.

Example Test Variations

Representative examples of Create Transfer Order scenarios Jarvis can generate from this business scenario, spanning organization pair, line item and quantity conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Standard Transfer Order	Positive	Transfer order created between two valid organizations	Syntra Ready
VAR-002	Multiple Line Items	Positive/Line Items	Transfer order created with multiple item lines	Syntra Ready
VAR-003	Different Organization Pair	Positive/Organization	Transfer order created between an alternate source and destination organization pair	Syntra Ready
VAR-004	Different Quantities	Positive/Line Items	Transfer order created with a range of valid line quantities	Syntra Ready
VAR-005	Different Ship Methods	Positive	Transfer order created using an alternate configured ship method	Syntra Ready
VAR-006	Scheduled Requested Date	Positive	Transfer order created with a future requested date	Syntra Ready
VAR-007	Invalid Source Organization	Negative/Organization	Source organization entered is invalid or not enabled for transfer	Syntra Ready
VAR-008	Invalid Destination Organization	Negative/Organization	Destination organization entered is invalid or not enabled for transfer	Syntra Ready
VAR-009	Same Source and Destination	Negative/Organization	Source and destination organization are entered as the same value	Syntra Ready
VAR-010	Inactive Item in Destination	Negative/Line Items	Item is not active in the destination organization	Syntra Ready
VAR-011	Invalid Quantity	Negative/Line Items	Line quantity entered as zero or a negative value	Syntra Ready
VAR-012	Invalid Ship Method	Negative	Ship method entered is not configured for the transfer	Syntra Ready
VAR-013	Missing Required Fields	Negative	A mandatory header or line field is left blank	Syntra Ready

Automatically Expand Positive and Negative Transfer Order Coverage

Positive Testing

Jarvis generates scenarios using organization pair, item, quantity, ship method and date combinations expected to successfully create a transfer order in Oracle Fusion.

Valid Source Organization + Valid Destination Organization + Active Item + Valid Quantity → Transfer Order Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around organization eligibility, item status, quantity and security.

Invalid Source Organization → Expected Organization Validation
Same Source and Destination → Expected Organization Validation
Inactive Item in Destination → Expected Item Validation
Invalid Quantity → Expected Quantity Validation
Unauthorized User → Expected Access Restriction

A negative scenario passes when Oracle correctly enforces the expected business rule or validation.

Scenario	Oracle Outcome	Test Result
Valid transfer order	Order created	PASS
Invalid organization	Organization validation occurs	PASS
Same source/destination	Validation occurs	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Create Transfer Order scenarios and group them into reusable execution packs.

SCM Inventory Management Create Transfer Order Regression Pack

Standard Transfer Order
Multiple Line Items
Different Organization Pair
Different Quantities
Different Ship Methods
Scheduled Requested Date
Invalid Source Organization
Same Source and Destination
Inactive Item in Destination
Security Restriction — Unauthorized Create Transfer Order

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected Create Transfer Order scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Create Transfer Order scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	SCM Inventory Management Create Transfer Order Regression Pack
Schedule	Quarterly Update Regression
Tests	13 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.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

Security & Approval Variations

Access to create a transfer order for a given source organization is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that transfer-order-creation access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Inventory Planner	Create Transfer Order	Allowed	PASS
Unauthorized User	Attempts Transfer Order	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.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Create Transfer Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Organization Pair coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

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.

Standard Library — Create Transfer Order, 8 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Select Source and Destination Organizations

May internally include

Open Organization Search → Enter Search Criteria → Select Source Organization → Select Destination Organization → Confirm Transfer Enabled → Add to Header

Business Step

Add Item Lines with Quantity and UOM

May internally include

Open Item Search → Select Item → Enter Quantity → Select UOM → Add Line → Confirm Line Accepted

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the transfer order was created 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 — for example DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Create Transfer Order failed — Likely category: CONFIGURATION_ERROR — Evidence: item is not enabled in the destination organization — Recommended action: enable the item in the destination organization and retry. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Add Item Lines with Quantity and UOM	Pass	—
Review and Submit Transfer Order	Pass	—
Verify Order Created with Correct Status	Pass	Pass

Related Transfer Tests

Create Transfer Order is the entry point of the Transfers cluster — explore the related interorganization transfer, shipment and receipt scenarios below.

Interorganization Transfer Ship Transfer Order Receive Transfer Order

Turn This Standard Test into Your Oracle SCM Create Transfer Order Regression Suite

Start with the Syntra Standard Create Transfer Order test, use DataVault to provide environment-specific test data, let Jarvis generate additional organization, item, quantity and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Inventory Management Transfers Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Oracle ERP Testing Tool Test Library SCM Test Library Inventory Management Test Library Transfers Test Library Syntra DataVault

Frequently Asked Questions

What is a transfer order in Oracle Fusion Inventory Management?

A transfer order is an Oracle Fusion SCM Inventory Management document that requests the movement of one or more items from a source inventory organization to a destination inventory organization, capturing item, quantity, unit of measure, ship method and requested date before shipment takes place.

What is the difference between a transfer order and a direct interorganization transfer?

A transfer order is created, and then separately shipped and received, giving visibility and control at each stage — covered by the Create Transfer Order, Ship Transfer Order and Receive Transfer Order scenarios in this cluster. A direct interorganization transfer moves stock between organizations in a single transaction without a separate order, ship and receive sequence, and is covered by the related Interorganization Transfer scenario.

How does security testing work for transfer order creation?

Access to create a transfer order for a given source organization is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an authorised inventory planner versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.

Does creating a transfer order reserve inventory immediately?

No. Creating a transfer order records the request to move stock, but reservation of on-hand inventory in the source organization typically occurs later, at shipment. This scenario validates order creation only; reservation and fulfillment behavior are exercised by the Ship Transfer Order scenario.

Do all the listed positive and negative variations need separate test library pages?

No. Rather than maintaining a separate public page for every organization pair, item, quantity or ship method combination, SyntraFlow maintains this one core Create Transfer Order scenario and uses Jarvis AI to generate the underlying variations from customer-specific DataVault test data. This page remains the canonical reference for all of them.