This is an old revision of the document!
Accessing SAP Business One using the Service Layer is a two-step process. The first step (Log in) responds with two cookies. These cookies are then used in any subsequent web service calls in the current processing cycle.
Accessing SAP Business One via the Service Layer is available for HANA on v9.3 only. It is available for both HANA and SQL Server, beginning with SAP Business One v10 PL02.
The difference in Bizweaver v2.6 is that a Service Layer global connection can be used to manage much of the detail work. Configuring a Service Layer global connection is described here.
Once the workflow has completed a successful login, the remaining steps will use the Interact With Data option.
Note the lack of array name. The service layer tool will add the array name, so the only thing needed is the array data.
Add Cumulative data from the data builder step to Values field
More information on the various objects and methods is available on your HANA server using this URL in a browser on your network.
https://<YourServerName>:50000
Information on sending data through the Service Layer including attachments is found here.
This workflow builds one section of a JSON structure for an SAP Business One sales order. The section is just the rows as the header information will be entered into the Web Service step. Each section consists of a SQL statement to gather the needed information and the DataBuilder to format it. Once the pieces are constructed, the output is sent to the SAP Service Layer API in the WebService step. Other APIs will work similarly.
In this example, we are using the SQL/Tool to gather all the relevant header information. This will be entered directly into the WebService step using the SAP Service Layer Connector.
This will be the next section in the expected data structure needed by the SAP Service layer. The object name will not be entered as the SAP Service Layer Connector will provide when submitting the data.
Once the DataBuilder steps for the lower-level objects have been created, they can be referenced in the WebServices step. This is what causes the entire data structure to be created when the workflow is executed.