SAP RV_CALL_CHANGE_TRANSACTION Function Module for Access SD document display transactions









RV_CALL_CHANGE_TRANSACTION is a standard rv call change transaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Access SD document display transactions 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 rv call change transaction FM, simply by entering the name RV_CALL_CHANGE_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.

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



Function RV_CALL_CHANGE_TRANSACTION 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 'RV_CALL_CHANGE_TRANSACTION'"Access SD document display transactions
EXPORTING
* BUKRS = ' ' "Company code (RF document)
* FCODE = ' ' "Function code
* GJAHR = '0000' "Fiscal year (RF document)
* LGNUM = ' ' "Storage location (WM)
* POSNR = '000000' "Line item
VBELN = "Document number
* VBTYP = ' ' "Document category
.



IMPORTING Parameters details for RV_CALL_CHANGE_TRANSACTION

BUKRS - Company code (RF document)

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

FCODE - Function code

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

GJAHR - Fiscal year (RF document)

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

LGNUM - Storage location (WM)

Data type: VBFA-LGNUM
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

POSNR - Line item

Data type: VBAP-POSNR
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VBELN - Document number

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

VBTYP - Document category

Data type: VBUK-VBTYP
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RV_CALL_CHANGE_TRANSACTION 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_bukrs  TYPE STRING, "   ' '
lv_fcode  TYPE STRING, "   ' '
lv_gjahr  TYPE STRING, "   '0000'
lv_lgnum  TYPE VBFA-LGNUM, "   ' '
lv_posnr  TYPE VBAP-POSNR, "   '000000'
lv_vbeln  TYPE VBUK-VBELN, "   
lv_vbtyp  TYPE VBUK-VBTYP. "   ' '

  CALL FUNCTION 'RV_CALL_CHANGE_TRANSACTION'  "Access SD document display transactions
    EXPORTING
         BUKRS = lv_bukrs
         FCODE = lv_fcode
         GJAHR = lv_gjahr
         LGNUM = lv_lgnum
         POSNR = lv_posnr
         VBELN = lv_vbeln
         VBTYP = lv_vbtyp
. " RV_CALL_CHANGE_TRANSACTION




ABAP code using 7.40 inline data declarations to call FM RV_CALL_CHANGE_TRANSACTION

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.

DATA(ld_bukrs) = ' '.
 
DATA(ld_fcode) = ' '.
 
DATA(ld_gjahr) = '0000'.
 
"SELECT single LGNUM FROM VBFA INTO @DATA(ld_lgnum).
DATA(ld_lgnum) = ' '.
 
"SELECT single POSNR FROM VBAP INTO @DATA(ld_posnr).
DATA(ld_posnr) = '000000'.
 
"SELECT single VBELN FROM VBUK INTO @DATA(ld_vbeln).
 
"SELECT single VBTYP FROM VBUK INTO @DATA(ld_vbtyp).
DATA(ld_vbtyp) = ' '.
 


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!