SAP FVD_CLERKS_SUBSCREEN_DISPLAY Function Module for Call the Processor Screen for Processing
FVD_CLERKS_SUBSCREEN_DISPLAY is a standard fvd clerks subscreen display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call the Processor Screen for Processing 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 fvd clerks subscreen display FM, simply by entering the name FVD_CLERKS_SUBSCREEN_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_CLERKS
Program Name: SAPLFVD_CLERKS
Main Program: SAPLFVD_CLERKS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_CLERKS_SUBSCREEN_DISPLAY 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 'FVD_CLERKS_SUBSCREEN_DISPLAY'"Call the Processor Screen for Processing.
EXPORTING
I_STR_VDARL = "Loan
* I_FLG_EDIT = ' ' "' ' = Anzeigemodus,' X' = Änderungsmodus
* I_FLG_SANLF_IA = ' ' "Investoren Vertrag: TRUE (='X') und FALSE (=' ')
IMPORTING
E_SUB_DYNNR = "Sachbearbeiter Subscreendynpro für Call Subscreen
E_SUB_REPID = "Sachbearbeiter Programmname für Call Subscreen
E_FLG_CHANGED = "Checkbox
E_TAB_VDGPO = "Business Partner Assignment
E_TAB_VDZSB = "Table Type for Table VDZSB
EXCEPTIONS
PARAMETER_ERROR = 1 NO_CLERKS_FOUND = 2
IMPORTING Parameters details for FVD_CLERKS_SUBSCREEN_DISPLAY
I_STR_VDARL - Loan
Data type: VDARLOptional: No
Call by Reference: Yes
I_FLG_EDIT - ' ' = Anzeigemodus,' X' = Änderungsmodus
Data type: XFELDDefault: ' '
Optional: No
Call by Reference: Yes
I_FLG_SANLF_IA - Investoren Vertrag: TRUE (='X') und FALSE (=' ')
Data type: BOOLE_DDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_CLERKS_SUBSCREEN_DISPLAY
E_SUB_DYNNR - Sachbearbeiter Subscreendynpro für Call Subscreen
Data type: SY-DYNNROptional: No
Call by Reference: Yes
E_SUB_REPID - Sachbearbeiter Programmname für Call Subscreen
Data type: SY-REPIDOptional: No
Call by Reference: Yes
E_FLG_CHANGED - Checkbox
Data type: XFELDOptional: No
Call by Reference: Yes
E_TAB_VDGPO - Business Partner Assignment
Data type: TRTY_VDGPOOptional: No
Call by Reference: Yes
E_TAB_VDZSB - Table Type for Table VDZSB
Data type: TRTY_VDZSBOptional: No
Call by Reference: Yes
EXCEPTIONS details
PARAMETER_ERROR - Importparameter oder Customizing fehlerhaft
Data type:Optional: No
Call by Reference: Yes
NO_CLERKS_FOUND - Keine Sachbearbeiter bzw. Customizing zum Buchungskreis gefunden
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_CLERKS_SUBSCREEN_DISPLAY 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_sub_dynnr | TYPE SY-DYNNR, " | |||
| lv_i_str_vdarl | TYPE VDARL, " | |||
| lv_parameter_error | TYPE VDARL, " | |||
| lv_i_flg_edit | TYPE XFELD, " ' ' | |||
| lv_e_sub_repid | TYPE SY-REPID, " | |||
| lv_no_clerks_found | TYPE SY, " | |||
| lv_e_flg_changed | TYPE XFELD, " | |||
| lv_i_flg_sanlf_ia | TYPE BOOLE_D, " SPACE | |||
| lv_e_tab_vdgpo | TYPE TRTY_VDGPO, " | |||
| lv_e_tab_vdzsb | TYPE TRTY_VDZSB. " |
|   CALL FUNCTION 'FVD_CLERKS_SUBSCREEN_DISPLAY' "Call the Processor Screen for Processing |
| EXPORTING | ||
| I_STR_VDARL | = lv_i_str_vdarl | |
| I_FLG_EDIT | = lv_i_flg_edit | |
| I_FLG_SANLF_IA | = lv_i_flg_sanlf_ia | |
| IMPORTING | ||
| E_SUB_DYNNR | = lv_e_sub_dynnr | |
| E_SUB_REPID | = lv_e_sub_repid | |
| E_FLG_CHANGED | = lv_e_flg_changed | |
| E_TAB_VDGPO | = lv_e_tab_vdgpo | |
| E_TAB_VDZSB | = lv_e_tab_vdzsb | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| NO_CLERKS_FOUND = 2 | ||
| . " FVD_CLERKS_SUBSCREEN_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CLERKS_SUBSCREEN_DISPLAY
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 DYNNR FROM SY INTO @DATA(ld_e_sub_dynnr). | ||||
| DATA(ld_i_flg_edit) | = ' '. | |||
| "SELECT single REPID FROM SY INTO @DATA(ld_e_sub_repid). | ||||
| DATA(ld_i_flg_sanlf_ia) | = ' '. | |||
Search for further information about these or an SAP related objects