SAP ISP_TEXTS_FOR_DATAELEMENT_GET Function Module for









ISP_TEXTS_FOR_DATAELEMENT_GET is a standard isp texts for dataelement 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 isp texts for dataelement get FM, simply by entering the name ISP_TEXTS_FOR_DATAELEMENT_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: J001
Program Name: SAPLJ001
Main Program: SAPLJ001
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISP_TEXTS_FOR_DATAELEMENT_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 'ISP_TEXTS_FOR_DATAELEMENT_GET'"
EXPORTING
FIELDNAME = "
* INCL_POINTS = ' ' "

IMPORTING
LEN_FIELD = "
FIELDTEXT = "
LEN_HEADER = "
LEN_LONG = "
LEN_MIDLE = "
LEN_SHORT = "
TEXT_HEADER = "
TEXT_LONG = "
TEXT_MIDLE = "
TEXT_SHORT = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for ISP_TEXTS_FOR_DATAELEMENT_GET

FIELDNAME -

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

INCL_POINTS -

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

EXPORTING Parameters details for ISP_TEXTS_FOR_DATAELEMENT_GET

LEN_FIELD -

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

FIELDTEXT -

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

LEN_HEADER -

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

LEN_LONG -

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

LEN_MIDLE -

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

LEN_SHORT -

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

TEXT_HEADER -

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

TEXT_LONG -

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

TEXT_MIDLE -

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

TEXT_SHORT -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for ISP_TEXTS_FOR_DATAELEMENT_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_fieldname  TYPE STRING, "   
lv_len_field  TYPE DD03L-INTLEN, "   
lv_not_found  TYPE DD03L, "   
lv_fieldtext  TYPE DFIES-FIELDTEXT, "   
lv_len_header  TYPE DD04L-HEADLEN, "   
lv_incl_points  TYPE DD04L, "   SPACE
lv_len_long  TYPE DD04L-SCRLEN3, "   
lv_len_midle  TYPE DD04L-SCRLEN2, "   
lv_len_short  TYPE DD04L-SCRLEN1, "   
lv_text_header  TYPE DD04T-REPTEXT, "   
lv_text_long  TYPE DD04T-SCRTEXT_L, "   
lv_text_midle  TYPE DD04T-SCRTEXT_M, "   
lv_text_short  TYPE DD04T-SCRTEXT_S. "   

  CALL FUNCTION 'ISP_TEXTS_FOR_DATAELEMENT_GET'  "
    EXPORTING
         FIELDNAME = lv_fieldname
         INCL_POINTS = lv_incl_points
    IMPORTING
         LEN_FIELD = lv_len_field
         FIELDTEXT = lv_fieldtext
         LEN_HEADER = lv_len_header
         LEN_LONG = lv_len_long
         LEN_MIDLE = lv_len_midle
         LEN_SHORT = lv_len_short
         TEXT_HEADER = lv_text_header
         TEXT_LONG = lv_text_long
         TEXT_MIDLE = lv_text_midle
         TEXT_SHORT = lv_text_short
    EXCEPTIONS
        NOT_FOUND = 1
. " ISP_TEXTS_FOR_DATAELEMENT_GET




ABAP code using 7.40 inline data declarations to call FM ISP_TEXTS_FOR_DATAELEMENT_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 INTLEN FROM DD03L INTO @DATA(ld_len_field).
 
 
"SELECT single FIELDTEXT FROM DFIES INTO @DATA(ld_fieldtext).
 
"SELECT single HEADLEN FROM DD04L INTO @DATA(ld_len_header).
 
DATA(ld_incl_points) = ' '.
 
"SELECT single SCRLEN3 FROM DD04L INTO @DATA(ld_len_long).
 
"SELECT single SCRLEN2 FROM DD04L INTO @DATA(ld_len_midle).
 
"SELECT single SCRLEN1 FROM DD04L INTO @DATA(ld_len_short).
 
"SELECT single REPTEXT FROM DD04T INTO @DATA(ld_text_header).
 
"SELECT single SCRTEXT_L FROM DD04T INTO @DATA(ld_text_long).
 
"SELECT single SCRTEXT_M FROM DD04T INTO @DATA(ld_text_midle).
 
"SELECT single SCRTEXT_S FROM DD04T INTO @DATA(ld_text_short).
 


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!