SAP BAL_DSP_TXT_ALTCODE_READ Function Module for Application Log: Display: Read transaction code text
BAL_DSP_TXT_ALTCODE_READ is a standard bal dsp txt altcode read 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: Display: Read transaction code text 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 txt altcode read FM, simply by entering the name BAL_DSP_TXT_ALTCODE_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBAL_TXT
Program Name: SAPLSBAL_TXT
Main Program: SAPLSBAL_TXT
Appliation area: S
Release date: 26-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BAL_DSP_TXT_ALTCODE_READ 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_TXT_ALTCODE_READ'"Application Log: Display: Read transaction code text.
EXPORTING
* I_LANGU = SY-LANGU "Language
I_TCODE = "Transaction code
IMPORTING
E_TEXT = "Text
IMPORTING Parameters details for BAL_DSP_TXT_ALTCODE_READ
I_LANGU - Language
Data type: TSTCT-SPRSLDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
I_TCODE - Transaction code
Data type: TSTCT-TCODEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BAL_DSP_TXT_ALTCODE_READ
E_TEXT - Text
Data type: COptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAL_DSP_TXT_ALTCODE_READ 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_e_text | TYPE C, " | |||
| lv_i_langu | TYPE TSTCT-SPRSL, " SY-LANGU | |||
| lv_i_tcode | TYPE TSTCT-TCODE. " |
|   CALL FUNCTION 'BAL_DSP_TXT_ALTCODE_READ' "Application Log: Display: Read transaction code text |
| EXPORTING | ||
| I_LANGU | = lv_i_langu | |
| I_TCODE | = lv_i_tcode | |
| IMPORTING | ||
| E_TEXT | = lv_e_text | |
| . " BAL_DSP_TXT_ALTCODE_READ | ||
ABAP code using 7.40 inline data declarations to call FM BAL_DSP_TXT_ALTCODE_READ
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.| "SELECT single SPRSL FROM TSTCT INTO @DATA(ld_i_langu). | ||||
| DATA(ld_i_langu) | = SY-LANGU. | |||
| "SELECT single TCODE FROM TSTCT INTO @DATA(ld_i_tcode). | ||||
Search for further information about these or an SAP related objects