Variant Setting

How to set any variant as default to selection screen?

Hi,

1.Go to the selection screen of the particular report.
2.Give ur inputs for select-options and parameters.
3.And click SAVE button, it will take u to the variant screen.
4.Give the name of the variant and save.
That's it.
Reward points if found useful.
Regards,
Sathya Rajkumar.

Similar Messages

Variable Personalization - "Save Value" Variant Setting missing in Bex 7.x

Hallo Experts,
in Bex 3.x when creating a Variant (Button "Save All Variants" in the Variable Pop-Up) i was able to decide (via field "Save Values" in the "Save All Variants" Screen) wheter i want to save the values for a certain variable or not (NO_IMPORT).
In Bex 7.x i'm not able to find a functionality (corresponding to NO_IMPORT) to decide which variable should be saved in the variant.
Does anybody know if/where i can find this feature in BEX 7.x?
Thanks in advance,
Sabine

Hallo Den,
thanks for your reply!
Unfortunately this doesn't solve my problem. It's not about saving variants in Bex 7.x. But different behaviour in Bex 7.x compared to Bex 3.x.
In Bex 3.x when saving a variant it was possible to decide, whether a value for the variable should be saved or not (via drop down boxes in the "Save All Variants" screen).
In Bex 7.x i just can set the variable value to blank, if i don't want a value to be saved. I have no more settings here, as in Bex 3.x.
As a consequence: i can set mandatory variables to blank in a 3.x query, when i set "Save Values" for this variable to "NO". In Bex 7.X i will always get an Error Message ("enter a value for variable XY") when selecting a variant with mandatory variable = blank.
Best regards,
Sabine

Broadcaster issue - variant setting

Hi experts,
we use Broadcaster for BI7 on portal and it runs good. But if I try to craete a new variant, this wil not take over. Following steps were done:
1. open a WebTemplate
2. go to tab 'General Precalculation'
3. select a variable (e.g. VAR03)
4. click 'Create'
5. get a popup and enter a name
6.SAVE
--> Unfortunaltely in the view for the used varialbe it is nothing shown.
Can you help me?
Thanks a lot.
Regards,
Marco

Hi Katrice,
      Thank you for the reply and the links, I will go through them, but please find below the code that I presently have in place, could you please advise if there is anything missing or wrong in here.
Thanks & Regards,
Divaker
lo_cmp_usage =   wd_this->wd_cpuse_pwq_alv( ).
IF lo_cmp_usage->has_active_component( ) IS INITIAL.
    lo_cmp_usage->create_component( ).
ENDIF.
lo_interfacecontroller =   wd_this->wd_cpifc_pwq_alv( ).
* enable column adjustment
lv_value = lo_interfacecontroller->get_model( ).
*-- Get the API reference
lo_api_interfacecontroller = lo_interfacecontroller->wd_get_api( ).
CALL METHOD lo_api_interfacecontroller->get_personalization_manager
    RECEIVING
      pers_manager = lo_pers.
IF lo_pers IS NOT INITIAL.
    CALL METHOD lo_pers->get_variants
      RECEIVING
        variants = lt_var.
ENDIF.
IF lt_var IS NOT INITIAL.
    READ TABLE lt_var INTO ls_var INDEX 1.
    IF sy-subrc = 0.
      ls_config_key-config_id   = ls_var-config_id.
      ls_config_key-config_type = ls_var-config_type.
      ls_config_key-config_var = ls_var-config_var.
    ENDIF.
    TRY.
        CALL METHOD lo_pers->set_default_variant
          EXPORTING
            config_key = ls_config_key
            set        = abap_true.
      CATCH cx_wd_personalization .
    ENDTRY.
    CALL METHOD lo_pers->load_config_by_key
      EXPORTING
        config_key            = ls_config_key
        fetch_default_variant = abap_true.
ENDIF.

User specific default variant setting

