Accessing SAP Business One using the Service Layer is a two-step process. The first step (Login) responds with two cookies. These cookies are then used in any subsequent web service calls in the current processing cycle.

The difference in Bizweaver v2.5 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.

• Select SAP Service Layer in the “Select Service” drop-down list.
• Select Authenticate in the next drop-down to the right.
• Select the Authentication Required checkbox.
• Select your previously defined Service Layer connection in the “Select Connection” drop-down.
• Click the Validate Login link to confirm that your connection is working. If the response is not True, check your connection information and try again.

Once the workflow has completed a successful login, the remaining steps will use the Interact With Data option.

• Select SAP Service Layer in the “Select Service” drop-down list.
• Select Interact With Data in the next drop-down to the right.
  • No other information is needed in this section as the Login step has provided the needed credentials.
• Enter the SAP Business One Object with which you want to work in the Construct URI field. Enter this information at the end of the pre-populated string, including the “/” before the object as shown in the image above.
• Select the desired interaction method from the Method drop-down list. The most common methods used in SAP Business One will be Get, Post, Patch, and Delete

https://<YourServerName>:50000

• Enter the Content Type as

  application/json

  for all Service Layer transactions.

The above image is shown for information only. It illustrates the cookies variables that used as credentials to interact with SAP Business One. The cookies will created in the initial Login step.

Information on sending data through the Service Layer is found here.

This workflow builds two sections of a JSON structure for an SAP Business One sales order. The sections are the header and the rows. Each section consists of a SQL statement to gather the needed information and the DataBuilder to format the information. Once the pieces are constructed, the output is sent to the SAP Service Layer API in the WebService step. Other APIs will work in a similar manner.

This should always contain the first items of the data structure.

1. Enter a workflow step name.
2. Select the data source from the Datasource Object drop-down list.
3. Select the desired data structure type to be created (JSON or XML).
4. Leave the “Add as an array” checkbox cleared unless you know that the top-level object needs to be any array. This is uncommon.
5. Select the “Top-level element” checkbox, assuming this is the top level (header) node of the structure.
   1. This option causes the “CumulativeData” step-variable to be cleared before starting to build a new structure.
6. Enter the name of the top-level object.
   1. The requirements of the receiving API will determine this.
   2. In some cases, a top-level object name is not used; e.g. SAP Service Layer and BigCommerce.
      1. If a top-level object name is not used, leave the field blank.
7. Create a row for each value to be included in the structure.
8. Enter the output field name values in the right-side grid.
   1. The Field Name value will need to exactly match (including case) the value the API is expecting.
9. Select the field type from the drop-down list.
10. Press <F4> to get a list of variables from the associated Datasource Object and select the appropriate value.

Continue this process for all desired fields in the top-level object.

The data structure being built is displayed in the left-side panel as elements are added. The data structure cannot be altered in this area. The display is for information only.

This will be the next section in the expected data structure. The process is the same as described in the “Main DataBuilder” step.

For objects such as a set of rows, the display will only display a single entry. However, all data received as input will be included when the workflow executes.

All objects other than the main one will require an Object Name. This must exactly match (including case) what is expected by the API.

Once the DataBuilder steps for the lower-level objects have been created, they can be referenced in the main DataBuilder step. This is what causes the entire data structure to be created when the workflow is executed.

1. Click the “Field Type” drop-down in the main DataBuilder step. The names of the lower-level objects are displayed in addition to the standard field type values.
2. Select the desired object.
   1. The Field Name and Value are automatically filled in.
   2. The lower-level object is displayed in the left-side data structure.

Here is the resulting JSON that is sent in the API call.

{
"CardCode": "C20000",
"DocDueDate": "20190313",
"DocumentLines": [
{
"ItemCode": "A00001",
"Quantity": 9,
"LineTotal": 33.75
},
{
"ItemCode": "A00001",
"Quantity": 7,
"LineTotal": 105
}
],
"AddressExtension": [
{
"CItyB": "New York"
}
]
}

The output of the main DataBuilder step is used in the API call. This is done by using the “CumulativeData” variable from the Main DataBuilder step. An example is shown in the image below.

Information on sending data through the Service Layer is found here.