Re: variants

Hi,
Iam using one logical databse to retrieve the data from bsis table. I have to run this program by using submit by using another program along with the parameters.
I could able to send the parameters on the selection screen values. But i could not able to send the dynamic selection-screen values. How it is possible to give the values for the dynamic selection-screen. Any idea.
I appreciate your help.
rgds
p. krishna prasad

Hi
This an extract of my old report where I call a std report with free selections, I hope it can be usefull for you:
RANGES: dd_augdt FOR sy-datum,
        dd_budat FOR sy-datum,
        kd_budat FOR sy-datum,
        dd_faedt FOR sy-datum.
DATA: trange TYPE rsds_trange,
      range   TYPE rsds_range,
      frange TYPE rsds_frange,
      selopt LIKE rsdsselopt.
DATA: texpr   TYPE rsds_texpr.
DATA: x_aisel TYPE c,
      x_clsel TYPE c,
      x_opsel TYPE c.
RANGES ro_augdt FOR bsik-augdt.
Data di registrazione
IF NOT budat IS INITIAL.
dd_budat(3) = 'ILE'.
dd_budat-low = budat.
APPEND dd_budat.
ENDIF.
Co.Ge. speciale
LOOP AT so_umskz.
MOVE-CORRESPONDING so_umskz TO selopt.
APPEND selopt TO frange-selopt_t.
ENDLOOP.
IF sy-subrc = 0.
frange-fieldname = 'UMSKZ'.
APPEND frange TO range-frange_t.
ENDIF.
Modalità di pagamento
REFRESH frange-selopt_t.
LOOP AT so_zlsch.
MOVE-CORRESPONDING so_zlsch TO selopt.
APPEND selopt TO frange-selopt_t.
ENDLOOP.
IF sy-subrc = 0.
frange-fieldname = 'ZLSCH'.
APPEND frange TO range-frange_t.
ENDIF.
IF p_now = space.
dd_augdt(3) = 'IEQ'.
dd_augdt-low = '00000000'.
APPEND dd_augdt.
dd_augdt(3) = 'IBT'.
dd_augdt-low    = budat.
dd_augdt-high   = '99991231'.
APPEND dd_augdt.
x_opsel = space.
x_clsel = space.
x_aisel = 'X'.
ELSE.
x_opsel = 'X'.
x_clsel = space.
x_aisel = space.
kd_budat[] = dd_budat[].
REFRESH dd_budat.
ENDIF.
IF NOT range-frange_t[] IS INITIAL.
range-tablename = 'BSIK'.
APPEND range TO trange.
CALL FUNCTION 'FREE_SELECTIONS_RANGE_2_EX'
      EXPORTING
        field_ranges = trange
      IMPORTING
        expressions = texpr.
ENDIF.
SUBMIT rfitemap
          WITH kd_augdt IN dd_augdt
          WITH kd_blart IN so_blart
          WITH kd_budat IN kd_budat
          WITH kd_bukrs = p_bukrs
          WITH kd_lifnr = l_total-lifnr
          WITH so_budat IN dd_budat
          WITH so_faedt IN dd_faedt
          WITH x_aisel = x_aisel
          WITH x_apar   = space
          WITH x_clsel = x_clsel
          WITH x_merk   = space
          WITH x_norm   = 'X'
          WITH x_opsel = x_opsel
          WITH x_park   = space
          WITH x_shbv   = 'X'
          WITH FREE SELECTIONS texpr AND RETURN.
Max

Similar Messages

Layout variant not working

Hi ,
I have executed a report . I hide one column and saved the layout. The layout name comes on to the selection screen parameter which i have defined on the selection screen.
PARAMETERS: p_vari LIKE disvariant-variant. " ALV Variant
i have made the i_save = 'A' and is_default = 'x'. and also used other function modules reg. Variants.
but if i select the layout variant in the selection screen and execute it is not working . the hidden column also coming on the output.
But if the select the layout variant on the output of the report from the icon select layout it is working fine. the column which i have hidden is not coming. it is perfect. why it is not working when i select the variant in the selection screen.
Regards,
Rose.

Hi,
Please try this code
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
w_variant-report = sy-repid.
* Function module to show the variant of a ALV report
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = w_variant
      i_save     = 'A'
    IMPORTING
      es_variant = w_kvariant
    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.
    p_vari = w_kvariant-variant.
