This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bw2:call_bizweaver_from_sql [2020/12/15 11:46] akoehler [Procedure Variables] |
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 **// | Some special program code, provided by Third Wave Business Systems, is required for this functionality to work. Configuration of the special code is described **// | ||
| </ | </ | ||
| + | <WRAP center round important> | ||
| + | 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: | ||
| + | </ | ||
| The call to the Bizweaver web service is initiated from the standard SAP Business One Stored Procedure **SBO_SP_PostTransactionNotice**. | The call to the Bizweaver web service is initiated from the standard SAP Business One Stored Procedure **SBO_SP_PostTransactionNotice**. | ||