SAP FVZ_CHECK_DEBITOR Function Module for NOTRANSL: Prüfen, ob Partner Debitor ist
FVZ_CHECK_DEBITOR is a standard fvz check debitor 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, ob Partner Debitor ist 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 fvz check debitor FM, simply by entering the name FVZ_CHECK_DEBITOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZ9
Program Name: SAPLFVZ9
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVZ_CHECK_DEBITOR 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 'FVZ_CHECK_DEBITOR'"NOTRANSL: Prüfen, ob Partner Debitor ist.
EXPORTING
* BUKRS = ' ' "Company Code
* KUNNR_IN = ' ' "Customer Number
* PARTNR_IN = ' ' "Partner Number
* MABER = ' ' "Dunning Area
IMPORTING
FLG_BUKRS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
FLG_MABER = "DE-EN-LANG-SWITCH-NO-TRANSLATION
KUNNR_OUT = "Customer Number
PARTNR_OUT = "Partner Number
EXCEPTIONS
DEBITOR_NOT_FOUND = 1 PARTNER_NOT_FOUND = 2
IMPORTING Parameters details for FVZ_CHECK_DEBITOR
BUKRS - Company Code
Data type: T001-BUKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
KUNNR_IN - Customer Number
Data type: BP000-CUSTOMERDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PARTNR_IN - Partner Number
Data type: BP000-PARTNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MABER - Dunning Area
Data type: T047M-MABERDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVZ_CHECK_DEBITOR
FLG_BUKRS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FLG_MABER - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KUNNR_OUT - Customer Number
Data type: BP000-CUSTOMEROptional: No
Call by Reference: No ( called with pass by value option)
PARTNR_OUT - Partner Number
Data type: BP000-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DEBITOR_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVZ_CHECK_DEBITOR 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_bukrs | TYPE T001-BUKRS, " SPACE | |||
| lv_flg_bukrs | TYPE T001, " | |||
| lv_debitor_not_found | TYPE T001, " | |||
| lv_kunnr_in | TYPE BP000-CUSTOMER, " SPACE | |||
| lv_flg_maber | TYPE BP000, " | |||
| lv_partner_not_found | TYPE BP000, " | |||
| lv_kunnr_out | TYPE BP000-CUSTOMER, " | |||
| lv_partnr_in | TYPE BP000-PARTNR, " SPACE | |||
| lv_maber | TYPE T047M-MABER, " SPACE | |||
| lv_partnr_out | TYPE BP000-PARTNR. " |
|   CALL FUNCTION 'FVZ_CHECK_DEBITOR' "NOTRANSL: Prüfen, ob Partner Debitor ist |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| KUNNR_IN | = lv_kunnr_in | |
| PARTNR_IN | = lv_partnr_in | |
| MABER | = lv_maber | |
| IMPORTING | ||
| FLG_BUKRS | = lv_flg_bukrs | |
| FLG_MABER | = lv_flg_maber | |
| KUNNR_OUT | = lv_kunnr_out | |
| PARTNR_OUT | = lv_partnr_out | |
| EXCEPTIONS | ||
| DEBITOR_NOT_FOUND = 1 | ||
| PARTNER_NOT_FOUND = 2 | ||
| . " FVZ_CHECK_DEBITOR | ||
ABAP code using 7.40 inline data declarations to call FM FVZ_CHECK_DEBITOR
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 BUKRS FROM T001 INTO @DATA(ld_bukrs). | ||||
| DATA(ld_bukrs) | = ' '. | |||
| "SELECT single CUSTOMER FROM BP000 INTO @DATA(ld_kunnr_in). | ||||
| DATA(ld_kunnr_in) | = ' '. | |||
| "SELECT single CUSTOMER FROM BP000 INTO @DATA(ld_kunnr_out). | ||||
| "SELECT single PARTNR FROM BP000 INTO @DATA(ld_partnr_in). | ||||
| DATA(ld_partnr_in) | = ' '. | |||
| "SELECT single MABER FROM T047M INTO @DATA(ld_maber). | ||||
| DATA(ld_maber) | = ' '. | |||
| "SELECT single PARTNR FROM BP000 INTO @DATA(ld_partnr_out). | ||||
Search for further information about these or an SAP related objects