ENDIF.
END-OF-SELECTION.
MOVE w_variant TO w_kvariant.
    MOVE p_vari TO w_kvariant-variant.
    MOVE sy-repid TO w_kvariant-report.
*   Function module to check the variant existence
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        i_save     = w_save
      CHANGING
        cs_variant = w_kvariant.
    w_variant = w_kvariant.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program          = sy-repid
      i_callback_pf_status_set    = 'SET_PF_STATUS'
      i_callback_user_command     = 'USER_COMMAND'
      i_callback_html_top_of_page = 'HTML_HEADING'
      i_grid_title                = text-t06
      i_grid_settings             = wa_grid_set
      is_layout                   = wa_layout
      it_fieldcat                 = t_fieldcat
      i_save                      = 'X'
      is_variant                  = w_variant
      is_print                    = wa_print
    TABLES
      t_outtab                    = t_header
    EXCEPTIONS
      program_error               = 1
      OTHERS                      = 2.
IF sy-subrc <> 0.
    CASE sy-subrc.
      WHEN 1. RAISE program_error.
      WHEN 2. RAISE others.
    ENDCASE.
ENDIF.
Regards
Krishna
Edited by: Krishna Gowrneni on Apr 17, 2009 5:27 PM

Layout variant is not working in background in ALV report

Hi,
I have one LAV report to send the report output through mail in foreground and backgroud.Final internal table is having 46 fileds to display the output.But here user is saving the layout variant and sending that layout variant output to mail id in excel format with zip file.Its working in foreground.But in background its not working.Even if we select the layout variant,its sending all the 46 fileds to mail.
here we have used the below FM to update the fieldcat itab.
CALL FUNCTION 'REUSE_ALV_GRID_LAYOUT_INFO_GET'
    IMPORTING
      et_fieldcat   = it_fieldcat[]
      es_variant    = v_disvariant
    EXCEPTIONS
      no_infos      = 1
      program_error = 2
      OTHERS        = 3.
In for ground NO_OUT = 'x' for non selected fields and NO_OUT = ' ' for selected fields.
But in background NO_OUT = ' ' for all the fileds, even if we select the layout variant.
Please suggest me with the solution.
Regards,
Jayaram

hi ,
Do according to this
SORT t_ekbe by belnr.
if t_ekbe[] is not initial .
      SELECT MBLNR
        BWART
        SMBLN
        ERFMG   " This is the new added field
        erfme     " This is the new added field
      INTO CORRESPONDING FIELDS OF TABLE t_mseg
    for all entries in t_ekbe
      from mseg
      where mblnr = t_ekbe-belnr
      AND   bwart = '101'.
endif.
after this
loop at t_ekbe .
loop at t_mseg where mblnr = t_ekbe-belnr .
t_ekbe-ERFMG = t_mseg-ERFMG .
t_ekbe-erfme =   t_mseg-erfme .
modify t_ekbe transporting ERFMG erfme .
clear t_mseg .
endloop.
clear t_ekbe .
endloop.
Regards
Deepak .

How to create a variant to a maintenance view (trans: SM31)

Hi gurus.
I have created a maintenance view (called z_jest). By running it from SM31 there is a variant option. However, I am not able to create the variant which I want to filter a selection upon in this transaction.
I have even looked into transaction SE54 and created a variant for the maintenance table view there( called z_jestv). Then going back to transaction SM31 and view z_jest, i push 'Variant' radiobutton and type as variant: 'z_jestv', I only get the message: "Variant z_jestv for object z_jest does not exist".
Can anybody please advice on how to create and/or connect the variant to the maintenance view?
Regards LL.

Hi Mahalakshmi
Thanks for reply.
When I look into the procedure, there is a prerequisite: "The basis dialog for which the maintenance variant is created already exists."
I am a little bit unsertain if I miss this 'Basic dialog'. Can you please advice on how to check / create this 'basic dialog' before I go on to create the variant. (I need this 'basic dialog' as input in the procedure you sent.)
(Note: I have already created a 'maintenance dialog' for the view, but I have a feeling, that is something different...)

How to Save Multiple Variants for a Report at a time?

Hi Experts,
I have a report in one server and I have copied the same into another server.
And now I also have to copy the variants of that report.
There are totally 192 variants for the report. So, is there any easier way to copy all those variants for the new report that I have created, rather than re-creating the variants one-by-one manually.
Note:There is no connection to both the servers. So I cannot transport them.
Thanks in advance.

