SAP SD_COND_VARA_FCODE_TO_DNNNR Function Module for Conditions: Returns requested screen
SD_COND_VARA_FCODE_TO_DNNNR is a standard sd cond vara fcode to dnnnr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conditions: Returns requested screen 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 sd cond vara fcode to dnnnr FM, simply by entering the name SD_COND_VARA_FCODE_TO_DNNNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: V13F
Program Name: SAPLV13F
Main Program: SAPLV13F
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_COND_VARA_FCODE_TO_DNNNR 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 'SD_COND_VARA_FCODE_TO_DNNNR'"Conditions: Returns requested screen.
EXPORTING
FCODE_I = "Function code
IMPORTING
DYNNR_O = "Requested screen numbers
IMPORTING Parameters details for SD_COND_VARA_FCODE_TO_DNNNR
FCODE_I - Function code
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SD_COND_VARA_FCODE_TO_DNNNR
DYNNR_O - Requested screen numbers
Data type: T671-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_COND_VARA_FCODE_TO_DNNNR 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_dynnr_o | TYPE T671-DYNNR, " | |||
| lv_fcode_i | TYPE T671. " |
|   CALL FUNCTION 'SD_COND_VARA_FCODE_TO_DNNNR' "Conditions: Returns requested screen |
| EXPORTING | ||
| FCODE_I | = lv_fcode_i | |
| IMPORTING | ||
| DYNNR_O | = lv_dynnr_o | |
| . " SD_COND_VARA_FCODE_TO_DNNNR | ||
ABAP code using 7.40 inline data declarations to call FM SD_COND_VARA_FCODE_TO_DNNNR
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 T671 INTO @DATA(ld_dynnr_o). | ||||
Search for further information about these or an SAP related objects