Variant value in background

Hi friends,
I have created a variant for job scheduling, i wants to use one field value in the
program when background job running from that variant. Please help me to get that value in background.
Thanks in Advance,
SB.

Hi Syed,
Hi
first Save the variant for that program and use in Job scheduling
Create a Variant for the Program and
Schedule JOB in background:
Go to SM36 create a Job
enter Program and Variant for that program in STEP..
click on Start Condition
Click on DATE and TIME enter date scheduled Start and END times
click on Period Values
Click on HOURLY/WEEKLY etc
CLick on RESTRICTIONS also to use further criteria.
so your job will be scheduled and run as per your requirement.
and in SM37 Transaction check the status of that JOB
Check this link for scheduling jobs..
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
<b>Kindly reward points if you found the reply helpful.<b>
Cheers,
Chaitanya.

Similar Messages

How to use a colum value as background color in a report template

I need to use a colum value as background color of report template
es.
<td style="padding:0px;border-bottom:1px #cccc99 solid;border-right:1px #cccc99 solid;font-size:8pt;background:??????;" #ALIGNMENT#>#COLUMN_VALUE# </td>
I have a column named COLORE_VAL1
I try with:
<td style="padding:0px;border-bottom:1px #cccc99 solid;border-right:1px #cccc99 solid;font-size:8pt;background:#COLORE_VAL1#;" #ALIGNMENT#>#COLUMN_VALUE# </td>
but the value remain #COLORE_VAL1#.
Please, help me.
Barbara

You need to change the processing type to customer exit of that variable.
Now in i_step = 1 write the following code:
Data:dt LIKE sy-datum,
      zper TYPE /bi0/oifiscper,
      YR type /bi0/oicalyear,
      per LIKE t009b-poper.
IF i_step = 1.
WHEN 'X_FSCPRC' .---User input variable based on cmod.
      dt = sy-datum.
      CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
        EXPORTING
          i_date         = dt
          i_periv        = 'M3'---Give the fiscal year variant                             according to your system
        IMPORTING
          e_buper        = per
          e_gjahr        = yr
        EXCEPTIONS
          input_false    = 1
          t009_notfound = 2
          t009b_notfound = 3
          OTHERS         = 4.
      IF sy-subrc = 0.
Concatenate YR Per into Zper.
        l_s_range-low = Zper.
        l_s_range-sign = 'I'.
        l_s_range-opt = 'EQ'.
        APPEND l_s_range TO e_t_range.
      ENDIF.
endif.

Variant Values during Run Time

Hi
I am running a report as background job with a variant "VarOne" which has the following values
1. Duration Interval - value - 60
2. Program ID. - value - 00123
3. Current Date ( Value not saved while creating variant)
4. Current Time ( Value not saved while creating variant)
While the report is scheduled as background job with a particular variant value.. Is there a table that stores all the VarOne variant values....I want to know the values of 3 and 4. I know that looking at the job scheduling time I can get approximate values..But I need to know a place( like a table) where these variant values are stored.
I have checked the following tables but didnt find the runtime values
VARID
VARIT
TRVAR
TRVARVC
TRVARV
VARICONCI
VARICON
Hope My question is clear
Thank you

VARCH is much the same as any editor (e.g. SE38 or SA38.. or where ever you can display development objects from and choose "variants" from the "Other Objects" menu).
If you can display the variant from anywhere, but not from VARCH, then your concept seems to be a bit strange...
Note that from VARCH you can display and also maintain the variants (if authorized), but you cannot execute the programs (via their variants). That is what it is designed to do, particularly in production systems...
If your program concept in intact and correctly secured, then I recommend requesting standard VARCH to fullfill your requirement.
Your security folks should give you the correct authority to do your job, and not rely on silly tcodes to secure the variants...
Cheers,
Julius
Edited by: Julius Bussche on Jan 3, 2009 10:21 PM

Function Module to Lock a Variant or see variant values in Disabled mode?

