SAP FKK_BUPA_DISPLAY Function Module for Display Business Partner
FKK_BUPA_DISPLAY is a standard fkk bupa display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Business Partner processing and below is the pattern details for this FM, 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 bupa display FM, simply by entering the name FKK_BUPA_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKBV
Program Name: SAPLFKBV
Main Program: SAPLFKBV
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_BUPA_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_BUPA_DISPLAY'"Display Business Partner.
EXPORTING
I_PARTNER = "Partner Number
* I_XINIT = ' ' "
EXCEPTIONS
WRONG_PARAMETERS = 1
IMPORTING Parameters details for FKK_BUPA_DISPLAY
I_PARTNER - Partner Number
Data type: BUT000-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
I_XINIT -
Data type: BUS000FLDS-CHAR1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_PARAMETERS - Wrong Parameter Passed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_BUPA_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_i_partner | TYPE BUT000-PARTNER, " | |||
| lv_wrong_parameters | TYPE BUT000, " | |||
| lv_i_xinit | TYPE BUS000FLDS-CHAR1. " SPACE |
|   CALL FUNCTION 'FKK_BUPA_DISPLAY' "Display Business Partner |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_XINIT | = lv_i_xinit | |
| EXCEPTIONS | ||
| WRONG_PARAMETERS = 1 | ||
| . " FKK_BUPA_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM FKK_BUPA_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 PARTNER FROM BUT000 INTO @DATA(ld_i_partner). | ||||
| "SELECT single CHAR1 FROM BUS000FLDS INTO @DATA(ld_i_xinit). | ||||
| DATA(ld_i_xinit) | = ' '. | |||
Search for further information about these or an SAP related objects