DX_RUN_GET_BALLOG SAP Function module

DX_RUN_GET_BALLOG is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DX_RUN_GET_BALLOG into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: DX_RUN
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM DX_RUN_GET_BALLOG - DX RUN GET BALLOG

CALL FUNCTION 'DX_RUN_GET_BALLOG' "
  EXPORTING
    project =                   " dxrun-project
    subproject =                " dxrun-subproject
    rundef =                    " dxrun-rundef
    runid =                     " dxrun-runid
  IMPORTING
    log_handles =               " bal_t_logh    Application Log: Log Handle Table
    log_headers =               " balhdr_t      Application Log: Log header data table
  EXCEPTIONS
    ERROR_WITH_BALLOG = 1       "
    NO_AUTHORITY = 2            "
    .  "  DX_RUN_GET_BALLOG

ABAP code example for Function Module DX_RUN_GET_BALLOG

The ABAP code below is a full code listing to execute function module DX_RUN_GET_BALLOG including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_log_handles  
 
 TYPE BAL_T_LOGH
,
ld_log_headers  
 
 TYPE BALHDR_T
.

 

SELECT single PROJECT 
  FROM DXRUN 
  INTO @DATA(ld_project).

 

SELECT single SUBPROJECT 
  FROM DXRUN 
  INTO @DATA(ld_subproject).

 

SELECT single RUNDEF 
  FROM DXRUN 
  INTO @DATA(ld_rundef).

 

SELECT single RUNID 
  FROM DXRUN 
  INTO @DATA(ld_runid).

.

CALL FUNCTION 'DX_RUN_GET_BALLOG'
  EXPORTING
    project =                    ld_project
    subproject =                 ld_subproject
    rundef =                     ld_rundef
    runid =                      ld_runid
  IMPORTING
    log_handles =                ld_log_handles
    log_headers =                ld_log_headers
  EXCEPTIONS
    ERROR_WITH_BALLOG =          1
    NO_AUTHORITY =               2
    .  "  DX_RUN_GET_BALLOG

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_log_handles
 
 TYPE BAL_T_LOGH ,
ld_project
 
 TYPE DXRUN-PROJECT ,
ld_log_headers
 
 TYPE BALHDR_T ,
ld_subproject
 
 TYPE DXRUN-SUBPROJECT ,
ld_rundef
 
 TYPE DXRUN-RUNDEF ,
ld_runid
 
 TYPE DXRUN-RUNID .



SELECT single PROJECT 
  FROM DXRUN 
  INTO ld_project.


SELECT single SUBPROJECT 
  FROM DXRUN 
  INTO ld_subproject.


SELECT single RUNDEF 
  FROM DXRUN 
  INTO ld_rundef.


SELECT single RUNID 
  FROM DXRUN 
  INTO ld_runid.