Throughout this page, SAP Business One would be referred to as SAP and Microsoft SQL Server would be abbreviated to MSSQL.
HSBC_IDS supports the version of SAP relies on Microsoft SQL Server to store data entered. In order for the HSBC_IDS application to retrieve data a connection to the datasource (MSSQL) is required, some IT assistance may be required to acquire these.

Please follow steps below to configure your SAP company to the HSBC_IDS application.
Click each step below for a pictorial view

Now that the application is installed please double click the HSBC_IDS desktop shortcut. The HSBC_IDS may attempt to automatically detect which software you have installed - if SAP is installed on the Server/PC you may have to select Sap Business One from a list. As detailed in the HSBC_IDS check List section above, particular Microsoft SQL Server (MSSQL) credentials are required to connect successfully. SQL Server name (and instance name if any): This is the Server name that MSSQL is installed on within your network. In addition the instance name should be known. If any of these are unknown, please open SAP and go to Administrator > Choose Company. The Server name is the second drop down field under 'Current Server' - see example in Orange adjacent. User / Password: These must be SQL Server authenticated logon details and not Windows Credentials. A default 'sa' user can be used to connect, alternatively a Read Only user can be used (or created) against the SAP Company database and SBO-COMMON database. Database Name: If unknown this can be found in the "Choose Company" screen, please see Green box adjacent. Click 'Test Connection' when the form is complete. The connection would successful if all credentials are correct and will prompt which is incorrect. A connection is now successful to your Company, data can be retrieved. Click the 'Extract' button to submit your first data load.

Your HSBC_IDS application may be setup to retrieve data automatically at a predefined schedule, this functionality relies to be logged on at the scheduled time. Due to the nature of Servers, it may rarely be logged into. So if the HSBC_IDS application is installed on a Server, extractions may not always perform automatically. To enable this feature a task scheduler would have to be created.
To create a task scheduler please go to the installation path of HSBC_IDS, usually held in C:\HSBC_IDS_xxx\ Open the taskSchedule.bat file and follow the instructions.

An MSSQL user can be created dedicated to the HSBC_IDS application. This user should be created and mapped to the desired database with db_readonly rights as a minimum requirement.
Click each step below for a pictorial view

Open Microsoft SQL Management Studio and connect to the Database Engine. Now expand the Security folder in the Object Explore and right-click Logins to create a New Login. Within the General page please create a username with SQL Server Authentication Remove the defaulted Enforced password policy (so the user doesn't expire). Now navigate to the User Mapping page to give the user rights to the database. Tick the database name in the top half panel, and give the user db_readonly rights (as a minimum requirement) in the bottom half panel.

If this error appears the Server isn�t able to be located. This could be due to a number of reasons.

• The server might be turned off
• The server may not be on the same network as the same PC HSBC_IDS is running from
• The PC HSBC_IDS is running from may not have access to that server
• The server may have an instance that the database (that SAP is using) is located on.
• The server may be using a different TCP/IP
• There might be spelling error

Please check the SAP server name, more info in Step 2 above.

If the error below appears, the SQL Server instance name is incorrect or doesn't exist. Please check the SAP server name/instance name, more info in Step 2 above

If this error appears the SQL Server user/password is incorrect.

IT assistance may be required with this type of error.

This error could mean the Database name has been entered incorrectly, or the SQL user doesn't have read permissions to this database. IT assistance may be required with this type of error.