Database Interface


Save logs in the database (function module BAL_DB_SAVE)

You can save logs in memory with the function module BAL_DB_SAVE. It can save all memory data in the database (importing parameter I_SAVE_ALL = 'X'). You can also specify a subset as a set of log handles (importing parameter I_T_LOG_HANDLE).

When you save logs, an internal log number is specified (field LOGNUMBER). At runtime this field has a temporary value (e.g. $00001).

The function module BAL_DB_SAVE returns a table (exporting parameter E_NEW_LOGNUMBERS), which matches LOG_HANDLE, external number EXTNUMBER, temporary LOGNUMBER and permanent LOGNUMBER. You can find out which number was assigned to a log, after saving.

You can save IN UPDATE TASK (importing parameter I_IN_UPDATE_TASK = 'X').

Find logs in the database (function mod. BAL_DB_SEARCH)

You can find logs in the database with the function module BAL_DB_SEARCH.

You pass the log header filter criteria (structure BAL_S_LFIL), and a table of log headers (structure BALHDR) which satisfy the criteria is returned. You can pass this to the function module BAL_DB_LOAD, which loads these logs into memory.

Load logs from the database (function module BAL_DB_LOAD)

You can load logs from the database with the function module BAL_DB_LOAD. You can specify which logs are to be loaded in memory in various ways:

    Log handle table
    Internal log number table
    Log header (return values from function module BAL_DB_SEARCH) table

Delete logs from the database (function module BAL_DB_DELETE)

The function module BAL_DB_DELETE deletes logs from the application. As in the function module BAL_DB_LOAD you can specify the set of logs to be deleted by log handles, log numbers or log headers.

Save can also be in UPDATE TASK as in function module BAL_DB_SAVE.