SAP POSTING_KEY_TEXT_GET Function Module for









POSTING_KEY_TEXT_GET is a standard posting key text get 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 posting key text get FM, simply by entering the name POSTING_KEY_TEXT_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVKE
Program Name: SAPLFVKE
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function POSTING_KEY_TEXT_GET 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 'POSTING_KEY_TEXT_GET'"
EXPORTING
* I_LANGU = SY-LANGU "
I_BSCHL = "
I_UMSKZ = "

IMPORTING
E_LTEXT = "

TABLES
* T_C_ERRORS = "

EXCEPTIONS
TEXT_NOT_FOUND = 1
.



IMPORTING Parameters details for POSTING_KEY_TEXT_GET

I_LANGU -

Data type: T002-SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BSCHL -

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

I_UMSKZ -

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

EXPORTING Parameters details for POSTING_KEY_TEXT_GET

E_LTEXT -

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

TABLES Parameters details for POSTING_KEY_TEXT_GET

T_C_ERRORS -

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

EXCEPTIONS details

TEXT_NOT_FOUND -

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

Copy and paste ABAP code example for POSTING_KEY_TEXT_GET 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_ltext  TYPE TBSLT-LTEXT, "   
lv_i_langu  TYPE T002-SPRAS, "   SY-LANGU
lt_t_c_errors  TYPE STANDARD TABLE OF SPROT_U, "   
lv_text_not_found  TYPE SPROT_U, "   
lv_i_bschl  TYPE TBSLT-BSCHL, "   
lv_i_umskz  TYPE TBSLT-UMSKZ. "   

  CALL FUNCTION 'POSTING_KEY_TEXT_GET'  "
    EXPORTING
         I_LANGU = lv_i_langu
         I_BSCHL = lv_i_bschl
         I_UMSKZ = lv_i_umskz
    IMPORTING
         E_LTEXT = lv_e_ltext
    TABLES
         T_C_ERRORS = lt_t_c_errors
    EXCEPTIONS
        TEXT_NOT_FOUND = 1
. " POSTING_KEY_TEXT_GET




ABAP code using 7.40 inline data declarations to call FM POSTING_KEY_TEXT_GET

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 LTEXT FROM TBSLT INTO @DATA(ld_e_ltext).
 
"SELECT single SPRAS FROM T002 INTO @DATA(ld_i_langu).
DATA(ld_i_langu) = SY-LANGU.
 
 
 
"SELECT single BSCHL FROM TBSLT INTO @DATA(ld_i_bschl).
 
"SELECT single UMSKZ FROM TBSLT INTO @DATA(ld_i_umskz).
 


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!