SAP FKK_PARTNER_LONGTEXT_GET Function Module for









FKK_PARTNER_LONGTEXT_GET is a standard fkk partner longtext 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 fkk partner longtext get FM, simply by entering the name FKK_PARTNER_LONGTEXT_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKGP
Program Name: SAPLFKGP
Main Program: SAPLFKGP
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FKK_PARTNER_LONGTEXT_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 'FKK_PARTNER_LONGTEXT_GET'"
EXPORTING
I_BUT000 = "
* I_FKKVKP = "
* I_NUMBER_OF_LINES = 3 "
* I_VALDT = SY-DATLO "Current User: Local Date

IMPORTING
E_LTEXT1 = "
E_LTEXT10 = "
E_LTEXT2 = "
E_LTEXT3 = "
E_LTEXT4 = "
E_LTEXT5 = "
E_LTEXT6 = "
E_LTEXT7 = "
E_LTEXT8 = "
E_LTEXT9 = "

TABLES
* TX_ADDRESS = "
.



IMPORTING Parameters details for FKK_PARTNER_LONGTEXT_GET

I_BUT000 -

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

I_FKKVKP -

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

I_NUMBER_OF_LINES -

Data type: ADRS-ANZZL
Default: 3
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VALDT - Current User: Local Date

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

EXPORTING Parameters details for FKK_PARTNER_LONGTEXT_GET

E_LTEXT1 -

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

E_LTEXT10 -

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

E_LTEXT2 -

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

E_LTEXT3 -

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

E_LTEXT4 -

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

E_LTEXT5 -

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

E_LTEXT6 -

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

E_LTEXT7 -

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

E_LTEXT8 -

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

E_LTEXT9 -

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

TABLES Parameters details for FKK_PARTNER_LONGTEXT_GET

TX_ADDRESS -

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

Copy and paste ABAP code example for FKK_PARTNER_LONGTEXT_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_ltext1  TYPE STRING, "   
lv_i_but000  TYPE BUS000_EXT, "   
lt_tx_address  TYPE STANDARD TABLE OF BUS020_EXT, "   
lv_e_ltext10  TYPE BUS020_EXT, "   
lv_e_ltext2  TYPE BUS020_EXT, "   
lv_i_fkkvkp  TYPE FKKVKP, "   
lv_e_ltext3  TYPE FKKVKP, "   
lv_i_number_of_lines  TYPE ADRS-ANZZL, "   3
lv_i_valdt  TYPE SY-DATLO, "   SY-DATLO
lv_e_ltext4  TYPE SY, "   
lv_e_ltext5  TYPE SY, "   
lv_e_ltext6  TYPE SY, "   
lv_e_ltext7  TYPE SY, "   
lv_e_ltext8  TYPE SY, "   
lv_e_ltext9  TYPE SY. "   

  CALL FUNCTION 'FKK_PARTNER_LONGTEXT_GET'  "
    EXPORTING
         I_BUT000 = lv_i_but000
         I_FKKVKP = lv_i_fkkvkp
         I_NUMBER_OF_LINES = lv_i_number_of_lines
         I_VALDT = lv_i_valdt
    IMPORTING
         E_LTEXT1 = lv_e_ltext1
         E_LTEXT10 = lv_e_ltext10
         E_LTEXT2 = lv_e_ltext2
         E_LTEXT3 = lv_e_ltext3
         E_LTEXT4 = lv_e_ltext4
         E_LTEXT5 = lv_e_ltext5
         E_LTEXT6 = lv_e_ltext6
         E_LTEXT7 = lv_e_ltext7
         E_LTEXT8 = lv_e_ltext8
         E_LTEXT9 = lv_e_ltext9
    TABLES
         TX_ADDRESS = lt_tx_address
. " FKK_PARTNER_LONGTEXT_GET




ABAP code using 7.40 inline data declarations to call FM FKK_PARTNER_LONGTEXT_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 ANZZL FROM ADRS INTO @DATA(ld_i_number_of_lines).
DATA(ld_i_number_of_lines) = 3.
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt).
DATA(ld_i_valdt) = SY-DATLO.
 
 
 
 
 
 
 


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!