Differences

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

--- bw:sap_business_one_integration_using_di [2020/12/14 17:32]
akoehler old revision restored (2020/05/04 16:02)
+++ bw:sap_business_one_integration_using_di [2022/08/02 16:46] (current)
akoehler
@@ Line 33: / Line 33: @@
 To illustrate the SAP Business One integration process, we will use the following workflow. In this case, the source data is coming from database tables that are associated with a Versago form. (Versago is a Web/Mobile portal application from Third Wave). However, the same principles apply for any data source (e.g. flat files, etc.).
-{{:bw:sapimage.png?576x99}}
+{{  :bw:sapimage.png?576x99  }}
 The basic process is:
@@ Line 50: / Line 50: @@
 ===== Define Connections =====
-{{:bw:sapimage2.png?384x81}}
+{{  :bw:sapimage2.png?384x81  }}
   - Select a **DI** **Connection** to an SAP Business One database from the drop-down list.
@@ Line 70: / Line 70: @@
 Double-click on the object name to continue.
-{{:bw:sapimage3.png?222x136}}
+{{  :bw:sapimage3.png?222x136  }}
 ===== Select the Desired Command =====
@@ Line 78: / Line 78: @@
 Double-click on the command to continue.
-{{:bw:sapimage4.png?328x439}}
+{{  :bw:sapimage4.png?328x439  }}
 ===== Select the Desired Object Components =====
@@ Line 84: / Line 84: @@
 The “Object Components” are the elements of the document or transaction that will be used. Most SAP Business One objects have multiple components and you must know which ones are appropriate for your application. In most cases, you will need “Documents” and “Document_Lines” at a minimum. “Documents” is the header information and “Document_Lines” is the information in the rows grid in SAP Business One.
-{{:bw:sapimage5.png?359x282}}
+{{  :bw:sapimage5.png?359x282  }}
 Double-click on the desired object component to select it.
@@ Line 101: / Line 101: @@
 ==== Header Mapping Example ====
-{{:bw:sapimage6.png?384x224}}
+{{  :bw:sapimage6.png?384x224  }}
 ==== Row Detail Mapping Example ====
-{{:bw:sapimage7.png?384x255}}
+{{  :bw:sapimage7.png?384x255  }}
@@ Line 130: / Line 130: @@
 The **SBO Update** tool handles the communication between Bizweaver and the SAP Business One DI. This is the step that updates SAP Business One.
-{{:bw:sapimage8.png?475x166}}
+{{  :bw:sapimage8.png?475x166  }}
 Select a **Mapper** workflow step from the drop-down list.
@@ Line 199: / Line 199: @@
 Bizweaver will create DI Server schemas for SAP Business One User Defined Objects (UDO). For this process to work the UDO **name** assigned in the registration process cannot contain any spaces. If you have followed the instructions above and still don’t see the UDO, this is the first place to check.
-{{:bw:sapimage10.png?384x259}}
+{{  :bw:sapimage10.png?384x259  }}
 Be sure to follow the manual update process described above after making this change.
@@ Line 228: / Line 228: @@
 The Custom Output File Writer option must be used to create this type of file. In this example, we are using all three sections of the custom output. The Body section of the file contains the response from the SAP Business One DI.
-{{:bw:sapimage14.png?346x360}}
+{{  :bw:sapimage14.png?346x360  }}
 The values that are used in the Body section are shown below. Press F4 to get a list of all available variables.
@@ Line 266: / Line 266: @@
 ====== Versago Uploaded Files to SAP Business One Attachments ======
-A Versago form can be configured to allow the user to upload files as part of the transaction. It is possible, using Bizweaver, to use these files to create attachments in SAP Business One. The following section describes this process for two scenarios.
+A Versago form can be configured to allow the user to upload files as part of the transaction. It is possible, using Bizweaver, to use these files to create attachments in SAP Business One using DI Server only. The following section describes this process for two scenarios.
 Note: the SAP Business One object (Business Partner, Document, etc.) must exist before attachments can be applied.
@@ Line 308: / Line 308: @@
-{{:bw:sapimage15.png?576x87}}
+{{  :bw:sapimage15.png?576x87  }}
   - A list of unique file upload records (column “Id”) is obtained. In this example, the Versago form ID (ObjectId) is 11. \\ <code sql>select
@@ Line 323: / Line 323: @@
       - In this case the SAP Business One object receiving the attachment is a Business Partner.
       - The transaction for attachment will always be an UPDATE.
