SAP FKK_PARTNER_HEADER_DISPLAY Function Module for
FKK_PARTNER_HEADER_DISPLAY is a standard fkk partner header display 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 header display FM, simply by entering the name FKK_PARTNER_HEADER_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKGP
Program Name: SAPLFKGP
Main Program: SAPLFKGP
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FKK_PARTNER_HEADER_DISPLAY 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_HEADER_DISPLAY'".
EXPORTING
* X_PARTNER = "Business Partner
* X_VKONT = "
* X_RESET_BUFFER = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_VALDT = SY-DATLO "Current User: Local Date
IMPORTING
Y_REPID = "Program Name
Y_DYNNR = "
Y_TEXT1 = "
Y_LTEXT1 = "
Y_LTEXT2 = "
Y_LTEXT3 = "
TABLES
* T_FKKVKP = "Contract Account
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for FKK_PARTNER_HEADER_DISPLAY
X_PARTNER - Business Partner
Data type: BUT000-PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
X_VKONT -
Data type: FKKVKP-VKONTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_RESET_BUFFER - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_VALDT - Current User: Local Date
Data type: SY-DATLODefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_PARTNER_HEADER_DISPLAY
Y_REPID - Program Name
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
Y_DYNNR -
Data type: SY-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
Y_TEXT1 -
Data type: FKGPD-TEXT1Optional: No
Call by Reference: No ( called with pass by value option)
Y_LTEXT1 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Y_LTEXT2 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Y_LTEXT3 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FKK_PARTNER_HEADER_DISPLAY
T_FKKVKP - Contract Account
Data type: FKKVKPOptional: Yes
Call by Reference: Yes
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 FKK_PARTNER_HEADER_DISPLAY 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_y_repid | TYPE SY-REPID, " | |||
lt_t_fkkvkp | TYPE STANDARD TABLE OF FKKVKP, " | |||
lv_not_found | TYPE FKKVKP, " | |||
lv_x_partner | TYPE BUT000-PARTNER, " | |||
lv_x_vkont | TYPE FKKVKP-VKONT, " | |||
lv_y_dynnr | TYPE SY-DYNNR, " | |||
lv_y_text1 | TYPE FKGPD-TEXT1, " | |||
lv_x_reset_buffer | TYPE BOOLE-BOOLE, " | |||
lv_x_valdt | TYPE SY-DATLO, " SY-DATLO | |||
lv_y_ltext1 | TYPE SY, " | |||
lv_y_ltext2 | TYPE SY, " | |||
lv_y_ltext3 | TYPE SY. " |
  CALL FUNCTION 'FKK_PARTNER_HEADER_DISPLAY' " |
EXPORTING | ||
X_PARTNER | = lv_x_partner | |
X_VKONT | = lv_x_vkont | |
X_RESET_BUFFER | = lv_x_reset_buffer | |
X_VALDT | = lv_x_valdt | |
IMPORTING | ||
Y_REPID | = lv_y_repid | |
Y_DYNNR | = lv_y_dynnr | |
Y_TEXT1 | = lv_y_text1 | |
Y_LTEXT1 | = lv_y_ltext1 | |
Y_LTEXT2 | = lv_y_ltext2 | |
Y_LTEXT3 | = lv_y_ltext3 | |
TABLES | ||
T_FKKVKP | = lt_t_fkkvkp | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
. " FKK_PARTNER_HEADER_DISPLAY |
ABAP code using 7.40 inline data declarations to call FM FKK_PARTNER_HEADER_DISPLAY
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 REPID FROM SY INTO @DATA(ld_y_repid). | ||||
"SELECT single PARTNER FROM BUT000 INTO @DATA(ld_x_partner). | ||||
"SELECT single VKONT FROM FKKVKP INTO @DATA(ld_x_vkont). | ||||
"SELECT single DYNNR FROM SY INTO @DATA(ld_y_dynnr). | ||||
"SELECT single TEXT1 FROM FKGPD INTO @DATA(ld_y_text1). | ||||
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_reset_buffer). | ||||
"SELECT single DATLO FROM SY INTO @DATA(ld_x_valdt). | ||||
DATA(ld_x_valdt) | = SY-DATLO. | |||
Search for further information about these or an SAP related objects