SAP SVRS_AFTER_CHANGED_ONLINE_INT Function Module for Version management call after release (in ONLINE)









SVRS_AFTER_CHANGED_ONLINE_INT is a standard svrs after changed online int SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Version management call after release (in ONLINE) 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 svrs after changed online int FM, simply by entering the name SVRS_AFTER_CHANGED_ONLINE_INT into the relevant SAP transaction such as SE37 or SE38.

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



Function SVRS_AFTER_CHANGED_ONLINE_INT 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 'SVRS_AFTER_CHANGED_ONLINE_INT'"Version management call after release (in ONLINE)
EXPORTING
E071_ENTRY = "Table E071 entry
* STATUS = 'A' "

IMPORTING
VERSION_NEW = "

EXCEPTIONS
NON_VERSIONABLE_OBJTYPE = 1 NO_TADIR_ENTRY = 2 OBJECT_NOT_FOUND = 3 OBJECT_NOT_LOCKED = 4
.



IMPORTING Parameters details for SVRS_AFTER_CHANGED_ONLINE_INT

E071_ENTRY - Table E071 entry

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

STATUS -

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

EXPORTING Parameters details for SVRS_AFTER_CHANGED_ONLINE_INT

VERSION_NEW -

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

EXCEPTIONS details

NON_VERSIONABLE_OBJTYPE -

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

NO_TADIR_ENTRY -

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

OBJECT_NOT_FOUND -

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

OBJECT_NOT_LOCKED -

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

Copy and paste ABAP code example for SVRS_AFTER_CHANGED_ONLINE_INT 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_e071_entry  TYPE E071, "   
lv_version_new  TYPE VRSD-VERSNO, "   
lv_non_versionable_objtype  TYPE VRSD, "   
lv_status  TYPE C, "   'A'
lv_no_tadir_entry  TYPE C, "   
lv_object_not_found  TYPE C, "   
lv_object_not_locked  TYPE C. "   

  CALL FUNCTION 'SVRS_AFTER_CHANGED_ONLINE_INT'  "Version management call after release (in ONLINE)
    EXPORTING
         E071_ENTRY = lv_e071_entry
         STATUS = lv_status
    IMPORTING
         VERSION_NEW = lv_version_new
    EXCEPTIONS
        NON_VERSIONABLE_OBJTYPE = 1
        NO_TADIR_ENTRY = 2
        OBJECT_NOT_FOUND = 3
        OBJECT_NOT_LOCKED = 4
. " SVRS_AFTER_CHANGED_ONLINE_INT




ABAP code using 7.40 inline data declarations to call FM SVRS_AFTER_CHANGED_ONLINE_INT

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 VERSNO FROM VRSD INTO @DATA(ld_version_new).
 
 
DATA(ld_status) = 'A'.
 
 
 
 


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!