Userspecific Variants

Hello,
i realized a central user administration. After synchronizing the user from all daugther systems with the central system all user specific variants are lost. Whta's the problem here? Is it a problem with the "user distribution field selection"? Which fields have to be set how that no user specific variants will be lost.

Hello,
i realized a central user administration. After synchronizing the user from all daugther systems with the central system all user specific variants are lost. Whta's the problem here? Is it a problem with the "user distribution field selection"? Which fields have to be set how that no user specific variants will be lost.

Similar Messages

  • How to create a new variant and a job sheduled to use it for the ......

    How to create a new variant and a job sheduled to use it for the exisisting programs

    Hi
    1. The ALV Grid Control is a tool with which you can output non-hierarchical lists in a
    standardized format. The list data is displayed as a table on the screen.
    The ALV Grid Control offers a range of interactive standard list functions that users need
    frequently (find, sort, filter, calculate totals and subtotals, print, print preview, send list,
    export list (in different formats), and so on. These functions are implemented in the
    proxy object class. You as the programmer have the possibility to turn off functions not
    needed. In most cases the implementations of the standard functions provided by the
    control are sufficient. However, if required, you can adjust these implementations to
    meet application-specific needs.
    You can add self-defined functions to the toolbar, if necessary.
    The ALV Grid Control allows users to adjust the layout of lists to meet their individual
    requirements (for example, they can swap columns, hide columns, set filters for the
    data to be displayed, calculate totals, and so on). The settings (list customizing) made
    by a specific user are called a display variant. Display variants can be saved on a userspecific
    or on a global basis. If such display variants exist for a list, they can be offered
    to the user for selection. If a display variant is set as the default variant, the associated
    list is always displayed based on the settings of this variant.
    2. REUSE_ALV_LIST_DISPLAY
    REUSE_ALV_GRID_DISPLAY
    REUSE_ALV_FIELDCATALOG_MERGE
    REUSE_ALV_COMMENTARY_WRITE
    3. Use of Field Catalog is to determines the technical properties & add formating information of the column.
    6. all the definition of internal table, structure, constants are declared in a type-pool called SLIS.
    7.fieldcat-fieldname
    fieldcat-ref_fieldname
    fieldcat-tabname
    fieldcat-seltext_m
    5. Form user_command using r_ucomm like sy-ucomm rs_selfield type slis_selfield.
    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
    In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
    The report output can contain up to 90 columns in the display with the wide array of display options.
    <b>The commonly used ALV functions used for this purpose are;</b>
    1. REUSE_ALV_VARIANT_DEFAULT_GET
    2. REUSE_ALV_VARIANT_F4
    3. REUSE_ALV_VARIANT_EXISTENCE
    4. REUSE_ALV_EVENTS_GET
    5. REUSE_ALV_COMMENTARY_WRITE
    6. REUSE_ALV_FIELDCATALOG_MERGE
    7. REUSE_ALV_LIST_DISPLAY
    8. REUSE_ALV_GRID_DISPLAY
    9. REUSE_ALV_POPUP_TO_SELECT
    Purpose of the above Functions are differ not all the functions are required in all the ALV Report.
    But either no.7 or No.8 is there in the Program.
    <b>
    How you call this function in your report?</b>
    After completion of all the data fetching from the database and append this data into an Internal Table. say I_ITAB.
    Then use follwing function module.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = 'Prog.name'
    I_STRUCTURE_NAME = 'I_ITAB'
    I_DEFAULT = 'X'
    I_SAVE = 'A'
    TABLES
    T_OUTTAB = I_ITAB.
    IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC .
    ENDIF.
    ENDFORM. " GET_FINAL_DATA
    The object F_IT_ALV has a field, the activity ACTVT, which can
    contain four permitted values: 01, 02, 03 and 70. Each of the
    activities 01, 02 and 70 controls the availability of particular
    functions (in the menu and the toolbar) of the ALV line item list:
    a) 01: "Settings -> Display variant -> Save..."
    b) 02: "Settings -> Display variant -> Current..." and
    "Settings -> Display variant -> Current header rows "
    c) 70: "Settings -> Display variant -> Administration..."
    Activity 03 corresponds to the minimum authorization, which is the
    most restricted one: The user can only select layouts which have
    been configured already. In particular, all of the other functions
    named above are inactive with activity 03.
    Now if you want to permit a user to change the column selection and
    the headers as well as to save the layout thus created, for example,
    but if you do not want to permit the user to administrate the
    layouts, you grant him or her the authorization for activities 01
    and 02.
    Check this link it will be mosty usefull for u
    http://www.sap-img.com/fu017.htm
    Reward all helpfull answers
    Regards
    Pavan

  • What is the button to change the variant in alv?

    Hi guys,
              can u tell me  is there any button to change the variant in alv?. what is tanscation varient in report , hw it will used.

    Hi
    The ALV Grid Control is a tool with which you can output non-hierarchical lists in a
    standardized format. The list data is displayed as a table on the screen.
    The ALV Grid Control offers a range of interactive standard list functions that users need
    frequently (find, sort, filter, calculate totals and subtotals, print, print preview, send list,
    export list (in different formats), and so on. These functions are implemented in the
    proxy object class. You as the programmer have the possibility to turn off functions not
    needed. In most cases the implementations of the standard functions provided by the
    control are sufficient. However, if required, you can adjust these implementations to
    meet application-specific needs.
    You can add self-defined functions to the toolbar, if necessary.
    The ALV Grid Control allows users to adjust the layout of lists to meet their individual
    requirements (for example, they can swap columns, hide columns, set filters for the
    data to be displayed, calculate totals, and so on). The settings (list customizing) made
    by a specific user are called a display variant. Display variants can be saved on a userspecific
    or on a global basis. If such display variants exist for a list, they can be offered
    to the user for selection. If a display variant is set as the default variant, the associated
    list is always displayed based on the settings of this variant.
    <b>2. REUSE_ALV_LIST_DISPLAY
    REUSE_ALV_GRID_DISPLAY
    REUSE_ALV_FIELDCATALOG_MERGE
    REUSE_ALV_COMMENTARY_WRITE</b>
    3. Use of Field Catalog is to determines the technical properties & add formating information of the column.
    6. all the definition of internal table, structure, constants are declared in a type-pool called SLIS.
    7.fieldcat-fieldname
    fieldcat-ref_fieldname
    fieldcat-tabname
    fieldcat-seltext_m
    5. Form user_command using r_ucomm like sy-ucomm rs_selfield type slis_selfield.
    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
    In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
    The report output can contain up to 90 columns in the display with the wide array of display options.
    The commonly used ALV functions used for this purpose are;
    <b>1. REUSE_ALV_VARIANT_DEFAULT_GET
    2. REUSE_ALV_VARIANT_F4
    3. REUSE_ALV_VARIANT_EXISTENCE
    4. REUSE_ALV_EVENTS_GET
    5. REUSE_ALV_COMMENTARY_WRITE
    6. REUSE_ALV_FIELDCATALOG_MERGE
    7. REUSE_ALV_LIST_DISPLAY
    8. REUSE_ALV_GRID_DISPLAY
    9. REUSE_ALV_POPUP_TO_SELECT</b>
    Purpose of the above Functions are differ not all the functions are required in all the ALV Report.
    But either no.7 or No.8 is there in the Program.
    How you call this function in your report?
    After completion of all the data fetching from the database and append this data into an Internal Table. say I_ITAB.
    Then use follwing function module.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = 'Prog.name'
    I_STRUCTURE_NAME = 'I_ITAB'
    I_DEFAULT = 'X'
    I_SAVE = 'A'
    TABLES
    T_OUTTAB = I_ITAB.
    IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC .
    ENDIF.
    ENDFORM. " GET_FINAL_DATA
    The object F_IT_ALV has a field, the activity ACTVT, which can
    contain four permitted values: 01, 02, 03 and 70. Each of the
    activities 01, 02 and 70 controls the availability of particular
    functions (in the menu and the toolbar) of the ALV line item list:
    a) 01: "Settings -> Display variant -> Save..."
    b) 02: "Settings -> Display variant -> Current..." and
    "Settings -> Display variant -> Current header rows "
    c) 70: "Settings -> Display variant -> Administration..."
    Activity 03 corresponds to the minimum authorization, which is the
    most restricted one: The user can only select layouts which have
    been configured already. In particular, all of the other functions
    named above are inactive with activity 03.
    Now if you want to permit a user to change the column selection and
    the headers as well as to save the layout thus created, for example,
    but if you do not want to permit the user to administrate the
    layouts, you grant him or her the authorization for activities 01
    and 02.
    Check this link it will be mosty usefull for u
    http://www.sap-img.com/fu017.htm
    Reward all helpfull answers
    Regards
    Pavan

  • Variant alv

    hi
    i have this program, i dont know how to do with variant, when i click in parameter variant i am not get anything , then what is the use of this variant.
    report ztest_0002
    no standard page heading
    message-id zmm.
    Tables.
    tables: mara.
    Global ALV Data Declarations
    type-pools: slis.
    Internal Tables
    data: begin of itab occurs 0,
    matnr type mara-matnr,
    maktx type makt-maktx,
    end of itab.
    data: fieldcat type slis_t_fieldcat_alv.
    data: variant type disvariant.
    Selection Screen
    selection-screen begin of block b1 with frame title text-002 .
    select-options: s_matnr for mara-matnr.
    parameters: p_var(30) type c.
    selection-screen end of block b1.
    initialization.
    variant-report = sy-repid.
    variant-username = sy-uname.
    at selection-screen on value-request for p_var.
    call function 'REUSE_ALV_VARIANT_F4'
    exporting
    is_variant = variant
    i_save = 'U'
    importing
    es_variant = variant
    exceptions
    not_found = 1
    program_error = 2
    others = 3.
    p_var = variant-variant.
    start-of-selection.
    perform get_data.
    perform call_alv.
    Form GET_DATA
    form get_data.
    select maramatnr maktmaktx
    into corresponding fields of table itab
    from mara
    inner join makt
    on maramatnr = maktmatnr
    where mara~matnr in s_matnr
    and makt~spras = sy-langu.
    endform.
    CALL_ALV
    form call_alv.
    perform build_field_catalog.
    Call ABAP List Viewer (ALV)
    call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
    it_fieldcat = fieldcat
    is_variant = variant
    i_save = 'U'
    tables
    t_outtab = itab.
    endform.
    BUILD_FIELD_CATALOG
    form build_field_catalog.
    data: fc_tmp type slis_t_fieldcat_alv with header line.
    data: label(30) type c.
    clear: fieldcat. refresh: fieldcat.
    perform update_catalog using 'Material Number'
    'ITAB'
    'MATNR'
    '18'
    space
    space
    'L'.
    perform update_catalog using 'Material Description'
    'ITAB'
    'MAKTX'
    '40'
    space
    space
    'L'.
    endform.
    UPDATE_CATALOG
    form update_catalog using col_head
    table
    field
    outputlen
    do_sum
    no_out
    just.
    data: tmp_fc type slis_t_fieldcat_alv with header line.
    tmp_fc-reptext_ddic = col_head.
    tmp_fc-fieldname = field.
    tmp_fc-tabname = table.
    tmp_fc-outputlen = outputlen.
    tmp_fc-just = just.
    tmp_fc-decimals_out = 0.
    tmp_fc-do_sum = do_sum.
    tmp_fc-no_out = no_out.
    append tmp_fc to fieldcat.
    endform.

    HI
    The ALV Grid Control is a tool with which you can output non-hierarchical lists in a
    standardized format. The list data is displayed as a table on the screen.
    The ALV Grid Control offers a range of interactive standard list functions that users need
    frequently (find, sort, filter, calculate totals and subtotals, print, print preview, send list,
    export list (in different formats), and so on. These functions are implemented in the
    proxy object class. You as the programmer have the possibility to turn off functions not
    needed. In most cases the implementations of the standard functions provided by the
    control are sufficient. However, if required, you can adjust these implementations to
    meet application-specific needs.
    You can add self-defined functions to the toolbar, if necessary.
    The ALV Grid Control allows users to adjust the layout of lists to meet their individual
    requirements (for example, they can swap columns, hide columns, set filters for the
    data to be displayed, calculate totals, and so on). The settings (list customizing) made
    by a specific user are called a display variant. Display variants can be saved on a userspecific
    or on a global basis. If such display variants exist for a list, they can be offered
    to the user for selection. If a display variant is set as the default variant, the associated
    list is always displayed based on the settings of this variant.
    2. REUSE_ALV_LIST_DISPLAY
    REUSE_ALV_GRID_DISPLAY
    REUSE_ALV_FIELDCATALOG_MERGE
    REUSE_ALV_COMMENTARY_WRITE
    3. Use of Field Catalog is to determines the technical properties & add formating information of the column.
    6. all the definition of internal table, structure, constants are declared in a type-pool called SLIS.
    7.fieldcat-fieldname
    fieldcat-ref_fieldname
    fieldcat-tabname
    fieldcat-seltext_m
    5. Form user_command using r_ucomm like sy-ucomm rs_selfield type slis_selfield.
    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
    In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
    The report output can contain up to 90 columns in the display with the wide array of display options.
    The commonly used ALV functions used for this purpose are;
    1. REUSE_ALV_VARIANT_DEFAULT_GET
    2. REUSE_ALV_VARIANT_F4
    3. REUSE_ALV_VARIANT_EXISTENCE
    4. REUSE_ALV_EVENTS_GET
    5. REUSE_ALV_COMMENTARY_WRITE
    6. REUSE_ALV_FIELDCATALOG_MERGE
    7. REUSE_ALV_LIST_DISPLAY
    8. REUSE_ALV_GRID_DISPLAY
    9. REUSE_ALV_POPUP_TO_SELECT
    Purpose of the above Functions are differ not all the functions are required in all the ALV Report.
    But either no.7 or No.8 is there in the Program.
    How you call this function in your report?
    After completion of all the data fetching from the database and append this data into an Internal Table. say I_ITAB.
    Then use follwing function module.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = 'Prog.name'
    I_STRUCTURE_NAME = 'I_ITAB'
    I_DEFAULT = 'X'
    I_SAVE = 'A'
    TABLES
    T_OUTTAB = I_ITAB.
    IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC .
    ENDIF.
    ENDFORM. " GET_FINAL_DATA
    The object F_IT_ALV has a field, the activity ACTVT, which can
    contain four permitted values: 01, 02, 03 and 70. Each of the
    activities 01, 02 and 70 controls the availability of particular
    functions (in the menu and the toolbar) of the ALV line item list:
    a) 01: "Settings -> Display variant -> Save..."
    b) 02: "Settings -> Display variant -> Current..." and
    "Settings -> Display variant -> Current header rows "
    c) 70: "Settings -> Display variant -> Administration..."
    Activity 03 corresponds to the minimum authorization, which is the
    most restricted one: The user can only select layouts which have
    been configured already. In particular, all of the other functions
    named above are inactive with activity 03.
    Now if you want to permit a user to change the column selection and
    the headers as well as to save the layout thus created, for example,
    but if you do not want to permit the user to administrate the
    layouts, you grant him or her the authorization for activities 01
    and 02.
    Check this link it will be mosty usefull for u
    http://www.sap-img.com/fu017.htm
    DATA: VARIANT TYPE  DISVARIANT.
      VARIANT-REPORT = SY-REPID.
      VARIANT-USERNAME = SY-UNAME.
      CALL METHOD ALV_GRID->SET_TABLE_FOR_FIRST_DISPLAY
          EXPORTING
               IS_VARIANT             = VARIANT
               I_SAVE                 = 'A'
          CHANGING
               IT_OUTTAB       = IALV[]
               IT_FIELDCATALOG = FIELDCAT[].
    Reward all helpfull answers
    Regards
    Pavan

  • 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

Maybe you are looking for