Inventory

Get Involved. Join the Conversation.

Topic

    Shailesh Dubey
    Webservice and Sample payload for receiving In-transit...
    Topic posted November 26, 2018 by Shailesh DubeyGreen Ribbon: 100+ Points 
    39 Views, 5 Comments
    Title:
    Webservice and Sample payload for receiving In-transit Shipment
    Summary:
    Webservice and Sample payload for receiving In-transit Shipment.
    Content:

    We are integrating Cloud WMS with Fusion Inventory. For this we need to create Receipt against an In-transit shipment. All our items are either Lot or Serial controlled. Can someone please provide the sample payload and webservice details to complete this transaction in fusion receiving. 

    Version:
    Fusion R13, Cloud WMS 9.0.0

    Comment

     

    • Lynn Warneka

      Can you please provide the documentation link for the web service you are using?  We have both REST and SOAP services.  

      • Shailesh Dubey

        Hi , 

        I don't have the webservice details and that's what i am looking for. We need Webservice to receive In-transit shipment for lot controlled item. Can you please provide me the details on which webservice we can use for this case. Please provide SOAP and REST both details.  

      • Shailesh Dubey

        We had planned to use below- but it does not have any lot and serial data that i can input. 

        <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
         <soap:Body>
         <ns1:processor
        xmlns:ns1="http://xmlns.oracle.com/apps/scm/receiving/receiptsInterface/transactions/pro
        cessorServiceV2/types/">
         <ns1:Receipt
        xmlns:ns2="http://xmlns.oracle.com/apps/scm/receiving/receiptsInterface/transactions/pro
        cessorServiceV2/">
         <ns2:TransactionType>NEW</ns2:TransactionType>
         <ns2:ASNType>STD</ns2:ASNType>
         <ns2:ReceiptSourceCode>INVENTORY</ns2:ReceiptSourceCode>
         <ns2:ShipToOrganizationCode>M2</ns2:ShipToOrganizationCode>
         <ns2:FromOrganizationCode>M1</ns2:FromOrganizationCode>
         <<ns2:ShipmentNumber>23451245</ns2:ShipmentNumber>
         <ns2:EmployeeName>Stock Pat</ns2:EmployeeName>
         <ns2:StagedReceivingTransaction>
         <ns2:ReceiptSourceCode>INVENTORY</ns2:ReceiptSourceCode>
         <ns2:SourceDocumentCode>INVENTORY</ns2:SourceDocumentCode>
         <ns2:TransactionType>RECEIVE</ns2:TransactionType>
         <ns2:AutoTransactCode>DELIVER</ns2:AutoTransactCode>
         <ns2:ToOrganizationCode>M2</ns2:ToOrganizationCode>
         <ns2:TransactionDate>2015-05-11T00:00:00.000</ns2:TransactionDate>
         <ns2:DocumentNumber>23451245</ns2:DocumentNumber>
         <ns2:DocumentLineNumber>1</ns2:DocumentLineNumber>
         <ns2:ItemNumber>RCV-100</ns2:ItemNumber>
         <ns2:Quantity unitCode="">1</ns2:Quantity>
         <ns2:UnitOfMeasure>Each</ns2:UnitOfMeasure>
         <ns2:Subinventory>Stores</ns2:Subinventory>
         </ns2:StagedReceivingTransaction>
         </ns1:Receipt>
         </ns1:processor>
         </soap:Body>
        </soap:Envelope>

         

        • Niamath Jeddy

          I think you will need to add this to your payload. 

          If both Lot and serial controlled:

          <ns2:StagedLotSerialItemLot>
          <ns2:LotExpirationDate></ns2:LotExpirationDate>
          <ns2:LotNumber>RKRCV090115-L8</ns2:LotNumber>
          <ns2:ParentLotNumber></ns2:ParentLotNumber>
          <ns2:TransactionQuantity unitCode="">2</ns2:TransactionQuantity>
          <ns2:StagedLotSerialItemSerial>
          <ns2:FmSerialNumber>RKRCV090115-S16</ns2:FmSerialNumber>
          <ns2:ToSerialNumber>RKRCV090115-S17</ns2:ToSerialNumber>
          </ns2:StagedLotSerialItemSerial>
          </ns2:StagedLotSerialItemLot>

           

          If just lot controlled:

          <ns2:StagedTransactionLot>
          <ns2:LotNumber>RKRCV090115-L8</ns2:LotNumber>
          <ns2:ParentLotNumber></ns2:ParentLotNumber>
          <ns2:TransactionQuantity unitCode="Ea">2</ns2:TransactionQuantity>
          </ns2:StagedTransactionLot>

          If just serial controlled:

           

          <ns2:StagedTransactionSerial>
          <ns2:FmSerialNumber>SHP-SN-001</ns2:FmSerialNumber>
          <ns2:ToSerialNumber>SHP-SN-002</ns2:ToSerialNumber>
          </ns2:StagedTransactionSerial>

          You can refer the SDO definitions contained receiving transaction sdo here:

          https://docs.oracle.com/en/cloud/saas/supply-chain-management/18c/oessc/staged-receiving-transaction-interface-version-2-StagedReceivingTransaction-svcDataObj-463.html

           

    • 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.