SAP EXIT_SAPLVEDE_004 Function Module for SD EDI REQOTE: Customer Enhancement to Import Additional Data









EXIT_SAPLVEDE_004 is a standard exit saplvede 004 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SD EDI REQOTE: Customer Enhancement to Import Additional Data 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 exit saplvede 004 FM, simply by entering the name EXIT_SAPLVEDE_004 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLVEDE_004 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 'EXIT_SAPLVEDE_004'"SD EDI REQOTE: Customer Enhancement to Import Additional Data
  EXPORTING
*  DOBJECT =  "Output Control
*  DCONTROL_RECORD_OUT =  "Control Record

CHANGING
*  DXVBAK =  "Order Header
*  DXHVBKD =  "Sales Document: Business Data

TABLES
*  DXVBPA =  "Order Partner
*  DXVBAP =  "Order Items
*  DXVBEP =  "Sales Order Schedule Lines
*  DXVBKD =  "Sales Document: Business Data

EXCEPTIONS
   ERROR_MESSAGE_RECEIVED = 1    DATA_NOT_RELEVANT_FOR_SENDING = 2
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
IDOC_OUTPUT_QUOTES NOTRANSL: Ausgabe Auftragsbestätigung für EDI in Zwischenstruktur ab Relea

IMPORTING Parameters details for EXIT_SAPLVEDE_004

DOBJECT - Output Control

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

DCONTROL_RECORD_OUT - Control Record

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

CHANGING Parameters details for EXIT_SAPLVEDE_004

DXVBAK - Order Header

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

DXHVBKD - Sales Document: Business Data

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

TABLES Parameters details for EXIT_SAPLVEDE_004

DXVBPA - Order Partner

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

DXVBAP - Order Items

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

DXVBEP - Sales Order Schedule Lines

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

DXVBKD - Sales Document: Business Data

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

EXCEPTIONS details

ERROR_MESSAGE_RECEIVED -

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

DATA_NOT_RELEVANT_FOR_SENDING -

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

Copy and paste ABAP code example for EXIT_SAPLVEDE_004 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_dxvbak  TYPE VBAK, "   
lt_dxvbpa  TYPE STANDARD TABLE OF VBPA, "   
lv_dobject  TYPE NAST, "   
lv_error_message_received  TYPE NAST, "   
lt_dxvbap  TYPE STANDARD TABLE OF VBAP, "   
lv_dxhvbkd  TYPE VBKD, "   
lv_dcontrol_record_out  TYPE EDIDC, "   
lv_data_not_relevant_for_sending  TYPE EDIDC, "   
lt_dxvbep  TYPE STANDARD TABLE OF VBEP, "   
lt_dxvbkd  TYPE STANDARD TABLE OF VBKD. "   

  CALL FUNCTION 'EXIT_SAPLVEDE_004'  "SD EDI REQOTE: Customer Enhancement to Import Additional Data
    EXPORTING
         DOBJECT = lv_dobject
         DCONTROL_RECORD_OUT = lv_dcontrol_record_out
    CHANGING
         DXVBAK = lv_dxvbak
         DXHVBKD = lv_dxhvbkd
    TABLES
         DXVBPA = lt_dxvbpa
         DXVBAP = lt_dxvbap
         DXVBEP = lt_dxvbep
         DXVBKD = lt_dxvbkd
    EXCEPTIONS
        ERROR_MESSAGE_RECEIVED = 1
        DATA_NOT_RELEVANT_FOR_SENDING = 2
. " EXIT_SAPLVEDE_004




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLVEDE_004

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.

 
 
 
 
 
 
 
 
 
 


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!