Basis can do a export and import transport, still if don't have connection between boxes.
or
check this
http://www.sap-basis-abap.com/abap/copy-program-variants-from-one-to-another.htm
a®

Error while saving FYV : Gaps in financial year variant periods

Hello Experts,
We are getting an error while saving a new FYV as:
Gaps in financial year variant periods XY
Message no. FGV556
Diagnosis
The period specification has gaps. The periods must be sequentially numbered without any gaps.
System Response
Only a correctly defined period assignment can be saved.
Procedure
Define the periods with consecutive numbers.
Details: The new FYV has 52/53 weeks as posting periods depending on calendar year.
For example, we are trying to define Fisc 2009 as follows. (Fiscal year 2009 = Nov 01 2008 to Oct 31 2009).
Month-Day-Period-Yearshift
11     ---     7     ---     1     ---     +1
11     ---     14     ---     2     ---     +1
11     ---     21     ---     3     ---     +1
11     ---     28     ---     4     ---     +1
12     ---     5     ---     5     ---     +1
12     ---     12     ---     6     ---     +1
12     ---     19     ---     7     ---     +1
12     ---     26     ---     8     ---     +1
12     ---     31     ---     9     ---     +1
1     ---     3     ---     9     ---     0
1     ---     10     ---     10     ---     0
1     ---     17     ---     11     ---     0
1     ---     24     ---     12     ---     0
1     ---     31     ---     13     ---     0
2     ---     7     ---     14     ---     0
2     ---     14     ---     15     ---     0
2     ---     21     ---     16     ---     0
2     ---     28     ---     17     ---     0
3     ---     7     ---     18     ---     0
3     ---     14     ---     19     ---     0
3     ---     21     ---     20     ---     0
3     ---     28     ---     21     ---     0
4     ---     4     ---     22     ---     0
4     ---     11     ---     23     ---     0
4     ---     18     ---     24     ---     0
4     ---     25     ---     25     ---     0
4     ---     2     ---     26     ---     0
5     ---     9     ---     27     ---     0
5     ---     16     ---     28     ---     0
5     ---     23     ---     29     ---     0
5     ---     30     ---     30     ---     0
6     ---     6     ---     31     ---     0
6     ---     13     ---     32     ---     0
6     ---     20     ---     33     ---     0
6     ---     27     ---     34     ---     0
7     ---     4     ---     35     ---     0
7     ---     11     ---     36     ---     0
7     ---     18     ---     37     ---     0
7     ---     25     ---     38     ---     0
8     ---     1     ---     39     ---     0
8     ---     8     ---     40     ---     0
8     ---     15     ---     41     ---     0
8     ---     22     ---     42     ---     0
8     ---     29     ---     43     ---     0
9     ---     5     ---     44     ---     0
9     ---     12     ---     45     ---     0
9     ---     19     ---     46     ---     0
9     ---     26     ---     47     ---     0
10     ---     3     ---     48     ---     0
10     ---     10     ---     49     ---     0
10     ---     17     ---     50     ---     0
10     ---     24     ---     51     ---     0
10     ---     31     ---     52     ---     0
The above entries cover all the dates in calendar year 2009, that is, Jan 2009 to Oct 2009 is covered by periods 10 to 52 and Nov 01 2009 to Dec 31 2009 is covered by period 1 to 9 of the following fiscal year 2010.
Inspite of making sure that all the days of 2009 are covered by periods 1 to 52. We are still unable to save the FYV.
Please help!
Susan

Hello, I am getting this error while saving the FSV. My FSV is based on Weeks. Below is what I am inputting for this. Other details are Calender Year - 2017, No. of posting periods - 53, checked year dependent. Also, I have FSV for previous years also where weeks are 52 but configured as 53. So, hope that this is not creating this issue. Solicit your early response.
Month
Day
Period
Year Shift
1
7
1
0
1
14
2
0
1
21
3
0
1
28
4
0
2
4
5
0
2
11
6
0
2
18
7
0
2
25
8
0
3
4
9
0
3
11
10
0
3
18
11
0
3
25
12
0
4
1
13
0
4
8
14
0
4
15
15
0
4
22
16
0
4
29
17
0
5
6
18
0
5
13
19
0
5
20
20
0
5
27
21
0
6
3
22
0
6
10
23
0
6
17
24
0
6
24
25
0
7
1
26
0
7
8
27
0
7
15
28
0
7
22
29
0
7
29
30
0
8
5
31
0
8
12
32
0
8
19
33
0
8
26
34
0
9
2
35
0
9
9
36
0
9
16
37
0
9
23
38
0
9
30
39
0
10
7
40
0
10
14
41
0
10
21
42
0
10
28
43
0
11
4
44
0
11
11
45
0
11
18
46
0
11
25
47
0
12
2
48
0
12
9
49
0
12
16
50
0
12
23
51
0
12
30
52
0
12
31
1
+1
Thanks
Deepankar

