Inter-Organization Transfer
An Inter-Organization Transfer moves inventory from one inventory organization to another. The integrator supports two sub-types depending on how the inter-org shipping network is configured in Oracle between the source and destination organization.
Direct Organization Transfer
Used when the inter-org shipping network between the two organizations is configured as Direct (INTRANSIT_TYPE = 1). Goods move immediately to the destination organization. The destination subinventory must be specified upfront.
Field |
Required |
Description |
Destination Organization code |
Yes |
The destination inventory organization. A Direct inter-org shipping network must be configured between the source and destination organizations. |
Destination Subinventory |
Yes |
The destination subinventory in the Transfer Organization. Must be an active asset-type subinventory. The item must be assigned to the destination organization. LOV is enabled only after Transfer Organization Code and Item Number are populated. |
Destination Locator |
cond. |
Required if the Transfer Subinventory is locator-controlled. Must be an active locator in the destination subinventory. |
Intransit Shipment
Used when the inter-org shipping network is configured as Intransit (INTRANSIT_TYPE = 2). Goods move into an intransit state and are received separately at the destination using a Shipment Number. The destination subinventory is not required at the time of shipment.
Transaction Quantity must be entered as a negative value — the Oracle REST Web Service requires this for Intransit Shipment transactions and will reject a positive quantity with an error.
Field |
Required |
Description |
Transfer Organization Code |
Yes |
The destination inventory organization. An Intransit inter-org shipping network must be configured between the source and destination organizations. |
Shipment Number |
Yes |
A unique identifier for the intransit shipment. Must not already exist in Oracle. Used to track the shipment until it is received at the destination organization. |
Expected Receipt Date |
Yes |
The expected date the goods will arrive at the destination organization. Must be on or after the Transaction Date. |
Destination Subinventory |
Optional |
Optional at shipment time. Goods are in transit and the destination subinventory is resolved at intransit receipt. If provided, must be a valid asset-type subinventory in the destination organization. |
Freight Carrier / Waybill / Containers |
Optional |
Optional shipping details. Freight Carrier must be active and enabled for both source and destination organizations if supplied. |
Note: The transaction type available for an inter-org pair (Direct Organization Transfer or Intransit Shipment) is determined by the shipping network configuration in Oracle. When a Transfer Organization Code is entered in the integrator, the Transaction Type field is automatically restricted to the single applicable type for that org pair. Both transfer types require the item to be assigned to the destination organization before the Transfer Subinventory LOV will return values.
Item Revision for Inter-Organization Transfers
When performing a Direct Organization Transfer or Intransit Shipment, the Revision field is driven by the destination organization rather than the source organization. This is because the revision must be valid in the organization that will be receiving the goods.
The Revision LOV will only activate once both the Transfer Organization Code and Item Number are populated. If the item is not revision-controlled in the destination organization, the Revision field will remain disabled.
For all other transaction types, the Revision field continues to depend on the source Inventory Organization Code and Item Number as normal.
