

Check SQL-Server: memory usage, SQL-load etc. Test data base access with Administrator accountĪ 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 Insufficient data access on data base server Restart PC in secured mode as administrator (in case of connection problems and other error Messages) Symptomīeas does not start within SAP environment: various error messages, license errors, For additional information see alternative DI-API-connection, user Administration Problems can arise in case of time receipts, when journal entries need to be created.

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. The user needs in Beas the same rights as in SBO. Issue material: DI-API-Problem: You have not enough rights (.)Įrror calling external object function getbusiness object Problems with DI-API can have various effects, for example: issue material: API-Connect-Error ue_fert_tools. SBO - Environment: Beas connects using a reference that is provided by the SAP UI-API 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. Thus Beas can get terminated for certain actions.īeas connects with the DI API in two different ways:īeas 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. For certain operations, especially for each kind of material entry or item change, the SBO Data-API is required.