How to find out list of variants in TVARV table

hi!
can anybody can guide me on the following issues? plz
How to list all variants in TVARV table?
How to find out any Z* programs that writes to TVARV table, using the variant name?
How to find out the programs which are reads the TVARV data into a program variant?
Thanks & Regards,
vijay

Or some help might be useful:
http://help.sap.com/saphelp_47x200/helpdata/en/c0/98037ae58611d194cc00a0c94260a5/frameset.htm
Regards,
Subramanian V.

Free goods determination in variant article

Hi ALL!!!!
The issue is regarding IS-Retail. In case of order processing with variant article free goods is not getting active. The item category of the parent article is TAG and for the variants is TAN. When I am maintaining freegoods for the variant then also its not getting picked up nor when I am maintaining free goods for the parent article.
Please suggest
regards

Hi
1) In IS-Retail Variant article as called Generic Articles (retail terminalogy).
2) Come to freegoods, In retail you can use promotion concept to maintain the freegoods determination for generic artilces and it should test with POS system.
regards
satish

Creation of a new costing variant to cost production orders

Hi all,
Currently the business is only able to cost a vehicleu2019s production order at the standard cost value which is determined at the start of the year.
During the year a number of the purchasing values will be updated with a new contract price, this increase will not be reflected in the standard cost until the end of the year.
The business would like a new costing variant which will cost an already created vehicle in SAP by its production order at the u201CCurrent Costu201D (current purchasing info record value).
It will need to be calculated in the following way:
u2022Purchased material - at purchase cost from info record (see below for applicable exchange rate).
u2022Manufactured material - child material to be at purchase cost (from info record). Routing cost (labour\overhead, etc) at current criteria.
u2022No allowance for CPI. [WHAT_ DOES_CPI_MEAN_?]
u2022Exchange rate: ideally, fields are provided to input exchange rate. If this is not possible then apply current monthu2019s exchange;
u2022FRAu2019s - current rate from the info record.
u2022Summary of total material cost by origin code with ability to drill down to line level.
u2022The output of the report will need to be similar to the layout of a production order but with only the current value displayed.
We have some problems to understand this request: we don't know the transaction which is used by the users to costificate a production order and what does it mean "CPI". We are not sure on the feasibility of the costing variant requested because it must consider both actual costs and standard costs.
It should costificate in this way:
(Actual Cost of Row Material * Bom's standard qty) + (Standard price * Standard production time (in the routings).
Could you help us?
Many thanks to all of you, best regards.
Alanis

You can create a new costing variant with a valuation variant that points to inforecords for material prices. Go to OKKN t-code and create the required configuration and start using the new costing variant to measure the current cost of making vehicles.

Creation of new Print Program & Variant for new Correspondence Type created

Dear Friends,
I have created 2 new Correspondence Types in SAP as SAP61 (Vendor Debit Note) & SAP62 (Vendor Credit Note) by copying SAP09 (Internal Document) properties like itu2019s Name of the print program - RFKORD30 & Name of variant - SAP09.
We are facing problem when we execute print program in F.64 for SAP09 it is coming same like SAP61 or SAP62. Actual script & print values of SAP09 are replaced by SAP61 or SAP62.
Please suggest us how we can differentiate both SAP09 & SAP61/62. Because we use these correspondences for different purposes like SAP09 gives the information for the Line items in the Document whereas SAP61/62 gives the information of vendor line item weather it is debit or credit entry.
Your kind co-operation in this matter is highly appreciated.
Thanks & Regards,
Naveen Kumar.P

"Assigned the from to the company code - progam in V_001F_B"
Check 'Form ID' field in this IMG transaction against the program and form that you have created.
I am assuming there are 2 lines with same entries but different form IDs.
Or there are 2 lines with the same entries but different CoCodes (seem to remember that the CoCode is not taken into account as a key in certain programs - not logical i know but remembered a previous issue I had many moons ago - could be to do with the blank entry for CoCode field if there is one being picked up by the program before the entry that has your CoCode).
Now check the variant attached and Form ID in step 'Created new program variants in SA38'
Ensure the correct program and variant are attached in step OB78.
My assumption is Form ID is the key.
Hope this helps

Multiple Fiscal Year Variant in the same client in SEM-BCS...

I have already looked at some earlier threads relating to this but didn't get a convincing answer to what I would like to know.
We have had a working SEM-BCS system with fiscal year variant K4. There was no need for defining leading fiscal year variant and none was defined. SAP, by default takes, K4 as the leading fiscal year variant.
Now there is a requirement for going on a different fiscal year variant for which we have created another databasis (there were a few other reasons besides these) with the same InfoObjects that we used earlier but with different fixed parameters, one of which is fisc year variant V9. Soon, we started experiencing bizarre dumps in the configuration which ultimately convinced me to define a leading fiscal year variant. I was reluctant to do so because there is a lot of old data (which will become 'historical' from new data basis point of view) from the working system on K4 that would still need to be reported on even when we have new BCS solution in the new fiscal year variant V9. That is not going away. There is a need to keep the old data for reporting (hence the rationale for a different data basis among a few others).
Since earlier Master Data was configured in the old fisc year variant K4, now I have defined the leading fiscal year variant as V9 so that MDF can appropriately identify the period dependency.
I would like to know if any of you have had an unexpected behavior from the system going forward. Does the system dump out when you try to read the old data (from earlier K4).
I have tried to explain the dilemma as clearly and succinctly as possible but if you need more clarifications, please do let me know.
I would really appreciate your help in this.

Is your requirement is that K4 to be changed to Z5.
The best way you can do it is in the transformation. Instead of directmapping,
Write a code like this in the trransformation to the cube
If SOURCE FIELD - 0FISCVAR eq 'k4'.
SOURCE FIELD - 0FISCVAR = 'Z5'.
I dont think we can change th data in the query being displayed. we can change the keyfigure values in query by frmulas etc...
but for a characteristic, i think we will be able to restrict bt not change the value.
to obtain the requirement, w have to get the data change before query designer that is in the cube leve.
Hope this helps,
Sri...

How can I get a variant's string data?

Greetings!
When I view a variant indicator, I see a (generally) human-readable block of text. This makes sense to me, since, as I understand it, a variant is, internally, a kind of flattened string. My question is: is there a way that I can get that string in LabVIEW, and can I then load that string back into a variant?
I'm trying to preserve the human-readable aspect of the variant data. Flatten to/Unflatten from String is not human readable, and the variant versions of Flatten/Unflatten drop the variant's attributes. I've also tried Flatten to/Unflatten from XML, which drops the attributes AND does not unflatten correctly.
Any help you can offer would be appreciated.
Thanks!
Allen C. Smith
Ktech Corporation

I think Allen wants to have access to the plain string that is displayed in the variant container and I have not found a way to get it. The method should require no code and should be independent on the complexity of the data contained in the variant.
I agree this could be somewhat useful and should be supported. For example, we could have a readable property for the variant indicator similar to the text.text property of string indicators.
The text.text string property gives the text formatted as shown in the indicator and thus depends on the display style (normal, '\'-codes, password, hex). It can be e.g. used to convert a plain string to a plain string that incorporates '\'-codes that is available to the code. (See image). This could be useful in a case where you want to mix '\'-codes and plain codes in a descriptive display, for example containing the following three lines:
"The received string in '\'-codes is:
ABC\tDEF\tGHI\n
please verify there are no unexpected characters"
Message Edited by altenbach on 01-17-2007 09:40 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
StringDisplay.png ‏10 KB

Variação de Preços em Listas de Preços

Bom dia.
Estou com um problema com listas de preços e taxas de câmbio. Por exemplo, tenho uma lista de preços em Kwanzas, baseada numa outra em USD. Sempre que existe variação do USD, os preços na lista de preços (em kwanzas) são também actualizados.
Existe alguma forma de não permitir que os preço da lista de preços sejam actualizados?
Neste exemplo, a moeda local é o Kwanza e a moeda de sistema o USD.
Obrigado
Marta Silva

Prezada Marta,
para a questão levantada, acredito que a nota 1255925 possa ajuda-la na solução deste caso.
Atenciosamente,
Wesley Honorato

Variação Cambial - Regime Competência

Bom dia Pessoal!
Poderiam me ajudar em um problema?
Ao fazer a baixa de uma nota fiscal pelo contas a receber (exemplo) é usada a variação cambial utilizando a data de inserção da nota (lançamento ou documento) e a data de inserção da baixa, isto esta correto se o cliente optou pelo Regime de Caixa, certo?
Para os optantes pelo Regimo de Competência o correto seria usar a taxa de Câmbio do último dia do mês anterior à baixa (se o título ficar parado nessa transição de mês). Não consegui fazer isso no SAP, utilizei o módulo de Diferenças de Taxa de Câmbio, ele faz os lançamentos certo para cada transição de mês, porém na hora da baixa puxa a cotação do dia do lançamento da nota.
Alguém já fez esse procedimento correto?
Obrigada,
Denise

Olá, Leandro.
Provavelmente você possui mais de uma moeda configurada para contabilizar e essa variação cambial está ocorrendo nessa outra moeda. Esse lançamento "zerado" é normal e acontece nesses casos.
Faça um teste: Consulte o documento através da FB03 e troque a moeda de visualização. Em pelo menos uma moeda haverá valor no lançamento da variação cambial, nem que seja 1 centavo.
Não há nada o que fazer quanto a isso. É o comportamento padrão do SAP. A menos que você configure o sistema para trabalhar com apenas uma moeda, mas me parece que nesse caso o ônus é maior que o bônus pois geralmente as empresas querem contabilizar os movimentos pelo menos em dólar além do real.
Att,
Jaisson.

Unable to save the ALV layout variant and display of selection screen on F4

Hi All,
The end user wants to directly select the layout variant (SLIS_VARI). I have used the following code to display the layout variant on selection screen. But, I am unable to save the variant on ALV. Whenever I am trying to select the layout variants (by doing F4 on selection screen) its displaying "No Layout found".
Following is the code for displaying layout variant:
PARAMETERS: p_var TYPE slis_vari.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_var.
PERFORM f4_variant CHANGING p_var.
FORM f4_variant CHANGING c_variant TYPE slis_vari.
DATA: ls_variant TYPE disvariant,
            l_exit     TYPE char1.
ls_variant-report = sy-repid.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = ls_variant
      i_save     = 'A'
    IMPORTING
      e_exit     = l_exit
      es_variant = ls_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.
      c_variant = ls_variant-variant.
    ENDIF.
ENDIF.
ENDFORM.                    " f4_variant
and following is the code for displaying the ALV:
FORM edition_alv.
ws_variant2 = ls_variant.
* Call ALV editor in list mode
IF p_list = 'X'.
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
      EXPORTING
        i_callback_program      = ws_extract1-report
        i_callback_user_command = ws_user_command
        is_layout               = ws_layout
        it_fieldcat             = wt_fieldcat
        it_sort                 = wt_sort
        i_save                  = 'A'
        is_variant              = ws_variant2
        it_events               = wt_events[]
      TABLES
        t_outtab                = wt_edition.
* Call ALV editor in grid mode
ELSE.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
      EXPORTING
        i_callback_program      = ws_extract1-report
        i_callback_user_command = ws_user_command
        it_fieldcat             = wt_fieldcat
        it_sort                 = wt_sort
        i_save                  = 'A'
        is_variant              = ws_variant2
        it_events               = wt_events[]
      TABLES
        t_outtab                = wt_edition.
ENDIF.
ENDFORM.
I am not sure whats going wrong, but I am unable to save variants.
Please help.
Thanks,
Vishal.

The F4 will display you the existing layouts only. So you need to save the layout first & then execute the report again & check if you are getting F4 values for that field.
The Layout needs to get stored with variant.
Regards,
Mahesh

Difference between sy-datm and sysdate in a variant of a report

hi,
I am working on a report which fills the database and i had assigned variant called SYSDATE -1 bcoz it will update the database table for all the plants for the previous date. can anybody guide me that whether i should use the variable SYSDATE- 1 or the sy-datum-1 ,so that uploading the data can be performed.

These are few options you may try
1. Create a wrapper program which will first modify date in variant and save it again. FM RS_VARIANT_CONTENTS, RS_CHANGE_CREATED_VARIANT and
RS_CREATE_VARIANT, RS_VARIANT_DELETE will be useful.
Submit program with this changed variant.
2. Same as above except variant change program can be scheduled and dependent step can be created to run from that variant.
3. While saving the variant you may assign "Selection Variable". This will fetch data from table TVARVC. You will need to periodically update value of your date field in this table.
Regards,
Mohaiyuddin

Re: variants

Similar Messages

Maybe you are looking for