SAP BAL_ARCHIVE_LOAD Function Module for Application Log: Archive: Load Logs

Search SAP Function Modules

BAL_ARCHIVE_LOAD is a standard bal archive load SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Application Log: Archive: Load Logs processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for bal archive load FM, simply by entering the name BAL_ARCHIVE_LOAD into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBAL_DB
Program Name: SAPLSBAL_DB
Main Program: SAPLSBAL_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAL_ARCHIVE_LOAD pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'BAL_ARCHIVE_LOAD'"Application Log: Archive: Load Logs
  EXPORTING
   I_S_ARCDATA =  "Application Log: Log header data table
*  I_EXCEPTION_IF_ALREADY_LOADED =  "Boolean Variable (X=true, -=false, space=unknown)
*  I_DO_NOT_LOAD_MESSAGES =  "

 IMPORTING
   E_T_LOG_HANDLE =  "Application Log: Log Handle Table
   E_T_MSG_HANDLE =  "Application Log: Message Handle Table

EXCEPTIONS
   NO_LOGS_SPECIFIED = 1    LOG_NOT_FOUND = 2    LOG_ALREADY_LOADED = 3 

.

IMPORTING Parameters details for BAL_ARCHIVE_LOAD

I_S_ARCDATA - Application Log: Log header data table

Data type: BAL_S_ARCDATA
Optional: No
Call by Reference: No ( called with pass by value option)

I_EXCEPTION_IF_ALREADY_LOADED - Boolean Variable (X=true, -=false, space=unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

I_DO_NOT_LOAD_MESSAGES -

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BAL_ARCHIVE_LOAD

E_T_LOG_HANDLE - Application Log: Log Handle Table

Data type: BAL_T_LOGH
Optional: No
Call by Reference: Yes

E_T_MSG_HANDLE - Application Log: Message Handle Table

Data type: BAL_T_MSGH
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_LOGS_SPECIFIED - No logs specified

Data type:
Optional: No
Call by Reference: Yes

LOG_NOT_FOUND - Log not found

Data type:
Optional: No
Call by Reference: Yes

LOG_ALREADY_LOADED - Log is already loaded

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAL_ARCHIVE_LOAD Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM BAL_ARCHIVE_LOAD

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects