Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Calling Bizweaver from SQL • Building a Workflow • about • Introduction (Email) • File Operations Tool • contact • downloads • Introduction (Crystal Reports) • Introduction (GraphqL)
bw2:call_bizweaver_from_sql

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
bw2:call_bizweaver_from_sql [2020/12/15 11:45]
akoehler created 		bw2:call_bizweaver_from_sql [2024/09/09 13:41] (current)
dlee [Calling Bizweaver from SAP Business One]
Line 1: Line 1:
-====== Calling Bizweaver from SAP Business One ======+====== Calling Bizweaver from SQL ======
  
 <WRAP center round important> <WRAP center round important>
-Some special program code, provided by Third Wave Business Systems, is required for this functionality to work.  Configuration of the special code is described **//[[bw:sqlws_config|here]]//**.  This is a technical process and should not be attempted by anyone not familiar with T-SQL stored procedures. Contact TWBS support if you need assistance.+Some special program code, provided by Third Wave Business Systems, is required for this functionality to work.  Configuration of the special code is described **//[[bw2:sqlws_config|here]]//**.  This is a technical process and should not be attempted by anyone not familiar with T-SQL stored procedures. Contact TWBS support if you need assistance.
 </WRAP> </WRAP>
 +<WRAP center round important>There are limitations associated with executing workflows via the Bizweaver web service. 
 +1) There is an upper limit on the number of HTTPS calls that can be made at which point SQL OLE gets blocked.
 +2) With SQL CLR the SAP commit waits until the BW workflow is complete and often, the user cannot wait that long.
  
 +To overcome these limitations use the direct communication method described here: [[bw2:bizweaver_trigger|Executing Workflows from SAP Business One Using Direct Communication]]
 +</WRAP>
 The call to the Bizweaver web service is initiated from the standard SAP Business One Stored Procedure **SBO_SP_PostTransactionNotice**.  The following SQL statements illustrate what needs to be added to the procedure.  The call to the Bizweaver web service is initiated from the standard SAP Business One Stored Procedure **SBO_SP_PostTransactionNotice**.  The following SQL statements illustrate what needs to be added to the procedure. 
  
Line 29: Line 34:
  
   * //YourTargetVariable// is the variable name expected in the Bizweaver workflow.   * //YourTargetVariable// is the variable name expected in the Bizweaver workflow.
-    * See **//[[bw:using_variables|Using Variables]]//** for more information.+    * See **//[[bw2:using_variables|Using Variables]]//** for more information.
  
   * //@list_of_cols_val_tab_del// is a standard variable defined by SAP.   * //@list_of_cols_val_tab_del// is a standard variable defined by SAP.
Line 37: Line 42:
     * Use HTTP:// or HTTPS:// as appropriate for your installation.     * Use HTTP:// or HTTPS:// as appropriate for your installation.
  
-  * //@wsAuthToken// is the web service token defined in **//[[bw:bizweaver_general_settings|Bizweaver General Settings]]//**.+  * //@wsAuthToken// is the web service token defined in **//[[bw2:bizweaver_general_settings|Bizweaver General Settings]]//**.
  
   * //@wsTaskId// is the ID number of the Bizweaver workflow being called.   * //@wsTaskId// is the ID number of the Bizweaver workflow being called.
bw2/call_bizweaver_from_sql.1608050722.txt.gz · Last modified: 2020/12/15 11:45 by akoehler

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki