SAP FVZ_ADDRESS_FIND Function Module for NOTRANSL: Holen einer Adresse zu einem Partner
FVZ_ADDRESS_FIND is a standard fvz address find 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: Holen einer Adresse zu einem Partner 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 address find FM, simply by entering the name FVZ_ADDRESS_FIND 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_ADDRESS_FIND 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_ADDRESS_FIND'"NOTRANSL: Holen einer Adresse zu einem Partner.
EXPORTING
* ADR_DATE_IN = SY-DATUM "ABAP System Field: Current Date of Application Server
ADR_SNUMOBJ = "Object Number
ADR_SOBJEKT = "DE-EN-LANG-SWITCH-NO-TRANSLATION
ADR_ROLETYP = "Role category
* ADDRESS_INTO_MEMORY = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
ADRS_OUT = "Address
ADR_PARTNR = "Partner Number
ADR_TEXT = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
PARTNER_NOT_FOUND = 1 PARTNER_RELATION_NOT_FOUND = 2
IMPORTING Parameters details for FVZ_ADDRESS_FIND
ADR_DATE_IN - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
ADR_SNUMOBJ - Object Number
Data type: VZGPO-SNUMOBJOptional: No
Call by Reference: No ( called with pass by value option)
ADR_SOBJEKT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ADR_ROLETYP - Role category
Data type: TPZ3-ROLETYPOptional: No
Call by Reference: No ( called with pass by value option)
ADDRESS_INTO_MEMORY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVZ_ADDRESS_FIND
ADRS_OUT - Address
Data type: ADRSOptional: No
Call by Reference: No ( called with pass by value option)
ADR_PARTNR - Partner Number
Data type: VZGPO-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
ADR_TEXT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARTNER_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_RELATION_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_ADDRESS_FIND 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_adrs_out | TYPE ADRS, " | |||
| lv_adr_date_in | TYPE SY-DATUM, " SY-DATUM | |||
| lv_partner_not_found | TYPE SY, " | |||
| lv_adr_partnr | TYPE VZGPO-PARTNR, " | |||
| lv_adr_snumobj | TYPE VZGPO-SNUMOBJ, " | |||
| lv_partner_relation_not_found | TYPE VZGPO, " | |||
| lv_adr_text | TYPE VZGPO, " | |||
| lv_adr_sobjekt | TYPE VZGPO, " | |||
| lv_adr_roletyp | TYPE TPZ3-ROLETYP, " | |||
| lv_address_into_memory | TYPE TPZ3. " SPACE |
|   CALL FUNCTION 'FVZ_ADDRESS_FIND' "NOTRANSL: Holen einer Adresse zu einem Partner |
| EXPORTING | ||
| ADR_DATE_IN | = lv_adr_date_in | |
| ADR_SNUMOBJ | = lv_adr_snumobj | |
| ADR_SOBJEKT | = lv_adr_sobjekt | |
| ADR_ROLETYP | = lv_adr_roletyp | |
| ADDRESS_INTO_MEMORY | = lv_address_into_memory | |
| IMPORTING | ||
| ADRS_OUT | = lv_adrs_out | |
| ADR_PARTNR | = lv_adr_partnr | |
| ADR_TEXT | = lv_adr_text | |
| EXCEPTIONS | ||
| PARTNER_NOT_FOUND = 1 | ||
| PARTNER_RELATION_NOT_FOUND = 2 | ||
| . " FVZ_ADDRESS_FIND | ||
ABAP code using 7.40 inline data declarations to call FM FVZ_ADDRESS_FIND
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 DATUM FROM SY INTO @DATA(ld_adr_date_in). | ||||
| DATA(ld_adr_date_in) | = SY-DATUM. | |||
| "SELECT single PARTNR FROM VZGPO INTO @DATA(ld_adr_partnr). | ||||
| "SELECT single SNUMOBJ FROM VZGPO INTO @DATA(ld_adr_snumobj). | ||||
| "SELECT single ROLETYP FROM TPZ3 INTO @DATA(ld_adr_roletyp). | ||||
| DATA(ld_address_into_memory) | = ' '. | |||
Search for further information about these or an SAP related objects