SAP BAL_DSP_PRINT_TEXTFORM Function Module for
BAL_DSP_PRINT_TEXTFORM is a standard bal dsp print textform SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 print textform FM, simply by entering the name BAL_DSP_PRINT_TEXTFORM into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBAL_DISPLAY
Program Name: SAPLSBAL_DISPLAY
Main Program: SAPLSBAL_DISPLAY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAL_DSP_PRINT_TEXTFORM 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_PRINT_TEXTFORM'".
EXPORTING
I_LOG_HANDLE = "
* IS_PRINT_PARAMETERS = "
IMPORTING
E_SPOOL_NUMBER = "
EXCEPTIONS
LOG_NOT_FOUND = 1 PRINT_ERROR = 2
IMPORTING Parameters details for BAL_DSP_PRINT_TEXTFORM
I_LOG_HANDLE -
Data type: BALLOGHNDLOptional: No
Call by Reference: No ( called with pass by value option)
IS_PRINT_PARAMETERS -
Data type: PRI_PARAMSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAL_DSP_PRINT_TEXTFORM
E_SPOOL_NUMBER -
Data type: SYSPONOOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOG_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
PRINT_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAL_DSP_PRINT_TEXTFORM 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.DATA: | ||||
lv_i_log_handle | TYPE BALLOGHNDL, " | |||
lv_log_not_found | TYPE BALLOGHNDL, " | |||
lv_e_spool_number | TYPE SYSPONO, " | |||
lv_print_error | TYPE SYSPONO, " | |||
lv_is_print_parameters | TYPE PRI_PARAMS. " |
  CALL FUNCTION 'BAL_DSP_PRINT_TEXTFORM' " |
EXPORTING | ||
I_LOG_HANDLE | = lv_i_log_handle | |
IS_PRINT_PARAMETERS | = lv_is_print_parameters | |
IMPORTING | ||
E_SPOOL_NUMBER | = lv_e_spool_number | |
EXCEPTIONS | ||
LOG_NOT_FOUND = 1 | ||
PRINT_ERROR = 2 | ||
. " BAL_DSP_PRINT_TEXTFORM |
ABAP code using 7.40 inline data declarations to call FM BAL_DSP_PRINT_TEXTFORM
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