Hi,
I have a requirement in which I create some jobs which takes some variant as one of the input.
My Problem is once i have executed the job successfully in SM37, I need to see the variant values. I know there is a function Module RS_VARIANT_CHANGE with which we can see the values of variant.
But i dont want the user to modify those values since the job has already been executed. I just want to see them.
Can anyone tell me is there any FM to see just the variant values in disabled mode or the the variant is locked so that the user cant modify it?

Hi,
I'm not sure if you really want to create a program to see the variant values?
Because you can see the values by simply going to SM37, select the job, display list of steps, position cursor and use menu Goto -> Variant
Moreover, (I don't know if it may answer your requirement) when you schedule a job with a report which outputs an ABAP list, you may define in the print parameters the option "Selection cover sheet" to print the values of selection screen parameters/select-options.
Sandra

Variants Values in BI 7.0 New Reporting Tools

Hello SDN,
We had an OSS Message (204968) to address the issue where we are NOT able to see query "predefined" Variants values in new reporting tools BI 7.0 BEx Analyzer.
SAP support has responded saying they are able to see the Variants values. We've tried again but I still CANNOT see the Variants values, could this be an authorization issue?
If yes, do you know if there are any new authorizations for query components and its access?
Many thanks for any helps and a highest point will be rewarded.
Best regards,
Niki

So as part of your upgrade to 7.0 -
Someone ran RSR_VARIANT_XPRA which converts Basis variants to new BW Variant tables - For use by 3.5 tools.
Table Name                     Short text
RSRVARIANT                     Variant Values
RSRVARIANTDIR                  Directory of Variants for Queries and Selection Objects
RSRVARIANTTXT                  Texts for Variants
RSRVARIANTVIEW                 Variant Header and Texts
Then RSR_MIGRATE_VARIANTS should have been run to convert the converted 3.5 variants to the to the new 7.0 variant tables?
Table Name                     Short text
RSRPARAMETRIZA                 Parametrization for a query, workbook, webapplication, pla
RSRPARAMETRIZAT                Text of parametrizations
I believe by default - all variants get converted as Global.
So if you look at the RSRPARAMETRZA* tables, do you have variants appearing in them or not?

R3 tables about job, program, variant and variant value

Hi, Experts,
    Now we are schedule lots of R3 jobs before BW uploading.
    every job has ABAP program, each ABAP program use one variant.
    my problem is: there are so much job sceduled, we are hard to go to check all setting is correct. so anyone can tell me what's R3 table have the information of job,program, variant and variant value
    I just some TBT* table which only have job info.
Thanks a lot

Hi Jie,
The variants can be found in <b>TVARV</b>,VARI,VARID,VARIT and VARIS tables.
Also Check these tables:
SMEN_OBLIG
SREPOVARI
SREPOLIST
SREPOUSER
Bye
Dinesh
Message was edited by: Dinesh Lalchand

Passing variant values in job_submit FM

Hi Guys,
              I am running a report in background using job_submit FM.
Currently I am using Get and Set parameters to pass selection screen values.
But these values are not effective when run in background.
If variant is an option, how to populate the variant from selection screen values.
Thanks

Hi,
U follow the given code. If u have taken varinat as parameter then ok.
other wise u have to pass rs_create_varaint* function module in the program.
DATA : v_jobhead LIKE tbtcjob.
DATA : v_jobcount LIKE tbtcjob-jobcount.
DATA : v_eventparm LIKE tbtcjob-eventparm.
DATA : v_flg_released TYPE c.
DATA: e_error.
DATA: running LIKE tbtcv-run.
TYPES: esp1_boolean LIKE boole-boole.
CONSTANTS: esp1_false TYPE esp1_boolean VALUE ' ',
           esp1_true TYPE esp1_boolean VALUE 'X'.
CONSTANTS: true TYPE boolean VALUE esp1_true,
           false TYPE boolean VALUE esp1_false.
PARAMETERS: v_jobnam LIKE tbtcjob-jobname,
            v_report LIKE sy-repid,
            v_varian LIKE raldb-variant,
            v_uname LIKE sy-uname.
START-OF-SELECTION.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = v_jobnam
       IMPORTING
            jobcount         = v_jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
    e_error = true.
ELSE.
    CALL FUNCTION 'JOB_SUBMIT'
         EXPORTING
              authcknam               = v_uname
              jobcount                = v_jobcount
              jobname                 = v_jobnam
              report                  = v_report
              variant                 = v_varian
         EXCEPTIONS
              bad_priparams           = 1
              bad_xpgflags            = 2
              invalid_jobdata         = 3
              jobname_missing         = 4
              job_notex               = 5
              job_submit_failed       = 6
              lock_failed             = 7
              program_missing         = 8
              prog_abap_and_extpg_set = 9
              OTHERS                  = 10.
    IF sy-subrc <> 0.
      e_error = true.
    ELSE.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount                    = v_jobcount
                jobname                     = v_jobnam
                strtimmed                   = 'X'
           IMPORTING
                job_was_released            = v_flg_released
           EXCEPTIONS
                cant_start_immediate        = 1
                invalid_startdate           = 2
                jobname_missing             = 3
                job_close_failed            = 4
                job_nosteps                 = 5
                job_notex                   = 6
                lock_failed                 = 7
                OTHERS                      = 8.
      IF sy-subrc <> 0.
        e_error = true.
      ELSE.
        DO.
          CALL FUNCTION 'SHOW_JOBSTATE'
            EXPORTING
              jobcount               = v_jobcount
              jobname                = v_jobnam
           EXCEPTIONS
             jobcount_missing       = 1
             jobname_missing        = 2
             job_notex              = 3
             OTHERS                 = 4.
          IF sy-subrc <> 0.
            e_error = true.
            MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
          ENDIF.
          IF running = space.
            exit.
         endif.
           enddo.
        endif.
        endif.
    endif.
Regards,
Naveen M.

Dynamic variants for a background job

Hi,
I need to set up a background job for a dynamic variant. To elaborate my selection screen has date ranges which need to change dynamically , if the job is secheduled on weekly basis the selection date range should change automatically in the variant. I got to know that the same is possible through the table TVARV. Can I know about the method of setting up the same?
Thanks,
Shailaja

You can set a dynamic date to today date or some other date without using the table TVARV.
To set the dynamic date:
Save variant on the selection screen.
In the vairant screen, press F4 against your field in the column "Selection Variable"
Select D here.
In the column Name of the variable, press F4 to have the list of the possible rules.
Here you can select "Current date - xxx,current date + yyy" if you want to have certain period.
When you select this system will pop up to put the values for XXX and YYY.
Say for last 7 days, you can set the values XXX as 7 and YYY as0.
But the best way is to change the program, if possible, and fill the select option in the intialization event.
Regards,
Naimesh Patel

Variant Creation for Background mode

hi
I am trying to create variants which will run the background jobs for CFM1 transaction with materials having 6000 records every time.
Can you tell me how to create variants for a particular transaction A using some other program B.
if I have 24000 records I want 4 different variants with 6000 records each for CFM1
All helpful answers will be rewarded

hi ,
you can categorize ur data for putting into different variants and create 4 different variant names. use the fm 'RS_CREATE_VARIANT' for creating variants in ur program B. use the following code in ur program..
      DATA : ls_variantdesc TYPE varid.
      DATA : lt_varianttext TYPE TABLE OF varit ,
             wa_varianttext TYPE varit.
      DATA : tt_reportparam TYPE TABLE OF rsparams,
             wa_reportparam TYPE rsparams.
DATA: jobcnt TYPE tbtcjob-jobcount,
        jobnam TYPE tbtcjob-jobname VALUE 'ZMIGO_RESERVE105'.
*Variant parameters
      wa_reportparam-selname = 'S_WERKS'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = mseg_wa-werks.
      APPEND wa_reportparam TO tt_reportparam.
      wa_reportparam-selname = 'S_MATNR'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = mseg_wa-matnr.
      APPEND wa_reportparam TO tt_reportparam.
      wa_reportparam-selname = 'S_BWTAR'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = mseg_wa-bwtar.
      APPEND wa_reportparam TO tt_reportparam.
      wa_reportparam-selname = 'S_ERFMG'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = mseg_wa-erfmg.
      APPEND wa_reportparam TO tt_reportparam.
      wa_reportparam-selname = 'S_LGORT'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = mseg_wa-lgort.
      APPEND wa_reportparam TO tt_reportparam.
      wa_reportparam-selname = 'S_WEMPF'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = mseg_wa-lfbnr.
      APPEND wa_reportparam TO tt_reportparam.
      wa_reportparam-selname = 'S_BDTER'.
      wa_reportparam-kind    = 'P'.
      wa_reportparam-low     = sy-datum.
      APPEND wa_reportparam TO tt_reportparam.
      CLEAR ls_variantdesc.
      ls_variantdesc-mandt   = sy-mandt.
      ls_variantdesc-report = 'ZMIGO_RESERVE105'.
      ls_variantdesc-variant = 'VARIANT'.
      ls_variantdesc-ename   = sy-uname.
      ls_variantdesc-edat    = sy-datum.
      ls_variantdesc-etime   = sy-uzeit.
      REFRESH lt_varianttext.
      CLEAR wa_varianttext.
      wa_varianttext-mandt    = sy-mandt.
      wa_varianttext-langu    = sy-langu.
      wa_varianttext-report   = 'ZMIGO_RESERVE105'.
      wa_varianttext-variant = 'VARIANT'.
      APPEND wa_varianttext TO lt_varianttext.
*Create Variant
      CALL FUNCTION 'RS_CREATE_VARIANT'
        EXPORTING
          curr_report               = 'ZMIGO_RESERVE105'
          curr_variant              = 'VARIANT'
          vari_desc                 = ls_variantdesc
        TABLES
          vari_contents             = tt_reportparam
          vari_text                 = lt_varianttext
        EXCEPTIONS
          illegal_report_or_variant = 1
          illegal_variantname       = 2
          not_authorized            = 3
          not_executed              = 4
          report_not_existent       = 5
          report_not_supplied       = 6
          variant_exists            = 7
          variant_locked            = 8
          OTHERS                    = 9.
      IF sy-subrc EQ 7.
If variant with same name already exists, change variant
        CALL FUNCTION 'RS_CHANGE_CREATED_VARIANT'
          EXPORTING
            curr_report               = 'ZMIGO_RESERVE105'
            curr_variant              = 'VARIANT'
            vari_desc                 = ls_variantdesc
          TABLES
            vari_contents             = tt_reportparam
          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.
      ELSEIF sy-subrc NE 0.
        MESSAGE s999(ymigo) WITH 'Cannot create/change variant for'
        sy-uname.
      ENDIF.
*Schedule background job
      CALL FUNCTION 'JOB_OPEN'
        EXPORTING
          jobname   = jobnam
          sdlstrtdt = sy-datum
          sdlstrttm = sy-uzeit
        IMPORTING
          jobcount = jobcnt.
      CALL FUNCTION 'JOB_SUBMIT'
        EXPORTING
          authcknam = sy-uname
          jobcount = jobcnt
          jobname   = jobnam
          report    = 'ZMIGO_RESERVE105'
          variant   = 'VARIANT'.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount = jobcnt
          jobname   = jobnam
          strtimmed = 'X'.
      COMMIT WORK AND WAIT.
for job name, u can give your transactions program name.

ALV layout variant missing in background job.

hi guys,
Having problem on getting the default ALV layout variant when run the job in backgorund. Please advise any correction needed in the following code.
Thanks.
*& Include           Z_MM_KBR_AGSUBCONINV_MOD2                        *
MODULE status_0100 OUTPUT.
SET PF-STATUS '100'.
SET TITLEBAR '100'.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module display_data OUTPUT
      text
MODULE display_data OUTPUT.
IF sy-batch IS INITIAL. "Foreground
IF w_container IS INITIAL.
    IF cl_gui_alv_grid=>offline( ) IS INITIAL.
*Creating the container
      CREATE OBJECT w_container
        EXPORTING
          container_name              = c_container
        EXCEPTIONS
          cntl_error                  = 1
          cntl_system_error           = 2
          create_error                = 3
          lifetime_error              = 4
          lifetime_dynpro_dynpro_link = 5
          OTHERS                      = 6.
      IF sy-subrc <> 0.
     MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    ENDIF.
*Creating the ALV GRID
    CREATE OBJECT w_grid
      EXPORTING
        i_parent          = w_container
        i_appl_events     = c_check
      EXCEPTIONS
        error_cntl_create = 1
        error_cntl_init   = 2
        error_cntl_link   = 3
        error_dp_create   = 4
        OTHERS            = 5.
    IF sy-subrc <> 0.
     MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    else.
     exit.
    ENDIF.
ELSE.
*Creating the ALV GRID
    CREATE OBJECT w_grid
      EXPORTING
        i_parent          = go_dock_container
        i_appl_events     = c_check
      EXCEPTIONS
        error_cntl_create = 1
        error_cntl_init   = 2
        error_cntl_link   = 3
        error_dp_create   = 4
        OTHERS            = 5.
    IF sy-subrc <> 0.
      WRITE:/ 'Error in grid'.
    ENDIF.
     CREATE OBJECT w_grid
      EXPORTING i_parent = go_dock_container.
ENDIF.
*getting the variant option
    wa_variant-report     = sy-repid.
    wa_variant-username   = sy-uname.
    wa_layout-grid_title = sy-title.
    wa_layout-cwidth_opt = c_check.
    wa_layout-zebra       = c_check.
    wa_layout-no_f4       = c_check.
    wa_layout-sel_mode    = 'D'.
*Excluding the unwanted buttons
     PERFORM exclude_toolbar_buttons.
build field catalog.
    CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
      EXPORTING
        i_buffer_active        = c_check
        i_structure_name       = c_fcat_str
        i_bypassing_buffer     = c_check
      CHANGING
        ct_fieldcat            = t_fieldcat
      EXCEPTIONS
        inconsistent_interface = 1
        program_error          = 2
        OTHERS                 = 3.
    IF sy-subrc <> 0.
     MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
             WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    loop at t_fieldcat into w_fieldcat.
     if w_fieldcat-FIELDNAME = 'AGING1'.
      W_FIELDCAT-NO_ZERO = 'X'.
      MODIFY t_fieldcat FROM W_FIELDCAT INDEX SY-TABIX.
     ENDIF.
    endloop.
Generate sort critria
    PERFORM generate_sort.
Create object of class lcl_event_receiver.
    CREATE OBJECT w_event.
Handler for events.
   SET HANDLER w_event->handle_top_of_page       FOR w_grid.
   SET HANDLER w_event->handle_print_top_of_page FOR w_grid.
   SET HANDLER w_event->handle_print_end_of_list FOR w_grid.
    SET HANDLER w_event->handle_hotspot_click     FOR w_grid.
*Displaying the alv
   IF NOT sy-batch IS INITIAL.
     PERFORM create_snp.
   ENDIF.
t_data = i_final.
    CALL METHOD w_grid->set_table_for_first_display
      EXPORTING
        i_save                        = 'A'
        is_layout                     = wa_layout
        is_variant                    = wa_variant
      CHANGING
        it_outtab                     = t_data
        it_fieldcatalog               = t_fieldcat
      EXCEPTIONS
        invalid_parameter_combination = 1
        program_error                 = 2
        too_many_lines                = 3
        OTHERS                        = 4.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDIF.
ENDMODULE.                 " display_data OUTPUT
*&      Module user_command_0100 INPUT
      text
MODULE user_command_0100 INPUT.
DATA: lt_rows TYPE lvc_t_row,
         w_rows TYPE lvc_s_row.
CASE sy-ucomm.
    WHEN c_back.
      LEAVE TO SCREEN 0.
    WHEN c_exit.
      LEAVE TO SCREEN 0.
    WHEN c_cancel.
      LEAVE TO SCREEN 0.
   WHEN 'BILDET'.
     CALL METHOD w_grid->get_selected_rows
       IMPORTING
         et_index_rows = lt_rows.
     CALL METHOD cl_gui_cfw=>flush.
     IF sy-subrc EQ 0.
       READ TABLE lt_rows INTO w_rows INDEX 1.
       READ TABLE i_vbfa INTO w_vbfa INDEX w_rows-index.
       IF sy-subrc EQ 0.
         CLEAR i_zbw_br_nf4.
         LOOP AT i_zbw_br_nf3 INTO w_zbw_br_nf3 WHERE
                     refkey = w_vbfa-v_vbeln.
           APPEND w_zbw_br_nf3 TO i_zbw_br_nf4.
         ENDLOOP.
call dialog screen and display new alv control
         CALL SCREEN 101 STARTING AT 10 5.
       ENDIF.
     ENDIF.
     WHEN 'NOTAF'.
     CALL METHOD w_grid->get_selected_rows
       IMPORTING
         et_index_rows = lt_rows.
     CALL METHOD cl_gui_cfw=>flush.
     IF sy-subrc EQ 0.
       READ TABLE lt_rows INTO w_rows INDEX 1.
       READ TABLE i_zbw_br_nf3 INTO w_zbw_br_nf3 INDEX w_rows-index.
       DATA docnum LIKE j_1bdydoc-docnum.
       docnum = w_zbw_br_nf3-docnum.
       SET PARAMETER ID 'JEF' FIELD docnum.
       CALL TRANSACTION 'J1B3N' AND SKIP FIRST SCREEN.
     ENDIF.
ENDCASE.
ENDMODULE.                 " user_command_0100 INPUT
*&      Form modify_col_name
      text
     -->P_<FCAT> text
     -->P_TEXT_H01 text
FORM modify_col_name USING pwa_fcat TYPE lvc_s_fcat
                             value(pw_text) TYPE any.
pwa_fcat-coltext   = pw_text.
pwa_fcat-scrtext_l = pw_text.
pwa_fcat-scrtext_m = pw_text.
pwa_fcat-scrtext_s = pw_text.
ENDFORM.                    " modify_col_name
      FORM display_hotspot                                          *
FORM display_hotspot USING pw_row_id    TYPE lvc_s_row
                           pw_column_id TYPE lvc_s_col.
FIELD-SYMBOLS <l_data> TYPE zbrforecast.
READ TABLE t_br_nf_acum ASSIGNING <l_data> INDEX pw_row_id-index.
CHECK sy-subrc = 0.
IF pw_column_id = ' '.
ENDIF.
ENDFORM.                    "display_hotspot
*&      Form generate_sort
      Genereate Sort criteria
FORM generate_sort.
Local variables
DATA: wal_sort TYPE lvc_s_sort,
       wl_pos   TYPE numc2.
wl_pos = 01.
sort ORDER
wal_sort-spos      = wl_pos.
wal_sort-fieldname = c_aufnr.
wal_sort-up        = c_check.
APPEND wal_sort TO t_sort.
ENDFORM.                    "generate_sort
*&      Form f4_variant
      text
     <--PW_VARI text
FORM f4_variant CHANGING pw_vari TYPE disvariant-variant.
wa_variant-report = sy-cprog.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant    = wa_variant
      i_save        = c_u
    IMPORTING
      es_variant    = wa_variant
    EXCEPTIONS
      not_found     = 1
      program_error = 2
      OTHERS        = 3.
IF sy-subrc IS INITIAL.
    pw_vari = wa_variant-variant.
ELSE.
    MESSAGE s208(00) WITH text-t04.
ENDIF.
ENDFORM.                    " f4_variant
*&      Form validate_layout
*This subroutine is to validate the layout
No parameters are passed to this subroutine
FORM validate_layout.
IF NOT p_layout IS INITIAL.
Check Layout
   wa_variant-report   = sy-repid.
   wa_variant-username = sy-uname.
   wa_variant-variant = p_layout.
   CALL FUNCTION 'LVC_VARIANT_EXISTENCE_CHECK'
     EXPORTING
       i_save     = c_u
     CHANGING
       cs_variant = wa_variant
     EXCEPTIONS
       OTHERS     = 01.
   IF NOT sy-subrc IS INITIAL.
     SET CURSOR FIELD 'P_LAYOUT'.
     MESSAGE s001(00) WITH text-t06 p_layout.
     STOP.
   ENDIF.
ELSE.
clear wa_variant.
ENDIF.
ENDFORM.                    " validate_layout
*&      Form validate_data
      text
FORM validate_data .
PERFORM validate_layout.
ENDFORM.                    " validate_data

Hi,
Before the call to method set_table_for_first_display, populate
wa_variant-report = sy-repid.
Best regards,
Prashant

How to get return values In Background Task?

Hi all,
I have a Call Function Module In Background Task.In this FM I defined a return tables to get related info.But if use In Background Task mode,how to look/get these table values? Many thanks!
Kelvin

Hi,
Create the list o/p of the return table and view the o/p in SP01 transaction.
Regards,
Prashant.

BBP_Get_Status_2 Variant values

Dear SRMers,
System Info SRM 4.0
We have a variant for BBP_GET_STATUS_2 called GetStatus.
This variant has the following values set a.) no Shopping cart time frame set
b.) the SC..... in last days is 0.
Does this mean it will pick up the shopping carts created today or does it process all shopping carts in the system
Points will be rewarded.
Thanks in advance,
Regards,
Bob

