For certain operations, especially for each kind of material entry or item change, the SBO Data-API is required. Thus Beas can get terminated for certain actions.
Beas connects with the DI API in two different ways:
Beas - Standalone
Beas connects with the help of user names and when there is no SAP user, it uses the password/user name that is stored in the configuration wizard. (See: Configuration wizard - System)
If one does NOT log in as a SBO-user, a DI API logon can be performed if necessary, e.g for material movement, item changes etc.
SBO - Environment: Beas connects using a reference that is provided by the SAP UI-API
Problems with DI-API can have various effects, for example: issue material: API-Connect-Error ue_fert_tools...
issue material: DI-API-Problem: You have not enough rights (...)
Error calling external object function getbusiness object
The user needs in Beas the same rights as in SBO. If the user has no right to copy items or to do material postings in SBO, this is also not possible in Beas, because functions of SBO are used. Problems can arise in case of time receipts, when journal entries need to be created. The authorizations in SBO are required. For additional information see alternative DI-API-connection, user Administration
(in case of connection problems and other error Messages)
|Symptom||What to do|
|Beas does not start within SAP environment: various error messages, license errors,
Program crashes ...
|restart PC in secured mode as administrator
(In domain: use domain Administrator)
|Windows authorizations not sufficient||
Set user account control to "low"
|Insufficient data access on data base server||Test data base access with Administrator account|
|Error 2038: Deadlock problems||A 2038-problem can occur if too many documents are created at the same time, the network is not working well, clients or server are to slow
If you found no solution, think about switching to WEB apps, because there every transaction is performed on the Server
Error message -119 "database type not supported"
|Problems with the DI-API-Installation
- current version installed?
When using Terminal-Servers
Also see SAP messages: Search for "b1-local-machine" or "UAC"
Error -119, -126, -129,-131
|Problems with License files
(-119) database type not supported)
delete or rename the file b1-local-machine.xml on the local machine
cd "C:\Program Files (x86)\SAP\SAP Business One DI API\Conf"
cd "C:\Program Files (x86)\SAP\SAP Business One\Conf"
Message number 1658707, 2015784 and Ticket 000109194620140120025231
|Error -131||(-131) Connection to license server failed.
If license server address is invalid, correct it; if TAO NT Naming Service stopped, activate it and restart License Manager
The license-server runs usually on port:30000. It may be necessary to enter it again.
update [SBO-COMMON].[dbo].[SLIC] set LSRV=N'SQLSERVER:30000'
|there is no disk in the drive. please insert disk into drive e:||
Uninstall SAP DI-API and re-install
Work around: create drive or directory. Currently the reason is unknown
|-1116 could not commit transaction error 1 detected during transaction" (AITM)||Problem is difference UDF between table OITM and AITM
Check the UDF Fields between OITM and AITM. Delete all fields from OITM which you don't need, change other
|Error in table SLSP, SLSSP||
a) Check, if current Database user have access to the SBO COMMON Table (Error: Table SLSP is empty or not accessible. Please check that current DB user has enought rights over )
b) Delete all entries of table SLSP and SLSPP in SBOCOMMON. Restart integration service. In SAP Business refresh the company list.
|Could not commit transaction: Error -1 detected during transaction '' (AITM)||
Problem can be a reason with UDF difference between OITM and AITM. Delete all UDF's, which do you not need. If this not solve your problem, check the structure of both tables (only the UDF Fields) and fix length and type, if you find a difference.
If the problem has not been solved, the DTW seem no to work. Please refer to your partner or directly to SAP.
If the problem occurs only at one work station: check, if Windows needs to be re-installed or replace the PC, please regard Hardware requirements
If it is possible to connect with DTW but not with Beas and if all the above-mentioned attempts have been made, then the problem must be investigated further by the Beas support team.
SBOCOMMON, SLSP, SLSPP