SAP SD_VEDA_CREATE Function Module for NOTRANSL: Setzen von Steuerungsdaten für die Ablauflogik des Subscreens









SD_VEDA_CREATE is a standard sd veda create 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: Setzen von Steuerungsdaten für die Ablauflogik des Subscreens 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 veda create FM, simply by entering the name SD_VEDA_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_VEDA_CREATE 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_VEDA_CREATE'"NOTRANSL: Setzen von Steuerungsdaten für die Ablauflogik des Subscreens
EXPORTING
I_TRTYP = "
I_PROFILE = "
I_VBELN = "Contract Document Number
I_VPOSN = "Item Number
* I_FEHGR = "
* I_DIALOG_INCOMPLETE = "
* I_UEPOS = "Higher-Level Item
I_TVAK = "Sales Documents: Types

TABLES
* T_HVBUV = "
* T_XVBUV = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV45W_001 SD Service Management: Forward Contract Data to Item

IMPORTING Parameters details for SD_VEDA_CREATE

I_TRTYP -

Data type: T180-TRTYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_PROFILE -

Data type: TVVD-VPROF
Optional: No
Call by Reference: No ( called with pass by value option)

I_VBELN - Contract Document Number

Data type: VEDA-VBELN
Optional: No
Call by Reference: No ( called with pass by value option)

I_VPOSN - Item Number

Data type: VEDA-VPOSN
Optional: No
Call by Reference: No ( called with pass by value option)

I_FEHGR -

Data type: TVUV-FEHGR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DIALOG_INCOMPLETE -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_UEPOS - Higher-Level Item

Data type: VEDA-VPOSN
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TVAK - Sales Documents: Types

Data type: TVAK
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SD_VEDA_CREATE

T_HVBUV -

Data type: VBUVVB
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_XVBUV -

Data type: VBUVVB
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SD_VEDA_CREATE 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_i_trtyp  TYPE T180-TRTYP, "   
lt_t_hvbuv  TYPE STANDARD TABLE OF VBUVVB, "   
lt_t_xvbuv  TYPE STANDARD TABLE OF VBUVVB, "   
lv_i_profile  TYPE TVVD-VPROF, "   
lv_i_vbeln  TYPE VEDA-VBELN, "   
lv_i_vposn  TYPE VEDA-VPOSN, "   
lv_i_fehgr  TYPE TVUV-FEHGR, "   
lv_i_dialog_incomplete  TYPE TVUV, "   
lv_i_uepos  TYPE VEDA-VPOSN, "   
lv_i_tvak  TYPE TVAK. "   

  CALL FUNCTION 'SD_VEDA_CREATE'  "NOTRANSL: Setzen von Steuerungsdaten für die Ablauflogik des Subscreens
    EXPORTING
         I_TRTYP = lv_i_trtyp
         I_PROFILE = lv_i_profile
         I_VBELN = lv_i_vbeln
         I_VPOSN = lv_i_vposn
         I_FEHGR = lv_i_fehgr
         I_DIALOG_INCOMPLETE = lv_i_dialog_incomplete
         I_UEPOS = lv_i_uepos
         I_TVAK = lv_i_tvak
    TABLES
         T_HVBUV = lt_t_hvbuv
         T_XVBUV = lt_t_xvbuv
. " SD_VEDA_CREATE




ABAP code using 7.40 inline data declarations to call FM SD_VEDA_CREATE

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 TRTYP FROM T180 INTO @DATA(ld_i_trtyp).
 
 
 
"SELECT single VPROF FROM TVVD INTO @DATA(ld_i_profile).
 
"SELECT single VBELN FROM VEDA INTO @DATA(ld_i_vbeln).
 
"SELECT single VPOSN FROM VEDA INTO @DATA(ld_i_vposn).
 
"SELECT single FEHGR FROM TVUV INTO @DATA(ld_i_fehgr).
 
 
"SELECT single VPOSN FROM VEDA INTO @DATA(ld_i_uepos).
 
 


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!