SAP SD_XVEDA_CHANGES Function Module for NOTRANSL: Änderungen der Vertragsdaten für die Änderungsbelege









SD_XVEDA_CHANGES is a standard sd xveda changes 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: Änderungen der Vertragsdaten für die Änderungsbelege 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 xveda changes FM, simply by entering the name SD_XVEDA_CHANGES 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_XVEDA_CHANGES 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_XVEDA_CHANGES'"NOTRANSL: Änderungen der Vertragsdaten für die Änderungsbelege
EXPORTING
I_DOCUMENT_NUMBER = "Contract Document Number
I_POSNR_LOW = "

TABLES
FXVEDA = "Current status
FYVEDA = "Old status
.




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_XVEDA_CHANGES

I_DOCUMENT_NUMBER - Contract Document Number

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

I_POSNR_LOW -

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

TABLES Parameters details for SD_XVEDA_CHANGES

FXVEDA - Current status

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

FYVEDA - Old status

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

Copy and paste ABAP code example for SD_XVEDA_CHANGES 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:
lt_fxveda  TYPE STANDARD TABLE OF VEDAVB, "   
lv_i_document_number  TYPE VEDA-VBELN, "   
lt_fyveda  TYPE STANDARD TABLE OF VEDAVB, "   
lv_i_posnr_low  TYPE VEDA-VPOSN. "   

  CALL FUNCTION 'SD_XVEDA_CHANGES'  "NOTRANSL: Änderungen der Vertragsdaten für die Änderungsbelege
    EXPORTING
         I_DOCUMENT_NUMBER = lv_i_document_number
         I_POSNR_LOW = lv_i_posnr_low
    TABLES
         FXVEDA = lt_fxveda
         FYVEDA = lt_fyveda
. " SD_XVEDA_CHANGES




ABAP code using 7.40 inline data declarations to call FM SD_XVEDA_CHANGES

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 VBELN FROM VEDA INTO @DATA(ld_i_document_number).
 
 
"SELECT single VPOSN FROM VEDA INTO @DATA(ld_i_posnr_low).
 


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!