SAP EXIT_SAPLVEDA_007 Function Module for SD EDI: Incoming Orders: Create Customer Number/Sales Area
EXIT_SAPLVEDA_007 is a standard exit saplveda 007 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: Incoming Orders: Create Customer Number/Sales Area 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 saplveda 007 FM, simply by entering the name EXIT_SAPLVEDA_007 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XVED
Program Name: SAPLXVED
Main Program: SAPLXVED
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLVEDA_007 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_SAPLVEDA_007'"SD EDI: Incoming Orders: Create Customer Number/Sales Area.
EXPORTING
* DVTCOMAG = "Communications Work Area for Cust.Master Accesses
* CNTRL = "IDOC Control Record
CHANGING
* DXVBAK = "Order Header (Enhanced)
* DD_FLAG_K = "Internal Structure Header Screen Control
TABLES
* DXBDCDATA = "Batch Input Table
* DXKOMV = "Condition Table
* DXVEKP = "Packing Proposal
* DYVEKP = "Shipping Units
* DXVBAP = "Order Items (Enhanced)
* DXVBEP = "Order Schedule Lines (1) (Enhanced)
* DYVBEP = "Order Schedule Lines (2) (Enhanced)
* DXVBADR = "Addresses (1) (enhanced)
* DYVBADR = "Addresses (2) (enhanced)
* DXVBPA = "Order Partner
* DXVBUV = "Sales Document: Incompletion Log
* DD_FLAG_P = "Internal Table Item Screen Control
EXCEPTIONS
USER_ERROR = 1
Related IDocs
Below is a list of IDoc processing function modules and the associated IDocs this Function user exits is relevant for.IDOC_INPUT_ORDERS - SAP IDoc ORDERS01
IDOC_INPUT_ORDERS - SAP IDoc ORDERS01
IDOC_INPUT_ORDERS - SAP IDoc ORDERS01
IDOC_INPUT_ORDERS - SAP IDoc ORDERS02
IDOC_INPUT_ORDERS - SAP IDoc ORDERS02
IDOC_INPUT_ORDERS - SAP IDoc ORDERS02
IDOC_INPUT_ORDERS - SAP IDoc ORDERS03
IDOC_INPUT_ORDERS - SAP IDoc ORDERS03
IDOC_INPUT_ORDERS - SAP IDoc ORDERS03
IDOC_INPUT_ORDERS - SAP IDoc ORDERS03
IDOC_INPUT_ORDERS - SAP IDoc ORDERS03
IDOC_INPUT_ORDERS - SAP IDoc ORDERS04
IDOC_INPUT_ORDERS - SAP IDoc ORDERS04
IDOC_INPUT_ORDERS - SAP IDoc ORDERS04
IDOC_INPUT_ORDERS - SAP IDoc ORDERS05
IDOC_INPUT_ORDERS - SAP IDoc ORDERS05
IDOC_INPUT_ORDERS - SAP IDoc ORDERS05
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.IDOC_ORDERS_ADV_RETURNS_CREATE Create ARM Returns Order in ORDERS IDoc Inbound
IMPORTING Parameters details for EXIT_SAPLVEDA_007
DVTCOMAG - Communications Work Area for Cust.Master Accesses
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
CNTRL - IDOC Control Record
Data type: EDIDCOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPLVEDA_007
DXVBAK - Order Header (Enhanced)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DD_FLAG_K - Internal Structure Header Screen Control
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLVEDA_007
DXBDCDATA - Batch Input Table
Data type: BDCDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
DXKOMV - Condition Table
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DXVEKP - Packing Proposal
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DYVEKP - Shipping Units
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DXVBAP - Order Items (Enhanced)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DXVBEP - Order Schedule Lines (1) (Enhanced)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DYVBEP - Order Schedule Lines (2) (Enhanced)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DXVBADR - Addresses (1) (enhanced)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DYVBADR - Addresses (2) (enhanced)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DXVBPA - Order Partner
Data type: VBPAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
DXVBUV - Sales Document: Incompletion Log
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
DD_FLAG_P - Internal Table Item Screen Control
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
USER_ERROR - Error in Customer Enhancement
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLVEDA_007 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 STRING, " | |||
| lv_dvtcomag | TYPE STRING, " | |||
| lt_dxbdcdata | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_user_error | TYPE BDCDATA, " | |||
| lt_dxkomv | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lt_dxvekp | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lt_dyvekp | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_cntrl | TYPE EDIDC, " | |||
| lt_dxvbap | TYPE STANDARD TABLE OF EDIDC, " | |||
| lv_dd_flag_k | TYPE EDIDC, " | |||
| lt_dxvbep | TYPE STANDARD TABLE OF EDIDC, " | |||
| lt_dyvbep | TYPE STANDARD TABLE OF EDIDC, " | |||
| lt_dxvbadr | TYPE STANDARD TABLE OF EDIDC, " | |||
| lt_dyvbadr | TYPE STANDARD TABLE OF EDIDC, " | |||
| lt_dxvbpa | TYPE STANDARD TABLE OF VBPAVB, " | |||
| lt_dxvbuv | TYPE STANDARD TABLE OF VBPAVB, " | |||
| lt_dd_flag_p | TYPE STANDARD TABLE OF VBPAVB. " |
|   CALL FUNCTION 'EXIT_SAPLVEDA_007' "SD EDI: Incoming Orders: Create Customer Number/Sales Area |
| EXPORTING | ||
| DVTCOMAG | = lv_dvtcomag | |
| CNTRL | = lv_cntrl | |
| CHANGING | ||
| DXVBAK | = lv_dxvbak | |
| DD_FLAG_K | = lv_dd_flag_k | |
| TABLES | ||
| DXBDCDATA | = lt_dxbdcdata | |
| DXKOMV | = lt_dxkomv | |
| DXVEKP | = lt_dxvekp | |
| DYVEKP | = lt_dyvekp | |
| DXVBAP | = lt_dxvbap | |
| DXVBEP | = lt_dxvbep | |
| DYVBEP | = lt_dyvbep | |
| DXVBADR | = lt_dxvbadr | |
| DYVBADR | = lt_dyvbadr | |
| DXVBPA | = lt_dxvbpa | |
| DXVBUV | = lt_dxvbuv | |
| DD_FLAG_P | = lt_dd_flag_p | |
| EXCEPTIONS | ||
| USER_ERROR = 1 | ||
| . " EXIT_SAPLVEDA_007 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLVEDA_007
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.See full list of SAP IDocs
See full list of SAP Function Modules
Search for further information about these or an SAP related objects