Get Involved. Join the Conversation.


  • Lynn Warneka

    Using the standard recommended approach, you would run Generate Shipment Request to transmit the data to WMS.  It would do a high level reservation prior to submission.  I can't comment on your subinventory transfer from WMS as that wouldn't happen in our recommended approach.  You can log an SR with all the details.  

  • Vijay Krishnamoorthy

    Thanks Lynn for your comments;  The document doesn't state much about the Reservations and the impact;  We are sending the shipment information from Oracle ERP to Logfire;  But again, the subinventory movement from WMS fails with "Negative on hand quantity not allowed"; 

    Note:  We have more transfer orders vying for limited on-hand quantity.

  • Lynn Warneka

    From an Oracle development perspective, we'd recommend using the product integration approach that we've introduced and have done training on.   It doesn't as an example, include doing Pick Release in Inventory Management Cloud or subinventory transfers for Transfer Orders.  

    We have done release training and other material on this integration which should be on the Support site.  In addition, we did a Customer Connect session in December 2018 at the following link:

  • Lynn Warneka

    For Inventory Management Cloud, we don't have a mobile solution yet.  We leverage partners such as RF Smart, DSI, etc.  Manufacturing does have some limited mobile capabilities and you can post in their forum for additional details.  

  • Sunil Dabekar

    Hi Vijay,


    Based on my understanding, I dont think we can actually create a pick release superficially (without a reservation I mean).

    Having said this, for your specific issue I think we should resort to SOP (standard operating procedures) considering there are 2 applications to account for.

    If ever there are sub-inventory transfers taking place as independent transaction then the warehouse team should check if there are any open picks coming from upstream system and then send a cancellation request for the picks ,if the required items are not in working condition anh hence you wish to move them from one sub-inventory to another.  Would like to know your thoughts on this



  • Rupa Tom

    TransactionSourceTypeId - indicates the source of the transaction, like Purchase Order, Inventory etc.

    13 is the value for inventory. You can get the relevant ids from inv_txn_source_types_tl


    TransactionTypeId -indicates the type of transaction like Misc Issue, Misc receipt etc. 2 is the value for subinventory transfer.

    You can get the relevant ids from inv_transaction_types_tl


    TransactionMode - Not sure what this is for :), Have seen this value as 3 in all types of examples . Do share the information if you get what this is for.

  • Prateek Parasar

    Hi Rupa, 

    Quick question on these 3 fields. Are they set to be like that for everyone or its your setup values. What do 3, 13 and 2 means here ?





  • Prateek Parasar

    Just for reference, Oracle MOS has this for this purpose


    Sample Payloads to Create Inventory Transactions (Doc ID 1952854.1)


  • Prateek Parasar

    Great, thanks


  • Rupa Tom

    attaching a sample with min required fields. its a single call.

  • Prateek Parasar

    Do you happen have any sample payload for this ? if not this transaction but any other will also help in structuring what to send.   Is it 2 step process ? ( I mean 2 calls )

  • Rupa Tom

    Please refer the below service available for inventory transactions, which supports subinventory transfer also

  • Mohanish Mahajan

    Hi Lynn,

    We are facing the same issue for sales order shipments. The details are - 

    SR 3-18936234011 : On Hand quantity is available but still shipment lines is backordered



  • Pallavi V

    for sample Payloads for webservices use below KM document :

    Fusion Receiving External Webservices Documentation With Sample Payloads (Doc ID 2221657.1)

    use services in chapters 8 and 9 . 8 to get the list of pending receipt transactions and 9 to perform them. Receipt confirmation service is very flexible and not as detailed as the Receipt Interface service , and works with minimal "id" information on the payload. When the item is lot and/or serial controlled, the payload should contain the lot and serial
    numbers that were delivered and/or returned/corrected.


    ns2: StagedReceiptConfirmationLotAndSerial – This node is used to transmit the
    lot and/or serial numbers that are to be transacted in fusion receiving as part of the
    receipt confirmation line. This node has been designed to flatten the lot and serial
    hierarchy to facilitate a simpler communication between EP and fusion receiving.
    So, if you are delivering Lot “Lot1” and serials “SN001”, “SN002”, you need to
    create two rows for ns2: StagedReceiptConfirmationLotAndSerial node. In the first
    row, give “Lot1” and “SN001” and for the second row, give “Lot1” and “SN002”,
    essentially repeating the lot number in two rows.

  • Eric Serra I Paradis

    Hello Vikram,

    OK, thank you very much for your help.

    Best regards,