Hi Bob,
Normally it is advised to create variant with 5 days runs for every 15 min, and 30 days for every 3 hours and 365 days for every weekend.
if you leave days 0, it will pick all the shopping carts.
Let me know if you need any further info on this.
Thank you
Sreedhar Vetcha

Where do variant values get stored in SAP?

Hello
This is basically an ABAP question, but I am still putting it here. If we have a custom report (program) in R.3, and a user creates multiple variants for that program, is there a table which stores the values that he has entered for that variant. I have read several posts and have searched on the web and have found that:
1. Most important tables for variants: VARID, VARI, VARIS, TVARVC. The table VARI has a field CLUSTD where the variant contents are stored are in encoded format.
2. And the FM which does the conversion (behind-the-scenes): RS_VARIANT_CONTENTS.
But is there an a proper database table that store the values (as there are) in SAP?
Thanks,
Srini.

Hello,
I think you can find the values in different tables like: TVARV, TVARVC, VARI, VARICON, VARICONCI, VARID, VARID_CI, VARIDESC, VARIDESCCI, VARINUM, VARIS, VARIS_CI, VARIT, VARIT_CI and VARI.
I hope it helps!
Thanks.
Beatriz.

How to receive variant-criteria after background-task had been executed

Hi ABAP-community,
i do run a program in background task. Once i enter sm37 the other day i can find the spool-file but i miss a opportunity to get the selection criteria as well. The job has been executed with variant xy. I now need to know/recreate what the selection-criteria was before the job has been executed. In the job-log functionality i can find report name and even a variant-name but haven't found a possibility to view the selection parameters.
I already found table vari, varid, etc. but no appropriate report/function/etc. on how to restore the selection-criteria.
Does anyone have a clue? Please let me know!
Thanks in advance....
...and bye for now!
Gunther

