SAP EXIT_SAPLVEDC_002 Function Module for Customer Enhancement for Data Segments Sales Order Confirmation









EXIT_SAPLVEDC_002 is a standard exit saplvedc 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customer Enhancement for Data Segments Sales Order Confirmation 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 saplvedc 002 FM, simply by entering the name EXIT_SAPLVEDC_002 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_SAPLVEDC_002 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_SAPLVEDC_002'"Customer Enhancement for Data Segments Sales Order Confirmation
EXPORTING
DXVBAK = "Sales Document: Header Data
DXHVBKD = "Sales Document: Business Data
* DOBJECT = "

TABLES
INT_EDIDD = "Data Segment (IDoc)
DXVBPA = "Sales Document: Partner
DXVBAP = "Sales Document: Item Data
DXVBEP = "Sales Document: Schedule Line Data
DXVBKD = "Sales Document: Business Data
* DIKOMV = "Pricing Communications-Condition Record
* DIKOMVD = "Pricing Communications_Conditions Record for D

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_ORDRSP Issue Order Confirmation for EDI in IDOC Type as of Release 3.0A

IMPORTING Parameters details for EXIT_SAPLVEDC_002

DXVBAK - Sales Document: Header Data

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

DXHVBKD - Sales Document: Business Data

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

DOBJECT -

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

TABLES Parameters details for EXIT_SAPLVEDC_002

INT_EDIDD - Data Segment (IDoc)

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

DXVBPA - Sales Document: Partner

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

DXVBAP - Sales Document: Item Data

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

DXVBEP - Sales Document: Schedule Line Data

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

DXVBKD - Sales Document: Business Data

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

DIKOMV - Pricing Communications-Condition Record

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

DIKOMVD - Pricing Communications_Conditions Record for D

Data type: KOMVD
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_SAPLVEDC_002 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_int_edidd  TYPE STANDARD TABLE OF EDIDD, "   
lv_error_message_received  TYPE EDIDD, "   
lt_dxvbpa  TYPE STANDARD TABLE OF VBPA, "   
lv_dxhvbkd  TYPE VBKD, "   
lv_data_not_relevant_for_sending  TYPE VBKD, "   
lt_dxvbap  TYPE STANDARD TABLE OF VBAP, "   
lv_dobject  TYPE NAST, "   
lt_dxvbep  TYPE STANDARD TABLE OF VBEP, "   
lt_dxvbkd  TYPE STANDARD TABLE OF VBKD, "   
lt_dikomv  TYPE STANDARD TABLE OF KOMV, "   
lt_dikomvd  TYPE STANDARD TABLE OF KOMVD. "   

  CALL FUNCTION 'EXIT_SAPLVEDC_002'  "Customer Enhancement for Data Segments Sales Order Confirmation
    EXPORTING
         DXVBAK = lv_dxvbak
         DXHVBKD = lv_dxhvbkd
         DOBJECT = lv_dobject
    TABLES
         INT_EDIDD = lt_int_edidd
         DXVBPA = lt_dxvbpa
         DXVBAP = lt_dxvbap
         DXVBEP = lt_dxvbep
         DXVBKD = lt_dxvbkd
         DIKOMV = lt_dikomv
         DIKOMVD = lt_dikomvd
    EXCEPTIONS
        ERROR_MESSAGE_RECEIVED = 1
        DATA_NOT_RELEVANT_FOR_SENDING = 2
. " EXIT_SAPLVEDC_002




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLVEDC_002

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!