SAP BAL_DSP_OUTPUT_SET_DATA Function Module for Application Log: Subscreen output: Set output data

Search SAP Function Modules

BAL_DSP_OUTPUT_SET_DATA is a standard bal dsp output set data 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: Subscreen output: Set output data 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 dsp output set data FM, simply by entering the name BAL_DSP_OUTPUT_SET_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBAL_DISPLAY
Program Name: SAPLSBAL_DISPLAY
Main Program: SAPLSBAL_DISPLAY
Appliation area: S
Release date: 26-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAL_DSP_OUTPUT_SET_DATA 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_DSP_OUTPUT_SET_DATA'"Application Log: Subscreen output: Set output data
  EXPORTING
*  I_T_LOG_HANDLE =  "Restrict display by log handle
*  I_T_MSG_HANDLE =  "Restrict display by message handle
*  I_S_LOG_FILTER =  "Restrict display by log filter
*  I_S_MSG_FILTER =  "Restrict display by message filter
*  I_T_LOG_CONTEXT_FILTER =  "Restrict display by log context filter
*  I_T_MSG_CONTEXT_FILTER =  "Restrict display by message context filter
*  I_SRT_BY_TIMSTMP = ' ' "Sort Logs by Timestamp ('X') or Log Number (' ')

 IMPORTING
   E_NO_DATA_AVAILABLE =  "No data found
   E_NO_AUTHORITY =  "No authorization

EXCEPTIONS
   INTERNAL_ERROR = 1    PROFILE_INCONSISTENT = 2 

.

IMPORTING Parameters details for BAL_DSP_OUTPUT_SET_DATA

I_T_LOG_HANDLE - Restrict display by log handle

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

I_T_MSG_HANDLE - Restrict display by message handle

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

I_S_LOG_FILTER - Restrict display by log filter

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

I_S_MSG_FILTER - Restrict display by message filter

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

I_T_LOG_CONTEXT_FILTER - Restrict display by log context filter

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

I_T_MSG_CONTEXT_FILTER - Restrict display by message context filter

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

I_SRT_BY_TIMSTMP - Sort Logs by Timestamp ('X') or Log Number (SPACE)

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

EXPORTING Parameters details for BAL_DSP_OUTPUT_SET_DATA

E_NO_DATA_AVAILABLE - No data found

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

E_NO_AUTHORITY - No authorization

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

EXCEPTIONS details

INTERNAL_ERROR - Internal data formatting error

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

PROFILE_INCONSISTENT - Inconsistent display profile

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAL_DSP_OUTPUT_SET_DATA 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_DSP_OUTPUT_SET_DATA

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