SAP FIND_CUSTOMER_BY_ADDRESS Function Module for NOTRANSL: Suchen von anhand von den Adressenbestandteilen









FIND_CUSTOMER_BY_ADDRESS is a standard find customer by address 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: Suchen von anhand von den Adressenbestandteilen 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 find customer by address FM, simply by entering the name FIND_CUSTOMER_BY_ADDRESS into the relevant SAP transaction such as SE37 or SE38.

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



Function FIND_CUSTOMER_BY_ADDRESS 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 'FIND_CUSTOMER_BY_ADDRESS'"NOTRANSL: Suchen von anhand von den Adressenbestandteilen
  EXPORTING
*  IV_NAME =  "Name 1
*  IV_COUNTRYCODE =  "Country Key
*  IV_REGIONCODE =  "Region (State, Province, County)
*  IV_CITY =  "Cty
*  IV_DISTRICT =  "District
*  IV_POSTALCODE =  "City Postal Code
*  IV_STREET =  "Street
*  IV_KEYWORDSTEXT1 =  "Search Term 1
*  IV_KEYWORDSTEXT2 =  "Search Term 2

 IMPORTING
   ET_CUSTOMERS =  "Complex External Interface for Customers (Tab.)
   ES_ERROR =  "Error Indicator Plus System Messages
.



IMPORTING Parameters details for FIND_CUSTOMER_BY_ADDRESS

IV_NAME - Name 1

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

IV_COUNTRYCODE - Country Key

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

IV_REGIONCODE - Region (State, Province, County)

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

IV_CITY - Cty

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

IV_DISTRICT - District

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

IV_POSTALCODE - City Postal Code

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

IV_STREET - Street

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

IV_KEYWORDSTEXT1 - Search Term 1

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

IV_KEYWORDSTEXT2 - Search Term 2

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

EXPORTING Parameters details for FIND_CUSTOMER_BY_ADDRESS

ET_CUSTOMERS - Complex External Interface for Customers (Tab.)

Data type: CMDS_EI_EXTERN_T
Optional: No
Call by Reference: Yes

ES_ERROR - Error Indicator Plus System Messages

Data type: CVIS_MESSAGE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FIND_CUSTOMER_BY_ADDRESS 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_iv_name  TYPE AD_NAME1, "   
lv_et_customers  TYPE CMDS_EI_EXTERN_T, "   
lv_es_error  TYPE CVIS_MESSAGE, "   
lv_iv_countrycode  TYPE LAND1, "   
lv_iv_regioncode  TYPE REGIO, "   
lv_iv_city  TYPE AD_CITY1, "   
lv_iv_district  TYPE AD_CITY2, "   
lv_iv_postalcode  TYPE AD_PSTCD1, "   
lv_iv_street  TYPE AD_STREET, "   
lv_iv_keywordstext1  TYPE AD_SORT1, "   
lv_iv_keywordstext2  TYPE AD_SORT2. "   

  CALL FUNCTION 'FIND_CUSTOMER_BY_ADDRESS'  "NOTRANSL: Suchen von anhand von den Adressenbestandteilen
    EXPORTING
         IV_NAME = lv_iv_name
         IV_COUNTRYCODE = lv_iv_countrycode
         IV_REGIONCODE = lv_iv_regioncode
         IV_CITY = lv_iv_city
         IV_DISTRICT = lv_iv_district
         IV_POSTALCODE = lv_iv_postalcode
         IV_STREET = lv_iv_street
         IV_KEYWORDSTEXT1 = lv_iv_keywordstext1
         IV_KEYWORDSTEXT2 = lv_iv_keywordstext2
    IMPORTING
         ET_CUSTOMERS = lv_et_customers
         ES_ERROR = lv_es_error
. " FIND_CUSTOMER_BY_ADDRESS




ABAP code using 7.40 inline data declarations to call FM FIND_CUSTOMER_BY_ADDRESS

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.

 
 
 
 
 
 
 
 
 
 
 


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!