SAP VAP_KNVK_DUPLICATE_CHECK Function Module for NOTRANSL: Prüfen der Existenz des Partners in der knvk
VAP_KNVK_DUPLICATE_CHECK is a standard vap knvk duplicate check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfen der Existenz des Partners in der knvk 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 vap knvk duplicate check FM, simply by entering the name VAP_KNVK_DUPLICATE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: VS03D
Program Name: SAPLVS03D
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VAP_KNVK_DUPLICATE_CHECK 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 'VAP_KNVK_DUPLICATE_CHECK'"NOTRANSL: Prüfen der Existenz des Partners in der knvk.
EXPORTING
I_KUNNR = "Customer Number
I_NAME1 = "Name 1
I_NAMEV = "First Name
I_PARGE = "Gender
I_GBDAT = "Date of Birth
I_PARNR = "Number of Contact Person
I_AKTYP = "Activity Category in the Transaction
* I_MSG_HANDLING = 'X' "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING Parameters details for VAP_KNVK_DUPLICATE_CHECK
I_KUNNR - Customer Number
Data type: KNA1-KUNNROptional: No
Call by Reference: Yes
I_NAME1 - Name 1
Data type: KNVK-NAME1Optional: No
Call by Reference: Yes
I_NAMEV - First Name
Data type: KNVK-NAMEVOptional: No
Call by Reference: Yes
I_PARGE - Gender
Data type: KNVK-PARGEOptional: No
Call by Reference: Yes
I_GBDAT - Date of Birth
Data type: KNVK-GBDATOptional: No
Call by Reference: Yes
I_PARNR - Number of Contact Person
Data type: KNVK-PARNROptional: No
Call by Reference: Yes
I_AKTYP - Activity Category in the Transaction
Data type: T020-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_MSG_HANDLING - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for VAP_KNVK_DUPLICATE_CHECK 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_kunnr | TYPE KNA1-KUNNR, " | |||
| lv_i_name1 | TYPE KNVK-NAME1, " | |||
| lv_i_namev | TYPE KNVK-NAMEV, " | |||
| lv_i_parge | TYPE KNVK-PARGE, " | |||
| lv_i_gbdat | TYPE KNVK-GBDAT, " | |||
| lv_i_parnr | TYPE KNVK-PARNR, " | |||
| lv_i_aktyp | TYPE T020-AKTYP, " | |||
| lv_i_msg_handling | TYPE C. " 'X' |
|   CALL FUNCTION 'VAP_KNVK_DUPLICATE_CHECK' "NOTRANSL: Prüfen der Existenz des Partners in der knvk |
| EXPORTING | ||
| I_KUNNR | = lv_i_kunnr | |
| I_NAME1 | = lv_i_name1 | |
| I_NAMEV | = lv_i_namev | |
| I_PARGE | = lv_i_parge | |
| I_GBDAT | = lv_i_gbdat | |
| I_PARNR | = lv_i_parnr | |
| I_AKTYP | = lv_i_aktyp | |
| I_MSG_HANDLING | = lv_i_msg_handling | |
| . " VAP_KNVK_DUPLICATE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM VAP_KNVK_DUPLICATE_CHECK
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 KUNNR FROM KNA1 INTO @DATA(ld_i_kunnr). | ||||
| "SELECT single NAME1 FROM KNVK INTO @DATA(ld_i_name1). | ||||
| "SELECT single NAMEV FROM KNVK INTO @DATA(ld_i_namev). | ||||
| "SELECT single PARGE FROM KNVK INTO @DATA(ld_i_parge). | ||||
| "SELECT single GBDAT FROM KNVK INTO @DATA(ld_i_gbdat). | ||||
| "SELECT single PARNR FROM KNVK INTO @DATA(ld_i_parnr). | ||||
| "SELECT single AKTYP FROM T020 INTO @DATA(ld_i_aktyp). | ||||
| DATA(ld_i_msg_handling) | = 'X'. | |||
Search for further information about these or an SAP related objects