Hi,
perfect! That's exactly what i was looking for!
Thank You and byebye!
Gunther

Does Safari support "cover" value of background-size property for CSS?

I'm a web developer. I've run into a Safari issue while coding up a new portfolio site. I was using an older version of Safari that came with my MacBookPro with leopard, where in my css the old Safari was recognizing and properly implementing the value "cover" for the property background-size.
body {
-webkit-background-size: cover;
I recently upgraded to Snow Leopard and I assume my Safari was upgraded too, because now the website I'm building does not look correct in the current version of Safari. Safari is not letting the "cover" value fill the browser window completely as it should. Instead Safari will only allow the image to fill the background so long as the width and heighth values are lower than the actual size of my background image. Once the browser size exceeds either the width or heighth size of my bg image, Safari shows nothing (empty space filled with bg color) beyond the image size. The current version of Safari is 4.0.4.
I want the image to fill the background of the browser window regardless of the browser window resizing in any direction while maintaining the proper aspect ratio, so overflow of image height is generally hidden.
You can see the site I'm building here, mikepriebe.ca. It should look fine in Chrome and Firefox. In Safari you should see what appears to be a large uneven border around the background photo.
Any thoughts or tips on how to fix this or work around this?

Thanks Roger. Although I'll still need to solve the issue for those viewers using the older versions of Safari, even if the property value is executing correctly in the latest version of Safari.

Variant value in background

Similar Messages

Maybe you are looking for