SAP FKKP0_GSBER_DETERMINE Function Module for
FKKP0_GSBER_DETERMINE is a standard fkkp0 gsber determine 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 fkkp0 gsber determine FM, simply by entering the name FKKP0_GSBER_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKKP0
Program Name: SAPLFKKP0
Main Program: SAPLFKKP0
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKKP0_GSBER_DETERMINE 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 'FKKP0_GSBER_DETERMINE'".
EXPORTING
I_GPART = "
I_VBKD = "Business Data
CHANGING
C_GSBER = "Business Area
IMPORTING Parameters details for FKKP0_GSBER_DETERMINE
I_GPART -
Data type: KNA1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
I_VBKD - Business Data
Data type: VBKDOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FKKP0_GSBER_DETERMINE
C_GSBER - Business Area
Data type: VBRP-GSBEROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKKP0_GSBER_DETERMINE 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_c_gsber | TYPE VBRP-GSBER, " | |||
| lv_i_gpart | TYPE KNA1-KUNNR, " | |||
| lv_i_vbkd | TYPE VBKD. " |
|   CALL FUNCTION 'FKKP0_GSBER_DETERMINE' " |
| EXPORTING | ||
| I_GPART | = lv_i_gpart | |
| I_VBKD | = lv_i_vbkd | |
| CHANGING | ||
| C_GSBER | = lv_c_gsber | |
| . " FKKP0_GSBER_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM FKKP0_GSBER_DETERMINE
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 GSBER FROM VBRP INTO @DATA(ld_c_gsber). | ||||
| "SELECT single KUNNR FROM KNA1 INTO @DATA(ld_i_gpart). | ||||
Search for further information about these or an SAP related objects