SAP VALIDATE_CUSTOMER Function Module for Joint Venture Validate Customer
VALIDATE_CUSTOMER is a standard validate customer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Joint Venture Validate Customer 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 validate customer FM, simply by entering the name VALIDATE_CUSTOMER into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVV
Program Name: SAPLGJVV
Main Program: SAPLGJVV
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VALIDATE_CUSTOMER 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 'VALIDATE_CUSTOMER'"Joint Venture Validate Customer.
EXPORTING
I_COMPANY = "Company Code
I_CUSTOMER = "Customer Number
IMPORTING
E_RECORD = "Export: Field String - Table KNB1
E_VALID = "Export: Valid Flag - 1=Valid, 0=Invalid
EXCEPTIONS
INCOMPLETE = 1
IMPORTING Parameters details for VALIDATE_CUSTOMER
I_COMPANY - Company Code
Data type: KNB1-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_CUSTOMER - Customer Number
Data type: KNB1-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VALIDATE_CUSTOMER
E_RECORD - Export: Field String - Table KNB1
Data type: KNB1Optional: No
Call by Reference: No ( called with pass by value option)
E_VALID - Export: Valid Flag - 1=Valid, 0=Invalid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INCOMPLETE - Input Parameters Incomplete or Invalid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VALIDATE_CUSTOMER 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_e_record | TYPE KNB1, " | |||
| lv_i_company | TYPE KNB1-BUKRS, " | |||
| lv_incomplete | TYPE KNB1, " | |||
| lv_e_valid | TYPE KNB1, " | |||
| lv_i_customer | TYPE KNB1-KUNNR. " |
|   CALL FUNCTION 'VALIDATE_CUSTOMER' "Joint Venture Validate Customer |
| EXPORTING | ||
| I_COMPANY | = lv_i_company | |
| I_CUSTOMER | = lv_i_customer | |
| IMPORTING | ||
| E_RECORD | = lv_e_record | |
| E_VALID | = lv_e_valid | |
| EXCEPTIONS | ||
| INCOMPLETE = 1 | ||
| . " VALIDATE_CUSTOMER | ||
ABAP code using 7.40 inline data declarations to call FM VALIDATE_CUSTOMER
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 KNB1 INTO @DATA(ld_i_company). | ||||
| "SELECT single KUNNR FROM KNB1 INTO @DATA(ld_i_customer). | ||||
Search for further information about these or an SAP related objects