SAP FKKSD_VBKD_VKONT_DETERMINE Function Module for









FKKSD_VBKD_VKONT_DETERMINE is a standard fkksd vbkd vkont 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 fkksd vbkd vkont determine FM, simply by entering the name FKKSD_VBKD_VKONT_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKKSD
Program Name: SAPLFKKSD
Main Program: SAPLFKKSD
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FKKSD_VBKD_VKONT_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 'FKKSD_VBKD_VKONT_DETERMINE'"
EXPORTING
I_VBELN = "Sales Document
I_POSNR = "Sales document item
I_UEPOS = "Higher-Level Item
I_VBTYP = "SD document category
I_BUKRS = "Company code to be billed
* I_USE_VBKD_STAT = "

IMPORTING
E_VKONT = "
E_VBKD_VKONT_CHANGED = "
E_VBKD_POSNR_CHANGED = "

CHANGING
X_VBKD = "

TABLES
IT_XVBPA = "
XT_XVBKD = "
.



IMPORTING Parameters details for FKKSD_VBKD_VKONT_DETERMINE

I_VBELN - Sales Document

Data type: VBAK-VBELN
Optional: No
Call by Reference: Yes

I_POSNR - Sales document item

Data type: VBAP-POSNR
Optional: No
Call by Reference: Yes

I_UEPOS - Higher-Level Item

Data type: VBAP-UEPOS
Optional: No
Call by Reference: Yes

I_VBTYP - SD document category

Data type: VBAK-VBTYP
Optional: No
Call by Reference: Yes

I_BUKRS - Company code to be billed

Data type: VBAK-BUKRS_VF
Optional: No
Call by Reference: Yes

I_USE_VBKD_STAT -

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FKKSD_VBKD_VKONT_DETERMINE

E_VKONT -

Data type: VBKD-VKONT
Optional: No
Call by Reference: Yes

E_VBKD_VKONT_CHANGED -

Data type: BOOLE-BOOLE
Optional: No
Call by Reference: Yes

E_VBKD_POSNR_CHANGED -

Data type: BOOLE-BOOLE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for FKKSD_VBKD_VKONT_DETERMINE

X_VBKD -

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

TABLES Parameters details for FKKSD_VBKD_VKONT_DETERMINE

IT_XVBPA -

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

XT_XVBKD -

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

Copy and paste ABAP code example for FKKSD_VBKD_VKONT_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_x_vbkd  TYPE VBKD, "   
lv_e_vkont  TYPE VBKD-VKONT, "   
lv_i_vbeln  TYPE VBAK-VBELN, "   
lt_it_xvbpa  TYPE STANDARD TABLE OF VBPAVB, "   
lv_i_posnr  TYPE VBAP-POSNR, "   
lt_xt_xvbkd  TYPE STANDARD TABLE OF VBKDVB, "   
lv_e_vbkd_vkont_changed  TYPE BOOLE-BOOLE, "   
lv_i_uepos  TYPE VBAP-UEPOS, "   
lv_e_vbkd_posnr_changed  TYPE BOOLE-BOOLE, "   
lv_i_vbtyp  TYPE VBAK-VBTYP, "   
lv_i_bukrs  TYPE VBAK-BUKRS_VF, "   
lv_i_use_vbkd_stat  TYPE CHAR1. "   

  CALL FUNCTION 'FKKSD_VBKD_VKONT_DETERMINE'  "
    EXPORTING
         I_VBELN = lv_i_vbeln
         I_POSNR = lv_i_posnr
         I_UEPOS = lv_i_uepos
         I_VBTYP = lv_i_vbtyp
         I_BUKRS = lv_i_bukrs
         I_USE_VBKD_STAT = lv_i_use_vbkd_stat
    IMPORTING
         E_VKONT = lv_e_vkont
         E_VBKD_VKONT_CHANGED = lv_e_vbkd_vkont_changed
         E_VBKD_POSNR_CHANGED = lv_e_vbkd_posnr_changed
    CHANGING
         X_VBKD = lv_x_vbkd
    TABLES
         IT_XVBPA = lt_it_xvbpa
         XT_XVBKD = lt_xt_xvbkd
. " FKKSD_VBKD_VKONT_DETERMINE




ABAP code using 7.40 inline data declarations to call FM FKKSD_VBKD_VKONT_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 VKONT FROM VBKD INTO @DATA(ld_e_vkont).
 
"SELECT single VBELN FROM VBAK INTO @DATA(ld_i_vbeln).
 
 
"SELECT single POSNR FROM VBAP INTO @DATA(ld_i_posnr).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_vbkd_vkont_changed).
 
"SELECT single UEPOS FROM VBAP INTO @DATA(ld_i_uepos).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_vbkd_posnr_changed).
 
"SELECT single VBTYP FROM VBAK INTO @DATA(ld_i_vbtyp).
 
"SELECT single BUKRS_VF FROM VBAK INTO @DATA(ld_i_bukrs).
 
 


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!