Upgrade - Variants layout
Hi All,
do you know what happens to layout of standard report saved before an upgrade release, in particular from ECC 5.0 to ECC 6.0?
They will appear in upgraded system or I have to save it before and import after upgrading activities.
Question is for SD, but all answer are welcome,for MM - FI - CO and go on.
Thanks in advance
Salvio
Thanks for your reply Santosh,
for sure i was not clear at all,
what I mean is layout of display in transaction such as VA05, S_LR_87012249, standard transaction that offer possibilities to save layouts different form standard one.
Thanks a lot
Salvio
Similar Messages
-
Report painter variants/ layouts
Dear sirs,
a colleague of mine needs your experience. Our customer needs us to create some Report Painter reports with the possibility to change the layout. Is this/ something like this possible?
An example would be to pick up the columns or to change number format: see numbers in units or tousands of units. Something like ALV variants/ layout?
Any customizing option or workaround would help, thanks OttoMy users are very lazy and want me to do the columns changes automatically. An example: the supervisors work with much money and the want to see the numbers in tousands only. The basic users need to see the whole numbers. This is the simplified problem. And I don´t want to copy each RP report 5-10 times. And yes, I am an ABAPer, and if it would not be so time demanding requirement I would program the ALV reports instead of these RP.
New idea: could you extract the RP report code out of the generated report to reuse it in the standard ALV report?
Thank you for your effort, Otto -
How to make display variant layout as default ?
Hi All,
I have created display variant for VA05 layout as per user requirement.
Now whenever I execute VA05, I want that display variant layout should get defaulted. Currently SAP default one is executing and everytime I have to select manually my own display variant layout.
Please suggest.
Thanks.
Swarup.Hi,
you can set your layout as default.
Goto VA05, enter necessary info. press enter. system will give list of sales order
Goto settings, select layout and choose administration.
click on default setting for your layout ( you get right symbol for your layout) and save it.
Regards,
Chandra -
Copying variants & Layouts from 4.7 to ECC 6.0
Hi All,
Upgrading Client system from 4.7 to ECC 6.0. The 4.7 server would have its own variants and layout for different objects.
How do I copy those variants and layouts to my ECC 6.0 server?
Thanks for your valuable inputs.
RajeshHello prashant,
SPDA_GET_STACK_INFO will check wether all PATCH prerequisites are met or not your ST related level is not up to the required level.
Please check this requirement up the level of STand run it agin.
Thank you,
Shyam -
I ve an option on 1st screen to choose the variant for layout.
my 1st display with any selected layout is executing fine and displaying the list.
from this screen, if i come back and change the variant and execute... then its not displaying accordingly.
i am doing this by OO ABAP.
Any help plzcheck this, i guess this might help u.......
*Variables for variant
data:
wk_variant like disvariant,
wx_variant like disvariant,
wk_variant_save(1) type c,
wk_repid like sy-repid,
wk_exit(1) type c.
selection-screen begin of block b3 with frame title text-027.
parameters:p_vari like disvariant-variant. "Variant
selection-screen end of block b3.
initialization.
perform f_init_variant.
perform f_variant_default using p_vari.
*This event is used for Layout Variant
at selection-screen on value-request for p_vari.
perform f_variant_f4 using p_vari.
form f_init_variant.
clear: wk_variant.
wk_repid = sy-repid.
wk_variant-report = wk_repid.
wk_variant-username = sy-uname.
wk_variant_save = 'A'. "All types
endform. "F_INIT_VARIANT
form f_variant_default using p_variant type disvariant-variant.
wx_variant = wk_variant.
if ( not p_variant is initial ).
wx_variant-variant = p_variant.
endif.
call function 'LVC_VARIANT_DEFAULT_GET'
exporting
i_save = wk_variant_save
changing
cs_variant = wx_variant
exceptions
wrong_input = 1
not_found = 2
program_error = 3
others = 4.
case sy-subrc.
when 0.
p_variant = wx_variant-variant.
when 2.
clear: p_variant.
endcase.
endform. "f_variant_default
form f_variant_f4 using p_variant type disvariant-variant.
call function 'LVC_VARIANT_F4'
exporting
is_variant = wk_variant
i_save = wk_variant_save
importing
e_exit = wk_exit
es_variant = wx_variant
exceptions
not_found = 1
program_error = 2
others = 3.
if sy-subrc <> 0.
message i122(zpp).
endif.
if wk_exit is initial.
wk_variant-variant = wx_variant-variant.
p_variant = wx_variant-variant.
endif.
endform. "F_VARIANT_F4
pass wk_variant to alv FM
call function 'REUSE_ALV_GRID_DISPLAY'
exporting
i_callback_program = sy-repid
i_background_id = 'ALV_BACKGROUND'
it_fieldcat = fieldcat[]
is_layout = wk_layout
it_events = v_events[]
i_default = 'X'
i_save = 'A'
is_variant = wk_variant
tables
t_outtab = it_final_list. -
Copying ALV variants/layouts between programs
Hi guys,
Does anyone know how to copy ALV layouts between programs in the same client? I have created a copy of a report which uses the ALV functionality via the REUSE_* function modules. The original report has over 40 layouts, so I don't want to have to re-create them manually in the new program. These programs are in the same client on the same system, so the Import Layout and Transport Layout options aren't going to be of any use (as far as I can see...)
Any ideas greatly appreciated.
Cheers,
AndrewI took this approach and it worked for me:
1) Change your program so that everytime an ALV function is called it is using the original program name in the variant declaration, ensure you keep the original code commented out, you will need to put it back later. Examples:
FORM variant_init USING varname TYPE slis_vari.
CLEAR g_variant.
g_variant-report = g_repid.
g_variant-report = 'ORIGINAL_PROGRAM_NAME'.
FORM f4_for_variant.
g_variant-report = sy-repid.
g_variant-report = ORIGINAL_PROGRAM_NAME.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
FORM check_variant.
IF NOT p_vari IS INITIAL.
g_variant-report = sy-repid.
g_variant-report = ORIGINAL_PROGRAM_NAME.
g_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
2) Display function lt_variant_save via SE37, set a breakpoint at the first executable line:
perform variant_save tables it_fieldcat
4) Run your program with the layout variant you wish to copy.
5) Hit Save Variant. You are now in debug mode.
6) Enter variable CS_VARIANT-REPORT in the variables 1 panel.
7) Double-click on CS_VARIANT-REPORT.
8) Hit the Change Field Content button
9) Change the value to the name of your new program, then hit Enter.
10) Hit Execute (F8). You have now saved the variant under your new program name.
11) Exit and rerun your program as necessary for as many variants as you want to copy
12) Change your program back to using sy-repid (or whatever else it was referencing) wherever you changed it in step 1.
13) The variants have now been copied and you can run your program with the new variants. -
CS 5.5 to CC upgrade causes layout issues
Hi there,
I've recently upgraded from CS 5.5 to CC.
Now when I open CS5.5 INDD documents in Indesign CC, the margins or something are wrong.
It seems to be chopping off parts and missing lines.
Any ideas?
Thanks!Fluid Grid layouts for one. CS5.5 CAN'T do them.
The FULL list of release notes is here:http://helpx.adobe.com/dreamweaver/dreamweaver-releasenotes.html -
Issue in setting layout variant in ALV tables
Hi,
I have 2 ALV’s displaying in a view, 1’st is a header data & 2’nd Item data.
Based on the row selection in the Header ALV, the data is determined and displayed in the 2’nd ALV i.e., the Item data.
Now the 2’nd ALV (Item data) can contain 20 columns so based on certain requirement I want to save a layout variant with only 10 Columns for display in the 2’nd ALV.
But the issue what is happening is once I change my row selection in the 1’st ALV (Header data) the layout in the second ALV is refreshing back to the 20 fields EVEN though the name of the variant layout still displays the one I saved earlier.
I have searched the SCN for this issue and found http://scn.sap.com/thread/1986147, but it does NOT work.
Could anyone please suggest a solution.
Thanks & Regards,
DivakerHi 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. -
Report painter layout variants
Dear sirs,
a colleague of mine needs your experience. Our customer needs us to create some Report Painter reports with the possibility to change the layout. Is this/ something like this possible?
An example would be to pick up the columns or to change number format: see numbers in units or tousands of units. Something like ALV variants/ layout?
Any customizing option or workaround would help, thanks OttoYou can pretty much do most of what your colleague is enquiring about.
1. Create a report library GR21
- Table name: E.g GLPCT. You can copy an existing library and modify.
- Description: E.g Branches P& L Reports
- Check off the characteristics he wants
- Check off key figures
- Check off basic key figures.
Define sets and variables if need to with t-codes GS01 and GS11 respectively.
2. Create a report group GR51
3. Create report either using GRR1 or GR31
- Enter the library you created above
- Enter report name
- You can copy from an existing report and make changes to your likeness
- Define you general data selection
- Element definition which is the columns and rows
- Click on Extras and define report headers
- Click on Formatting to format columns and rows
4. Assign report to report group created earlier on.
The above guidelines are the basics on how to proceed.
Refer back for any further clarifications.
Elias
Edited by: Elias Akorli on Nov 24, 2009 2:16 PM -
Gnome 2.28 GDM Keyboard layout
Hello,
A few months ago I installed Arch + Gnome 2.26 and never had problems since then until I upgraded to Gnome 2.28. Now with the rewritten GDM the keyboard layout (for entering the username because I don't like select-your-user-from-the-list-thingies) is set to USA (qwerty) while the rest of my system is completely BE (standard, no variant) layout. Before the upgrade also GDM was 100% BE, but now the username is USA and when I want to enter the password it changes immediately to BE (because in the panel down I chose BE). Is there a way to also make the username respond to the BE layout?
==> What works in BE?
TTY's
password prompt of GDM
gnome session
terminals
==> What works not in BE and responds to USA layout?
GDM username prompt
How weird is that? My system is setup as described in the beginners guide (keyboard layout in 10-osvendor.fdi file + hal + evdev) which was system-wide until the update.
I looked around and found some similar threads, but only complaining about keyboard variants, which is not my issue. Also on the Gnome forums, there is no-one with this problem. I checked all config files and XML files related to GDM I could found, but nothing helped.
I noticed that with the Ubuntu Karmic Beta live CD, upon entering the keyboard layout from the boot screen, everything was BE as I want it to be. It proves to me it's all possible, but I can't find how.
Any help would be appreciated!killajoe wrote:
/etc/gdm/custom.conf is the file to configure gdm:
http://library.gnome.org/admin/gdm/2.28 … on.html.en
there is no gui but for what we need a gui for that?
That's very interesting, thanks for the link. Sure, it's possible that way, but a few weeks ago there still was a GUI for it and now everything has to be done manually again. That sounds very much like a regression to me Anyway, that's not really the point. GDM documentation pages tell us that the system keyboard layout is used to login and that every user logging in can choose their preferred session. However, our system languages (which are different than USA) are not detected correctly and there is no option to override this in custom.conf.
/apps/gdm/simple-greeter/recent-languages
[] (string list)
Set to a list of languages to be shown by default in the login window. Default value is "[]". With the default setting only the system default language is shown and the option "Other..." which pops-up a dialog box showing a full list of available languages which the user can select.
Users are not intended to change this setting by hand. Instead GDM keeps track of any languages selected in this configuration key, and will show them in the language combo box along with the "Other..." choice. This way, commonly selected languages are easier to select.
/apps/gdm/simple-greeter/recent-layouts
[] (string list)
Set to a list of keyboard layouts to be shown by default in the login panel. Default value is "[]". With the default setting only the system default keyboard layout is shown and the option "Other..." which pops-up a dialog box showing a full list of available keyboard layouts which the user can select.
Users are not intended to change this setting by hand. Instead GDM keeps track of any keyboard layouts selected in this configuration key, and will show them in the keyboard layout combo box along with the "Other..." choice. This way, commonly selected keyboard layouts are easier to select.
Has someone the answer to the questions I asked earlier:
1. Will I still be able to update gdm via pacman -Syu after rebuilding gdm with this patch?
2. And will there come an official Arch GDM update with this patch to solve the problem or is the only way to get it solved dealing with the patch now?
Last edited by ulukai (2009-10-17 15:28:35) -
How to Restrict the users from changing the Default variant of report.
Hello everybody,
The requirement is to restrict the users to save and overwrite the default layout variant (Layout for higher managenet)set for the report, but at the same time they should be able to change and save the other layouts for which they are having access.
I have written the logic in the program which is working fine for all the scenario when we execute the report. But the logic doesnt work if the user is selecting the layout on the output screen of the report.
for e.g if the user runs the report using the layout varaint for which he is having the authorization then he gets the all 4 options so he then he can select the layout for which he is not authorized and he can overwrite.
i have debugged and check as i have found that after the report output is shown all the layout paramater is controllled by the statndard SAP objects.
Can anyone help me out in this issue.
Thankyou in advance.
*to get the default layout variant.
w_save = 'A'.
if p_vari is initial.
clear disvariant.
disvariant-report = sy-repid.
w_variant = disvariant.
call function 'REUSE_ALV_VARIANT_DEFAULT_GET'
exporting
i_save = w_save
changing
cs_variant = w_variant
exceptions
not_found = 2.
if sy-subrc = 0.
p_vari = w_variant-variant.
endif.
endif.
*logic to check user authorization to change the layout setting.
if p_vari = c_layout.
if not sy-uname is initial.
select single * from agr_users
where agr_name = c_role
and uname = sy-uname.
if sy-subrc = 0.
w_save = 'A'.
else.
w_save = ' '.
endif.
endif.
endif.
Regards,
Satish.Hi Maine,
Thanks for your reply.
As you mentioned for your own program, you can control the parameter "I_SAVE", when calling "REUSE_ALV_GRID_DISPLAY".
so already i have use the same logic and control the parameter through I_SAVE and here i am calling method ALV_GRID->SET_TABLE_FOR_FIRST_DISPLAY instead of "REUSE_ALV_GRID_DISPLAY".
and it works fine when we execute the report but the logic doesnt work when the user tries to change and save the layout variant on the output screen of the report.
Regards,
Satish -
Creating layouts in ALV report
Hi all,
I have created a report when a user creates a layout in the report it should save the variant(layout) and display in the selection-screen with alv_variant and search help.Its working properly.
But I have to create different layouts like the following:
Layout with sort and subtotals,
layout with sort and filter conditions like that.
Can anybody help me regarding this matter.
with regards
chanduSai,
Here is a little sample program which shows you how to recall saved ALV Layouts. It requires the user to run the report, create their own variants, and this program allwos them to recall it from the selection screen.
You can create gobal layouts (for your sorts, and totals) which canbe accessed by any user.
Hope this helps.
Cheers,
Pat.
*& Report ZPATS_ALV *
REPORT zpats_alv .
TABLES: kna1.
TYPE-POOLS: kkblo.
* structures *
DATA: st_fieldcat TYPE slis_fieldcat_alv.
DATA: st_variant1 LIKE disvariant.
DATA: st_variant2 LIKE disvariant.
* internal tables *
DATA: BEGIN OF tbl_kna1 OCCURS 0,
kunnr LIKE kna1-kunnr,
name1 LIKE kna1-name1,
stras LIKE kna1-stras,
telf1 LIKE kna1-telf1,
ort01 LIKE kna1-ort01,
pstlz LIKE kna1-pstlz,
sortl LIKE kna1-sortl,
ernam LIKE kna1-ernam,
spras LIKE kna1-spras,
END OF tbl_kna1.
DATA: tbl_fieldcat TYPE slis_t_fieldcat_alv.
* global variables *
DATA: fieldname(30) TYPE c.
DATA: variant_exit(1) TYPE c,
variant_save(1) TYPE c,
variant_def(1) TYPE c.
* Seelction Screen
PARAMETERS: p_vari LIKE disvariant-variant.
* Initialization Event
INITIALIZATION.
PERFORM variant_init USING st_variant1.
st_variant2 = st_variant1.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
i_save = 'A'
CHANGING
cs_variant = st_variant2
EXCEPTIONS
not_found = 2.
IF sy-subrc = 0.
p_vari = st_variant2-variant.
ENDIF.
* At Selection Screen On Value Request
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
PERFORM f4_for_variant.
* Start of Selection Event
START-OF-SELECTION.
SELECT kunnr name1 stras telf1 ort01 pstlz sortl ernam spras
INTO CORRESPONDING FIELDS OF TABLE tbl_kna1
FROM kna1.
* End of Selection Event
END-OF-SELECTION.
PERFORM get_fieldcat.
PERFORM create_report.
*& Form get_fieldcat
* text
* --> p1 text
* <-- p2 text
FORM get_fieldcat.
PERFORM write_fieldcat USING 'KUNNR' 'X' 1.
PERFORM write_fieldcat USING 'NAME1' 'X' 2.
PERFORM write_fieldcat USING 'STRAS' ' ' 3.
PERFORM write_fieldcat USING 'TELF1' ' ' 4.
PERFORM write_fieldcat USING 'ORT01' ' ' 5.
PERFORM write_fieldcat USING 'PSTLZ' ' ' 6.
PERFORM write_fieldcat USING 'SORTL' ' ' 7.
PERFORM write_fieldcat USING 'ERNAM' ' ' 8.
PERFORM write_fieldcat USING 'SPRAS' ' ' 9.
ENDFORM. " get_fieldcat
*& Form write_fieldcat
* text
* -->P_0060 text
* -->P_0061 text
* -->P_0062 text
* -->P_0063 text
* -->P_1 text
FORM write_fieldcat USING name
key
pos.
st_fieldcat-fieldname = name.
st_fieldcat-tabname = 'TBL_KNA1'.
st_fieldcat-ref_tabname = 'KNA1'.
st_fieldcat-key = key.
st_fieldcat-col_pos = pos.
IF name = 'PSTLZ'.
st_fieldcat-row_pos = '2'.
ENDIF.
APPEND st_fieldcat TO tbl_fieldcat.
CLEAR st_fieldcat.
ENDFORM. " write_fieldcat
*& Form create_report
* text
* --> p1 text
* <-- p2 text
FORM create_report.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
i_interface_check = ' '
i_callback_program = 'ZPATS_ALV'
i_callback_user_command = 'USER_COMMANDS'
it_fieldcat = tbl_fieldcat
i_default = 'X'
i_save = 'A'
is_variant = st_variant2
TABLES
t_outtab = tbl_kna1
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.
ENDFORM. " create_report
*& Form USER_COMMANDS
* text
* --> p1 text
* <-- p2 text
FORM user_commands USING syst-ucomm LIKE syst-ucomm
selfield TYPE slis_selfield.
CASE syst-ucomm.
WHEN '&IC1'.
READ TABLE tbl_kna1 INDEX selfield-tabindex.
SET PARAMETER ID 'KUN' FIELD tbl_kna1-kunnr.
CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.
WHEN OTHERS.
ENDCASE.
ENDFORM. " USER_COMMANDS
*& Form VARIANT_INIT
FORM variant_init USING g_variant LIKE disvariant.
* Initialise the Variant Structure
CLEAR g_variant.
g_variant-report = sy-repid.
ENDFORM. " VARIANT_INIT
*& Form f4_for_variant
FORM f4_for_variant.
CLEAR st_variant1.
st_variant1-report = sy-repid.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
EXPORTING
is_variant = st_variant1
i_save = 'A'
IMPORTING
e_exit = variant_exit
es_variant = st_variant2.
IF variant_exit = space.
p_vari = st_variant2-variant.
ENDIF.
ENDFORM. " f4_for_variant -
Change Layout in Selection Screen for OO ALV-Grid
Hello everyone,
I got a problem regarding layouts for objectoriented ALV Grid. I want to make it possible that user can take the layout for ALV he wants to on the selection screen. So far thats no problem and it works. But there are some little problems which I do not know how to fix them. But first the facts:
(1) I got my parameter for layout
PARAMETER: p_vari TYPE disvariant-variant.
(2) I fill my global layout structure in initialization
INITIALIZATION.
* Variante vorbelegen
gs_variant-username = sy-uname.
gs_variant-report = sy-repid.
* Layout holen
CALL FUNCTION 'LVC_VARIANT_DEFAULT_GET'
EXPORTING
i_save = 'A'
CHANGING
cs_variant = gs_variant
EXCEPTIONS
wrong_input = 1
not_found = 2
program_error = 3
OTHERS = 4.
IF sy-subrc = 0.
p_vari = gs_variant-variant.
ENDIF.
(3) I got my handling for F4-value help on variant parameter
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
CALL FUNCTION 'LVC_VARIANT_F4'
EXPORTING
is_variant = gs_variant
i_save = 'A'
IMPORTING
es_variant = gs_variant
EXCEPTIONS
not_found = 1
program_error = 2
OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE text-m01 TYPE 'S'.
ELSE.
p_vari = gs_variant-variant.
ENDIF.
(4) I give back my parameters content into the variant structure at start of selection
START-OF-SELECTION.
gs_variant-username = sy-uname.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
This works all fine but I got some problems when using default variants/layouts. For example I got a default variant only for me. When starting the selection screen it works fine that the default layout was written. It is displayed automatically in the variant parameter. But I want that if i I empty the content (blank it out) from my variant parameter, that report should start with "normal" layout how it was written in the report and NOT with default layout.
When I clear the gs_variant it works like I want it, but then the alv layout button looks like (without functions for layout), because I do not have the reference to my report.
So what to do? :-)
Regards
MichaelWow that was fast, works great, thanks :-)
I did not use this parameter in set table method but now I fill it dynamically.
Ok next problem, one step harder ;-)
Now I have one selection screen for one ALV-Grid, but four radio buttons which control with which data the ALV gets filled (four different fieldcats, data tables and so on). Each Grid got an own HANDLE so that the layouts can be separated in four categories.
Now I want that by changing the radio button the individual standard layout for the chosen alv grid is getting filled.
This works fine when using it in selection screen output.
AT SELECTION-SCREEN OUTPUT.
CLEAR gs_variant.
* Layout-Handles individuell für Klausel-Radiobuttons setzen
IF p_py IS NOT INITIAL.
gs_variant-username = sy-uname.
gs_variant-report = sy-repid.
gs_variant-handle = 'KLPY'.
ELSEIF p_rh IS NOT INITIAL.
gs_variant-username = sy-uname.
gs_variant-report = sy-repid.
gs_variant-handle = 'KLRH'.
ELSEIF p_aj IS NOT INITIAL.
gs_variant-username = sy-uname.
gs_variant-report = sy-repid.
gs_variant-handle = 'KLAJ'.
ELSEIF p_sr IS NOT INITIAL.
gs_variant-username = sy-uname.
gs_variant-report = sy-repid.
gs_variant-handle = 'KLSR'.
ENDIF.
* Layout holen
CALL FUNCTION 'LVC_VARIANT_DEFAULT_GET'
EXPORTING
i_save = 'A'
CHANGING
cs_variant = gs_variant
EXCEPTIONS
wrong_input = 1
not_found = 2
program_error = 3
OTHERS = 4.
IF sy-subrc = 0.
p_vari = gs_variant-variant.
ELSE.
CLEAR p_vari.
ENDIF.
But unfortunately selection screen output is getting passed by EACH changing in the selection screen. This means when I try to clear the default layout in my parameter field, it gets refilled automatically with default layout. If I do a condition around the filling (only if not initial) the default value filling does not work fine in every case, e.g. when clearing the parameters field and then change the radiobutton -> then it does not get filled automatically. -
Layout is not defaulted in ESS My Expenses
Hi,
I have gone to transaction POWL_QUERY to maintain the layout variant
for FITV_POWL_TRIPS_EXP. After I saved the variant to be the default
variant for all, I logged into ESS and try to access the query.
However, the newly created variant layout is not defaulted.
I have also executed POWL_D01 to refresh the cache.
Anyone encountered this issue before or tried changing the default variant?
Thanks.Hello folks,
I hope you don't mind me jumping in to rant a bit, since this thread concerns two of my favourit pet hates, the Admin Personalization Layer and POWL
I am not suprised it doesnt work and not sure any OSS note will solve the problem... I think it is because POWLs for FI-TV are "strangely" developed
This, exactly.
1/ Launch your fitv_powl_trips web dynpro application from se80
2/ Add &sap-config-mode=X at the end of the URL path and type enter.
3/ Use option buton to create your ivew as you did it in the layout (store it in a customizing TR).
4/ Launch POWL_D01 and it should be working now.
@ Matthieu: I object. IMO the approach Yvonne described in her opening post is the cleaner one. Doesn't matter much though, since the technical outcome of Yvonne's approach and yours is identical, only the 'functional point of entry' differs. However, implicit WDA Personalization that is supposed to be valid system wide and for all users should never never never be issued via the Admin Personalization Layer, i.e. &sap-config-mode=X, because:
the Layer is overall superfluous and unstable
it is a User Specific customiziation, even if the user scope is "A"
Transporting Admin Personalization is a mess and scarcely works stable
@ Yvonne: What you should do now to clean things up is:
1. Delete your Admin Personalizations you've created via WDA WD_ANALYZE_CONFIG_USER and Transport this Deletion (and hope the Transport works, otherwise delete the Personalizations on each subsequent system manually)
2. Repeat what you wrote you did in your opening post, i.e. TA POWL_QUERY, Button Layout-Variant, but then before doing anything, in the URL change the parameter from "&sap-config-mode=X" to "&sap-config-mode=config". You'll notice that orange-like banner above the application changing from "Customizing-Mode" to "Configuration-Mode". Now repeat doing your adjustments, save them, make a Transport, enter the Layout IDs in the query (Note: enter them via the F4-help, not manually) and finally run POWL_D01.
The outcome is an in-built component configuration that can be transported cleanly, isn't unstable and even works pretty well with the horrible POWL-technology. To verify that you've created configurations of the correct type, check WD_ANALYZE_CONFIG_COMP, your configurations should be here. Subsequently check that the entries are NOT in WD_ANALYZE_CONFIG_USER, if they are, things went wrong again.
Hope that helps
Cheers, Lukas -
How to make Default ALV layout
Hi,
I want to make 'STANDARD view' as a default ALV Layout...If anybody execute my ALV Report STARD Layout variant should display by default. Other variant layouts they can select from drill down..
I know class and method but i don't know how to write code for this with paremeters..Can anybody help on code please..
CLASS : CL_SALV_WD_C_TABLE
METHOD : IF_SALV_WD_COMP_TABLE_PERS~SET_STANDARD_VIEW
My current ALV CODE
DATA: l_ref_interfacecontroller TYPE REF TO iwci_salv_wd_table .
DATA: l_value TYPE REF TO cl_salv_wd_config_table.
l_ref_interfacecontroller = wd_this->wd_cpifc_alv( ).
l_value = l_ref_interfacecontroller->get_model( ).
Thanks.,
SubbaHi sarbjeet singh,
Thanks for your reply...
I didn't understand your answer...Already this view gone to production system and every USER created his own view..
Now how can make default standard view to all users..
If i keep Standard view as Intial view and release transport to production is it effected to all users and display standard view as initial view?
Thanks,
Subba
Maybe you are looking for
-
Files missing from external drive
I have a 4 TB G-Tech RAID drive attached via FireWire 800. It was formerly a backup drive for photos/videos, moved up to a main drive when the old drive it was backing up failed. Problems got in the way of replacing it.... Anyway, all of a sudden, my
-
S540 low performanc​e
Hello everyone, My issue is - brand new Lenovo s540 works very slow. Symptoms: 1) HD video playback lags (i have descibed it here https://forums.lenovo.com/t5/ThinkPad-Edge-S-series/s540-HD-video-playback-lags/td-p/1843284) 2) Low benchmark results.
-
Chinese Charcters in PDF using Apache FOP
Hi, I am creating a PDF using Apache FOP. This data contains Chinese characters. On APEX 3.1, I couldn't contain Chinese characters in PDF. On APEX 3.2, is it possible? Is there any way that I don't have to use BI Publisher? Please advise on this. Th
-
Carrying some calculations in ABAP
Dear Friends, We are having two ztables. One table which is quantity table is hving fields Co Code, Bus Area, Item & Quantity. In this table mainly Items are of 4 types. In the other ztable which is rates table we are having fields like Year, Product
-
Transport Release Issue For Process Chain
Hi Gurus, While trying to relase my request, which has Process Chain to be imported to testing environment i am getting a message like below: Check Objects before release and msg as key :R3TR TABU RSCOMPTLOGOT ERSPC*(Application Component