Hi gurus,
My requirement is Report should get executed with default user specific Variant.
For example while running MB51 system should pick the corresponding variant based on the user who is executing the report.
Based on threads i created variants with U_userid like U_RAM & U_LAX.
I checked with user ids of RAM and LAX, But system is not picking automatically.
can u help me

hi,
see this.
https://forums.sdn.sap.com/click.jspa?searchID=14929390&messageID=5872211

Fiscal Year Variant set up

Hi Emmanuel,
Can you please explain me how the FYV works with an example?
I want to know how it works, if we follow 4,4,5 in demand planning.I am unable to set up the fyv.
I hope u can elaborate the set up in detail.
Thanks in advance

Hi Emmanuel,
Here i have some qns reg the set up,
How do i configure the fyv if i want to save or view the data in posting periods (granularity is less than a week....e.g. week is divided into two)?
Can you please help me in understanding this concept more clearly with an example and give me the steps to configure, so that i can try it out in my system.
I need step by step procedure, begining creating of posting periods till i see it in pbook. I will try the same in my system and see how it works.
we currently do planning in both weeks and months.
4-4-5 means
1st period -4 weeks
2nd period -4weeks
3rd period -5 weeks.
If my qn is not clear, please use your own example from one of your previous implementation and give me the config steps ,if possible with some screen shots.
I hope you will help me on this, as it is very crucial
Regards,

[SOLVED] Keyboard layout not setting correctly after gnome 3.14 update

Hey all,
After the gnome 3.14 update my keyboard appears to be reverting to US when I want to have it set to UK layout. It was fine before the update, and I have i3 & XFCE installed and for both of those my keyboard layout is getting set to UK just fine, so it appears to be just the gnome 3.14 update that is the problem.
Here is my contents of /etc/X11/xorg.conf.d/10-keyboard.conf:
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "gb"
EndSection
Anyone have any ideas what the problem could be?
Last edited by Morgy (2014-10-18 17:18:09)

