Comments

  • 1-4 of 4
  • Jesus Escobar
    Hi, i  try doing the following,  in the event ( Work Order Update) a filter was created so that it only triggers when the release status unreleased to release
     
    <xpathExpr xmlns="http://schemas.xmlsoap.org/soap/envelope/"  xmlns:ns1="http://xmlns.oracle.com/apps/scm/commonWorkExecution/workOrders/workOrdersService/" xmlns:ns2="http://xmlns.oracle.com/apps/scm/commonWorkExecution/workOrders/workOrdersService/types/">$eventPayload/ns2:result/ns1:WoStatusCode='ORA_RELEASED'</xpathExpr>
     
    Is to avoid consulting through GET every 10 min if an OT status change.
     
    That work for me.
     
     
  • Jesus Escobar
     
    hi dev I leave a white paper that explains how to achieve the specific scenario.
  • Jesus Escobar

    By Example 

    The lot A5465 is available for that article should be available to be consumed by FIFO

     

  • Jesus Escobar
    Hi Valerie.
     
    I Make the invocation of web / fscmService / WorkOrderMaterialTransactionService? WSDL
     
     
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/scm/commonWorkExecution/workOrderMaterialTransactions/materialTransactionsService/types/" xmlns:mat="http://xmlns.oracle.com/apps/scm/commonWorkExecution/workOrderMaterialTransactions/materialTransactionsService/" xmlns:lot="http://xmlns.oracle.com/apps/flex/scm/commonWorkExecution/workOrderMaterialTransactions/model/massImport/lot/" xmlns:ser="http://xmlns.oracle.com/apps/flex/scm/commonWorkExecution/workOrderMaterialTransactions/model/massImport/serial/" xmlns:wor="http://xmlns.oracle.com/apps/flex/scm/commonWorkExecution/workOrders/">
       <soapenv:Header/>
       <soapenv:Body>
          <typ:createWorkOrderMaterialTransactionsAsync>
                <mat:SourceSystemCode>FUSION_MOBILE</mat:SourceSystemCode>
                <mat:MaterialTransactionInput>
                   <mat:Organization>RENOPACK</mat:Organization>            
                   <mat:WorkOrderNumber>256</mat:WorkOrderNumber>        
                   <mat:OperationSequence>10</mat:OperationSequence>           
                   <mat:TransactionType>MATERIAL_ISSUE</mat:TransactionType>           
                   <mat:InventoryItemNumber>BANDEJ_01_30</mat:InventoryItemNumber>
                   <mat:TransactionQuantity unitCode="UN">1</mat:TransactionQuantity>
                   <mat:TransactionUnitOfMeasure>UN</mat:TransactionUnitOfMeasure>
                   <mat:Subinventory>AMP</mat:Subinventory>
                   <mat:Locator>01.01.01.01</mat:Locator>
                   <mat:TransactionLotInput>
                      <mat:LotNumber>L004</mat:LotNumber>
                      <mat:TransactionQuantity unitCode="UN">1</mat:TransactionQuantity>
                   </mat:TransactionLotInput>
                </mat:MaterialTransactionInput>
             </typ:batchInput>
          </typ:createWorkOrderMaterialTransactionsAsync>
       </soapenv:Body>
    </soapenv:Envelope>
     
     
    The situation is how indicate to the Web services that it must look for the Lot number through FIFO conditions.
     
    <mat: TransactionLotInput>               
            <mat: LotNumber> L004 </ mat: LotNumber>            
           <mat: TransactionQuantity unitCode = "UN"> 1 </ mat: TransactionQuantity>           
    </ mat: TransactionLotInput> 
     
    This must have been that a raw material BANDEJ_01_30 has L004,  L005 … L00N, indicated that it must first take L004 and then at the end of that L004  start with L005  and so on.  FIFO conditions.