SAP FVZ_PARTNER_IN_PRINTFORM Function Module for NOTRANSL: Aufbereiten von Partner- und Adreßdaten
FVZ_PARTNER_IN_PRINTFORM is a standard fvz partner in printform 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: Aufbereiten von Partner- und Adreßdaten 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 partner in printform FM, simply by entering the name FVZ_PARTNER_IN_PRINTFORM 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_PARTNER_IN_PRINTFORM 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_PARTNER_IN_PRINTFORM'"NOTRANSL: Aufbereiten von Partner- und Adreßdaten.
EXPORTING
* ADDRESS_INTO_MEMORY = 'X' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* KZ_BPLANGU = ' ' "ABAP System Field: Highlighted Input in Dynpro Field
* ADRTYP = ' ' "Address ID
* BUKRS_IN = ' ' "Company Code
* DATE_IN = SY-DATUM "ABAP System Field: Current Date of Application Server
* NO_ADDRESS = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* PARTNR = ' ' "Business Partner Number
* ROLETYP = ' ' "Business Partner Role Category
* LINES = 5 "Number of Lines in Address
* CNTRY_IN = "Country Key
IMPORTING
ANSCHWA_OUT = "Address formating function module transfer structure
NAME_OUT = "Business Partner Master (General Data)
ADREF_OUT = "BP Structure: Business Partner - Address
EXCEPTIONS
ADDRESS_NOT_FOUND = 1 PARTNER_NOT_FOUND = 2
IMPORTING Parameters details for FVZ_PARTNER_IN_PRINTFORM
ADDRESS_INTO_MEMORY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
KZ_BPLANGU - ABAP System Field: Highlighted Input in Dynpro Field
Data type: SY-DATARDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ADRTYP - Address ID
Data type: BP030-ADR_REF_KDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
BUKRS_IN - Company Code
Data type: T001-BUKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
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)
NO_ADDRESS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PARTNR - Business Partner Number
Data type: BP000-PARTNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ROLETYP - Business Partner Role Category
Data type: BP1000-ROLETYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LINES - Number of Lines in Address
Data type: ADRS-ANZZLDefault: 5
Optional: Yes
Call by Reference: No ( called with pass by value option)
CNTRY_IN - Country Key
Data type: T005-LAND1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVZ_PARTNER_IN_PRINTFORM
ANSCHWA_OUT - Address formating function module transfer structure
Data type: ADRSOptional: No
Call by Reference: No ( called with pass by value option)
NAME_OUT - Business Partner Master (General Data)
Data type: BP000Optional: No
Call by Reference: No ( called with pass by value option)
ADREF_OUT - BP Structure: Business Partner - Address
Data type: BPDADREFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADDRESS_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_PARTNER_IN_PRINTFORM 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_anschwa_out | TYPE ADRS, " | |||
| lv_address_not_found | TYPE ADRS, " | |||
| lv_address_into_memory | TYPE ADRS, " 'X' | |||
| lv_kz_bplangu | TYPE SY-DATAR, " SPACE | |||
| lv_adrtyp | TYPE BP030-ADR_REF_K, " SPACE | |||
| lv_name_out | TYPE BP000, " | |||
| lv_partner_not_found | TYPE BP000, " | |||
| lv_bukrs_in | TYPE T001-BUKRS, " SPACE | |||
| lv_adref_out | TYPE BPDADREF, " | |||
| lv_date_in | TYPE SY-DATUM, " SY-DATUM | |||
| lv_no_address | TYPE SY, " SPACE | |||
| lv_partnr | TYPE BP000-PARTNR, " SPACE | |||
| lv_roletyp | TYPE BP1000-ROLETYP, " SPACE | |||
| lv_lines | TYPE ADRS-ANZZL, " 5 | |||
| lv_cntry_in | TYPE T005-LAND1. " |
|   CALL FUNCTION 'FVZ_PARTNER_IN_PRINTFORM' "NOTRANSL: Aufbereiten von Partner- und Adreßdaten |
| EXPORTING | ||
| ADDRESS_INTO_MEMORY | = lv_address_into_memory | |
| KZ_BPLANGU | = lv_kz_bplangu | |
| ADRTYP | = lv_adrtyp | |
| BUKRS_IN | = lv_bukrs_in | |
| DATE_IN | = lv_date_in | |
| NO_ADDRESS | = lv_no_address | |
| PARTNR | = lv_partnr | |
| ROLETYP | = lv_roletyp | |
| LINES | = lv_lines | |
| CNTRY_IN | = lv_cntry_in | |
| IMPORTING | ||
| ANSCHWA_OUT | = lv_anschwa_out | |
| NAME_OUT | = lv_name_out | |
| ADREF_OUT | = lv_adref_out | |
| EXCEPTIONS | ||
| ADDRESS_NOT_FOUND = 1 | ||
| PARTNER_NOT_FOUND = 2 | ||
| . " FVZ_PARTNER_IN_PRINTFORM | ||
ABAP code using 7.40 inline data declarations to call FM FVZ_PARTNER_IN_PRINTFORM
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.| DATA(ld_address_into_memory) | = 'X'. | |||
| "SELECT single DATAR FROM SY INTO @DATA(ld_kz_bplangu). | ||||
| DATA(ld_kz_bplangu) | = ' '. | |||
| "SELECT single ADR_REF_K FROM BP030 INTO @DATA(ld_adrtyp). | ||||
| DATA(ld_adrtyp) | = ' '. | |||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_bukrs_in). | ||||
| DATA(ld_bukrs_in) | = ' '. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date_in). | ||||
| DATA(ld_date_in) | = SY-DATUM. | |||
| DATA(ld_no_address) | = ' '. | |||
| "SELECT single PARTNR FROM BP000 INTO @DATA(ld_partnr). | ||||
| DATA(ld_partnr) | = ' '. | |||
| "SELECT single ROLETYP FROM BP1000 INTO @DATA(ld_roletyp). | ||||
| DATA(ld_roletyp) | = ' '. | |||
| "SELECT single ANZZL FROM ADRS INTO @DATA(ld_lines). | ||||
| DATA(ld_lines) | = 5. | |||
| "SELECT single LAND1 FROM T005 INTO @DATA(ld_cntry_in). | ||||
Search for further information about these or an SAP related objects