My situation showed an extra issue related to this change.
After the upgrade I started getting two layouts (us,us) instead of just one (us).
$ setxkbmap -query
rules: evdev
model: pc104
layout: us,us
variant: ,
options: ctrl:nocaps
That broke my variant setting, which was altgr-intl (set via /etc/X11/xorg.conf.d/10-evdev.conf). I was able to manually set that to "altgr-intl,altgr-intl" (with setxkbmap), and that worked.
After adding an input source as described above, of "English (international AltGr dead keys)", everything started working again for my purposes, without manually running setxkbmap, but I still have the extra layout:
$ setxkbmap -query
rules: evdev
model: pc104
layout: us,us
variant: altgr-intl,
options: ctrl:nocaps
Does anyone know a current method for completely disabling GNOME's keyboard management?
(I've tried several things from Google, but nothing seems to work for the current version).

Modify hidden parameter in variant

I'm submitting a report in a program using a variant just to be sure (the report fills many optional parameters depending on user parameters).
Yesterday I found out the program is crashing because of a hidden parameter that gets filled depending on previous action from some users.
So I have two options
- Change the submit to make sure the parameters is always set to off.
- Change the variant setting the parameter off.
I would think the second option is the easiest, but I can't find a way to manually modify the hidden parameter in the variant in the production system.
Yes, I could modify it in development and then transport it but that would imply a transport request and I'm trying to avoid that.

Yes, there is a parameter id involved.
The no-display parameter has three states.
Y- Display ALV grid
N- Display ALV list
Others - Check previous user preferences using a parameter id
I want the report to always be displayed as an ALV List because I need to export it to memory. However, I never submit this parameter in the first place and the variant I'm using has the parameter empty, so it always checks the user preferences.
Changing the parameter id is not an option.
I tried in development and I do can change the content of the parameter using the debugger and later saving the variant the value stays.
But as I said, I want to avoid anything concerning a transport request right now. If I can change the value of the parameter to 'N' right into production it would be great

ALV Variant chosen in grid

Hi.
I have to following issue.
I have a program that through the use of additional buttons I added to my ALV grid can jump between different ALV grids.
The problem I'm having is that when you change the variant for ALV grid1 while viewing it and than change to grid 2, when you go back to grid1 the selected variant isn't used anymore.
So what I need is a way see check which variant is active when I get to the USER_COMMAND function of the ALV grid.
If someone has the answer to this I'd be very happy.
Regards,
Arthur

A. Parisius,
Do the following step so that you cant loose variant u set when u come to primary alv from secondary ALV.
1.
When you export I_SAVE = 'X' or 'A' through REUSE_ALV_GEID_DISPLAY, you can save variant on ALV output.you can save different variants for one output.
2.
Define one parameter to select variant on selection-screen itself instead of selecting on Output.
parameters :p_layout like disvariant-variant.
3.
F4 help to get variants set for the report.
at selection-screen on value-request for p_layout.
perform get_variant.
subroutine code and define w_variant structure type disvariant.
*& Form get_variant
form get_variant.
data: lw_variant type disvariant,
 l_exit type char1.
lw_variant-report = sy-repid.
call function 'REUSE_ALV_VARIANT_F4'
 exporting
 is_variant = lw_variant
 i_save = 'A'
 importing
 e_exit = l_exit
 es_variant = lw_variant
 exceptions
 not_found = 2.
if sy-subrc = 2.
 message id sy-msgid type 'S' number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
 if l_exit eq space.
 p_layout = lw_variant-variant.
 if not p_layout is initial.
 perform get_w_variant.
 endif.
 endif.
endif.
endform. " get_variant
*& Form get_w_variant
form get_w_variant.
w_variant-report = sy-repid.
w_variant-handle = space.
w_variant-log_group = space.
w_variant-username = space.
w_variant-variant = p_layout.
w_variant-text = space.
w_variant-dependvars = space.
endform. " get_w_variant
4.
Pass w_variant structure through REUSE_ALV_GRID_DISPLAY FM .
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
 I_CALLBACK_PROGRAM = 'ZVENKAT_TEST1' "Program name
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 IT_FIELDCAT = i_field
 IT_SORT = i_sort
 I_SAVE = 'X'
 IS_VARIANT = w_variant "If you pass variant selected on selection-screen
 "on F4 help,corresponding output is displayed
TABLES
 T_OUTTAB = <i_tab>
EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
5.
If you select variant and pass through FM it will be remained when u come back from secondary ALV..
I hope that it helps u .
Regards,
Venkat.O

Requisitions Document Overview Personal Variant

Hello all,
I am creating a variant for Purchasing Requisitions Document Overview and want it to be always shown in 'my variants' tab just below the standard one of the system.Occasionally the variant is lost and have to run it through Purchase Requisitions standard systems variants in order to be entered again in the variants set for me.
Is there any way to avoid this?
Thank you for any help.

Please do not confuse the "release date" in the PR detail tab Quantities/Dates and the DATE the PR was released (assuming you have release strategies). The release date is the date when the buyer must send a PO to the vendor or the material will not be received on time (includes Total Replenishment Lead Time). The F1 help on this field states:
Purchase Requisition Release Date
    Specifies the date on which the purchase order should be initiated on
    the basis of the purchase requisition.
    The release date is based on:
    o   The purchasing department processing time defined for the plant
    o   The planned delivery time from the material master record or purchasing info record
    o   The delivery date
    o   The goods receipt processing time from the material master record
    Note
        The planned delivery time from the purchasing info record and the GR
        processing time are only taken into account if the purchase
        requisition was generated via materials planning.*
Hope this helps

WD -SALV- setting initial view

Hi everyone,
I saw some forums in SDN about setting the initial View in a SALV.
Someone suggested to use R_COMPONENT of type IF_SALV_WD_COMP_TABLE_PERS in order to call the method SET_STANDARD_VIEW.
But noone was able to indicate how r_component could be properly referenced. (Such Forums are anyhow marked as closed but unanswered).
I would be very pleased to know if someone managed to do it, and how.
Thank you so much.
Best Regards,
Christian

Hi,
Please refer to this code and make changes accordingly as per the conditions -
METHOD wddoinit.
DATA:
 lo_nd_mara TYPE REF TO if_wd_context_node,
 lt_mara TYPE wd_this->elements_mara,
 lo_cmp_usage TYPE REF TO if_wd_component_usage,
 lo_interfacecontroller TYPE REF TO iwci_salv_wd_table ,
 lo_api_interfacecontroller TYPE REF TO if_wd_controller,
 lo_pers TYPE REF TO if_wd_personalization,
 lv_value TYPE REF TO cl_salv_wd_config_table,
 lt_var TYPE wdr_pers_variants,
 wa_var TYPE wdr_pers_variant,
 ls_config_key TYPE wdy_config_key.
* navigate from <CONTEXT> to <MARA> via lead selection
lo_nd_mara = wd_context->get_child_node( name = wd_this->wdctx_mara ).
* Get material master data
SELECT * FROM mara INTO TABLE lt_mara UP TO 10 ROWS.
* @TODO handle non existant child
IF lo_nd_mara IS NOT INITIAL.
 lo_nd_mara->bind_table( new_items = lt_mara set_initial_elements = abap_false ).
ENDIF.
* Instantiate ALV
lo_cmp_usage = wd_this->wd_cpuse_alv_materials( ).
IF lo_cmp_usage->has_active_component( ) IS INITIAL.
 lo_cmp_usage->create_component( ).
ENDIF.
* Get the interface controller of the component usage
lo_interfacecontroller = wd_this->wd_cpifc_alv_materials( ).
* Get the model object of ALV
IF lo_interfacecontroller IS NOT INITIAL.
 lv_value = lo_interfacecontroller->get_model(
* Get the API reference
 lo_api_interfacecontroller = lo_interfacecontroller->wd_get_api( ).
ENDIF.
* Get personalization obect
IF lo_api_interfacecontroller IS NOT INITIAL.
 CALL METHOD lo_api_interfacecontroller->get_personalization_manager
 RECEIVING
 pers_manager = lo_pers.
ENDIF.
* Get variants
IF lo_pers IS NOT INITIAL.
 CALL METHOD lo_pers->get_variants
 RECEIVING
 variants = lt_var.
ENDIF.
* Set the default variant
* Required variant is read
* READ statement can be modified as per the requirement.
* As this application holds only one user variant, first record is read.
##read the respective records based on your condition
IF lt_var IS NOT INITIAL.
 READ TABLE lt_var INTO wa_var INDEX 1.
 IF sy-subrc EQ 0.
 ls_config_key-config_id = wa_var-config_id .
 ls_config_key-config_type = wa_var-config_type.
 ls_config_key-config_var = wa_var-config_var.
 ENDIF.
 TRY.
 CALL METHOD lo_pers->set_default_variant
 EXPORTING
 config_key = ls_config_key
 set = abap_true.
 CATCH cx_wd_personalization .
 ENDTRY.
* Get the variant information based on variant id
* Load the variant/ Set the default variant
 CALL METHOD lo_pers->load_config_by_key
 EXPORTING
 config_key = ls_config_key
 fetch_default_variant = abap_true.
ENDIF.
ENDMETHOD.
Regards,
Lekha.

Variant or Substitution for F-57

Hi Friends,
I want to update the profit center fileds of all items which is not happening in my posting. No enhancement available for this, so it is possible to make it thru substitution or thru variant.if it so thru variant then....
I want to create a Zvariant for Tcode:F-57 but its showing error that 'Variants are possible for dialog transaction'
I donno what's this? and please advise is it possible to do screen variant setting for F-57 in SHD0 and how?
or is there any standard variant available for Tcode:F-57
Please advise.
Its a main issue for me to reslove.
thanks & regards
sankar.
Edited by: sankar babu on Aug 23, 2008 6:55 AM

Not resolved
Posted as new issue.
regards
sankar.

Transction Variants

How can we Create and edit transaction variants?
How can we Create and edit screen variants?
How can we Manipulate screens with GuiXT?
Any one explain step by step with one example to practice?

Hi,
Variants are more useful when you need to schedule a job in background and fill the selection screen variables with some value.
Then you save the screen values in a variant and schedule the program in background with this variant setting. At the scheduled time, the program will execute with the values what you have set through the variant.
Transaction Variants
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
tables: tbtco.
data: jobcnt(1) type n,
t_sdluname like tbtco-sdluname,
t_strtdate like tbtco-strtdate,
t_strttime like tbtco-strttime.
ZXXX is the job name to check for
select * from tbtco where jobname = 'ZXXX'
and strtdate = sy-datum
and status = 'R'.
add 1 to jobcnt = jobcnt.
if jobcnt = 1.
t_sdluname = tbtco-sdluname.
t_strtdate = tbtco-strtdate.
t_strttime = tbtco-strttime.
else.
exit.
endif.
endselect.
if sy-subrc = 0.
if jobcnt >= 1.
message i999(b1) with t_sdluname ' has released job on '
t_strtdate t_strttime.
endif.
endif.
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
Using Transaction variants
Change SAP standard screens by hiding fields, screens, tabstrips, changing field properties, ... read on
Show all users per Application server
Transaction AL08
To log a user off via an ABAP
CALL 'SYST_LOGOFF'.
Advanced SM04 program
The following program displays the Ip address , workstation name , Nt user name etc. Plus you can send instant messages to users just by clicking on the user name. It will show a red band for users who exceeds session limit. ( That you can adjust ). Created this for R/3 4.6C and above. (Submitted by Joy Ramachandran) - Click here to download zuser.txt
Changing the SAP Logo on the top right of the SAPGui
Change file sapalogo.bmp in directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\default (SAP 4.6C)
Changing the Logo on the Right Hand Side ( Courtesy of: http://sapr3.tripod.com/ )
Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name Value to be set
START_IMAGE ZXXXX.GIF
RESIZE_IMAGE NO
Logoff and Login again
Automated transports
...so no need of giving the value for variable when the query runs next time,
BUT YOU HAVE TO CHOOSE THE VARIANT SAVED BEFORE...
Otherwise, if your intention is doing nothing, you have to look at personalization function:
http://help.sap.com/saphelp_nw2004s/helpdata/en/01/42c73c13b0ce5be10000000a114084/frameset.htm
Regards,
Padmam.

Can an Image Variant be configured to generate square resolutions?

My customer has a requirement that all Web Variants be square in dimension. The example: We create a "Web Standard" variant, set scale to "Yes", set width and height to a maximum of 150x150; and the original is 300x150.
We want the variant to be generated on a 150x150 white palette, with the actual image centered at 150x75.
I've been through table 37 in the MDM Console Reference Guide but cannot come up with the correct combination of parameters to produce the desired results.
Does anyone know if this is even possible? Is so, I would greatly appreciate some guidance.
Regards,
Mark Werkiser

My customer has a requirement that all Web Variants be square in dimension. The example: We create a "Web Standard" variant, set scale to "Yes", set width and height to a maximum of 150x150; and the original is 300x150.
We want the variant to be generated on a 150x150 white palette, with the actual image centered at 150x75.
I've been through table 37 in the MDM Console Reference Guide but cannot come up with the correct combination of parameters to produce the desired results.
Does anyone know if this is even possible? Is so, I would greatly appreciate some guidance.
Regards,
Mark Werkiser

Change Column content of ALV Variant

Hi,
I need to add a field in an existing variant for the layout of an ALV report. What I did was to add a field in a structure using Append Structure. The text that I first entered was wrong (field label of the data type of the field). Now, when I run the ALV Report, then when I choose to add a hidden field in the variant(setting>display variant>Current...), the wrong text is appearing even if I've already modified the field label of the data type.
Do I need to adjust something in order for the "Column Content" of the variant to be displayed properly?

After you made the change to the ALV catalog, try to re-create the variant again.
Thanks & regards,
Hadiman

Change Variant Issue [RS_VARIANT_CHANGE]

Hi,
I'm hoping to get some help with the problem below.
There are currently a number of variants set-up to be used with Program RGJVUXDT. On the bottom of the screen on the 2nd tab "Selections" there is a GL Accounts Range. I want to change the GL Accounts Selection Parameters that are associated with the variants.
The problem is I want to do this in an automated manner. A potential solution to this would be to use the RS_Variant* FM's to achieve this. But I have limited experience in the use of them.
Can I achieve the above by using RS_VARIANT_CHANGE? As I can't see any way for me to pass in the parameters I want to change.
Any sample code of a simple example of how to do this would be greatly appreciated.
Many thanks,
 Philip Johannesen

I've managed to write up some template code that works after looking at the range of RS_Variant FM's. If anyone else had a similiar question to mine above then here is a template solution:
REPORT ZCHANGE_VARIANT.
data: LS_VARIANTDESC LIKE VARID,
 ls_report_name type VARI_REPRT,
 ls_variant type VARIANT,
 it_selparam like standard table of RSPARAMS,
 wa_selparam like line of it_selparam.
 CLEAR LS_VARIANTDESC.
wa_selparam-selname ='S_MATNR'.
wa_selparam-kind ='S'.
wa_selparam-sign ='I'.
wa_selparam-option ='EQ'.
wa_selparam-low ='10830'.
append wa_selparam to it_selparam.
wa_selparam-selname ='S_MATNR'.
wa_selparam-kind ='S'.
wa_selparam-sign ='I'.
wa_selparam-option ='EQ'.
wa_selparam-low ='10860'.
append wa_selparam to it_selparam.
ls_report_name = 'ZDEMO_ALV_001'.
ls_variant = 'TEST1'.
LS_VARIANTDESC-REPORT = ls_report_name.
LS_VARIANTDESC-VARIANT = ls_variant.
LS_VARIANTDESC-ENVIRONMNT = 'A'.
LS_VARIANTDESC-AENAME = sy-mandt.
LS_VARIANTDESC-AENAME = SY-UNAME.
LS_VARIANTDESC-AEDAT = SY-DATUM.
LS_VARIANTDESC-AETIME = SY-UZEIT.
CALL FUNCTION 'RS_CHANGE_CREATED_VARIANT'
EXPORTING
 CURR_REPORT = ls_report_name
 CURR_VARIANT = ls_variant
 VARI_DESC = LS_VARIANTDESC
* ONLY_CONTENTS =
TABLES
 VARI_CONTENTS = it_selparam
* VARI_TEXT =
* VARI_SEL_DESC =
* OBJECTS =
* EXCEPTIONS
* ILLEGAL_REPORT_OR_VARIANT = 1
* ILLEGAL_VARIANTNAME = 2
* NOT_AUTHORIZED = 3
* NOT_EXECUTED = 4
* REPORT_NOT_EXISTENT = 5
* REPORT_NOT_SUPPLIED = 6
* VARIANT_DOESNT_EXIST = 7
* VARIANT_LOCKED = 8
* SELECTIONS_NO_MATCH = 9
* OTHERS = 10
Points to note:
Make sure the values of wa_selparam-selname, ls_report_name & ls_variant are Uppercase. Otherwise the variant will not be updated, as the select query makes no match on Table: VARID.
Regards,
 Philip Johannesen

Variant Setting

Similar Messages

Maybe you are looking for