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.
Functionality
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 an 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
Effects
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
Lacking authorizations
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 the 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
Troubleshooting
(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, | Restart PC in secured mode as administrator |
Program crashes ... | (In domain: use domain Administrator) |
Windows authorizations are not sufficient | Set user account control to "low" |
Insufficient data access on the database server | Test database access with an 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 servers are too slow |
Action: | |
- Check SQL-Server: memory usage, SQL-load, etc. | |
- Check client (vie station settings): enough memory, enough disk space | |
- Backup: did a problem arise during a backup? | |
- Was the database blocked by another user See standstill | |
If you found no solution, think about switching to WEB apps, because there every transaction is performed on the Server | |
Problems with the DI-API-Installation | |
Error message -119 "database type not supported" | - Current version installed? |
- Start Beas without SAP B, click "options" on the login screen, check settings under "driver". The connection type to DI-API is set up here | |
- SAP 8.82: delete DI-API-directory (see above) | |
- Delete license-help files (see error 126) | |
- Start with extended authorization control (see Windows-authorization not sufficient) | |
When using Terminal-Servers | |
- the Remote station requires access to the %temp%-directory. There logon data is stored. That is why the directory may not be deleted after logoff. Please check terminal settings | |
Also, see SAP messages: Search for "b1-local-machine" or "UAC" | |
Problems with License files | |
Error -119, -126, -129,-131 | (-119) Database type not supported) |
(-126) Invalid license server address | |
(-129) Connection with license server failed | |
(-131) Connection to the license server failed | |
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" | |
Rename b1-local-machine.xml b1-local-machine_org.xml | |
Cd "C:\Program Files (x86)\SAP\SAP Business One\Conf" | |
Xcopy b1-local-machine.xml "C:\Program Files (x86)\SAP\SAP Business One DI API\Conf" /Y | |
Message number 1658707, 2015784 and Ticket 000109194620140120025231 | |
Error -131 | (-131) Connection to the license server failed. |
If the license server address is invalid, correct it; if TAO NT Naming Service stopped, activate it and restart License Manager | |
Note | |
At various SAP-Update this information is deleted. It is saved in the table | |
[SBO-COMMON].dbo.SLIC.LSRV | |
The license-server runs usually on port:30000. It may be necessary to enter it again. | |
Example | |
If Servername = "SQLSERVER" and default port 30000 was not changed, use the following script for correction: | |
Update [SBO-COMMON].[dbo].[SLIC] set LSRV=N'SQLSERVER:30000' | |
There is no disk in the drive. please insert a disk into drive e: | Uninstall SAP DI-API and re-install. |
Workaround: create drive or directory. Currently, the reason is unknown | |
-1116 could not commit transaction error 1 detected during transaction" (AITM) | The problem is the difference UDF between table OITM and AITM |
Check the UDF Fields between OITM and AITM. Delete all fields from OITM that you don't need, change other | |
Error in table SLSP, SLSSP | a) Check, if the current Database user has access to the SBO COMMON Table (Error: Table SLSP is empty or not accessible. Please check that the current DB user has enough 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) | The problem can be a reason with UDF difference between OITM and AITM. Delete all UDF's, which do you not need. If this does 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 seems not 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.
TAG:
SBOCOMMON, SLSP, SLSPP
Comments
0 comments
Please sign in to leave a comment.