-      - The FileName and FileContent values are both mapped to the “AttachmentEntry” (AtcEntry) value in SAP Business One. \\ {{:bw:sapimage16.png?564x239}}
+      - The FileName and FileContent values are both mapped to the “AttachmentEntry” (AtcEntry) value in SAP Business One. \\ {{  :bw:sapimage16.png?564x239  }}
   - The mapped information is passed into the SAP Business One update tool for processing.
@@ Line 330: / Line 330: @@
 In this example, a Versago form is used to capture information to create a Purchase Order in SAP Business One. The order is created in SAP Business One, and then the attachments are associated with the new order.
-{{:bw:sapimage17.png?576x212}}
+{{  :bw:sapimage17.png?576x212  }}
   - A list of records created from the Versago form is created, and an SAP Business One purchase document is created for each one.
@@ Line 346: / Line 346: @@
       - In this case the SAP Business One object receiving the attachment is the purchase order created previously in the process and defined by the “DocEntry” value from step 2.
       - The transaction for attachment will always be an UPDATE.
-      - The FileName and FileContent values are both mapped to the “AttachmentEntry” (AtcEntry) value in SAP Business One. \\ {{:bw:sapimage18.png?384x202}}
+      - The FileName and FileContent values are both mapped to the “AttachmentEntry” (AtcEntry) value in SAP Business One. \\ {{  :bw:sapimage18.png?384x202  }}
   - The mapped information is passed into the SAP Business One update tool for processing.
@@ Line 362: / Line 362: @@
 The file to be attached must be identified as a Bizweaver //Variable// in the workflow. This will typically be done using a File Operations-Get step. The results of the “get” are then identified in a subsequent Variable step.
-  - File Operations – Get step to get file information. \\ {{:bw:sapimage19.png?384x192}} \\ In this example we are getting one file (TestFile.txt) from C:\Shared\Infiles.
+  - File Operations – Get step to get file information. \\ {{  :bw:sapimage19.png?384x192  }} \\ In this example we are getting one file (TestFile.txt) from C:\Shared\Infiles.
-  - Set variable to the value from the “get” step. \\ {{:bw:sapimage20.png?384x338}} \\ Note that the “FileName” value is used from the “get” step. This value includes the folder path, file name, and file extension.
+  - Set variable to the value from the “get” step. \\ {{  :bw:sapimage20.png?384x338  }} \\ Note that the “FileName” value is used from the “get” step. This value includes the folder path, file name, and file extension.
-  - Map the needed information in a Mapper step. \\ {{:bw:sapimage21.png?384x197}} \\ In this example we are adding an attachment to a Business Partner. The only values needed are the BP Code (CardCode) and the variable set earlier with the file information.
+  - Map the needed information in a Mapper step. \\ {{  :bw:sapimage21.png?384x197  }} \\ In this example we are adding an attachment to a Business Partner. The only values needed are the BP Code (CardCode) and the variable set earlier with the file information.
   - A subsequent SBOUpdate tool step is used to post the information to SAP Business One. \\ Any object in SAP Business One that supports attachments can be updated using the above process. You only need to provide the key value for the object and the file information. The two most common objects for attachments are Business Partners where the key value is //CardCode//, and Marketing documents (e.g. Orders, Deliveries/Receipts, Invoices) where the key value is //DocEntry//.
+====SAP Update Variables====
+^Name	^Description^
+|Message|This indicates the message returned from the DI API/DI Server interaction|
+|RetKey|This indicates the DocNum that is returned from the DI API/DI Server when a record is created|
+|RetType|This indicates the Document Type returned from the DI API/DI Server|
+|VALUE|This indicates if adding, updating, deleting etc. The record in SAP via the DI API/DI Server was successful with a Y = Yes and N = No|
+|Command|Command is type of operation, Add/Update/Delete/Getbykey etc|
+|FieldName|The indicates the Primary field name used for that object |
+|Input|This is for legacy versions of Bizweaver and no longer displays any data|
+|Output|This is for legacy versions of Bizweaver and no longer displays any data|
+|ProcessedCount|If performing bulk operations ex multiple records, then a number of processed records will be this. If we are looping through records|
+|ProcessInput|Currently processing record.|
+|ServiceName|This indicates the service name used in the mapper tool|
+|ServiceType|In the case of DI Server/ DIAPI, specify whether the object currently in process is a System object or User defined object|
+|ThrowErrorOnFail|True or False, When bulk operations are processing if one record fails this will stop all further processing if continue on error is selected it will process all other records that are left to process|
+|TotalCount	Total|count of all records if there is a bulk operation|
+|StepMessage|During a failure the reason for failure will be populated here|
+|StepStatus|True or False|

Wiki

User Tools

Site Tools

Differences

Page Tools