Open Forum

 View Only
  • 1.  SOP Process Hold - Webservices

    Posted Oct 19, 2022 03:57 AM
    Hello, 

    We are using GP WebServices for creating and updating Sales Fulfilment Orders but have run into a problem with the Credit Hold order fulfilment workflow / process. 

    We have a Hold ID called "ON STOP" which is one of our Sales Process Holds, and the process hold is set to apply the hold to every action other than Printing Documents.  

    Using GP to enter the order, the process hold applies as expected.  When using WebServices, the process hold appears to be fully ignored.    If we add a new line to that order, the process hold kicks in,   if we update the line that was created using integration / WebServices, the process hold DOESNT kick it. 

    Something on sales line itself must be triggering the process hold to run / apply where necessary. 

    Has anyone come across this before?  Is there a way to kick the process hold check to happen by calling a Stored Proc for example? 

    Hoping someone can help! 


    Thanks

     #GP2018and2018R2 #Functional​​

    ------------------------------
    Jay Adams
    Sykes Seafoods Ltd
    Manchester
    ------------------------------


  • 2.  RE: SOP Process Hold - Webservices

    Posted Oct 20, 2022 06:34 AM
    Edited by Dexterity Developer Oct 20, 2022 06:35 AM
      |   view attached
    Hello Jay Adams,

    Try calling 

    CreateSalesProcessHoldSetup/UpdateSalesFulfillmentOrder() method for hold, as web service manage all sales transactions except creating process holds.


    ------------------------------
    dexteritydeveloper
    dexteritydeveloper@gmail.com
    https://keptonworking.blogspot.com/
    ------------------------------



  • 3.  RE: SOP Process Hold - Webservices

    Posted Oct 20, 2022 06:38 AM
    And you can also call eConnect for creating/updating hold  for sales orders.
    USE [TWO18]
    GO
    
    DECLARE @RC int
    DECLARE @I_vSOPTYPE smallint
    DECLARE @I_vSOPNUMBE char(21)
    DECLARE @I_vPRCHLDID char(15)
    DECLARE @I_vDSCRIPTN char(30)
    DECLARE @I_vPASSWORD char(15)
    DECLARE @I_vXFERPHOL tinyint
    DECLARE @I_vPOSTPHOL tinyint
    DECLARE @I_vFUFIPHOL tinyint
    DECLARE @I_vPRINPHOL tinyint
    DECLARE @I_vHOLDDATE datetime
    DECLARE @I_vUSERID char(15)
    DECLARE @I_vTIME1 datetime
    DECLARE @I_vDELETE1 int
    DECLARE @I_vUpdateIfExistsMaster int
    DECLARE @I_vUpdateSopIfExists int
    DECLARE @I_vRequesterTrx smallint
    DECLARE @O_iErrorState int
    DECLARE @oErrString varchar(255)
    
    -- TODO: Set parameter values here.
    
    EXECUTE @RC = [dbo].[taSopUpdateCreateProcessHold] 
       @I_vSOPTYPE=6
      ,@I_vSOPNUMBE='FULORD1011' 
      ,@I_vPRCHLDID='ON STOP'        
      ,@I_vDSCRIPTN='ON STOP TEST'
      ,@I_vPASSWORD='sa'
      ,@I_vXFERPHOL=1
      ,@I_vPOSTPHOL=1
      ,@I_vFUFIPHOL=1
      ,@I_vPRINPHOL=1
      ,@I_vHOLDDATE=1
      ,@I_vUSERID='sa'
      --,@I_vTIME1
      ,@I_vDELETE1=1
      --,@I_vUpdateIfExistsMaster=1
      ,@I_vUpdateSopIfExists=1
      --,@I_vRequesterTrx
      ,@O_iErrorState=@O_iErrorState
      ,@oErrString=@oErrString
    
      
    
    
    GO
    
    
    ​


    ------------------------------
    dexteritydeveloper
    dexteritydeveloper@gmail.com
    https://keptonworking.blogspot.com/
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role