Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Working with the Service Layer • SAP Business One Service Layer using Bizweaver v2.5
bw2:sap_business_one_integration_using_di

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
bw2:sap_business_one_integration_using_di [2021/07/19 17:03]
akoehler 		bw2:sap_business_one_integration_using_di [2022/08/02 16:45] (current)
akoehler
Line 369: Line 369:
   - Map the needed information in a Mapper step. \\ {{ :bw2:bizweaverdi16.png |}} \\ 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. \\ {{ :bw2:bizweaverdi16.png |}} \\ 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). The key value is //DocEntry//.   - 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). 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|
bw2/sap_business_one_integration_using_di.1626728598.txt.gz · Last modified: 2021/07/19 17:03 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