This is an old revision of the document!
Table of Contents
Calling Bizweaver from SAP Business One
Some special program code, provided by Third Wave Business Systems, is required for this functionality to work. Configuration of the special code is described 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.
There are limitations associated with calling 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: Triggering Workflows from SAP Business One via Direct Communication
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 statements can be added by using copy/paste from here.
- You can enter this same SQL code set for as many objects as you need to monitor.
- You can also test what type of transaction has been posted (Add, Update, etc.).
The Bizweaver call can only be made using a POST transaction.
Procedure Variables
/* Static variables for Bizweaver web service call - Start */ DECLARE @Arguments nvarchar(100) /* Static variables for Bizweaver web service call - End */
- This variable only needs to be defined once within the SBO_SP_PostTransactionNotice procedure.
- @object_type is a standard variable defined by SAP.
- It represents the type of transaction being processed.
- The 'X' in the examples is replaced with the appropriate ID number.
- It is always enclosed in single quotes.
- YourTargetVariable is the variable name expected in the Bizweaver workflow.
- See Using Variables for more information.
- @list_of_cols_val_tab_del is a standard variable defined by SAP.
- It generally represents the primary key of the transaction being processed.
- YourURL is the URL that points to your Bizweaver installation.
- Use HTTP: or HTTPS: as appropriate for your installation.
- @wsAuthToken is the web service token defined in Bizweaver General Settings.
- @wsTaskId is the ID number of the Bizweaver workflow being called.
- @wsPort is the port number used for your Bizweaver web service.
- 443 is the standard for HTTPS installations.
- 80, 8080, 8081, 8090 are examples of ports typically used in HTTP installation.
Calling Bizweaver Using POST
IF @object_type = 'X' BEGIN SET @Arguments = '{"YourTargetVariable":' + '"' + @list_of_cols_val_tab_del + '"' + '}' EXECUTE [dbo].[spCallBizweaverWS] @wsMethod='POST' -- add your URL. Be sure to use http or https as appropriate. ,@wsURL='https://YourURL' ,@wsContent='application/json' -- Add your Auth Token from Bizweaver ,@wsAuthToken='xyxyxyxyxyxyxyxyx' -- Add your workflow ID from Bizweaver ,@wsTaskId='999' ,@wsStartAfter='' ,@wsParameters= @Arguments -- Add your port number ,@wsPort='443' END
