SAP Reading SLG1 is registered in the client program

I am developing a Gateway and Proxy interface for modifying SAP hardware data. In order to have an idea of ​​what is happening with the data that comes in, I registered the data with the help of functional modules BAL_*. It works great, it has been useful so far.

In the end, although we are going to have end users who work exclusively through the web interface and will not have access to the SAP GUI. They cannot use a transaction SLG1. Thus, I was asked to create a gateway object so that our third-party developers could make a beautiful view for messages from the journal. I have already noticed that a descriptor is created for each log, for example, something similar to 051MjXRE7jMmdAR2X6GWoW. I have established a connection between each run and each descriptor.

I have a lot of googled and called by a functional group BAL_DSP_LOG_DISPLAY, as well as other functions BAL_*like BAL_LOG_EXISTetc. No matter which of these functions I use, they all continue to report that the log does not exist (and then in brackets not found in memory). I also did not find an example of using these functions outside of its first creation, and then immediately showing it. I assume that the log has just been created, the data is already in memory and can simply be displayed.

However, I cannot do this. Most of the calls made for this interface are asynchronous, and I cannot send a message to the client, and there is no SAP GUI. Also, digging into the functions and returning a macro that checks the memory, I found that it apparently does, well, nothing.

Macro Function within the BAL Function Group

Boot function that does nothing

-, , , ? , , , , - .

+4
2

.

, " " (BAL_S_LOG-EXTNUMBER) , .

, , - BAL_DB_SEARCH BAL_DB_LOAD. SZAL - . SBAL_DEMO_05 .


: FORM load (-) SBAL, ASSIGN , . , .

+7

DB, BALHDR BALDAT. BALHDR LOG_HANDLE, .
- APPL_LOG_READ_DB FM. , , .

+1

Source: https://habr.com/ru/post/1625481/


All Articles