SAP K_LTXT_HANDLING Function Module for









K_LTXT_HANDLING is a standard k ltxt handling 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 k ltxt handling FM, simply by entering the name K_LTXT_HANDLING into the relevant SAP transaction such as SE37 or SE38.

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



Function K_LTXT_HANDLING 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 'K_LTXT_HANDLING'"
EXPORTING
LTEXT = "
L_AKTYP = "

IMPORTING
FLG_LTEXT_CHANGED = "

CHANGING
TXFLG_CHG = "
.



IMPORTING Parameters details for K_LTXT_HANDLING

LTEXT -

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

L_AKTYP -

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

EXPORTING Parameters details for K_LTXT_HANDLING

FLG_LTEXT_CHANGED -

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

CHANGING Parameters details for K_LTXT_HANDLING

TXFLG_CHG -

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

Copy and paste ABAP code example for K_LTXT_HANDLING 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_ltext  TYPE KKEK0_LTEXT, "   
lv_txflg_chg  TYPE XFLAG, "   
lv_flg_ltext_changed  TYPE XFLAG, "   
lv_l_aktyp  TYPE C. "   

  CALL FUNCTION 'K_LTXT_HANDLING'  "
    EXPORTING
         LTEXT = lv_ltext
         L_AKTYP = lv_l_aktyp
    IMPORTING
         FLG_LTEXT_CHANGED = lv_flg_ltext_changed
    CHANGING
         TXFLG_CHG = lv_txflg_chg
. " K_LTXT_HANDLING




ABAP code using 7.40 inline data declarations to call FM K_LTXT_HANDLING

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!