Before getting started, you must first create and define an OData service to connect to SAP B1 HANA. This method creates the service in SAP HANA extended application services (SAP HANA XS Classic) using SAP HANA Studio. The complete service is comprised of tables, views, and an xsodata document in which the service is defined.
Note: The scripts provided by Solver are basic views written in SQL. The schemas defined in the view scripts use the “SBODEMOUS” demo company. They will need to be changed using your company’s schema before they can be deployed in your database. Simply do a “Search and Replace” to set them to match your company’s database schema in each individual script.
- Begin by saving the scripts in your Linux file system. Then, launch SAP HANA Studio.
- From within your company database schema, open and execute each of the view scripts. If you are using the scripts provided by Solver, be sure to run the script named ‘BI360_Account_Period’ first, then ‘BI360_Dims’ second. The rest are potentially optional depending on which SAP Business One modules you use. The optional views are mainly organized by module and can be run in any order.
- To open a script, click File –> Open File…and navigate to the script.
- Then click the ‘Choose Connection’ icon in the upper right and select the proper connection.
- Then click on the green arrow in the upper right to execute the script or press the (F8) key. Check the message pane to be sure each script runs successfully. You can also expand and refresh the Views folder to verify successful creation of the views.
- To add your own custom views to an OData service, begin creating the view by right-clicking on the ‘Views’ folder.
- Use the following syntax to create a view as in this example.
create view <VIEW_NAME> as select “AcctCode” from OACT
- Run the script by clicking on the Execute button (green arrow in upper right hand section of the SQL Console window) or pressing (F8).
- If there are no errors, then a message confirming successful creation of the view displays in the message pane.
- Switching to the Development perspective shows the Project and Repository tabs.
- In the Repository tab, right-click on the schema name to create a new Repository Workspace.
- In the “Create New Repository Workspace” window, enter a name. Be aware that this name will be part of the URL endpoint. There is more information on this at the bottom of this page.
- After creating the Workspace, the next step is to create a new Repository Package. Begin by right-clicking on the Workspace and select NewàRepository Package.
- In the “Create Repository Package” window, enter in the “Package Name” field. This name will also be used in the URL. Click Next, then Finish.
- After creating the Repository Package, the next step is to create the xsodata document in which the service will be defined.
- Begin by expanding the workspace folder and the XSodata package below it.
- Right-click on the XSodata package, select Newà..
- Select XS OData File and begin the wizard by clicking Next>.
- Enter a File name, leave the template field blank, and click ‘Finish.’ Be aware that the file name you choose will be used in the URL of the service.
- A blank document is created into which the service can be defined.
The service is defined with the following syntax:
Tables and views can be placed in between the curly brackets.
- When exposing tables in the xsodata document, be sure to forbid create, update, and delete as shown to keep your data secure. However, this is not necessary for the views as they are read-only. Here is an example using the “VIEW_NAME” created earlier along with some sample tables.
- Right-click and save the changes.
- Right-click again and choose TeamàActivate to activate the service. The service will now be running.
The URL will be https://<host>:<port number>//XSOdata/<filename>.xsodata
The <repo name> is the name chosen when creating the repository workspace.
The <filename> is the one you chose when creating the xsodata document.
This completes the pre-configuration needed for Solver to connect to SAP Business One for HANA. When using the BI360 Cloud the username, password, security token, customer secret and customer key are all needed in order to log in. Salesforce REST API displays all available objects, and the access to the data is based on the security access of the user credentials being used in the BI360 Salesforce Connector.