SAP RS_VARIANT_ADD Function Module for









RS_VARIANT_ADD is a standard rs variant add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rs variant add FM, simply by entering the name RS_VARIANT_ADD into the relevant SAP transaction such as SE37 or SE38.

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



Function RS_VARIANT_ADD 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 'RS_VARIANT_ADD'"
EXPORTING
REPORT = "Name of report created for variant
* VARIANT = ' ' "
* SCREENNUMBER = ' ' "

IMPORTING
VARIANT = "

TABLES
* SCREENS = "

EXCEPTIONS
ILLEGAL_VARIANT_NAME = 1 NO_SELECTIONSCREENS = 10 NOT_AUTHORIZED = 2 NOT_EXECUTED = 3 NO_REPORT = 4 REPORT_NOT_EXISTENT = 5 REPORT_NOT_SUPPLIED = 6 VARIANT_EXISTS = 7 VARIANT_LOCKED = 8 VARIANT_NOT_SUPPLIED = 9
.



IMPORTING Parameters details for RS_VARIANT_ADD

REPORT - Name of report created for variant

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

VARIANT -

Data type: RSVAR-VARIANT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCREENNUMBER -

Data type: RSVAR-DYNNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RS_VARIANT_ADD

VARIANT -

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

TABLES Parameters details for RS_VARIANT_ADD

SCREENS -

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

EXCEPTIONS details

ILLEGAL_VARIANT_NAME - Incorrect variant name

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

NO_SELECTIONSCREENS -

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

NOT_AUTHORIZED - No Authorization

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

NOT_EXECUTED - No variant created

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

NO_REPORT - Program type other than '1'

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

REPORT_NOT_EXISTENT - Report does not exist

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

REPORT_NOT_SUPPLIED - No report name specified

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

VARIANT_EXISTS - Layout Already Exists

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

VARIANT_LOCKED - Variant locked

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

VARIANT_NOT_SUPPLIED - No variant name specified

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

Copy and paste ABAP code example for RS_VARIANT_ADD 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_report  TYPE RSVAR-REPORT, "   
lt_screens  TYPE STANDARD TABLE OF RSSCREENS, "   
lv_variant  TYPE RSVAR-VARIANT, "   
lv_illegal_variant_name  TYPE RSVAR, "   
lv_no_selectionscreens  TYPE RSVAR, "   
lv_variant  TYPE RSVAR-VARIANT, "   SPACE
lv_not_authorized  TYPE RSVAR, "   
lv_not_executed  TYPE RSVAR, "   
lv_screennumber  TYPE RSVAR-DYNNR, "   SPACE
lv_no_report  TYPE RSVAR, "   
lv_report_not_existent  TYPE RSVAR, "   
lv_report_not_supplied  TYPE RSVAR, "   
lv_variant_exists  TYPE RSVAR, "   
lv_variant_locked  TYPE RSVAR, "   
lv_variant_not_supplied  TYPE RSVAR. "   

  CALL FUNCTION 'RS_VARIANT_ADD'  "
    EXPORTING
         REPORT = lv_report
         VARIANT = lv_variant
         SCREENNUMBER = lv_screennumber
    IMPORTING
         VARIANT = lv_variant
    TABLES
         SCREENS = lt_screens
    EXCEPTIONS
        ILLEGAL_VARIANT_NAME = 1
        NO_SELECTIONSCREENS = 10
        NOT_AUTHORIZED = 2
        NOT_EXECUTED = 3
        NO_REPORT = 4
        REPORT_NOT_EXISTENT = 5
        REPORT_NOT_SUPPLIED = 6
        VARIANT_EXISTS = 7
        VARIANT_LOCKED = 8
        VARIANT_NOT_SUPPLIED = 9
. " RS_VARIANT_ADD




ABAP code using 7.40 inline data declarations to call FM RS_VARIANT_ADD

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 REPORT FROM RSVAR INTO @DATA(ld_report).
 
 
"SELECT single VARIANT FROM RSVAR INTO @DATA(ld_variant).
 
 
 
"SELECT single VARIANT FROM RSVAR INTO @DATA(ld_variant).
DATA(ld_variant) = ' '.
 
 
 
"SELECT single DYNNR FROM RSVAR INTO @DATA(ld_screennumber).
DATA(ld_screennumber) = ' '.
 
 
 
 
 
 
 


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!